Rsync error in socket io code 10

rsync error: error in socket IO (code 10) at clientserver.c(122) [sender=3.0.7]
rsync failed!

Rsync error code 10 is a common error message that is triggered while working with rsync. Basically, it occurs when the rsync service is not running in the server.

As part of our Server Management Services for online service providers and website owners, we have seen several other causes for this error.

Today we’ll go through the top cause and fix for this rsync error.

Why does rsync operation ends with error 10?

Rsync is a command-line tool that allows local and remote file transfer. This is mostly used for taking backup, transferring files, etc.

But when the rsync tool is not installed/enabled in any of the servers during a remote transfer, rsync operations end with an error code 10.

More specifically, this error is triggered when both the servers are not able to establish a proper connection between them. At times lack of proper password-less authentication between the servers or firewall restrictions can also trigger this error.

Rsync is not enabled in the server

The most common reason for this error is rsync not running on the server, probably due to a reboot. To check if this is the case, you can run the following on the server that is supposed to reject the connection (destination):

$ systemctl list-unit-files |grep rsync
rsync.service disabled

This indicates that rsync is disabled in the server. We could fix this error easily by enabling the rsync service.

$ sudo systemctl enable rsync.service
Synchronizing state for rsync.service with sysvinit using update-rc.d...
Executing /usr/sbin/update-rc.d rsync defaults
Executing /usr/sbin/update-rc.d rsync enable

Once the service is enabled, the next step is to activate it. It can be done easily with the help of following commands:

$ sudo systemctl start rsync.service

This activates the service. Now we can check the service with:

$ systemctl |grep rsync
rsync.service loaded active running   fast remote file copy program daemon

Other common causes of rsync error 10

Apart from the reasons that we mentioned earlier some alternate reasons can also trigger the rsync error 10. These are basically those reasons that create a hindrance in establishing a  secure connection between the two servers.

Firewall restrictions, low time out value of script, are a few among them. The clue about the exact reason can be obtained from the dmesg log. For instance, a sample log entry is shown below:

dmesg | grep rsync
[85852.560086] Out of memory: Kill process 4242 (rsync) score 194 or sacrifice child [85852.562695] Killed process 4243 (rsync) total-vm:121948kB, anon-rss:65752kB, file-rss:4kB – Sparhawk

This confirms that the rsync service it getting terminated due to insufficient memory. The fix here would be to adjust the rsync parameters to reduce the memory usage or to increase the resource availability of the server.

[Need assistance to fix rsync errors? – We’ll help you.]

Conclusion

In short, rsync error code 10 occurs when rsync is not enabled/installed in the server. Today, we saw some other possible reasons for this error and how our Support Engineers fixed the rsync errors.

var google_conversion_label = «owonCMyG5nEQ0aD71QM»;

Rsync error code 10 : How to fix it

by Arya MA | Jun 15, 2020

rsync error: error in socket IO (code 10) at clientserver.c(122) [sender=3.0.7]
rsync failed!

Rsync error code 10 is a common error message that is triggered while working with rsync. Basically, it occurs when the rsync service is not running in the server.

As part of our Server Management Services for online service providers and website owners, we have seen several other causes for this error.

Today we’ll go through the top cause and fix for this rsync error.

Why does rsync operation ends with error 10?

Rsync is a command-line tool that allows local and remote file transfer. This is mostly used for taking backup, transferring files, etc.

But when the rsync tool is not installed/enabled in any of the servers during a remote transfer, rsync operations end with an error code 10.

More specifically, this error is triggered when both the servers are not able to establish a proper connection between them. At times lack of proper password-less authentication between the servers or firewall restrictions can also trigger this error.

Rsync is not enabled in the server

The most common reason for this error is rsync not running on the server, probably due to a reboot. To check if this is the case, you can run the following on the server that is supposed to reject the connection (destination):

This indicates that rsync is disabled in the server. We could fix this error easily by enabling the rsync service.

