Register for the iXsystems Community to get an ad-free experience and exclusive discounts in our eBay Store.

RSYNC Service fails to start

Western Digital Drives - The Preferred Drives of FreeNAS and TrueNAS CORE

saimike

Newbie
Joined
Dec 10, 2018
Messages
2
I setup the RSYNC Service to allow another machine to backup to my FreeNAS machine. No problems getting it set up and the initial backup from the remote machine completed without errors. I needed to reboot the FreeNAS machine and now the RSYNC service with not start. I get the following errors:

Dec 16 19:44:20 saifs rsyncd[12872]: unable to bind any inbound sockets on port 873
Dec 16 19:44:20 saifs rsyncd[12872]: rsync error: error in socket IO (code 10) at socket.c(555) [Receiver=3.1.3]

I'm running FreeNAS-11.2-RELEASE. Any ideas?
 

saimike

Newbie
Joined
Dec 10, 2018
Messages
2
More info.

If I run 'sockstat | grep 873', it tells me that rpc.statd is using port 873. So, apparently statd must have started before rsyncd on boot and grabbed the port before rsyncd did?

I can then run 'ps -auxw | grep statd' and get the PID for rpc.statd

I can then use 'kill <PID>' to kill it and then restart rsync from the web interface.

Once rsync is running again, I can restart statd with 'service statd start' and my problem is fixed.

Is this a bug since statd can start before rsyncd and steal its port? And, the port it is stealing is 873 which is the well-known TCP port for rsync?
 
D

dlavigne

Guest
If this is reproducible it is worth reporting at bugs.freenas.org.
 

melloa

Dedicated Sage
Joined
May 22, 2016
Messages
1,726
If this is reproducible it is worth reporting at bugs.freenas.org.
Did this got a bug ticket? Getting the same on 11.1-U7.

1548944192174.png
 
D

dlavigne

Guest
I have not seen one, please post the issue number here once you create one.
 

melloa

Dedicated Sage
Joined
May 22, 2016
Messages
1,726
I have not seen one, please post the issue number here once you create one.
Not working from the GUI - maybe new link to bug site is incorrect?

Code:
Before filing a bug report or feature request, search http://bugs.freenas.org to ensure the issue has not already been reported. If it has, add a comment to the existing issue instead of creating a new one.
For enterprise-grade storage solutions and support, please visit http://www.ixsystems.com/storage/.

If you do not have an account, please register.


I think the new url is https://redmine.ixsystems.com/
 
D

dlavigne

Guest
Is that message in the tooltip or the Guide? And which FreeNAS version?
 

melloa

Dedicated Sage
Joined
May 22, 2016
Messages
1,726

melloa

Dedicated Sage
Joined
May 22, 2016
Messages
1,726

Newbie69

Newbie
Joined
Sep 24, 2020
Messages
1
Did this ever get resolved, and if so, how? The bug report lead nowhere, and I'm seeing exactly the same with TrueNAS Core 12.0-RC1.

Code:
Sep 27 09:05:17 truenas 1 2020-09-27T09:05:17.578998+02:00 truenas.kruemel.org rsyncd 2147 - - rsyncd version 3.1.3 starting, listening on port 873
Sep 27 09:05:17 truenas 1 2020-09-27T09:05:17.579090+02:00 truenas.kruemel.org rsyncd 2147 - - bind() failed: Address already in use (address-family 28)
Sep 27 09:05:17 truenas 1 2020-09-27T09:05:17.579101+02:00 truenas.kruemel.org rsyncd 2147 - - bind() failed: Address already in use (address-family 2)
Sep 27 09:05:17 truenas 1 2020-09-27T09:05:17.579109+02:00 truenas.kruemel.org rsyncd 2147 - - unable to bind any inbound sockets on port 873
Sep 27 09:05:17 truenas 1 2020-09-27T09:05:17.579131+02:00 truenas.kruemel.org rsyncd 2147 - - rsync error: error in socket IO (code 10) at socket.c(555) [Receiver=3.1.3]


Code:
# sockstat | grep 873
root     rpc.statd  1381  4  udp6   *:873                 *:*
root     rpc.statd  1381  5  tcp6   *:873                 *:*
root     rpc.statd  1381  6  udp4   *:873                 *:*
root     rpc.statd  1381  7  tcp4   *:873                 *:*
 
Top