Backup Central

Hi,

What may have caused the following stack traces,
and how might they be fixed?

They seemed to happen at about the same time as
upgrading several Debian linux packages.

Thanks,
Kingsley


Exception '15' raised of class 'rdiff_backup.robust.SignalException':
File "/usr/lib/python2.3/site-packages/rdiff_backup/robust.py", line 32, in check_common_error
try: return function(*args)
File "/usr/lib/python2.3/site-packages/rdiff_backup/rpath.py", line 788, in listdir
return self.conn.os.listdir(self.path)
File "/usr/lib/python2.3/site-packages/rdiff_backup/robust.py", line 84, in signal_handler
raise SignalException(signum)

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 260, in Main
take_action(rps)
File "/usr/lib/python2.3/site-packages/rdiff_backup/Main.py", line 230, in take_action
elif action == "backup": Backup(rps[0], rps[1])
File "/usr/lib/python2.3/site-packages/rdiff_backup/Main.py", line 279, 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 225, in patch_and_increment
for diff in rorpiter.FillInIter(source_diffiter, dest_rpath):
File "/usr/lib/python2.3/site-packages/rdiff_backup/rorpiter.py", line 181, in FillInIter
for rp in rpiter:
File "/usr/lib/python2.3/site-packages/rdiff_backup/backup.py", line 103, in get_diffs
for dest_sig in dest_sigiter:
File "/usr/lib/python2.3/site-packages/rdiff_backup/backup.py", line 165, in get_sigs
for src_rorp, dest_rorp in cls.CCPP:
File "/usr/lib/python2.3/site-packages/rdiff_backup/backup.py", line 299, in next
source_rorp, dest_rorp = self.iter.next()
File "/usr/lib/python2.3/site-packages/rdiff_backup/rorpiter.py", line 92, in Collate2Iters
try: relem1 = riter1.next()
File "/usr/lib/python2.3/site-packages/rdiff_backup/rorpiter.py", line 340, in next
next_elem = self.iter.next()
File "/usr/lib/python2.3/site-packages/rdiff_backup/selection.py", line 132, in Iterate_fast
try: rpath, val = diryield_stack[-1].next()
File "/usr/lib/python2.3/site-packages/rdiff_backup/selection.py", line 118, in diryield
for filename in self.listdir(rpath):
File "/usr/lib/python2.3/site-packages/rdiff_backup/selection.py", line 180, in listdir
dir_listing = robust.check_common_error(error_handler, dir_rp.listdir)
File "/usr/lib/python2.3/site-packages/rdiff_backup/robust.py", line 32, in check_common_error
try: return function(*args)
File "/usr/lib/python2.3/site-packages/rdiff_backup/rpath.py", line 788, in listdir
return self.conn.os.listdir(self.path)
File "/usr/lib/python2.3/site-packages/rdiff_backup/robust.py", line 84, in signal_handler
raise SignalException(signum)
rdiff_backup.robust.SignalException: 15
Exception exceptions.TypeError: "'NoneType' object is not callable" in <bound method GzipFile.__del__ of <gzip open file '/mnt/backup/rdiff-backup-data/extended_attributes.2005-09-03T10:25:56-07:00.snapshot.gz', mode 'wb' at 0x40251220 0x4056b1cc>> ignored
Exception exceptions.TypeError: "'NoneType' object is not callable" in <bound method GzipFile.__del__ of <gzip open file '/mnt/backup/rdiff-backup-data/file_statistics.2005-09-03T10:25:56-07:00.data.gz', mode 'wb' at 0x40207da0 0x4056b26c>> ignored
Exception exceptions.TypeError: "'NoneType' object is not callable" in <bound method GzipFile.__del__ of <gzip open file '/mnt/backup/rdiff-backup-data/error_log.2005-09-03T10:25:56-07:00.data.gz', mode 'wb' at 0x4024c220 0x4055ac2c>> ignored
Exception exceptions.TypeError: "'NoneType' object is not callable" in <bound method GzipFile.__del__ of <gzip open file '/mnt/backup/rdiff-backup-data/mirror_metadata.2005-09-03T10:25:56-07:00.snapshot.gz', mode 'wb' at 0x40251ae0 0x4056b2ac>> ignored

On Mon, 5 Sep 2005, Kingsley G. Morse Jr. wrote:

Hi,

What may have caused the following stack traces,
and how might they be fixed?

They seemed to happen at about the same time as
upgrading several Debian linux packages.

the upgrade was happening while rdiff-backup was running? did you get new
python2.3 packages? (istr there was a security fix in at least deb
unstable python 2.3 this week...)

signal 15 is SIGTERM... sounds suspiciously like something tried to kill
your rdiff-backup... does this happen every time?

-dean

Hi,

After installing gcc-4.0-base, libwxgtk2.4-1,
linux-sound-base, discover1-data, libdiscover1,
and discover1 and upgrading alsa-utils from
1.0.6-4 to 1.0.9a-4, libgcc1 from 1:4.0.0-11 to
1:4.0.1-6, libstdc++6 from 3.4.3-5 to 4.0.1-6,
audacity from 1.2.3-1 to 1.2.3-2, libsndfile1-dev
from 1.0.10-2 to 1.0.11-1, alsa-base from
1.0.6a-11 to 1.0.9b-4 and libasound2 from 1.0.8-3
to 1.0.9-3, I ran rdiff-backup again.

It worked.

Thanks,
Kingsley

On 09/05/05 13:01, dean gaudet wrote:
On Mon, 5 Sep 2005, Kingsley G. Morse Jr. wrote:

Hi,

What may have caused the following stack traces,
and how might they be fixed?

They seemed to happen at about the same time as
upgrading several Debian linux packages.

the upgrade was happening while rdiff-backup was running? did you get new
python2.3 packages? (istr there was a security fix in at least deb
unstable python 2.3 this week...)

signal 15 is SIGTERM... sounds suspiciously like something tried to kill
your rdiff-backup... does this happen every time?

-dean