RSYNC not auto starting

[Juggler]

I recently upgraded to 2545 and now realizing that RSYNC isn't syncing after a reboot. I have to go into settings to kick-start it then it works. Any ideas?

[BraM]

Kick start? how?

I too am experiencing errors after a recent build.

Code: Select all

rsync: read error: Operation timed out (60)
rsync error: error in socket IO (code 10) at io.c(785) [sender=3.1.2]

I'm not sure how to diagnose this issue as RSYNC has always just worked. Is it related to the other errors recently reported?

[F8BOE]

Hello,

I'm still using 10.2.0.2.2535 x86_32. RSYNC runs OK as Local service (no RSYNC server).
But what happened to 2535? I only see 2433 in the file folder!!! What was wrong with 2535 to dump it from the server?
An error I suppose...

As I read the changelog for the 2545 revision I came across an interresting thing: RSYNC was upgraded to ver. 3.1.2... But it is the same text in the 2433 revision changelog: Upgrade rsync to 3.1.2. so what is the real use of sluggish changelogs? I can also do copy-paste to fill up empty spaces!

And now which info can you trust?

Ciao @+

[BraM]

RSYNC was upgraded to ver. 3.1.2

I've checked and RSYNC was upgraded to 3.1.2 in build 10.2.0.2.2332 which was released in late February. I'm still trying to ascertain if RSYNC is broken since then or is merely broken on my two servers. It does seem to me that there are a few posts popping up with RSYNC errors in the latest builds. In my experience RSYNC has worked flawlessly as far back as the fork from FreeNAS.

I guess that I could revert to 10.2.0.2.2268 and test. That will perhaps give us a potential difference between the current and previous RSYNC versions.

[BraM]

I'm getting the same error as above with RSYNC 3.1.1

Code: Select all

rsync: read error: Operation timed out (60)
rsync error: error in socket IO (code 10) at io.c(785) [sender=3.1.1]

I'm still not sure how to track this error down.

[F8BOE]

Hello,

I made the upgrade to 2535 yesterday and this morning I had a normal local rsync log. The folders I sync were synced (MGA5 and MGA cauldron).
So RSYNC in client mode still works... It could be a faulty RSYNC server configuration or a thing like this:

"Fix run now on cron don't use Who field."

Whatever it means... Typo or broken english problems.
But this fix can be followed since 2407... And this is not really informative because of the copy-paste politics ending up with misleading changelogs!

On my systems the RSYNC is run as root to avoid problems with user rights.

Ciao @+

[BraM]

I still have no idea why RSYNC is failing. I have since gone over to syncthing which works fine but is agonisingly slow.

On my systems the RSYNC is run as root to avoid problems with user rights.

But the GUI only has the option to map to guest user. Are you saying that you run the service via CLI? I've never used that option myself but would consider looking into it. Especially if it helps overcome the current error.

[F8BOE]

Hello,

No, it's the default when you configure a new RSYNC action, the task is set to be done with the root privileges.

[attachment=0]RSYNCclient.jpg[/attachment]

The little problem is that the files on the server can only be modified with the root privileges, but in my case it's not really an matter as these files are OS update files.

Ciao @+

[ijeffsc]

Juggler & BraM,

Could you provide a bit more detail?

add a -v to your rsync options to get additional output in the rsync log files.
Share your configuration - look in /conf/config.xml for the rsync configuration info.
Look in /var/run for the rsync script you are running and try running it on the command line while logged in as the user.

Read my posts for bugs 283 and 284 as examples of detail that would be helpful including the xml configuration info.

IJ

[BraM]

As stated above I switched to syncthing, which worked fine but was slow.

Yesterday I gave rsync another try and the damn thing worked without any errors. Nothing in my setup was different other than enabling/disabling syncthing. Very frustrating that rsync dropped out and came back all of its own like that. But it is working fine now.