Public bug reported:
Binary package hint: upstart
Lately I have a strange thing happening on my server:
When I exit e.g. vim, some bash process eats up all cpu cycles. This looks like
the "su" process "I'm in" - likely using "screen.
It showed up as "su -" and "-su" in "ps fauxww".
I could not really find out where this process comes from or what it does
(attaching gdb did not really help, when I've tried; once the last entry was
"termsig_sighandler"):
When I killed it, or its parent, it was respawn.
Therefor it's probably from "init" or just some "su -" mechanism. In the
last case it may not really be related to the crash, mentioned below.
However, in this state I cannot reboot anymore: "reboot" sends a message to all
ttys, but then nothing happens.
On the last reboot I've tried "init 2" (just for testing) and this was the
result:
# init 2
*** glibc detected *** /sbin/init: malloc(): memory corruption (fast):
0x080b38c0 ***
======= Backtrace: =========
/lib/tls/i686/cmov/libc.so.6[0xb7e3e6fc]
/lib/tls/i686/cmov/libc.so.6(__libc_malloc+0x7e)[0xb7e3f60e]
/lib/tls/i686/cmov/libc.so.6(realloc+0x146)[0xb7e410d6]
/sbin/init[0x805145b]
/sbin/init[0x80514eb]
/sbin/init[0x8053605]
/sbin/init[0x8053866]
/sbin/init[0x8053dae]
/sbin/init[0x80532f5]
/sbin/init[0x8055813]
/sbin/init[0x804a033]
/lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xdc)[0xb7debebc]
/sbin/init[0x8049ad1]
======= Memory map: ========
08048000-0805d000 r-xp 00000000 08:03 4947969 /sbin/init
0805d000-0805e000 rwxp 00015000 08:03 4947969 /sbin/init
0805e000-080c1000 rwxp 0805e000 00:00 0 [heap]
b7c00000-b7c21000 rwxp b7c00000 00:00 0
b7c21000-b7d00000 ---p b7c21000 00:00 0
b7dc9000-b7dd4000 r-xp 00000000 08:03 1441829 /lib/libgcc_s.so.1
b7dd4000-b7dd5000 rwxp 0000a000 08:03 1441829 /lib/libgcc_s.so.1
b7dd5000-b7dd6000 rwxp b7dd5000 00:00 0
b7dd6000-b7f11000 r-xp 00000000 08:03 1983235 /lib/tls/i686/cmov/libc-2.5.so
b7f11000-b7f12000 r-xp 0013b000 08:03 1983235 /lib/tls/i686/cmov/libc-2.5.so
b7f12000-b7f14000 rwxp 0013c000 08:03 1983235 /lib/tls/i686/cmov/libc-2.5.so
b7f14000-b7f17000 rwxp b7f14000 00:00 0
b7f23000-b7f25000 rwxp b7f23000 00:00 0
b7f25000-b7f3e000 r-xp 00000000 08:03 1441816 /lib/ld-2.5.so
b7f3e000-b7f40000 rwxp 00019000 08:03 1441816 /lib/ld-2.5.so
bfcb8000-bfccd000 rw-p bfcb8000 00:00 0 [stack]
ffffe000-fffff000 r-xp 00000000 00:00 0 [vdso]
Unfortunately, I had not upstart-dbg installed then yet, and could not
reproduce it yet.
AFAIR I've not tried "shutdown -f", but I do not believe it would have helped,
given that "upstart" was not responding anymore, e.g. "initctl list" hung:
# strace initctl list
...
bind(3, {sa_family=AF_FILE, path=@/com/ubuntu/upstart/11549}, 28) = 0
setsockopt(3, SOL_SOCKET, SO_PASSCRED, [1], 4) = 0
sendmsg(3, {msg_name(22)={sa_family=AF_FILE, path=@/com/ubuntu/upstart},
msg_iov(1)=[{"upstart\n\0\0\1\0S", 13}], msg_controllen=0, msg_flags=0}, 0) = 13
getsockname(3, {sa_family=AF_FILE, path=@/com/ubuntu/upstart/11549���
}, [28]) = 0
recvmsg(3,
Any hint to debug this further?
** Affects: upstart (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
"init" not responding anymore / problems shutting down
https://bugs.launchpad.net/bugs/119653
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
