Hello.
My problem is Rsync stops when I use it between 2 of my servers (2 NAS
Synology) ( named "*.22*" and "*.6*" ).
The problem continue...
For example :
_ Rsync run correctly between my server "*.22*" and ".6" (
in the 2
directions )
_ Rsync run correctly between my server ".6" and "*.8*" ( in
the 2
directions )
_ Rsync *doesn't run* correctly between my server "*.8*" and
"*.22*" ( in
the 2 directions ) :
With little files ( ~ 2 Ko ) the replication works correctly ! But, with
larger files ( > 20Ko ), Rsync "stops" on the middle, and always at
the same
moment : It's seems to stop to send datas.
Here an example of Rsync's error between my server "*.8*" and
"*.22*" (with
the file "port-stagiaire.htm" ~20Ko )
#> rsync -avvvv --timeout=60 /volume1/old/port-stagiaire.htm
root at 192.168.0.8:/volume1/NetBackup/test5
*cmd=<NULL> machine=192.168.0.8 user=root path=/volume1/NetBackup/test5
cmd[0]=ssh cmd[1]=-l cmd[2]=root cmd[3]=192.168.0.8 cmd[4]=rsync
cmd[5]=--server cmd[6]=-vvvvlogDtpre.iLs cmd[7]=--timeout=60 cmd[8]=.
cmd[9]=/volume1/NetBackup/**test5
opening connection using: ssh -l root 192.168.0.8 rsync --server
-vvvvlogDtpre.iLs --timeout=60 . /volume1/NetBackup/test5
note: iconv_open("ANSI_X3.4-1968", "ANSI_X3.4-1968")
succeeded.
(Client) Protocol versions: remote=30, negotiated=30
(Server) Protocol versions: remote=30, negotiated=30
sending incremental file list
[sender] make_file(port-stagiaire.htm,***,0)
[sender] flist start=1, used=1, low=0, high=0
[sender] i=1 /volume1/old port-stagiaire.htm mode=0100744 len=21250 uid=0
gid=0 flags=5
send_file_list done
file list sent
send_files starting
server_recv(2) starting pid=7785
gid 0() maps to 0
recv_file_name(port-stagiaire.**htm)
received 1 names
[receiver] flist start=1, used=1, low=0, high=0
[receiver] i=1 1 port-stagiaire.htm mode=0100744 len=21250 uid=0 gid=0
flags=0
recv_file_list done
get_local_name count=1 /volume1/NetBackup/test5
generator starting pid=7785
recv_files(1) starting
delta-transmission enabled
recv_generator(port-stagiaire.**htm,1)
send_files(1, /volume1/old/port-stagiaire.**htm)
count=0 n=0 rem=0
send_files mapped /volume1/old/port-stagiaire.**htm of size 21250
calling match_sums /volume1/old/port-stagiaire.**htm
port-stagiaire.htm
sending file_sum
false_alarms=0 hash_hits=0 matches=0
sender finished /volume1/old/port-stagiaire.**htm
generate_files phase=1
_exit_cleanup(code=30, file=io.c, line=237): entered
rsync error: timeout in data send/receive (code 30) at io.c(237)
[receiver=3.0.4]
_exit_cleanup(code=30, file=io.c, line=237): about to call exit(30)
Killed by signal 2.
_exit_cleanup(code=20, file=rsync.c, line=582): entered
rsync error: unexplained error (code 255) at rsync.c(582) [sender=3.0.4]
_exit_cleanup(code=20, file=rsync.c, line=582): about to call exit(255)*
Here it's the log on the "backup" server ( the "*.8*"
for example ), when I
use Rsync's daemon connection (with command "rsync ...
root at 192.168.0.8::NetBackup/test5"
) :
*2009/07/15 11:21:13 [7793] connect from pc22.priv (192.168.0.22)
2009/07/15 11:21:17 [7793] rsync to NetBackup/test5 from
root at pc22.priv(192.168.0.22)
2009/07/15 11:21:17 [7793] receiving file list
2009/07/15 11:22:17 [7793] rsync error: timeout in data send/receive (code
30) at io.c(237) [receiver=3.0.4]
2009/07/15 11:22:17 [7793] rsync: connection unexpectedly closed (88 bytes
received so far) [generator]
2009/07/15 11:22:17 [7793] rsync error: rsync service is no running (code
43) at io.c(633) [generator=3.0.4]*
For information, the server ".6" runs a 2.6.3 version of rsync
(protocol
v.28).
the server "*.22*" and "*.6*" run a 3.0.4 version of rsync
(protocol v.30).
( I searched on the net, no problem for this version. )
I tried to force to use the protocol v.28 with the "*.22*" and
"*.6*" =>
same error.
I'm not sure the problem comes from Rsync...
My team and me doesn't know from which that can come. If somebody has an
idea ... :)
Thx
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.samba.org/pipermail/rsync/attachments/20090717/429e7a38/attachment.html>
