OK, so a bit of an update, and this may ultimately be a RSYNC issue, or perhaps a samba client problem...?
Last night the machine died...TWICE...lol, within 10 mins of each reboot. As it happened my cron schedule has multiple RSYNC jobs scheduled (they do NOT run in parallel though) and the 1st reboot happened in the middle of the 1st RSYNC, and the 2nd during the next scheduled run (different SOURCE & TARGET locations though, but both copying from a LOCAL directory to the NAS box - which is accessed through a NetDrive samba share).
So seeing as I had just about touched on all the other things I could possibly think of, I decided to run the same RSYNC job manually (as in not scheduled).
The RSYNC CLI is this:
RSYNC --archive --delete --progress --stats --whole-file --no-xattrs --human-readable --quiet --exclude-from=G:\mptn\etc\rsync_exclude --log-file=G:\tmp\log\rsync_REMOTE_backup.log G:/DESKTOP/Automotive V:/public/documents
...but having kicked off this very run manually after much much longer than it normally runs I eventually killed it with CTRL-C in the CLI window, which produced the following error message:
...
2025/05/06 13:57:20 [126] rsync: writefd_unbuffered failed to write 4 bytes to socket [sender]: Broken pipe (32)
2025/05/06 13:57:20 [126] rsync: connection unexpectedly closed (78453 bytes received so far) [sender]
2025/05/06 13:57:20 [126] rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9.1]
...
Soooo...I'm going to retry this again, but quite honestly I'm at a complete loss as to what's going on here.
This example here normally runs for all of two minutes...yup, that's all. Meanwhile today's run was 4 hrs. long and I suspect there was some kind of networking hangup that was encountered given that last error message.
This CTRL-C kill did not generate a process dump, which I think is the correct outcome.
EDIT #1
======One more thing: take a look at the attached Theseus screenshot...RSYNC actually seems to create THREE processes, of which two have 2 threads, and the last one has a single thread...is that normal???
EDIT #2
======...and yet the very next run of RSYNC, albeit with a different SOURCE & TARGET combo, completes just fine!!!
WHAT DA?
