Synching files using rsync utility

Shell Programming and Scripting
1

Iam using rsync tool to sync files from one linux server to other linux server, however it takes huge time to finish it. so I tried running multiple instances of rsync for different directories in background and it resulted in the below mentioned error.

rsync comand used:

/usr/bin/rsync -acrz ${ABS_DIR} -e /usr/bin/rsh ${TARGET}:${TARGET_DIR} &

the below error was thrown,

poll: protocol failure in circuit setup
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(463) [sender=2.6.8]

Please let me know whether is it possible to run multiple instances from one server to another server and if it is possible, please guide me...

Thanks:b:

The network connections are fine...

2

What does the rsyncd.conf file have for max connections?

What does syslog say about errors on the remote side?

3

There is no rsyncd.conf file, as per my understanding it is needed only when you are running rsync as a daemon (let me know if Iam wrong)

This is what the syslog shows

Nov 20 09:34:33 H00HOST xinetd[2404]: START: shell pid=11703 from=192.168.10.3
Nov 20 09:34:33 H00HOST xinetd[2404]: EXIT: shell status=0 pid=11703 duration=0(sec)
Nov 20 09:34:33 H00HOST xinetd[2404]: START: shell pid=11705 from=192.168.10.3
Nov 20 09:34:33 H00HOST xinetd[2404]: START: shell pid=11706 from=192.168.10.3
Nov 20 09:34:33 H00HOST xinetd[2404]: START: shell pid=11707 from=192.168.10.3
Nov 20 09:34:33 H00HOST xinetd[2404]: START: shell pid=11708 from=192.168.10.3
Nov 20 09:34:33 H00HOST xinetd[2404]: START: shell pid=11710 from=192.168.10.3
Nov 20 09:34:33 H00HOST xinetd[2404]: START: shell pid=11713 from=192.168.10.3
Nov 20 09:34:33 H00HOST xinetd[2404]: START: shell pid=11714 from=192.168.10.3
Nov 20 09:34:33 H00HOST xinetd[2404]: START: shell pid=11715 from=192.168.10.3
Nov 20 09:34:33 H00HOST xinetd[2404]: START: shell pid=11716 from=192.168.10.3
Nov 20 09:34:33 H00HOST xinetd[2404]: START: shell pid=11717 from=192.168.10.3
Nov 20 09:34:33 H00HOST xinetd[2404]: FAIL: shell per_source_limit from=192.168.10.3
Nov 20 09:34:33 H00HOST last message repeated 10 times
Nov 20 09:34:33 H00HOST xinetd[2404]: EXIT: shell status=0 pid=11707 duration=0(sec)
Nov 20 09:34:33 H00HOST xinetd[2404]: START: shell pid=11739 from=192.168.10.3
Nov 20 09:34:33 H00HOST xinetd[2404]: FAIL: shell per_source_limit from=192.168.10.3
Nov 20 09:34:33 H00HOST last message repeated 9 times
Nov 20 09:34:33 H00HOST xinetd[2404]: EXIT: shell status=0 pid=11713 duration=0(sec)
Nov 20 09:34:33 H00HOST xinetd[2404]: START: shell pid=11752 from=192.168.10.3
Nov 20 09:34:34 H00HOST xinetd[2404]: FAIL: shell per_source_limit from=192.168.10.3
Nov 20 09:34:34 H00HOST last message repeated 3 times
Nov 20 09:34:34 H00HOST xinetd[2404]: EXIT: shell status=0 pid=11708 duration=1(sec)
Nov 20 09:34:34 H00HOST xinetd[2404]: START: shell pid=11759 from=192.168.10.3
Nov 20 09:34:34 H00HOST xinetd[2404]: FAIL: shell per_source_limit from=192.168.10.3
Nov 20 09:34:34 H00HOST xinetd[2404]: EXIT: shell status=0 pid=11716 duration=1(sec)
Nov 20 09:34:34 H00HOST xinetd[2404]: EXIT: shell status=0 pid=11752 duration=1(sec)
Nov 20 09:34:35 H00HOST xinetd[2404]: EXIT: shell status=0 pid=11714 duration=2(sec)
Nov 20 09:34:35 H00HOST xinetd[2404]: EXIT: shell status=0 pid=11705 duration=2(sec)
Nov 20 09:34:36 H00HOST xinetd[2404]: EXIT: shell status=0 pid=11759 duration=2(sec)
Nov 20 09:34:36 H00HOST xinetd[2404]: EXIT: shell status=0 pid=11715 duration=3(sec)
Nov 20 09:34:36 H00HOST xinetd[2404]: EXIT: shell status=0 pid=11739 duration=3(sec)
Nov 20 09:34:44 H00HOST xinetd[2404]: EXIT: shell status=0 pid=11710 duration=11(sec)
Nov 20 09:34:44 H00HOST xinetd[2404]: EXIT: shell status=0 pid=11717 duration=11(sec)
Nov 20 09:34:44 H00HOST xinetd[2404]: EXIT: shell status=0 pid=11706 duration=11(sec)

This is what the error shown in the screen

poll: protocol failure in circuit setup
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(463) [sender=2.6.8]
poll: protocol failure in circuit setup
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(463) [sender=2.6.8]
poll: protocol failure in circuit setup
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(463) [sender=2.6.8]
poll: protocol failure in circuit setup
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(463) [sender=2.6.8]
poll: protocol failure in circuit setup
poll: protocol failure in circuit setup
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(463) [sender=2.6.8]
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(463) [sender=2.6.8]