** Also affects: udev (Ubuntu Karmic)
Importance: High
Status: Confirmed
--
sshd zombie processes and strange behavior after karmic upgrade
https://bugs.launchpad.net/bugs/407428
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Patch is now in udev:
http://git.kernel.org/?p=linux/hotplug/udev.git;a=commitdiff;h=d412a685736e3b3350b555f4d7d8ebfc80aa54c9
--
sshd zombie processes and strange behavior after karmic upgrade
https://bugs.launchpad.net/bugs/407428
You received this bug notification because you are a member of
Looks like this patch has been accepted to udev:
http://www.spinics.net/lists/hotplug/msg02675.html
The udev.git tree doesn't look like it has been updated though, I assume
Kay hasn't pushed recent changes yet.
--
sshd zombie processes and strange behavior after karmic upgrade
The attached patch fixes the problem for me. From the patch comments:
External programs triggered by events (via RUN=) will inherit udev's
signal mask, which is set to block all but SIGALRM. For most utilities,
this is OK, but if we start daemons from RUN=, we run into trouble
(especially as
I can also confirm this problem. As can I confirm that /etc/init.d/ssh
restart is a valid (but time consuming and probably proportional in
time to number of processes) workaround. When I noticed this problem
(after about 15 hours of uptime), there were something in the region of
3000 defunct ssh
I am also experiencing this problem, and found that some other processes have
this strange signal mask.
udevd and dhclient3.
They are not descendants of sshd.
So I guess the culprit is not sshd but somewhere in the system startup scripts.
** Attachment added: Output from ps axsf
The culprit is udev.
udev runs ifup when it founds eth0, then ifup starts dhclient3 and restarts
sshd!
Temporary fix to this:
- Remove auto eth0 from /etc/network/interfaces
- Add /sbin/ifup eth0 to /etc/rc.local (before exit 0, of course)
Now only udev has the strange signal mask on my
Wow, yes, excellent catch. udevd.c:worker_new() blocks a load of signals
and nothing puts them back.
Bug tennis :-)
** Package changed: openssh (Ubuntu) = udev (Ubuntu)
** Changed in: udev (Ubuntu)
Milestone: karmic-alpha-5 = karmic-alpha-6
--
sshd zombie processes and strange behavior
I can also confirm this problem. As can I confirm that /etc/init.d/ssh
restart is a valid (but time consuming and probably proportional in
time to number of processes) workaround. When I noticed this problem
(after about 15 hours of uptime), there were something in the region of
3000 defunct ssh
I am also experiencing this problem, and found that some other processes have
this strange signal mask.
udevd and dhclient3.
They are not descendants of sshd.
So I guess the culprit is not sshd but somewhere in the system startup scripts.
** Attachment added: Output from ps axsf
The culprit is udev.
udev runs ifup when it founds eth0, then ifup starts dhclient3 and restarts
sshd!
Temporary fix to this:
- Remove auto eth0 from /etc/network/interfaces
- Add /sbin/ifup eth0 to /etc/rc.local (before exit 0, of course)
Now only udev has the strange signal mask on my
Wow, yes, excellent catch. udevd.c:worker_new() blocks a load of signals
and nothing puts them back.
Bug tennis :-)
** Package changed: openssh (Ubuntu) = udev (Ubuntu)
** Changed in: udev (Ubuntu)
Milestone: karmic-alpha-5 = karmic-alpha-6
--
sshd zombie processes and strange behavior
are the Ctrl-C and screen issues listed as separate bugs or is it really
the same problem?
--
sshd zombie processes and strange behavior after karmic upgrade
https://bugs.launchpad.net/bugs/407428
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Hi Michael
Please paste the result of cat /proc/`pidof sshd | awk '{print
$1}'`/status | grep SigBlk. If the problem is not caused by sigmask.
The workaround can't work. :)
--
sshd zombie processes and strange behavior after karmic upgrade
https://bugs.launchpad.net/bugs/407428
You received
are the Ctrl-C and screen issues listed as separate bugs or is it really
the same problem?
--
sshd zombie processes and strange behavior after karmic upgrade
https://bugs.launchpad.net/bugs/407428
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hi Michael
Please paste the result of cat /proc/`pidof sshd | awk '{print
$1}'`/status | grep SigBlk. If the problem is not caused by sigmask.
The workaround can't work. :)
--
sshd zombie processes and strange behavior after karmic upgrade
https://bugs.launchpad.net/bugs/407428
You received
Hi Brett.
I forgot to mention that:
You need to logout from current console. Then login your machine.
Sorry for that.
--
sshd zombie processes and strange behavior after karmic upgrade
https://bugs.launchpad.net/bugs/407428
You received this bug notification because you are a member of Ubuntu
I have no success, too.
# ./sigwrapper /etc/init.d/ssh restart
father return;
r...@menk:~# * Restarting OpenBSD Secure Shell server sshd
r...@menk:~#
On another ssh session started thereafter, still no Ctrl-C.
--
sshd zombie processes and strange behavior after karmic upgrade
hehe, no probs Wisefox. I tried a new session and ctrl+c does appear to
work as expected now.
Bravo!
--
sshd zombie processes and strange behavior after karmic upgrade
https://bugs.launchpad.net/bugs/407428
You received this bug notification because you are a member of Ubuntu
Server Team, which
I have no success, too.
# ./sigwrapper /etc/init.d/ssh restart
father return;
r...@menk:~# * Restarting OpenBSD Secure Shell server sshd
r...@menk:~#
On another ssh session started thereafter, still no Ctrl-C.
--
sshd zombie processes and strange behavior after karmic upgrade
hehe, no probs Wisefox. I tried a new session and ctrl+c does appear to
work as expected now.
Bravo!
--
sshd zombie processes and strange behavior after karmic upgrade
https://bugs.launchpad.net/bugs/407428
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hi Brett.
I forgot to mention that:
You need to logout from current console. Then login your machine.
Sorry for that.
--
sshd zombie processes and strange behavior after karmic upgrade
https://bugs.launchpad.net/bugs/407428
You received this bug notification because you are a member of Ubuntu
I confirm this bug
--
sshd zombie processes and strange behavior after karmic upgrade
https://bugs.launchpad.net/bugs/407428
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in ubuntu.
--
Ubuntu-server-bugs mailing list
Well. Provide a piece of code as a workaround. compile the following C code:
#include signal.h
int main( int argc, char ** argv )
{
sigset_t oldset, newset;
sigfillset( newset );
sigprocmask( SIG_UNBLOCK, newset, oldset );
int pid =
OK, I did that. Apart from a warning regarding printf it went OK but it
did not make a difference to the ctrl+c problem
Console output is below;
bre...@jupiter:~$ gcc -o sigwapper sshfix.c
sshfix.c: In function ‘main’:
sshfix.c:17: warning: incompatible implicit declaration of built-in function
I confirm this bug
--
sshd zombie processes and strange behavior after karmic upgrade
https://bugs.launchpad.net/bugs/407428
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Well. Provide a piece of code as a workaround. compile the following C code:
#include signal.h
int main( int argc, char ** argv )
{
sigset_t oldset, newset;
sigfillset( newset );
sigprocmask( SIG_UNBLOCK, newset, oldset );
int pid =
OK, I did that. Apart from a warning regarding printf it went OK but it
did not make a difference to the ctrl+c problem
Console output is below;
bre...@jupiter:~$ gcc -o sigwapper sshfix.c
sshfix.c: In function ‘main’:
sshfix.c:17: warning: incompatible implicit declaration of built-in function
Seems latest update fix the problem. But now, I get ext4 and shutdown
problem.
--
sshd zombie processes and strange behavior after karmic upgrade
https://bugs.launchpad.net/bugs/407428
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Actually ... few reboots later the problem is back. :-(
--
sshd zombie processes and strange behavior after karmic upgrade
https://bugs.launchpad.net/bugs/407428
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in ubuntu.
--
Might any of you have restarted sshd from within a su session? I don't
have definite proof that it's related, but I note that the quoted
blocked signal mask corresponds exactly to those signals that su blocks.
I wonder if it's due to some PAM session module ...
--
sshd zombie processes and
Seems latest update fix the problem. But now, I get ext4 and shutdown
problem.
--
sshd zombie processes and strange behavior after karmic upgrade
https://bugs.launchpad.net/bugs/407428
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Same here. CTRL-C handling on SSH works again, I don't see zombies, but
poweroff hangs at checking for unattended upgrades .. * asking all remaining
processes to terminate . No CTRL-ALT-DEL or anything else helps in this state,
only hard resetting. And there are more mysterious things going on
Actually ... few reboots later the problem is back. :-(
--
sshd zombie processes and strange behavior after karmic upgrade
https://bugs.launchpad.net/bugs/407428
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Might any of you have restarted sshd from within a su session? I don't
have definite proof that it's related, but I note that the quoted
blocked signal mask corresponds exactly to those signals that su blocks.
I wonder if it's due to some PAM session module ...
--
sshd zombie processes and
how is it possible to set the SigBlk-mask?
That would be a workaround, or?
--
sshd zombie processes and strange behavior after karmic upgrade
https://bugs.launchpad.net/bugs/407428
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh
I can confirm this bug
--
sshd zombie processes and strange behavior after karmic upgrade
https://bugs.launchpad.net/bugs/407428
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in ubuntu.
--
Ubuntu-server-bugs mailing list
how is it possible to set the SigBlk-mask?
That would be a workaround, or?
--
sshd zombie processes and strange behavior after karmic upgrade
https://bugs.launchpad.net/bugs/407428
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I can confirm this bug
--
sshd zombie processes and strange behavior after karmic upgrade
https://bugs.launchpad.net/bugs/407428
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Don't know the developer already get the root cause or not. I can
provide some clue deeper into this issue.
When Karmic starts the ssh and other several services(udevd,dhcp etc.), it uses
a wrong Sigmask set for the program:
Check the Sigblk for sshd:
$ cat /proc/`pidof sshd| awk '{print
Don't know the developer already get the root cause or not. I can
provide some clue deeper into this issue.
When Karmic starts the ssh and other several services(udevd,dhcp etc.), it uses
a wrong Sigmask set for the program:
Check the Sigblk for sshd:
$ cat /proc/`pidof sshd| awk '{print
FWIW, I see this as well. A /etc/init.d/ssh restart does clear
everything out and ssh is ok for a while. I noticed that nagios tends to
aggravate things (/usr/lib/nagios/plugins/check_ssh -4 ip address),
but not immediately after a restart. Eg, I had 883 zombies a moment ago,
then I did restart
FWIW, I see this as well. A /etc/init.d/ssh restart does clear
everything out and ssh is ok for a while. I noticed that nagios tends to
aggravate things (/usr/lib/nagios/plugins/check_ssh -4 ip address),
but not immediately after a restart. Eg, I had 883 zombies a moment ago,
then I did restart
I am experiencing more strange behavior: When I start aptitude directly
with the ssh command, i.e. something like
ssh -t r...@machine.box aptitude -V dist-upgrade
then I always get kicked out after the packages are downloaded, or
more precise, I assume directly before dpkg is called. I only have
I am experiencing more strange behavior: When I start aptitude directly
with the ssh command, i.e. something like
ssh -t r...@machine.box aptitude -V dist-upgrade
then I always get kicked out after the packages are downloaded, or
more precise, I assume directly before dpkg is called. I only have
Finally, I find this describe the common problem
In my first trying to install karmic via network install script and update to
the latest version. I found my desktop refuse to interrupt process with Ctrl +
c in ssh. It's really hard to use because I only work with sshI was
thinking that
I have been able to reproduce this issue on my hardware. Definitely a
regression that needs attention.
** Changed in: openssh (Ubuntu)
Importance: Undecided = High
** Changed in: openssh (Ubuntu)
Milestone: None = karmic-alpha-5
--
sshd zombie processes and strange behavior after
as a workaround, when booting with kernel 2.6.28-14 logoff and Ctrl-C/Z
work normal.
--
sshd zombie processes and strange behavior after karmic upgrade
https://bugs.launchpad.net/bugs/407428
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
as a workaround, when booting with kernel 2.6.28-14 logoff and Ctrl-C/Z
work normal.
--
sshd zombie processes and strange behavior after karmic upgrade
https://bugs.launchpad.net/bugs/407428
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I don't know if those are the same type of Signals, but maybe this bug I
found is related:
https://bugs.launchpad.net/ubuntu/+bug/412972
Could the ones of you that are also affected by the zombie processes try the
kill example?
--
sshd zombie processes and strange behavior after karmic upgrade
I don't know if those are the same type of Signals, but maybe this bug I
found is related:
https://bugs.launchpad.net/ubuntu/+bug/412972
Could the ones of you that are also affected by the zombie processes try the
kill example?
--
sshd zombie processes and strange behavior after karmic upgrade
it's not bash. I use tcsh (both on the client and the server) and i'm
also impacted.
--
sshd zombie processes and strange behavior after karmic upgrade
https://bugs.launchpad.net/bugs/407428
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
i checked the diff between the jaunty and the karmic version and i can only
find 2 options:
a) colin's debian patch is making this break (using READ and WRITE respectively
instead of RW)
b) is a bug in libkrb5-3
--
sshd zombie processes and strange behavior after karmic upgrade
it's not bash. I use tcsh (both on the client and the server) and i'm
also impacted.
--
sshd zombie processes and strange behavior after karmic upgrade
https://bugs.launchpad.net/bugs/407428
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
i checked the diff between the jaunty and the karmic version and i can only
find 2 options:
a) colin's debian patch is making this break (using READ and WRITE respectively
instead of RW)
b) is a bug in libkrb5-3
--
sshd zombie processes and strange behavior after karmic upgrade
Most of my computers have been upgraded from earlier versions. The only one
showing this behaviour is my server which was initially installed with 6.06.
Issues are the same as reported:
* Ctrl-C and Ctrl-Z do not work
* login takes time
* logout hangs until I kill it with '~.'
* loads of zombie
I can confirm that one /etc/init.d/sshd restart after seems to fix the
issue with the zombie processes.
--
sshd zombie processes and strange behavior after karmic upgrade
https://bugs.launchpad.net/bugs/407428
You received this bug notification because you are a member of Ubuntu
Server Team,
Most of my computers have been upgraded from earlier versions. The only one
showing this behaviour is my server which was initially installed with 6.06.
Issues are the same as reported:
* Ctrl-C and Ctrl-Z do not work
* login takes time
* logout hangs until I kill it with '~.'
* loads of zombie
I can confirm that one /etc/init.d/sshd restart after seems to fix the
issue with the zombie processes.
--
sshd zombie processes and strange behavior after karmic upgrade
https://bugs.launchpad.net/bugs/407428
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hi Mathias,
the system is a physical one. It was installed via ISO, but with some earier
ubuntu version, and then upgraded release by release. I've already tried
'aptitude reinstall openssh-server' without success.
Rebooting doesn't solve the problem. However, it isn't totally reproducable:
On Fri, Jul 31, 2009 at 06:53:30PM -, Michael Helmling wrote:
Rebooting doesn't solve the problem. However, it isn't totally reproducable:
After the last /etc/init.d/ssh restart, I could exit ssh sessions normally
without leaving zombie processes. However, now after another reboot, the
I'm experiencing the same bug, karmic x64, tons of ssh zombies.
Happens with interactive and non-interactive shells, and with ssh tunnels.
if i restarts the main sshd, it works for a little while, then starts
leaving zombies behind.
My shell is tcsh (doesn't seem to matter though).
If i strace
Hi Mathias,
the system is a physical one. It was installed via ISO, but with some earier
ubuntu version, and then upgraded release by release. I've already tried
'aptitude reinstall openssh-server' without success.
Rebooting doesn't solve the problem. However, it isn't totally reproducable:
On Fri, Jul 31, 2009 at 06:53:30PM -, Michael Helmling wrote:
Rebooting doesn't solve the problem. However, it isn't totally reproducable:
After the last /etc/init.d/ssh restart, I could exit ssh sessions normally
without leaving zombie processes. However, now after another reboot, the
I'm experiencing the same bug, karmic x64, tons of ssh zombies.
Happens with interactive and non-interactive shells, and with ssh tunnels.
if i restarts the main sshd, it works for a little while, then starts
leaving zombies behind.
My shell is tcsh (doesn't seem to matter though).
If i strace
65 matches
Mail list logo
