/srv/irclogs.ubuntu.com/2007/11/26/#upstart.txt

sorenKeybuk: I've got defunct process with ppid 1.. :( Anything you want me to do?12:06
Keybuksoren: ps output?12:14
sorenAll of it? Or just: soren    13177  0.1  0.0      0     0 ?        Zl   Nov23   5:31 [epiphany-browse] <defunct>12:15
Keybukps ajx for that pid12:16
Keybukps j -p 1317712:18
Keybukshould do the trick12:18
soren13177  7364  7364 ?        Zl     5:31 [epiphany-browse] <defunct>12:19
Keybukit's ppid isn't 1 then12:19
Keybuk?12:19
sorenThat's what ps -efl says.12:19
Keybukps -j ! :)12:19
sorenps -j -p gives these headers:12:20
Keybukno12:20
Keybukps j12:20
sorenGah.12:20
Keybukps j -p 1317712:20
Keybuk;)12:20
sorenI'm an idiot.12:20
soren PPID   PID  PGID   SID TTY      TPGID STAT   UID   TIME COMMAND12:20
soren    1 13177  7364  7364 ?           -1 Zl    1000   5:31 [epiphany-browse] <defunct>12:20
Keybukand curse ps for having the most insanely bad command-line ever12:20
Keybukhmm12:20
Keybukif you kill -CHLD 1 does it go away?12:20
sorenWow.. No.12:21
Keybuksudo initctl version12:21
Keybuk?12:21
Keybuk(note: no --)12:21
sorenNow init (upstart 0.3.9)12:21
sorenEr.. -now :)12:22
Keybukdid it go away?12:22
sorenNo.12:22
Keybuk*shrug*12:22
Keybukiz kernel boog12:22
sorenWhat makes you say that?12:22
sorenSurely, it's upstart's job to wait() for it?12:22
Keybukyes12:22
Keybukand you just did two things that guaranteed that upstart would have called wait() :P12:23
sorenEh? What was the other one? initctl version?12:23
Keybukyeah12:23
soren*g*12:23
sorenWhy?12:23
Keybukupstart always calls wait() in a loop inside its main loop12:23
sorenOh.12:23
Keybukrather than in a signal handler12:23
Keybukso you just did two things that would have definitely caused upstart to repeat its main loop12:24
Keybukso definitely caused wait() to be called12:24
Keybukwhich kernel version?12:24
sorenJust once? Or until there aren't any more children?12:24
Keybukuntil there aren't any more children12:24
Keybukit calls waitid (..., WNOHANG) in a loop12:24
sorenuname -a says: Linux butch 2.6.22-14-generic #1 SMP Sun Oct 14 21:45:15 GMT 2007 x86_64 GNU/Linux12:24
sorenI may or may not have upgraded the kernel package since I booted, so that's the best I've got.12:25
Keybuksudo stop tty112:25
Keybuksudo start tty112:25
sorenSame.12:25
Keybukany getty processes now zombies?12:25
sorenNope12:25
Keybuksudo status tty112:26
Keybukthen kill that pid12:26
Keybukdoes it respawn?12:26
sorenYup12:26
Keybukany zombie gettys?12:26
sorenNope.12:26
Keybukepiphany still there?12:26
sorenYup12:27
Keybuk*shrug*12:27
Keybuknot my fault then ;)12:27
sorenGah..12:27
Keybukdefinitely a kernel issue12:27
Keybuktry sending SIGCONT to 13177 ?12:27
sorenTo a zombie? Er.. No. I can, though.12:28
Keybuktry ie12:28
Keybuktry it12:28
sorenSame.12:28
Keybukfair enough12:28
sorenWhat effect could that possibly have?12:28
Keybuk-> #ubuntu-kernel :)12:28
Keybukmight have released an in-kernel lock12:28
sorenOh.12:28
sorenThe epiphany process has an npviewer.bin child process, but I doubt that can mess things up this badly.12:29
Keybukwell12:30
Keybukthat kinda proves the kernel is stuffed then12:30
sorenThat's a good point.12:30
soren:)12:30
Keybukzombie processes can't, by definition, have children12:32
sorenPrecisely.12:32
Keybuksince when they exit, the children would have been reparented to init first12:33
sorenI didn't think of that.12:33
sorenYeah.12:33
sorenAh... dmesg reveals trouble, too.12:33
sorenE.g. "Fixing recursive fault but reboot is needed!"12:33
soren...but I had the vmware server modules loaded, so I'm SOL.12:34
sorenI'll just blame them. There. Problem solved.12:35

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!