Trying to fix rsync error timeout waiting for daemon connection (code 35)? We can help you.

Here at Bobcares, we have seen several such rsync command related errors as part of our Server Management Services for web hosts and online service providers.

Today we’ll take a look at the causes for this error and see the fix.

What causes rsync error timeout waiting for daemon connection (code 35) to occur

Normally, this error occurs while trying to get a directory listing of the remote server,

$ rsync –contimeout=2 remoteserver::
rsync error: timeout waiting for daemon connection (code 35) at socket.c(281) [Receiver=3.1.2]

While using the rsync client, we have the option to set a maximum I/O timeout in seconds. However, if we don’t send any data in the specified time, then the transfer will be aborted.

Using this timeout option, we can override the timeout defined by the client. This is useful to avoid waiting for a dead client.

By default, the timeout value is zero which means no timeout.

Normally, this error occurs due to many reasons that include,

1. Providing an incorrect username or password.
2. rsync daemon or ssh service not running in destination server
3. Port 873 is not open in the firewall

How we fix this rsync error

Now let’s get into the solution part of the error. Here are the steps that our Support Engineers provide to get rid of this error.

1. Make sure that you have provided the right login details. If you are not sure about the password then try resetting it before entering the wrong ones.

2. Services must be running on the server. If necessary, restart the services.

3. Make sure to check the port 873 is open. If not, then open it in the firewall.

[Need any further assistance in fixing rsync errors? – We are here to help you.]

Conclusion

In short, this rsync error can occur due to incorrect username or password, blockage of port 873 in a firewall, or ssh service not running in the destination server. Today, we saw the solution to this rsync error.