NAS540: When backup [rsync] error starting client-server protocol
Verfasst: Sa 16. Mai 2020, 13:41
I have a daily rsync job that mirrors all data from NAS1 to NAS2. This worked for years. For a few days, I see these messages in my log file:
At first I thought it would work the next day again, so I waited for that. Same result. Then I started the job manually but it failed as well. I searched for more detailed information in the web interface, but there is only the response of the rsync job in the task planner and the same message in the maintenance protocol. Not helpful.
I logged in to SSH and did not find much either. There is no entry in the crontab at the scheduled time of the day which I expected. I searcheed for /var/log/messages but that file does not exist. Where do I need to look for? I did not find any log file for the rsync jobs or files for the raw configuration that is written when the job is created in the web UI.
As the web interface is lacking all edit and almost all view methods to inspect the job that worked for years, I disabled that one and set up a new one. It took twelf hours to copy files from NAS1 to NAS2 and finished with a 'successful' message. I checked the files: NAS2 had ca. 80% of data before setting up the new job, now it has about 85% of the data received from NAS1. There are files that exist with the same date stamp and protection bits in source and target but the file size differs a lot, e.g. 127GB on NAS1 but only 9GB on NAS2. This is definitely not what rsync can call 'successful'.
Where can I find log files on the rsync job that might tell me why the old job stopped working and the new one did synchronize only 90% of the data?
Code: Alles auswählen
When backup [rsync] error starting client-server protocol
I logged in to SSH and did not find much either. There is no entry in the crontab at the scheduled time of the day which I expected. I searcheed for /var/log/messages but that file does not exist. Where do I need to look for? I did not find any log file for the rsync jobs or files for the raw configuration that is written when the job is created in the web UI.
As the web interface is lacking all edit and almost all view methods to inspect the job that worked for years, I disabled that one and set up a new one. It took twelf hours to copy files from NAS1 to NAS2 and finished with a 'successful' message. I checked the files: NAS2 had ca. 80% of data before setting up the new job, now it has about 85% of the data received from NAS1. There are files that exist with the same date stamp and protection bits in source and target but the file size differs a lot, e.g. 127GB on NAS1 but only 9GB on NAS2. This is definitely not what rsync can call 'successful'.
Where can I find log files on the rsync job that might tell me why the old job stopped working and the new one did synchronize only 90% of the data?