Re: Backup-Probleme? - slbackup [solved]
Am Samstag, 30. Juni 2007 schrieb Harald Meyer:
> Hallo,
>
> Das automatische slbackup bringt ein Haufen Fehlermeldungen. Oft stürzt
> danach scheinbar der LDAP ab und die User können sich am nächsten Tag nicht
> anmelden.
> Kann es sein das meine Festplatten (Raid) den Geist aufgeben? Oder wie
> interpretiere ich folgende Log-Aufzüge:
> -------
> Jun 30 00:15:02 - Removing backups older than 185 days succeeded!
> Jun 30 00:15:26 -
> Previous backup seems to have failed, regressing destination now.
> Warning, metadata file has entry for
> skole/tjener/home0/vitaliy/.mozilla/firefox/cjcss356.default/Cache/1514D5B3
>d01, but there are no associated files.
> Warning, metadata file has entry for
> skole/tjener/home0/vitaliy/priv/aufgaben/Ordner1.rar,
> but there are no associated files.
> Traceback (most recent call last):
> File "/usr/bin/rdiff-backup", line 23, in ?
> rdiff_backup.Main.Main(sys.argv[1:])
> File "/usr/lib/python2.3/site-packages/rdiff_backup/Main.py", line 286,
> in Main
> take_action(rps)
> File "/usr/lib/python2.3/site-packages/rdiff_backup/Main.py", line 256,
> in take_action
> elif action == "backup": Backup(rps[0], rps[1])
> File "/usr/lib/python2.3/site-packages/rdiff_backup/Main.py", line 306,
> in Backup
> backup.Mirror_and_increment(rpin, rpout, incdir)
> File "/usr/lib/python2.3/site-packages/rdiff_backup/backup.py", line 51,
> in Mirror_and_increment
> DestS.patch_and_increment(dest_rpath, source_diffiter, inc_rpath)
> File "/usr/lib/python2.3/site-packages/rdiff_backup/backup.py", line 229,
> in patch_and_increment
> ITR(diff.index, diff)
> File "/usr/lib/python2.3/site-packages/rdiff_backup/rorpiter.py", line
> 288, in __call__
> branch.start_process(*args)
> File "/usr/lib/python2.3/site-packages/rdiff_backup/backup.py", line 640,
> in start_process
> diff_rorp, base_rp, self.get_incrp(index))
> File "/usr/lib/python2.3/site-packages/rdiff_backup/backup.py", line 470,
> in check_long_name
> try: result = func(*args)
> File "/usr/lib/python2.3/site-packages/rdiff_backup/increment.py", line
> 41, in Increment
> elif mirror.isdir(): incrp = makedir(mirror, incpref)
> File "/usr/lib/python2.3/site-packages/rdiff_backup/increment.py", line
> 94, in makedir
> dirsign = get_inc(incpref, "dir")
> File "/usr/lib/python2.3/site-packages/rdiff_backup/increment.py", line
> 114, in get_inc
> assert not incrp.lstat(), incrp
> AssertionError:
> Path:
> /skole/backup/tjener/rdiff-backup-data/increments/etc.2007-06-29T10:04:38+0
>2:00.dir Index: ('etc.2007-06-29T10:04:38+02:00.dir',)
> Data: {'uid': 0, 'perms': 493, 'type': 'reg', 'gname': 'root', 'ctime':
> 1183155302, 'devloc': 2058L, 'uname': 'root', 'nlink': 1, 'gid': 0,
> 'mtime': 1183103665, 'atime': 1183155302, 'inode': 1822208L, 'size': 0L}
> Exception exceptions.TypeError: "'NoneType' object is not callable"
> in /usr/lib/python2.3/gzip.py:129: FutureWarning: hex()/oct() of negative
> int will return a signed string in Python 2.4 and up
> return '<gzip ' + s[1:-1] + ' ' + hex(id(self)) + '>'
> <bound method GzipFile.__del__ of <gzip open
> file
> '/skole/backup/tjener/rdiff-backup-data/file_statistics.2007-06-30T00:15:02
>+02:00.data.gz', mode 'wb' at 0xb7d14060 0xb7a8e8cc>> ignored
> Exception exceptions.TypeError: "'NoneType' object is not callable" in
> <bound method GzipFile.__del__ of <gzip open
> file
> '/skole/backup/tjener/rdiff-backup-data/error_log.2007-06-30T00:15:02+02:00
>.data.gz', mode 'wb' at 0xb7d0ea20 0xb7a8d3cc>> ignored
> Exception exceptions.TypeError: "'NoneType' object is not callable" in
> ignored
>
> Jun 30 00:15:26 - Failed backing up client tjener
> Jun 30 00:15:26 - Successfully running of scripts in /etc/slbackup/post.d.
> Jun 30 00:15:26 - Finished slbackup.
> Jun 30 00:16:06 -
> UpdateError
> skole/tjener/home0/vitaliy/.mozilla/firefox/cjcss356.default/Cache/1514D5B3
>d01 File changed from regular file before signature
> UpdateError
> skole/tjener/home0/vitaliy/.mozilla/firefox/cjcss356.default/Cache/1515D5B3
>d01 File changed from regular file before signature
> ------
>
> Jun 30 00:15:01 - Successfully run /etc/slbackup/pre.d/ldapdump.sh:
> Stopping OpenLDAP: slapd.
> Starting OpenLDAP: running BDB recovery - failed:
> Automatic recovery of the OpenLDAP directory database in
>
> /var/lib/ldap
>
> failed. You will need to perform a manual recovery, possibly from backup.
> The failed command was db4.2_recover -eh /var/lib/ldap. Output:
>
> db_recover: PANIC: fatal region error detected; run recovery
> db_recover: dbenv->close: DB_RUNRECOVERY: Fatal error, run database
> recovery EOF
> Successfully dumped the LDAP-database to /var/backups/slapd/ldapdump.ldif.
> -------
>
Hi,
nach eingehender Untersuchung stellte sich heraus, dass eine Kopie der Datei
slbackup noch als slbackup.org im /etc/cron.d/ lag und von cron auch
zeitgleich mitausgeführt wurde.
Da das slbackupscript aber nicht prüft, ob ein process gleichen Namens bereits
läuft, wie es das IMO tuen sollte, kamen sich die beiden Prozesse in die
Quere.
Dies erklärt natürlich, warum es nur zu dieser Uhrzeit zu den beschriebenen
Problemen kam.
Also, erstens sollten scripte sowas abfangen und zweitens sollte man Dateien
nicht als Sicherung aktiv in den cron Verzeichnissen rumliegen lassen. ;-)
Grüsse, Jürgen Leibner
Reply to: