On 02/06/2020 14:31, Adrian wrote:
> In message , A. Dumas
>  writes
>> Adrian  wrote:
>>> In message , A. Dumas
>>>  writes
>>>> I didn't read that :) but my guess would certainly be that it has
>>>> nothing
>>>> to do with rsync and everything with a lost connection/route. Maybe
>>>> a flaky
>>>> ethernet cable or jack? It could happen. Try & set up a ping log
>>>> from both
>>>> to both and to the router.
>>>>
>>>
>>> I've already got a ping log [...]
>>
>> Ah right, bummer that that's not it.
>>
>
> Indeed.
>
> And what I forgot to mention is that those other Pis are running a copy
> of the rsync script (same target machine, different file locations)
> without problem, and my source machine does a daily "pull" rsync from
> the target which is much bigger, and that always works.
>
So its machine specific. I still think it's hardware.

I've seen effects like this where the combination of  the right I/O and
using in the next instruction a piece of slow ram can do this.

I'd be inclined to ditch that Pi
> Adrian


--
"When one man dies it's a tragedy. When thousands die it's statistics."

Josef Stalin

--- SoupGate-Win32 v1.05