Once the service is enabled, the next step is to activate it. It can be done easily with the help of following commands:

$ sudo systemctl start rsync.service

This activates the service. Now we can check the service with:

Other common causes of rsync error 10

Apart from the reasons that we mentioned earlier some alternate reasons can also trigger the rsync error 10. These are basically those reasons that create a hindrance in establishing a secure connection between the two servers.

Firewall restrictions, low time out value of script, are a few among them. The clue about the exact reason can be obtained from the dmesg log. For instance, a sample log entry is shown below:

This confirms that the rsync service it getting terminated due to insufficient memory. The fix here would be to adjust the rsync parameters to reduce the memory usage or to increase the resource availability of the server.

[Need assistance to fix rsync errors? – We’ll help you.]

Conclusion

In short, rsync error code 10 occurs when rsync is not enabled/installed in the server. Today, we saw some other possible reasons for this error and how our Support Engineers fixed the rsync errors.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

Источник

Rsync error code 10 : How to fix it

rsync error: error in socket IO (code 10) at clientserver.c(122) [sender=3.0.7]
rsync failed!

Rsync error code 10 is a common error message that is triggered while working with rsync. Basically, it occurs when the rsync service is not running in the server.

As part of our Server Management Services for online service providers and website owners, we have seen several other causes for this error.

Today we’ll go through the top cause and fix for this rsync error.

Why does rsync operation ends with error 10?

Rsync is a command-line tool that allows local and remote file transfer. This is mostly used for taking backup, transferring files, etc.

But when the rsync tool is not installed/enabled in any of the servers during a remote transfer, rsync operations end with an error code 10.

More specifically, this error is triggered when both the servers are not able to establish a proper connection between them. At times lack of proper password-less authentication between the servers or firewall restrictions can also trigger this error.

Rsync is not enabled in the server

The most common reason for this error is rsync not running on the server, probably due to a reboot. To check if this is the case, you can run the following on the server that is supposed to reject the connection (destination):

This indicates that rsync is disabled in the server. We could fix this error easily by enabling the rsync service.

Once the service is enabled, the next step is to activate it. It can be done easily with the help of following commands:

$ sudo systemctl start rsync.service

This activates the service. Now we can check the service with:

Other common causes of rsync error 10

Apart from the reasons that we mentioned earlier some alternate reasons can also trigger the rsync error 10. These are basically those reasons that create a hindrance in establishing a secure connection between the two servers.

Firewall restrictions, low time out value of script, are a few among them. The clue about the exact reason can be obtained from the dmesg log. For instance, a sample log entry is shown below:

This confirms that the rsync service it getting terminated due to insufficient memory. The fix here would be to adjust the rsync parameters to reduce the memory usage or to increase the resource availability of the server.

[Need assistance to fix rsync errors? – We’ll help you.]

Conclusion

In short, rsync error code 10 occurs when rsync is not enabled/installed in the server. Today, we saw some other possible reasons for this error and how our Support Engineers fixed the rsync errors.

Источник

rsync error: error in socket IO (code 10)

I am trying to backup my database using vbr.py script onto remote servers. I set up passwordless ssh connection for dbadmin user between the production server and backup server and ssh works fine, but the backup is failing with the following error

rsync: failed to connect to 15.224.232.169: Connection timed out (110)
rsync error: error in socket IO (code 10) at clientserver.c(122) [sender=3.0.7]
rsync failed!

53961: vbr client subproc on 1.1.54.3 terminates with returncode 1. Details in vbr_v_verprd1_node0002_client.log on that host.
rsync: failed to connect to 15.224.232.168: Connection timed out (110)
rsync error: error in socket IO (code 10) at clientserver.c(122) [sender=3.0.7]
rsync failed!

Child processes terminated abnormally.
backup failed!

Some of the files are being copied and it suddenly terminates. Can you please help me out on why this is happening and whats the fix for it.

Please verify that you have password less ssh access to all nodes in the cluster and also password less ssh access to self node.

