In message , Richard Kettlewell
 writes
>Adrian  writes:
>> Adrian  writes
>>> Richard Kettlewell  writes
>>>>
>>>>You’ll have to find a copy of it...
>>>>
>>>
>>> That will have to wait for it to fail again (it is too far up my
>>> terminal screen for the buffer)
>>>
>>>>The apparent difference in error output is because you’re only capturing
>>>>stdout to rsync.log, not stderr. The redirection operators are in the
>>>>wrong order if that’s not what you wanted.
>>>>
>>>
>>>
>>>
>>> Now fixed.  It might throw up an error tomorrow, or it could be a
>>> few days before it happens again.
>>
>> It's happened again.
>>
>> sending incremental file list
>> etc/fake-hwclock.data
>> home/pi/.cache/lxsession/LXDE-pi/run.log
>> home/pi/stats/
>> deleting home/pi/stats/temperature_log_200530.csv
>> home/pi/stats/temperature_log_200531.csv
>> packet_write_wait: Connection to 192.168.1.118 port 22: Broken pipe
>
>packet_write_wait suggests that (from the point of view of the local SSH
>endpoint) the remote SSH endpoint terminated. So, logs on that system
>would be worth a look.
>

Looking at the target Pi, there is nothing of note in either syslog or
messages, however, auth.log has the following :

04:05:02 sshd[13415]: Nasty PTR record "192.168.1.18" is set up for
192.168.1.18, ignoring
04:05:02 sshd[13145]: Accepted publickey for root from 192.168.1.18 port
49632 ssh2
04:05:02 sshd[13145]: pam_unix(sshd:session): session opened for user
root by (uid=0)
04:06:14 sshd[13145]: Received disconnect from 192.168.1.18: 11:
disconnected by user
04:06:14 sshd[13145]: pam_unix(sshd:session): session closed for user
root

However, the script which runs the rsync then emails me the log, and the
email is timed at 04:21, so something was "hanging" for about 15
minutes, which is what usually happens when it fails.

I've just rerun the cron job (altered the scheduled time), and added a
couple of date commands to the script, one at the start, and one after
the rsync command, and I get this :

Sun 31 May 12:50:01 UTC 2020

sending incremental file list
etc/fake-hwclock.data
home/pi/.bash_history
home/pi/.cache/lxsession/LXDE-pi/run.log
home/pi/stats/temperature_log_200531.csv
root/bin/
root/bin/rsync_script.sh
packet_write_wait: Connection to 192.168.1.118 port 22: Broken pipe
rsync: connection unexpectedly closed (58154 bytes received so far)
[sender]
rsync error: unexplained error (code 255) at io.c(235) [sender=3.1.2]
Sun 31 May 13:07:00 UTC 2020

Running watch "ps -ef | grep rsync" on both source and target machines,
the source machine lost its rsync processes at 13:07, but the target
machines were still running 20 minutes later.

>What’s the basis for saying there’s a timeout involved?
>

When this first happened, I thought I saw a message mentioning a time
out, but I'm not seeing one now.

Adrian
--
To Reply :
replace "bulleid" with "adrian" - all mail to bulleid is rejected
Sorry for the rigmarole, If I want spam, I'll go to the shops
Every time someone says "I don't believe in trolls", another one dies.

--- SoupGate-Win32 v1.05