Rsync replication error

[NocturnalFilth]

I am still having this issue with 3.7.3 Build 20120801 (412 and 459). Is it planned for later releases or should it already have been fixed?

[onlyalex]

Most likely next fw release or soon. I sure hope qnap fix it soon.

[Briain]

Hi

I have three Qnaps on 3.7.3:

TS-659 Pro -> TS-219P+ worked okay
TS-659 Pro -> TS-119P+ brought the error up 14 hours into a 16 hours backup job (same backup that worked with the above) and I spotted it several hours into attempt 2 (so I stopped it, wiped the destination and have just created a new job to try it again). In both cases, the rsync was a manually started job and the destination NAS's were completely empty. I've added a post to the other thread (here) and, like the others, I do hope there will be a reasonably swift patch to fix this.

Bri

[oetzy]

Same Problem here ... 3.7.3 Build 20120801

[Remote Replication] XXXXX failed: rsync: Can't remove the inotify watch of "/etc/config/rsync_schedule.conf" 5467 error! (-22)#012: Invalid argument (22). Begin 1st retry.

hope Problem is fixed with next Update !

[uutelst]

Same problem here with 578 error and unsuccessful backups to a rsync server (Synology DS710+).
When will Qnap resolve this problem?
I cannot leave my phone on at night (I subscribed to the AED alert) so I have to disable the sms warnings......

[doktornotor]

Same problem here with 578 error and unsuccessful backups to a rsync server (Synology DS710+).
When will Qnap resolve this problem?

Probably not anytime soon since this appears to be a bug in the QNAP's over two years kernel. The "fix" is to hide the error so that you do not get spammed.

[big_marcelo]

I have the same problem..... 1079 backing into a 669.....

I can't downgrade to 3.6.1 since that FW has timemachine issues.... oh well ... waiting for the next release.....

the funny thing is that there were no issues until a few weeks ago .....

does anyone know when 3.8 will coming out?

[doktornotor]

does anyone know when 3.8 will coming out?

The beta is already out. (No, I do not think it fixes anything, you can download, install and try.)

Should make clear that the rsync backup actually works, you can compare the files in case you think it does not.

[big_marcelo]

does anyone know when 3.8 will coming out?

The beta is already out. (No, I do not think it fixes anything, you can download, install and try.)

Should make clear that the rsync backup actually works, you can compare the files in case you think it does not.

are you saying that the backup actually works, but the error logs are showing for no reason? just need to clarify ...

I may rollback to 3.7.2 if that fixes it..

thanks,

[doktornotor]

are you saying that the backup actually works, but the error logs are showing for no reason? just need to clarify ...

Yes - at least if you are talking about the inotify error. Already explained above.

[doktornotor]

confirmed by Qnap RD and will be fixed for next fw release.

Which firmware is "next", dear QNAP? Nothing fixed here.

[pedro77]

I'm getting the same error since upgrading to 3.8.0 on a 659 Pro+:

[Remote Replication] Photos failed: rsync: Can't add an inotify watch of "/etc/config/rsync_schedule.conf" error! (28): No space left on device (28). Begin 1st retry.

All the RSYNC jobs had been working fine for me before on 3.7.3 and previous firmwares. Should I downgrade or will a fix be soon?

[pwilson]

The error message

Can't remove the inotify watch of "/etc/config/rsync_schedule.conf

is confirmed by Qnap RD and will be fixed for next fw release.

viewtopic.php?f=142&t=60645
Cheers.

See: QNAPJason's article: Re: [3.8.0 1012] Not Acceptable Beta written on: Sun Oct 21, 2012 4:52 pm:

After some internal meetings, we have decided to put R&D resources and spend some months to update the libraries and patches (and of course the OpenSSL version) during these months.
We agree to make the base more secure and reliable.
Please give us some time for the updates.

[Rinkel80]

After the upgrade to 3.8 the same problem. It worked for years between my two qnaps.

[Rinkel80]

After the upgrade to 3.8 the same problem. It worked for years between my two qnaps.