SearchFAQMemberlist Log in
Reply to topic Page 1 of 1
rdiff-backup crash
Author Message
Reply with quote
Post rdiff-backup crash 
Hi,

I've been running rdiff-backup (ver. 13.4) reliably for quite some time
but now consistently get the following crash when trying to backup up a
particular machine (see below). Has anyone any ideas?

Thanks
Dave Hawkes


rdiff_backup.Main.Main(sys.argv[1:])
File "/usr/lib/python2.2/site-packages/rdiff_backup/Main.py", line
247, in Main
take_action(rps)
File "/usr/lib/python2.2/site-packages/rdiff_backup/Main.py", line
218, in take_action
elif action == "backup": Backup(rps[0], rps[1])
File "/usr/lib/python2.2/site-packages/rdiff_backup/Main.py", line
265, in Backup
backup.Mirror_and_increment(rpin, rpout, incdir)
File "/usr/lib/python2.2/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.2/site-packages/rdiff_backup/backup.py", line
226, in patch_and_increment
ITR(diff.index, diff)
File "/usr/lib/python2.2/site-packages/rdiff_backup/rorpiter.py", line
279, in __call__
last_branch.fast_process(*args)
File "/usr/lib/python2.2/site-packages/rdiff_backup/backup.py", line
607, in fast_process
inc = self.inc_with_checking(tf, rp, self.get_incrp(index))
File "/usr/lib/python2.2/site-packages/rdiff_backup/backup.py", line
593, in inc_with_checking
try: inc = increment.Increment(new, old, inc_rp)
File "/usr/lib/python2.2/site-packages/rdiff_backup/increment.py",
line 36, in Increment
log.Log("Incrementing mirror file " + mirror.path, 5)
File "/usr/lib/python2.2/site-packages/rdiff_backup/log.py", line 121,
in __call__
self.log_to_term(message, verbosity)
File "/usr/lib/python2.2/site-packages/rdiff_backup/log.py", line 134,
in log_to_term
termfp.write(self.format(message, self.term_verbosity))
IOError: [Errno 11] Resource temporarily unavailable
Exception exceptions.TypeError: "'NoneType' object is not callable" in
<bound method GzipFile.__del__ of <gzip open file
'/mnt/cadlink1/tornado/usr/www/rdiff-backup-data/file_statistics.2004-04-16T10:30:25-04:00.data.gz',
mode 'wb' at 0x8bca488 0x8bcb5dc>> ignored
Exception exceptions.TypeError: "'NoneType' object is not callable" in
<bound method GzipFile.__del__ of <gzip open file
'/mnt/cadlink1/tornado/usr/www/rdiff-backup-data/mirror_metadata.2004-04-16T10:30:25-04:00.snapshot.gz',
mode 'wb' at 0x8c64a20 0x8c6464c>> ignored
Exception exceptions.TypeError: "'NoneType' object is not callable" in
<bound method GzipFile.__del__ of <gzip open file
'/mnt/cadlink1/tornado/usr/www/rdiff-backup-data/error_log.2004-04-16T10:30:25-04:00.data.gz',
mode 'wb' at 0x8bd2ee0 0x8bd2ec4>> ignored
Traceback (most recent call last):
File "/usr/bin/rdiff-backup", line 24, in ?
rdiff_backup.Main.Main(sys.argv[1:])
File "/usr/lib/python2.2/site-packages/rdiff_backup/Main.py", line
247, in Main
take_action(rps)
File "/usr/lib/python2.2/site-packages/rdiff_backup/Main.py", line
216, in take_action
connection.PipeConnection(sys.stdin, sys.stdout).Server()
File "/usr/lib/python2.2/site-packages/rdiff_backup/connection.py",
line 336, in Server
self.get_response(-1)
File "/usr/lib/python2.2/site-packages/rdiff_backup/connection.py",
line 298, in get_response
try: req_num, object = self._get()
File "/usr/lib/python2.2/site-packages/rdiff_backup/connection.py",
line 221, in _get
raise ConnectionReadError("Truncated header string (problem "
rdiff_backup.connection.ConnectionReadError: Truncated header string
(problem probably originated remotely)

Reply with quote
Post rdiff-backup crash 
I have this exact problem as well and reported it to the list on 5/20:

http://mail.gnu.org/archive/html/rdiff-backup-users/2004-03/msg00033.html

I have not had any success troubleshooting the problem.

I am in the process of switching to dirvish, http://www.pegasys.ws/dirvish/,
because of this. Though if anybody has new information or suggestions, I
would be glad to hear it.

Dan Knighten

-----Original Message-----
From: Dave Hawkes [mailto:daveh < at > cadlink.com]
Sent: Friday, April 16, 2004 11:12 AM
To: rdiff-backup-users < at > nongnu.org
Subject: [rdiff-backup-users] rdiff-backup crash


Hi,

I've been running rdiff-backup (ver. 13.4) reliably for quite some time but
now consistently get the following crash when trying to backup up a
particular machine (see below). Has anyone any ideas?

Thanks
Dave Hawkes


rdiff_backup.Main.Main(sys.argv[1:])
File "/usr/lib/python2.2/site-packages/rdiff_backup/Main.py", line
247, in Main
take_action(rps)
File "/usr/lib/python2.2/site-packages/rdiff_backup/Main.py", line
218, in take_action
elif action == "backup": Backup(rps[0], rps[1])
File "/usr/lib/python2.2/site-packages/rdiff_backup/Main.py", line
265, in Backup
backup.Mirror_and_increment(rpin, rpout, incdir)
File "/usr/lib/python2.2/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.2/site-packages/rdiff_backup/backup.py", line
226, in patch_and_increment
ITR(diff.index, diff)
File "/usr/lib/python2.2/site-packages/rdiff_backup/rorpiter.py", line
279, in __call__
last_branch.fast_process(*args)
File "/usr/lib/python2.2/site-packages/rdiff_backup/backup.py", line
607, in fast_process
inc = self.inc_with_checking(tf, rp, self.get_incrp(index))
File "/usr/lib/python2.2/site-packages/rdiff_backup/backup.py", line
593, in inc_with_checking
try: inc = increment.Increment(new, old, inc_rp)
File "/usr/lib/python2.2/site-packages/rdiff_backup/increment.py",
line 36, in Increment
log.Log("Incrementing mirror file " + mirror.path, 5)
File "/usr/lib/python2.2/site-packages/rdiff_backup/log.py", line 121,
in __call__
self.log_to_term(message, verbosity)
File "/usr/lib/python2.2/site-packages/rdiff_backup/log.py", line 134,
in log_to_term
termfp.write(self.format(message, self.term_verbosity))
IOError: [Errno 11] Resource temporarily unavailable
Exception exceptions.TypeError: "'NoneType' object is not callable" in
<bound method GzipFile.__del__ of <gzip open file
'/mnt/cadlink1/tornado/usr/www/rdiff-backup-data/file_statistics.2004-04-16T
10:30:25-04:00.data.gz',
mode 'wb' at 0x8bca488 0x8bcb5dc>> ignored
Exception exceptions.TypeError: "'NoneType' object is not callable" in
<bound method GzipFile.__del__ of <gzip open file
'/mnt/cadlink1/tornado/usr/www/rdiff-backup-data/mirror_metadata.2004-04-16T
10:30:25-04:00.snapshot.gz',
mode 'wb' at 0x8c64a20 0x8c6464c>> ignored
Exception exceptions.TypeError: "'NoneType' object is not callable" in
<bound method GzipFile.__del__ of <gzip open file
'/mnt/cadlink1/tornado/usr/www/rdiff-backup-data/error_log.2004-04-16T10:30:
25-04:00.data.gz',
mode 'wb' at 0x8bd2ee0 0x8bd2ec4>> ignored
Traceback (most recent call last):
File "/usr/bin/rdiff-backup", line 24, in ?
rdiff_backup.Main.Main(sys.argv[1:])
File "/usr/lib/python2.2/site-packages/rdiff_backup/Main.py", line
247, in Main
take_action(rps)
File "/usr/lib/python2.2/site-packages/rdiff_backup/Main.py", line
216, in take_action
connection.PipeConnection(sys.stdin, sys.stdout).Server()
File "/usr/lib/python2.2/site-packages/rdiff_backup/connection.py",
line 336, in Server
self.get_response(-1)
File "/usr/lib/python2.2/site-packages/rdiff_backup/connection.py",
line 298, in get_response
try: req_num, object = self._get()
File "/usr/lib/python2.2/site-packages/rdiff_backup/connection.py",
line 221, in _get
raise ConnectionReadError("Truncated header string (problem "
rdiff_backup.connection.ConnectionReadError: Truncated header string
(problem probably originated remotely)





_______________________________________________
rdiff-backup-users mailing list at rdiff-backup-users < at > nongnu.org
http://mail.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL:
http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

Reply with quote
Post rdiff-backup crash 
Dave Hawkes wrote:

Quote:
Hi,

I've been running rdiff-backup (ver. 13.4) reliably for quite some time
but now consistently get the following crash when trying to backup up a
particular machine (see below). Has anyone any ideas?


I have found a problem with some file names using .13.3. These are
backed up from a mounted ntfs filesystem using smbfs in kernel 2.4.25.
i might be able to fix it by specifiying a different code page format.

as for you,
can you first start with a fresh rdiff-backup-data dir, then try and
replicate the problem - does it still happen then if you backup that
particular dir? try exclude that dir from the source and see if its a
similar problem to what I had, maybe we can narrow it down.

dave

Reply with quote
Post rdiff-backup crash 
On Saturday 17 April 2004 02:51, David Kempe schreef:
Quote:
Dave Hawkes wrote:
Quote:
Hi,

I've been running rdiff-backup (ver. 13.4) reliably for quite some time
but now consistently get the following crash when trying to backup up a
particular machine (see below). Has anyone any ideas?

There are some known issues with mounted (NFS) volumes. In fact those issues
are more NFS issues than rdiff-backup issues. To make sure it will work, it
is better to use the built-in possibility of rdiff-backup to backup from one
machine to another (using an ssh connection). There are examples in the
manual for that.

--
Cheers,

D.J. Kniep
Lindix BV
Tel. +31 36 5215580

Reply with quote
Post rdiff-backup crash 
I managed to fix the problem by lowering the terminal-verbosity setting
to 4 from 5. It would appear that there was some contention for stdout,
though I'm not sure how that could happen. The problem can likely be
fixed with an exception handler around the code that writes to stdout
and then deals with this event in an intelligent way.

Thanks
Dave Hawkes

David Kempe wrote:

Quote:
Dave Hawkes wrote:

Quote:
Hi,

I've been running rdiff-backup (ver. 13.4) reliably for quite some time
but now consistently get the following crash when trying to backup up a
particular machine (see below). Has anyone any ideas?


I have found a problem with some file names using .13.3. These are
backed up from a mounted ntfs filesystem using smbfs in kernel 2.4.25.
i might be able to fix it by specifiying a different code page format.

as for you,
can you first start with a fresh rdiff-backup-data dir, then try and
replicate the problem - does it still happen then if you backup that
particular dir? try exclude that dir from the source and see if its a
similar problem to what I had, maybe we can narrow it down.

dave


_______________________________________________
rdiff-backup-users mailing list at rdiff-backup-users < at > nongnu.org
http://mail.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL:
http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki


Display posts from previous:
Reply to topic Page 1 of 1
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
  


Magic SEO URL for phpBB