Missing password less ssh to self node is often the problem.
Missing password less ssh on one of the nodes could be causing this error.

The vbr.py uses an rsync port of 50000 check that this port is open

Rsync by default uses port 873

To test open for open ports:

1. On each node including node 1 make it a listening node for port activity using

Each node will go into listen mode and wait for remote input across the port.

2. On another session on node 1 make it a sending node and send a message over port

nc nodename 873

3. Where nodename is the hostname or IP Address of node 1, it will go into send mode waiting for you to input keystrokes.
Entering text and hitting return should push the text across the port and display on the listening machine.

CTRL C gets you out.

Repeat for each node to ensure the port on all nodes from the initiator node are open.

Other Vertica Ports

Vertica
5433 TCP (All connections)
Spread
4803 TCP (Client connections)
4803 UDP (Daemon Daemon)
4804 UDP (Daemon Daemon)
4805 UDP (Monitor to Daemon) (optional and only if «DangerousMonitor = yes» in config file)

The ssh connection passwordless is fine from all the production servers to the backup remote hosts. i do see that the backup directory on the remote host is created and some files copied.

However, the ssh passwordless from the backup host to production server is not working.. can that be an issue? is that required or if we just have from production to backup server that is enough?

The ssh is setup between both the servers and the ports are opened too now but still it fails with the same issue.

Please let me know what is wrong here.

When i try the command rsync directly it works fine without issue but the backup always fails with the error. please help.

[[email protected] config]$ rsync -avr —rsh=/usr/bin/ssh /opt/vertica/config/prod_backup_remote.ini VERRWCSTDB01:/opt/vertica/config/

sending incremental file list
prod_backup_remote.ini

sent 666 bytes received 31 bytes 464.67 bytes/sec
total size is 557 speedup is 0.80

rsync: failed to connect to 192.168.201.202: Connection timed out (110)
rsync error: error in socket IO (code 10) at clientserver.c(122) [sender=3.0.7]
rsync failed!

Child processes terminated abnormally.

how do i do that?

I tried with both the ports 873 and 50000. When using 873 I get the error message as connection refused and when using 50000 it gives error of connection time out. Please let me know how to fix this. We do not have backups since a long time and really need this running.

rsync: failed to connect to 192.168.201.204: Connection refused (111)
rsync error: error in socket IO (code 10) at clientserver.c(122) [sender=3.0.7]
rsync failed!

]# cat /tmp/vbr/vbr_rsyncd.log
2014/04/01 11:44:19 [28758] rsyncd version 3.0.7 starting, listening on port 873
2014/04/01 11:44:19 [28758] bind() failed: Permission denied (address-family 2)
2014/04/01 11:44:19 [28758] socket(10,1,6) failed: Address family not supported by protocol
2014/04/01 11:44:19 [28758] unable to bind any inbound sockets on port 873
2014/04/01 11:44:19 [28758] rsync error: error in socket IO (code 10) at socket.c(541) [Receiver=3.0.7]
2014/04/01 11:48:46 [29388] rsyncd version 3.0.7 starting, listening on port 873
2014/04/01 11:48:46 [29388] bind() failed: Permission denied (address-family 2)
2014/04/01 11:48:46 [29388] socket(10,1,6) failed: Address family not supported by protocol
2014/04/01 11:48:46 [29388] unable to bind any inbound sockets on port 873
2014/04/01 11:48:46 [29388] rsync error: error in socket IO (code 10) at socket.c(541) [Receiver=3.0.7]

### When using 50000

rsync: failed to connect to 192.168.201.202: Connection timed out (110)
rsync error: error in socket IO (code 10) at clientserver.c(122) [sender=3.0.7]
rsync failed!

