bugrdiff-backup - Bugs: bug #25324, SpecialFileError...

 
 

bug #25324: SpecialFileError var/run/postgresql/.s.PGSQL.5432 Socket error: AF_UNIX path too long

Submitter:  Charl Matthee <charl>
Submitted:  Thu 15 Jan 2009 04:03:54 AM UTC
   
 
Category:  None Severity:  3 - Normal
Item Group:  None Status:  None
Privacy:  Public Assigned to:  None
Open/Closed:  Closed
* Mandatory Fields

Add a New Comment Rich Markup
   

Thu 15 Jan 2009 09:40:02 PM UTC, comment #3: 

Thanks for the reply.

Andrew Ferguson <owsla>
Group administrator
Thu 15 Jan 2009 09:24:42 PM UTC, comment #2: 

Unfortunately the errors have been lost. I did however only run the increased debugging command after the addition of --exclude-sockets for the first time so you're most likely correct that running the backup again with --exclude-sockets silenced the warnings.

You can most likely close this. If I come across it again I'll be sure to capture the warnings/errors I saw and reopen this item or create a new one referencing this one.

Charl Matthee <charl>
Thu 15 Jan 2009 06:06:15 PM UTC, comment #1: 

Yes, Unix sockets are restricted to ~107 characters in path name. It is a very strange restriction. When a program attempts to violate that restriction, the AF_UNIX "path too long" error is generated.

The solution is to use --exclude-sockets, since they probably shouldn't be backed-up anyway. From your email, it looks like you did that.

However, what you mean by: "I naturally added --exclude-sockets to the commandline above which caused a spureous amount of errors."

What errors did you get? Can you post them please? Thanks.

It could be that the errors (or, more likely, Warnings or messages) can from turning --exclude-sockets on after a first backup had been completed. After the first backup with --exclude-sockets was run, there were no more messages. The fact that you increased verbosity was unrelated. (And, in no way could affect any errors)

Andrew Ferguson <owsla>
Group administrator
Thu 15 Jan 2009 04:03:54 AM UTC, original submission:  

This error pops up when I use the following to back some remote system up:

/usr/bin/rdiff-backup --print-statistics --exclude /tmp --exclude /mnt --exclude /proc --exclude /sys --exclude /dev --exclude /cdrom --exclude /floppy --exclude /backup REMOTE_HOST::/ /backups/REMOTE_HOST

Where REMOTE_HOST is a valid hostname that the backup server can reach.

I naturally added --exclude-sockets to the commandline above which caused a spureous amount of errors.

I then turned debugging on by adding v5 to the commandline and the errors disappeared. Running the backup again after turning the debugging back off the errors (both the initial and subsequent ones) were gone.

I wonder if some inconsistent state was not trampled by the debugging switch being turned on which had the side effect of fixing the problem :)

Charl Matthee <charl>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by owsla (Posted a comment)
  • -email is unavailable- added by charl (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

    Follows 1 latest change.

    Date Changed by Updated Field Previous Value => Replaced by
    2009-01-15 owsla Open/ClosedOpen Closed

    Back to the top

    Powered by Savane 3.13-4b48.
    Corresponding source code