[SOLVED] Rsyncd unable to start

[Conti93]

Hello
I've just finished embedded installing (for the third time) N4F 10.2.0.2 rev2268 on a Core 2 Duo machine with 2GB RAM, 500GB HD and 4GB USB thumb drive; default config, only a 500GB HD UFS formatted and mounted.
I've tried to enable Rsync, but when I click "Apply" in fails showing "Error: The changes could not be applied (error code 1)."
If I check the log there are messages about "failed to start rsyncd", screenshotted in the attachment.
What am I missing?

Regards from Italy.
Mattia

[riki]

I had a similar problem, but just restarting the system solved it. It seems like rsyncd must be run at boot time. I hope this helps you!

[aerou]

I have the same problem since upgrading to 10.2.0.2.2268

Having to restart the whole server is not a solution. I like to change, add and remove modules on the fly.

[okuturn]

I have this problem on the 3 boxes I've upgraded to 10.2.0.2 rev2268. It occurs when you toggle rsync on and off as well as any change to a server side module. Client side modules don't seem to be affected by the condition which I suspect but haven't looked means that it doesn't cause rsync to be restarted. I have to make my changes, whether a server module or turning the rsync on or off, then reboot in order for it to work. It sucks as a solution but hardly anyone complains of this so I figure it isn't used much by the populace. I tried to migrate to syncthing but it is so much slower between the two boxes on the same subnet.

Edit: I did forget to mention that it occurs on a clean install as well as an install that has the config imported from a previous installation.

[jim71]

I have the same problem. I am running latest version 10.2.0.2.2268. I cannot say if it was on older version as I was not using rsync before.
I got this 2 logs:

rsyncd[4472]: rsync: getpeername on fd0 failed: Socket is not connected (57)
rsyncd[4472]: rsync error: error in socket IO (code 10) at clientname.c(173) [Receiver=3.1.1]

do not understand what fd0 has to do here (floppy ?) ? My system has a hostname and domain as nas4free.home.

The reboot trick does not seem to work, rsyncd is not running.

[jim71]

Actually what I said is not exact. Rebooting does start rsyncd. But as soon as you modify the config in the GUI, the config is correctly modified (/var/etc/rsyncd.conf) but the daemon is stopped and not restarted.

A much easier and less painful workaround than rebooting is to simply start the daemon in cli (as root):

/etc/rc.d/rsyncd start

So for me there is definitely a bug in nas4free here.

[riki]

A much easier and less painful workaround than rebooting is to simply start the daemon in cli (as root):
/etc/rc.d/rsyncd start

Good point, thanks!

So for me there is definitely a bug in nas4free here.

Agreed. Hope they fix the relevant scripts with next release.

[jim71]

For info version 10.2.0.2.2332 has just been release a few hours ago.

In the fix list you have:

- Fix rsync does not start/restart on WebGUI.

I've not upgraded yet, but it should fix our problem

Thanks !

[fouinix]

Hello,
For information, I have this issue with a fresh install (2332).
I can start rsyncd manually with "/etc/rc.d/rsyncd start".
But in the RSYNC Server module settings, I can't apply change : Error: The changes could not be applied (error code 1).
When I try to apply new change rsyncs is stopped and not restarted.

If I start manually I can connect and transfer files to rsyncd without any authentication!

[ms49434]

Hello,
For information, I have this issue with a fresh install (2332).
I can start rsyncd manually with "/etc/rc.d/rsyncd start".
But in the RSYNC Server module settings, I can't apply change : Error: The changes could not be applied (error code 1).
When I try to apply new change rsyncs is stopped and not restarted.

If I start manually I can connect and transfer files to rsyncd without any authentication!

A workaround has been added to the new release (2407).
So please report back here.