Icinga flagged a disk space warning for seaborgium's root partition. It currently has 1221 transaction log file chunks (10 megs each) in /var/lib/ldap/labs named like /var/lib/ldap/labs/log.0000001 etc. This is described in the OpenLDAP FAQ: http://www.openldap.org/faq/index.cgi?_highlightWords=bdb&file=738
I ran db_archive on pollux and seaborgium and it showed that all files expect the last one are not currently in use and could be removed, Still the documentation advises to keep them around:
The db5.3_archive utility writes the pathnames of log files that are no longer in use (for example, no longer involved in active transactions), to the standard output, one pathname per line. These log files should be written to backup media to provide for recovery in the case of catastrophic failure (which also requires a snapshot of the database files), but they may then be deleted from the system to reclaim disk space.
We could add these to the backup and prune them from the servers (with a current disk requirement of 13 GB for nine months total life time of seaborgium), but that's something that is growing continuously) or we could discard older entries and only keep the last N transaction logs around, which would still allow to store previous snapshots I guess. In the event if a catastrophic failure of both serpens/seaborgium we would rather restore from backup anyway. Opinions?