worker signal mask inherited by children
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
udev (Ubuntu) |
Fix Released
|
High
|
Kees Cook | ||
Karmic |
Fix Released
|
High
|
Kees Cook |
Bug Description
Binary package hint: openssh-server
Hi, since upgrading to karmic on one machine I get a strange behavior of sshd:
- After exitting an SSH-session, the terminal on the client machine hangs instead of closing
- On the server there is a "sshd <defunct>" after each such session (this is especially annoying since I have a nagios server checking the SSH status every few minutes, so the number of zombie processes rapidly increases)
- Additionally, I noticed that "Ctrl-C" does not work inside the SSH session, which is a bash shortcut that I use very often ;-) (should start a new empty command line ignoring what you've entered so far)
Restarting sshd takes exceptionally long, but at least kills all the zombies.
When I'm working on a terminal directly at the machine (i.e. not over SSH), the behavior is totally normal, so I consider this an ssh (or at least ssh-related) bug.
summary: |
- sshd zombie processes and strange behavior after karmic upgrade + worker signal mask inherited by children |
Changed in udev (Ubuntu Karmic): | |
assignee: | nobody → Scott James Remnant (scott) |
Changed in udev (Ubuntu Karmic): | |
assignee: | Scott James Remnant (scott) → Kees Cook (kees) |
Hi Michael,
On Fri, Jul 31, 2009 at 05:24:34PM -0000, Michael Helmling wrote:
> Public bug reported:
>
> Binary package hint: openssh-server
>
> Hi, since upgrading to karmic on one machine I get a strange behavior of
> sshd:
>
> - After exitting an SSH-session, the terminal on the client machine hangs instead of closing
> - On the server there is a "sshd <defunct>" after each such session (this is especially annoying since I have a nagios server checking the SSH status every few minutes, so the number of zombie processes rapidly increases)
> - Additionally, I noticed that "Ctrl-C" does not work inside the SSH session, which is a bash shortcut that I use very often ;-) (should start a new empty command line ignoring what you've entered so far)
>
>
> Restarting sshd takes exceptionally long, but at least kills all the zombies.
> When I'm working on a terminal directly at the machine (i.e. not over SSH), the behavior is totally normal, so I consider this an ssh (or at least ssh-related) bug.
>
I've seen a similar behavior when I clone virtual machines. Rebooting
the virtual instance fixes all of the issue though.
Is your system a virtual machine or a physical machine? What happens if
you reboot the system? How is the system installed (from an iso, the
network)?
status incomplete
-- www.ubuntu. com
Mathias Gug
Ubuntu Developer http://