Re: Unkillable zombie sshd-s?
Ronald Klop wrote: On Thu, 02 Dec 2004 15:06:21 +0100, Ivan Voras <[EMAIL PROTECTED]> wrote: Can I find out what their parent processes are? (something like tree-shaped ps?) /usr/ports/sysutils/pstree and ps can display the ppid (parent pid). Thanks, parents were stuck and had to be killed. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Unkillable zombie sshd-s?
On Thu, 2 Dec 2004, Ivan Voras wrote: Mark Andrews wrote: Is there a way to find out what has happened and why does the situation occur? (I can't reboot the server for testing) You can't kill them because they are already dead. They are just holding state so that the parent process can know how they died. Once the parent process wait()'s on them (or the parent dies) they will disappear. I knew that (except the bit that they're ukillable by design :) ), but I was hoping it's a known ssh problem - this is the first time I saw sshd processes as zombies (and it seems they've been zombies for a long time, so parents are probably in error). Can I find out what their parent processes are? (something like tree-shaped ps?) No tree, but try ps -axl. PPID = parent process ID -- Lars Eighner [EMAIL PROTECTED] -finger for geek code- http://www.io.com/~eighner/index.html 8800 N IH35 APT 1191 AUSTIN TX 78753-5266 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Unkillable zombie sshd-s?
On Thu, 02 Dec 2004 15:06:21 +0100, Ivan Voras <[EMAIL PROTECTED]> wrote: Can I find out what their parent processes are? (something like tree-shaped ps?) /usr/ports/sysutils/pstree and ps can display the ppid (parent pid). -- Ronald Klop, Amsterdam, The Netherlands ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Unkillable zombie sshd-s?
Mark Andrews wrote: Is there a way to find out what has happened and why does the situation occur? (I can't reboot the server for testing) You can't kill them because they are already dead. They are just holding state so that the parent process can know how they died. Once the parent process wait()'s on them (or the parent dies) they will disappear. I knew that (except the bit that they're ukillable by design :) ), but I was hoping it's a known ssh problem - this is the first time I saw sshd processes as zombies (and it seems they've been zombies for a long time, so parents are probably in error). Can I find out what their parent processes are? (something like tree-shaped ps?) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Unkillable zombie sshd-s?
> I found out today that I have two zombie sshd processes on a busy server > (dozen or so users over ssh, many other services), and I can't kill them. > > sshd38653 0.0 0.0 00 ?? ZMon08AM 0:00.03 > sshd75851 0.0 0.0 00 ?? Z 7:33PM 0:00.08 > > kill -9 doesn't complain, but doesn't do the job either. > > Is there a way to find out what has happened and why does the situation > occur? (I can't reboot the server for testing) You can't kill them because they are already dead. They are just holding state so that the parent process can know how they died. Once the parent process wait()'s on them (or the parent dies) they will disappear. This is a FAQ that is over 20 years old. Mark -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Unkillable zombie sshd-s?
I found out today that I have two zombie sshd processes on a busy server (dozen or so users over ssh, many other services), and I can't kill them. sshd38653 0.0 0.0 00 ?? ZMon08AM 0:00.03 sshd75851 0.0 0.0 00 ?? Z 7:33PM 0:00.08 kill -9 doesn't complain, but doesn't do the job either. Is there a way to find out what has happened and why does the situation occur? (I can't reboot the server for testing) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
