Can't kill rsync

[Jogie214]

Hello!

I have 10 rsync processes, and I can't kill anyone of it, I tried kill -9, -15 (to be honest I tried every signal form -1 to -15), is there anything else I can do? I know, I can reboot, but then all my friends who tell me ubuntu is more stable would be right, and I don't like that idea.... .

Thanks
Seb

[iphands]

what about killall

Code: Select all

killall -9 rsync

should kill all processes with that name...

Why 9? If you don't mind my asking.

[Jogie214]

Hi!

Sorry, I forgot to mention it, that I also tried killall and kill .. $(pidof rsync).
To be honest I'm not able to explain why -9, I always used -9 or -15....
BTW, the rsync processes still occupy memory, they are no zombie processes.

Seb

[Hu]

Please post the output of ps auxwwwww | grep rsync and for a in $(pgrep rsync); do /usr/sbin/lsof -p $a; done. ps is part of sys-process/procps; lsof is from sys-process/lsof. I suspect the rsync is in a device wait state, since that is the only way to survive a SIGKILL. Note that -9 is short for -KILL, which sends SIGKILL, a non-blockable fatal signal. Processes which receive a SIGKILL are immediately terminated and cannot execute any cleanup code. However, if a process is in a device wait state, the kernel may defer handling the kill until the device wait is completed.

[iphands]

Hi!

Sorry, I forgot to mention it, that I also tried killall and kill .. $(pidof rsync).
To be honest I'm not able to explain why -9, I always used -9 or -15....
BTW, the rsync processes still occupy memory, they are no zombie processes.

Seb

Weird...
Oh no -9 is kill (really kill) without waiting for the process to close up or do any clean up. Its kinda like pulling the power on a process.
I meant why 10 (the number of rsync processes) how did they get there. I am at a loss as to why they aren't getting killed properly.

[Captain Newbie]

Hi!

Sorry, I forgot to mention it, that I also tried killall and kill .. $(pidof rsync).
To be honest I'm not able to explain why -9, I always used -9 or -15....
BTW, the rsync processes still occupy memory, they are no zombie processes.

Seb

Weird...
Oh no -9 is kill (really kill) without waiting for the process to close up or do any clean up. Its kinda like pulling the power on a process.
I meant why 10 (the number of rsync processes) how did they get there. I am at a loss as to why they aren't getting killed properly.

KILL's not supposed to be caught or ignored like that (obviously)...let's see that output Hu asked for.

[Jogie214]

Thanks everybody!

But I had to reboot in the mean time, because I needed to emerge iverilog (I need it for my diploma work), and I wasn't able to emerge anything, apparently my portage got corrupted (only God knows how), I wasn't even able to delete or move portage until I rebooted, know I'm able to sync again...
Checkfs hasn't found any errors on /usr/portage/ during the reboot, so some of the portage files must have been looked.
BTW, I erased my whole /usr/portage (previously xfs) and use ext4dev from now one, ext4 is much faster with this huge number of small files.

Thanks again
Seb

P.S.: Sorry for my bad english

[Stephen_Cataldo]

I had processes like these, with rsync running over ssh:
m2tech 25467 0.4 -0.2 29876 3156 ?? S Sat12AM 19:30.32 ssh -l svpadmin example.org rsync --server ...
m2tech 524 0.4 -0.1 29544 1756 ?? S Wed12AM 51:46.28 rsync -verbose -iavHz --progress --numeric-ids -e ssh ...

killall -9 rsync
did NOT work for me, but this did:
killall -9 ssh