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.

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

--
https://www.greenend.org.uk/rjk/

--- SoupGate-Win32 v1.05