Beruflich Dokumente
Kultur Dokumente
I took a look at the rsyncd.log on WDMyCloud and the only errors I'm seeing are:
[code]2016/01/10 03:20:20 [25708] rsync: link_stat "/MyDocuments/@app/SYNOLOGYNA
S_20160109.dss" (in SynologyNAS) failed: No such file or directory (2)
2016/01/10 03:20:27 [25725] rsync: link_stat "/MyDocuments/MyDocuments/Important
/_Syno_BkpMetadata.db" (in SynologyNAS) failed: No such file or directory (2)[/c
ode]
There are no rsync/rsyncd errors in /var/log/messages on WDMyCloud.
When it fails, the rsync daemon is still running on WDMyCloud.
When it fails, restarting rsyncd on WDMyCloud, and starting the task again, does
n't help.
The destination disk on WDMyCloud has penty of space (over 3TB); tha data I'm co
pying is less than 1TB
The WDMyCloud and Synology are on the same switch.
No special setup (no VLANS, no DMZ, no port mirroring, not routing through some
intermediary IDS/IPS system etc.)
Because other data backup tasks are completing successfully, and the rsyncd.log
is getting written to, I do not believe this to be an issue with the rsyncd.conf
on WDMyCloud.
To me, the obvious troubleshooting step would be to run the rsync command on Syn
ology with -vvv leaving everything else the same. However, because of the way S
ynology has things setup, it makes it harder to troubleshoot in my humble opinio
n:
[list][*]Because I setup a schedule, I assumed it was a cron job so I cat'd /etc
/crontab
[*]I found my job based on the schedule
2016/01/10 03:20:23 [25719] sent 87 bytes received 138 bytes total size 0
2016/01/09 22:20:23 [25721] connect from synologynas.f.q.d.n (10.0.1.5)
2016/01/10 03:20:23 [25721] rsync on SynologyNAS/MyDocuments/@app/_Syno_NetShare
Archive.db from SynologyNAS@synologynas.f.q.d.n (10.0.1.5)
2016/01/10 03:20:23 [25721] building file list
2016/01/10 03:20:23 [25721] sent 128 bytes received 87 bytes total size 2048
2016/01/09 22:20:23 [25722] connect from synologynas.f.q.d.n (10.0.1.5)
2016/01/10 03:20:23 [25722] rsync on SynologyNAS/MyDocuments/@app/_Syno_NetShare
Archive.db from SynologyNAS@synologynas.f.q.d.n (10.0.1.5)
2016/01/10 03:20:23 [25722] building file list
2016/01/10 03:20:23 [25722] sent 2219 bytes received 106 bytes total size 2048
2016/01/09 22:20:24 [25723] connect from synologynas.f.q.d.n (10.0.1.5)
2016/01/10 03:20:24 [25723] rsync to SynologyNAS/MyDocuments/MyDocuments/ from S
ynologyNAS@synologynas.f.q.d.n (10.0.1.5)
2016/01/10 03:20:24 [25723] receiving file list
2016/01/10 03:20:24 [25723] Important/
2016/01/10 03:20:27 [25723] sent 1589 bytes received 277673 bytes total size 7
925302415
2016/01/09 22:20:27 [25725] connect from synologynas.f.q.d.n (10.0.1.5)
2016/01/10 03:20:27 [25725] rsync on SynologyNAS/MyDocuments/MyDocuments/Importa
nt/_Syno_BkpMetadata.db from SynologyNAS@synologynas.f.q.d.n (10.0.1.5)
2016/01/10 03:20:27 [25725] building file list
2016/01/10 03:20:27 [25725] rsync: link_stat "/MyDocuments/MyDocuments/Important
/_Syno_BkpMetadata.db" (in SynologyNAS) failed: No such file or directory (2)
2016/01/09 22:20:27 [25726] connect from synologynas.f.q.d.n (10.0.1.5)
2016/01/10 03:20:27 [25726] rsync on SynologyNAS/MyDocuments/@app/@metadata/MyDo
cuments/Important/_Syno_BkpMetadata.db from SynologyNAS@synologynas.f.q.d.n (10.
0.1.5)
2016/01/10 03:20:27 [25726] building file list
2016/01/10 03:20:27 [25726] sent 124 bytes received 87 bytes total size 3072
2016/01/09 22:20:28 [25727] connect from synologynas.f.q.d.n (10.0.1.5)
2016/01/10 03:20:28 [25727] rsync on SynologyNAS/MyDocuments/@app/@metadata/MyDo
cuments/Important/ from SynologyNAS@synologynas.f.q.d.n (10.0.1.5)
2016/01/10 03:20:28 [25727] building file list
2016/01/09 22:20:47 [25747] connect from synologynas.f.q.d.n (10.0.1.5)
2016/01/10 03:20:47 [25747] rsync to SynologyNAS/MyDocuments/synobkpinfo.db from
SynologyNAS@synologynas.f.q.d.n (10.0.1.5)
2016/01/10 03:20:47 [25747] receiving file list
2016/01/10 03:20:47 [25747] sent 95 bytes received 3209 bytes total size 3072[
/code]