Univention Bugzilla – Bug 31997
Nightly LDIF backup is corrupted
Last modified: 2013-11-19 06:42:29 CET
/var/univention-backup/ldap-backup_*.ldif.gz contains the stderr of slapcat. Problem: the stderr output is injected at random positions within stdout output (the actual LDIF). ---[cut]--- [...] dn: cn=S-1-5-21-2545846719-49063496434-6083847334-123456,cn=sid,cn=temp51633e09 OVER: db_close 51633e09 OVER: db_destroy orary,cn =univention,dc=my,dc=example,dc=com objectClass: top objectClass: lock lockTime: 1365419802 [...] ---[cut]---
add "-d 0" to the slapcat call to prevent the debug output from the overlay module.
And maybe replace the 'slapcat >"$ldapbackupname" 2>&1' by ldapbackuplog="/var/univention-backup/ldap-backup_$(date +%Y%m%d).log" slapcat >"$ldapbackupname" 2>"$ldapbackuplog" or something similar.
A seperate logfile is created during the backup process. r43510: univention-ldap 10.0.9-7.607.201308281113
OK: r43510 OK: zgrep -l OVER /var/univention-backup/ldap-backup_20130* OK: univention-ldap-backup ; zcat $PWD/ldap-backup_20130917.log.gz FIXED: ChangeLog r43511 + r44155 FYI: The (useless) debug output is still logged, but now to a different file.
UCS 3.2 has been released: http://docs.univention.de/release-notes-3.2-en.html http://docs.univention.de/release-notes-3.2-de.html If this error occurs again, please use "Clone This Bug".