What could cause rsync to kill ssh?

Maurice R Volaski maurice.volaski at einsteinmed.edu
Sat Jun 3 05:05:07 UTC 2023


Rsync 3.2.7 is running on the Gentoo computer, which doesn't have a version, other than it's "current". I'm running the script from this computer.

Rsync 3.1.2 is on the source computer, where the files come from, which is Ubuntu 18.0.4.6.

I'm copying to a CIFS share mounted on the Gentoo computer.

The rsync scripts are all similar to this one:

/usr/bin/rsync -v -a --progress --exclude-from=${exclude} --safe-links --itemize-changes --no-perms --no-owner --progress --stats \
alexa at labadmin-precision-tower-3620.montefiore.org:/home/alexa/ /mnt/data.einstein/luke/all_but_dat/alexa/desktop_bkup/profile \
>> /home/maurice/logs/rsync-client-alexa.log

I re-ran the scripts skipping this one. The next one was running and during that period, ssh stopped responded to new connections, so it may be the case that the failure is taking place across time, and it doesn't fail wholesale immediately.

However, I have other scripts like these copying from other sources (not Ubuntu) and they are not causing these failures. 


On 6/3/23, 12:40 AM, "Perry Hutchison" <pluto at agora.rdrop.com <mailto:pluto at agora.rdrop.com> <mailto:pluto at agora.rdrop.com <mailto:pluto at agora.rdrop.com>>> wrote:




CAUTION: This email comes from an external source; the attachments and/or links may compromise our secure environment. Do not open or click on suspicious emails. Please click on the “Phish Alert” button on the top right of the Outlook dashboard to report any suspicious emails.




Maurice R Volaski via rsync <maurice.volaski at lists.samba.org <mailto:maurice.volaski at lists.samba.org> <mailto:maurice.volaski at lists.samba.org <mailto:maurice.volaski at lists.samba.org>>> wrote:




> I have an rsync script that it is copying one computer (over ssh)
> to a shared CIFS mount on Gentoo Linux, kernel 6.3.4. The script
> runs for a while and then at some point quits knocking my ssh
> session offline on all terminals and it blocks ssh from being able
> to connect again. Even restarting sshd doesn't help. Rsync has
> apparently killed it. I have to reboot.




For starters:




What OS and version is the rsync script running on?




Which end do you have to reboot? The machine running the script,
or the Gentoo Linux?




What versions of rsync are running on each end?




Can you show the command line that fails?




Based on the mention of multiple terminals, it sounds as if you
have a fairly complex ssh environment. Can you get it to fail in
a simpler environment, ideally with only one terminal?











More information about the rsync mailing list