I do apologize. The backuppc server is Ubuntu 9.10 and the server being backed up is Centos 5.4. I have changed everything back to rsync and tried a manual full backup (since that is what it was attempting to do when it failed) I ran strace on the PID of rsync on the remote server being backed up. The last few lines of the output are below.
read(0, "\276\202\271p\351\235\273\357g\36\274~[\4Y\265z\276,\321\344`\246\266\341\276\3158\264RA\366"..., 8184) = 8184
select(1, [0], [], NULL, {60, 0}) = 1 (in [0], left {60, 0})
read(0, "4\274\370\2620\20\6\312\244M\22\353\r\304{\211\32h\276\310\\\256\303\217\4\217X\274\237\6z\311"..., 8184) = 8184
select(1, [0], [], NULL, {60, 0}) = 1 (in [0], left {60, 0})
read(0, "\303\255\0374n\360D\355dvvi\254\264\333\224]lX\n*\336Y*\205\3510\374`t\210\303"..., 8184) = 8184
select(1, [0], [], NULL, {60, 0}) = 1 (in [0], left {60, 0})
read(0, "\256\374O\362\350\224\30\3101(Y\"8\3279z\300nt\10*\367\26+\355\364\245W)/\224\301"..., 8184) = 8184
select(1, [0], [], NULL, {60, 0}) = 1 (in [0], left {60, 0})
read(0, "\314\326\4\242P\345\3\332\245b\317\363\4\253'\307\3056Y\307X\313\364I\5\3746\fH\340\212w"..., 8184) = 1056
select(1, [0], [], NULL, {60, 0}) = 1 (in [0], left {58, 296000})
read(0, "", 8184) = 0
select(2, NULL, [1], [1], {60, 0}) = 1 (out [1], left {60, 0})
write(1, "O\0\0\10rsync: connection unexpected"..., 83) = -1 EPIPE (Broken pipe)
--- SIGPIPE (Broken pipe) @ 0 (0) ---
write(2, "rsync: writefd_unbuffered failed"..., 87) = -1 EPIPE (Broken pipe)
--- SIGPIPE (Broken pipe) @ 0 (0) ---
rt_sigaction(SIGUSR1, {0x1, [], 0}, NULL, 8) = 0
rt_sigaction(SIGUSR2, {0x1, [], 0}, NULL, 8) = 0
write(2, "rsync error: errors with program"..., 83) = -1 EPIPE (Broken pipe)
--- SIGPIPE (Broken pipe) @ 0 (0) ---
rt_sigaction(SIGUSR1, {0x1, [], 0}, NULL, 8) = 0
rt_sigaction(SIGUSR2, {0x1, [], 0}, NULL, 8) = 0
gettimeofday({1259785360, 391955}, NULL) = 0
select(0, NULL, NULL, NULL, {0, 100000}) = 0 (Timeout)
gettimeofday({1259785360, 492092}, NULL) = 0
exit_group(13) = ?
Process 28645 detached
Backuppc shows the following error when it fails:
2009-12-02 14:17:58 full backup started for directory /; updating partial #4
2009-12-02 14:24:59 Aborting backup up after signal PIPE
2009-12-02 14:25:00 Got fatal error during xfer (aborted by signal=PIPE)
remote machine: rsync version 3.0.6 protocol version 30
backuppc: rsync version 3.0.6 protocol version 30
Both using ext3 filesystem
Donny B.
On Wed, Dec 2, 2009 at 2:18 PM, Les Mikesell <lesmikesell AT gmail DOT com> wrote:
Kameleon wrote:
> I have an issue with one of my backuppc servers. This server is used to
> only backup one server and has been doing flawless since it was
> installed about a week ago. Until last night....
>
> I checked it this morning to find the above error in the host summary. I
> did some checking and even manually ran the backup with an strace on the
> process on the remote server. Every time it would fail. I had a similar
> issue on my home backuppc server on a few servers and switching them
> from rsync to rsyncd and changing the needed settings did the trick. Not
> so much with this one. Here are the last few lines of the log when doing
> both rsync and rsyncd:
>
> via rsync:
>
> 2009-12-02 10:18:04 full backup started for directory /; updating partial #4
> 2009-12-02 10:25:09 Aborting backup up after signal PIPE
> 2009-12-02 10:25:10 Got fatal error during xfer (aborted by signal=PIPE)
> 2009-12-02 10:25:10 Saved partial dump 4
>
> Via rsyncd:
>
> 2009-12-02 11:09:00 full backup started for directory main; updating
> partial #4
> 2009-12-02 11:15:01 Aborting backup up after signal PIPE
> 2009-12-02 11:15:02 Got fatal error during xfer (aborted by signal=PIPE)
>
> I am at a loss. Something is causing the remote end to fail. I did a
> little research and found that if doing backup via rsync and ssh it
> could be a large file causing it, as in over 2GB. I looked in the
> directories being backed up and there are a few files larger than 2GB
> that are being backed up. Is there a workaround for this?
be the only thing with low size limits and I think that might be version
specific.
--
Les Mikesell
lesmikesell AT gmail DOT com
------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
BackupPC-users mailing list
BackupPC-users AT lists.sourceforge DOT net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev _______________________________________________
BackupPC-users mailing list
BackupPC-users AT lists.sourceforge DOT net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
|
