[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [rdiff-backup-users] "AF_UNIX path too long" error

From: Alan
Subject: Re: [rdiff-backup-users] "AF_UNIX path too long" error
Date: Tue, 10 Jun 2003 12:47:32 -0700
User-agent: Mutt/1.5.4i

On Tue, Jun 10, 2003 at 02:31:16PM -0400, Andrew K. Bressen wrote:
> Alan <address@hidden> writes:
> > Exception 'AF_UNIX path too long' raised of class 'socket.error':
> Under 0.10 I got that error for most open socket files. 
> Upgrading to 0.11.4 seems to have cured it. 

Well, both server and client are up to .11.4 now, but I'm getting the
following error:

Executing rdiff
Warning: Metadata file not found.
Metadata will be read from filesystem.
Traceback (most recent call last):
  File "/usr/bin/rdiff-backup", line 24, in ?
  File "/usr/lib/python2.2/site-packages/rdiff_backup/Main.py", line 236, in 
  File "/usr/lib/python2.2/site-packages/rdiff_backup/Main.py", line 210, in 
    elif action == "backup": Backup(rps[0], rps[1])
  File "/usr/lib/python2.2/site-packages/rdiff_backup/Main.py", line 250, in 
    backup.Mirror_and_increment(rpin, rpout, incdir)
  File "/usr/lib/python2.2/site-packages/rdiff_backup/backup.py", line 47, in 
    DestS.patch_and_increment(dest_rpath, source_diffiter, inc_rpath)
  File "/usr/lib/python2.2/site-packages/rdiff_backup/connection.py", line 424, 
in __call__
    return apply(self.connection.reval, (self.name,) + args)
  File "/usr/lib/python2.2/site-packages/rdiff_backup/connection.py", line 346, 
in reval
    if isinstance(result, Exception): raise result
master:/usr/ufbackup/ufies.org# Traceback (most recent call last):
  File "/usr/bin/rdiff-backup", line 24, in ?
  File "/usr/lib/python2.2/site-packages/rdiff_backup/Main.py", line 236, in 
  File "/usr/lib/python2.2/site-packages/rdiff_backup/Main.py", line 208, in 
    connection.PipeConnection(sys.stdin, sys.stdout).Server()
  File "/usr/lib/python2.2/site-packages/rdiff_backup/connection.py", line 331, 
in Server
  File "/usr/lib/python2.2/site-packages/rdiff_backup/connection.py", line 293, 
in get_response
    try: req_num, object = self._get()
  File "/usr/lib/python2.2/site-packages/rdiff_backup/connection.py", line 216, 
in _get
    raise ConnectionReadError("Truncated header string (problem "
rdiff_backup.connection.ConnectionReadError: Truncated header string (problem 
probably originated remotely)
Exception exceptions.TypeError: "'NoneType' object is not callable" in <bound 
method GzipFile.__del__ of <gzip open file 
 mode 'wb' at 0x8288c70 0x82890dc>> ignored

It looks like it's failing on the metadata, but then trying to recover.  
I dont know python well enough to hazard a guess as to what is actually
going on :)

Another thing. Is there a way to not try to recover from a bad backup?
or is there compatibility with older (.10.x) rdiff-backups?  I am trying 
to backup to the local filesystem, which has a few gig of data already
there from rdiff-backup ( I have it remove older than 30d I think), but
when I run the rdiff I get:

master:/usr/local/sbin# sh test.sh
Executing rdiff
Previous backup seems to have failed, regressing destination now.
Fatal Error: No metadata for time Mon May  5 03:11:49 2003 found, cannot regress

I don't see a way to not regress and just start a fresh backup, or
delete just that one last failed backup.  I'll probably end up nuking
the local backup anyway, just to test, but these features might be put
in a wishlist?  Finding out what the original problem above is would be
better of course :)


Alan <address@hidden> - http://arcterex.net
"There are only 3 real sports: bull-fighting, car racing and mountain 
climbing. All the others are mere games."                -- Hemingway

reply via email to

[Prev in Thread] Current Thread [Next in Thread]