Also, running the rsync command manually for the data directory works fine without issue. only when using vbr.py it is failing, why is this the case?

]$ ps -ef |grep rsync
dbadmin 11250 1 0 Jan02 ? 00:00:00 /opt/vertica/bin/rsync —daemon —config=/tmp/vbr/vbr_rsyncd.conf —port=50000
[[email protected]

]$ /opt/vertica/bin/rsync -avz /data/backups [email protected]:/data/backups
sending incremental file list
backups/
backups/v_verprd1_node0001/
backups/v_verprd1_node0001/.production_backup_test.done/
backups/v_verprd1_node0001/production_backup_test/
backups/v_verprd1_node0001/production_backup_test/production_backup_test.info
backups/v_verprd1_node0001/production_backup_test/production_backup_test.txt
backups/v_verprd1_node0001/production_backup_test/catalog/
backups/v_verprd1_node0001/production_backup_test/catalog/VERPRD1/
backups/v_verprd1_node0001/production_backup_test/catalog/VERPRD1/v_verprd1_node0001_catalog/
backups/v_verprd1_node0001/production_backup_test/catalog/VERPRD1/v_verprd1_node0001_catalog/vertica.conf
backups/v_verprd1_node0001/production_backup_test/catalog/VERPRD1/v_verprd1_node0001_catalog/Snapshots/
backups/v_verprd1_node0001/production_backup_test/catalog/VERPRD1/v_verprd1_node0001_catalog/Snapshots/catalog.ctlg
backups/v_verprd1_node0001/production_backup_test/data/
backups/v_verprd1_node0001/production_backup_test/data/VERPRD1/
backups/v_verprd1_node0001/production_backup_test/data/VERPRD1/v_verprd1_node0001_data/

Yes, I checked the netstat on 50000 port when its running the backup using vbr.py and see that its opened as i do see the message below in the log

[[email protected] vbr]# tail -f vbr_rsyncd.log
2014/04/01 15:01:21 [20252] rsyncd version 3.0.7 starting, listening on port 50000

And while the backup is running i do see that the port 873 is being used by rsync on all the nodes so that is open too

egrep rsync /etc/services
rsync 873/tcp # rsync
rsync 873/udp # rsync
airsync 2175/tcp # Microsoft Desktop AirSync Protocol
airsync 2175/udp # Microsoft Desktop AirSync Protocol

I tried with two ports 50001 and 50002 and its the same error

rsync: failed to connect to 192.168.201.202: Connection timed out (110)
rsync error: error in socket IO (code 10) at clientserver.c(122) [sender=3.0.7]
rsync failed!

Child processes terminated abnormally.
backup failed!

Источник

Why does rsync fail with Broken pipe (32), error in socket IO (code 10) at io.c(820)? [closed]

Questions describing a problem that can’t be reproduced and seemingly went away on its own (or went away when a typo was fixed) are off-topic as they are unlikely to help future readers.

Closed 5 years ago .

I bought a new hard drive for my server, and I’m trying to reorganise my files. For the first transfer, rsync copied

3 GB perfectly. However, with the equivalent rsync command, the second transfer fails.

The first run copied about 550 of 800 GB before choking. More recent attempts only manage to copy 1 GB before dying. I’m not sure if it’s relevant, but the source is a backintime incremental backup drive, so it contains a ton of hard links. How can I fix this error and complete the command?

I’m running rsync version 3.1.1 protocol version 31.

1 Answer 1

[85852.560086] Out of memory: Kill process 4242 (rsync) score 194 or sacrifice child [85852.562695] Killed process 4243 (rsync) total-vm:121948kB, anon-rss:65752kB, file-rss:4kB – Sparhawk

• change your rsync speed to below that of your disks. —bwlimit=6000 .. USB 2 is 60MB/s /4 for rw over 2 drives or /10 for seeking on non ssd. or get a XU4 with 2GB RAM and USB3.
• change the kernel memory parameters echo 100 > /proc/sys/vm/watermark_scale_factor
• force a memory purge during operation echo 3 > /proc/sys/vm/drop_caches
• make sure you are using kernel 4.9.29 uname -r

Источник