hello again,
here are the messages from my backupPC server,
via email notifications :
exemple 1)
"The following hosts had an error that is probably caused by a
misconfiguration. Please fix these hosts:
- mars (aborted by signal=PIPE)"
example 2)
"The following hosts had an error that is probably caused by a
misconfiguration. Please fix these hosts:
- mars (Child exited prematurely)"
the first example is the most encountered.
below you will find my first email about this problem.
any suggestions are welcome
thanks,
Pierre
- on the backup server : BackupPC 2.1.2, using its own rsync perl module
- on the box being backed up : rsync 2.6.6 , runing as a daemon (rsyncd)
the module to be backed up is a r ather big area : ~120 Gb
the rsyncd daemon is configured with a big timeout = 7200.
a) this is what I get on the backup server side (backupPC) :
[...]
2006-01-20 02:00:20 Started full backup on mars (pid=2898, share=zone21)
2006-01-20 04:35:16 Backup failed on mars (aborted by signal=PIPE)
[...]
b) this is what I get into the rsyncd log file :
[...]
Jan 20 03:35:14 mars rsyncd[12624]: rsync: writefd_unbuffered failed to write 4096 bytes: phase "unknown" [sender]: Connection timed out (110)
Jan 20 03:35:15 mars rsyncd[12624]: rsync error: error in rsync protocol data stream (code 12) at io.c(1099)
[...]
when running rsyncd with strace, here's what I get :
strace -f /usr/local/bin/rsync --daemon --config=/usr/local/rsync/etc/rsyncd.conf --daemon --no-detach
[...]
[pid 12624] sel ect(7, NULL, [6], NULL, {60, 0}) = 0 (Timeout)
[pid 12624] time(NULL) = 1137728011
[pid 12624] select(7, NULL, [6], NULL, {60, 0}) = 0 (Timeout)
[pid 12624] time(NULL) = 1137728071
[pid 12624] select(7, NULL, [6], NULL, {60, 0}) = 1 (out [6], left {16, 793000})
[pid 12624] write(6, "\374\17\0\7\7\360\377\377\6\360\377\377\5\360\377\377\4"..., 4096) = -1 ETIMEDOUT (Connection timed out)
[pid 12624] time([1137728114]) = 1137728114
[pid 12624] open("/etc/localtime", O_RDONLY) = -1 ENOENT (No such file or directory)
[pid 12624] open("/etc/localtime", O_RDONLY) = -1 ENOENT (No such file or directory)
[pid 12624] open("/etc/localtime", O_RDONLY) = -1 ENOENT (No such file or directory)
[pid 12624 ] rt_sigaction(SIGPIPE, {0x400f5000, [], 0}, {SIG_IGN }, 8) = 0
[pid 12624] send(3, "<156>Jan 20 03:35:14 rsyncd[1262"..., 143, 0) = 143
[pid 12624] rt_sigaction(SIGPIPE, {SIG_IGN}, NULL, 8) = 0
[pid 12624] rt_sigaction(SIGUSR1, {SIG_IGN}, {0x8055cd0, [USR1], SA_RESTART}, 8) = 0
[pid 12624] rt_sigaction(SIGUSR2, {SIG_IGN}, {0x8055cf0, [USR2], SA_RESTART}, 8) = 0
[pid 12624] time([1137728115]) = 1137728115
[pid 12624] open("/etc/localtime", O_RDONLY) = -1 ENOENT (No such file or directory)
[pid 12624] open("/etc/localtime", O_RDONLY) = -1 ENOENT (No such file or directory)
[pid 12624] open("/etc/localtime", O_RDONLY) = -1 ENOENT (No such file or directory)
[pid 12624] rt_sigaction(SIGPIPE, {0x400f5000, [], 0}, {SIG_IGN}, 8) = 0
[pid 12624] send(3, "<156>Jan 20 03:35:15 rsyncd[1262"..., 109, 0) = 109
[pid 12624] rt_sigaction(SIGPIPE, {SIG_IGN}, NULL, 8) = 0
[pid 12624 ] exit_group(12) = ?
Process 12624 detached
<... select resumed> ) = ? ERESTARTNOHAND (To be restarted)
--- SIGCHLD (Child exited) @ 0 (0) ---
waitpid(-1, NULL, WNOHANG) = 12624
waitpid(-1, NULL, WNOHANG) = -1 ECHILD (No child processes)
rt_sigaction(SIGCHLD, {0x8064620, [CHLD], SA_RESTART}, {0x8064620, [CHLD], SA_RESTART}, 8) = 0
sigreturn() = ? (mask now [])
select(6, [4 5], NULL, NULL, NULL
this problem also happens with previous ver sions of rsyncd.
May it be a problem with the rsync client perl implementation into backupPC ?
or is it a problem on the rsyncd side?
any suggestion will help,
thanks
Pierre
Nouveau : téléphonez moins cher avec Yahoo! Messenger ! Découvez les tarifs exceptionnels pour appeler la France et l'international. Téléchargez la version beta.
