Rsync error “socket operation on non-socket”

Some of our users have recently reported seeing the following error in their rsync logs:

rsync: Failed to dup/close: Socket operation on non-socket (108)
rsync error: error in IPC code (code 14) at pipe.c(72) [sender=3.0.3]
rsync: read error: Connection reset by peer (104)
rsync error: error in IPC code (code 14) at io.c(803) [sender=3.0.3]

BackupAssist 5.1 reports this error as BA3012 “Error in rsync protocol data stream”. BackupAssist 5.2 reports either BA3302 “Could not establish connection” or BA3014 “Error in IPC code”.

We have identified two possible causes for this error:

  1. Windows Data Execution Prevention (DEP) preventing rsync from running.
  2. Another program, such as the Kaseya Agent inserting itself into the Windows networking stack

To resolve the DEP issue you need to go to Control Panel > System > Advanced > Performance > Data Execution Prevention.
Data Execution Prevention settings
Either change the DEP setting to “essential Windows programs and services only”, or add exceptions for the three programs required for rsync: rsync.exe, ssh.exe and ssh-keygen.exe. These programs are located in "C:\ProgramData\BackupAssist v5\temp\Rsync" on Windows Vista and Server 2008, or in "C:\Documents and Settings\All Users\Application Data\BackupAssist v5\temp\Rsync" on earlier versions of Windows.

If you have the Kaseya Agent installed on your machine, please see this Kaseya KB article for information on resolving the problem.

1 thought on “Rsync error “socket operation on non-socket””

  1. Great post, you have pointed out some excellent points, I as well think this is a very excellent website.


Leave a Comment

Share on email
Share on print
Share on facebook
Share on google
Share on twitter
Share on linkedin

Subscribe to Blog via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email. Join 1,874 other subscribers