↑back Search ←Prev date Next date→ Show only urls | (Click on time to select a line by its url) |
Who | What | When |
---|---|---|
*** | jcv_ has quit IRC (Quit: leaving)
jcv has joined #arpnetworks | [04:48] |
............................ (idle for 2h16mn) | ||
sjackso has joined #arpnetworks | [07:04] | |
....................................................... (idle for 4h34mn) | ||
up_the_irons | I actually had to attach to init(1) with gdb and reap a zombie process. Supposed to be a "this should never happen" scenario with init, but ...
http://serverfault.com/questions/575162/remove-a-zombie-process-from-the-process-table It ended up working :) | [11:38] |
*** | staticsafe has quit IRC (Ping timeout: 248 seconds) | [11:41] |
Lucifer333 has joined #arpnetworks | [11:51] | |
brycec | Interesting. And here I thought a reboot was the only way to reap zombies.
(Trusty serverfault/stackoverflow - Initial question is "Yes I know the usual reasons *lists them off*" and someone responds with one of those reasons. Morons.) | [11:58] |
up_the_irons | Yeah I never knew there was an alternative to reboot | [12:03] |
*** | staticsafe has joined #arpnetworks | [12:04] |
......... (idle for 44mn) | ||
up_the_irons | I think kvr18 just crashed | [12:48] |
brycec | I'm inclined to agree :(
Description: No report from Monit for 182 seconds: the network, the host or Monit is down. Last report was 19 Jan 2017 15:45:53 -0500 brycec demands that up_the_irons fix it | [12:54] |
*** | brycec[m] has joined #arpnetworks | [12:59] |
brycec | brycec wonders why it's still down 20 minutes after it was acknowledged down | [13:06] |
up_the_irons | brycec: i see everything up now; are you still having problems? | [13:13] |
brycec | my vps hasn't phoned-home yet and isn't pinging. 1s while I check console
manual fsck >:( (thanks for the prodding) | [13:14] |
up_the_irons | :) | [13:15] |
brycec | up_the_irons: thoughts/clues on what happened to kvr18?
(just curious) | [13:20] |
up_the_irons | brycec: no idea; i was doing that zombie reaping. worked at first, but then didn't subsequent times, and there was a VPS stuck in shutdown. I've actually never seen it like that before, ever. Maybe something was up with the host, b/c eventually the whole thing froze. | [13:22] |
brycec | Huh, weird.
brycec ticks the "blame up_the_irons" reason tickbox | [13:22] |
up_the_irons | up_the_irons cries | [13:22] |
mercutio | i'm not sure zombie reaping is helpful | [13:22] |
up_the_irons | mercutio: VM wouldn't start until I reaped the zombie; then it started fine | [13:23] |
mercutio | it used to be when things started zombieing that it was due to memory management etc bugs iirc | [13:23] |
up_the_irons | I have no idea why all it's resources (tap, disk , etc...) were still held by the zombie | [13:23] |
mercutio | hmm
was that the same vps that got stuck? | [13:23] |
up_the_irons | yup, got stuck 3 times | [13:24] |
mercutio | weird. t's still strange. why that host, why that vm | [13:24] |
up_the_irons | exactly | [13:24] |
mercutio | it may be some weird race condition that hardly ever happens
that broke something that made it break again | [13:24] |
...... (idle for 29mn) | ||
*** | toddf_ is now known as toddf | [13:54] |
.......... (idle for 49mn) | ||
hazardous has quit IRC (Ping timeout: 245 seconds) | [14:43] | |
hazardous has joined #arpnetworks | [14:53] | |
........................ (idle for 1h57mn) | ||
Lucifer333 has quit IRC (Quit: Leaving) | [16:50] | |
............... (idle for 1h12mn) | ||
up_the_irons | yeah | [18:02] |
..................... (idle for 1h41mn) | ||
*** | Nahual has joined #arpnetworks | [19:43] |
...... (idle for 26mn) | ||
Nahual has quit IRC (Quit: Leaving.) | [20:09] | |
.......... (idle for 46mn) | ||
nathani | whats a zombie? | [20:55] |
mercutio | when a process state says Z in top
it's basically a stuck process | [21:00] |
mike-burns | It's a child process that is not properly detached, right? | [21:00] |
mercutio | https://en.wikipedia.org/wiki/Zombie_process | [21:00] |
BryceBot | Zombie process :: On Unix and Unix-like computer operating systems, a zombie process or defunct process is a process that has completed execution (via the exit system call) but still has an entry in the process table: it is a process in the "Terminated state". This occurs for child processes, where the entry is still needed to allow the parent process to read its child's exit status: once the exit status is read via the wait system call... | [21:00] |
mike-burns | Yeah, that. | [21:00] |
................................. (idle for 2h44mn) | ||
*** | ben1 has joined #arpnetworks
ChanServ sets mode: +o ben1 KILLALLH1MANS01 has joined #arpnetworks KILLALLH1MANS01 has quit IRC (Changing host) KILLALLH1MANS01 has joined #arpnetworks KILLALLH1MANS01 has quit IRC (Changing host) KILLALLH1MANS01 has joined #arpnetworks | [23:44] |
KILLALLHUMANS01 has quit IRC (Remote host closed the connection)
mercutio has quit IRC (Ping timeout: 240 seconds) up_the_irons has quit IRC (Ping timeout: 240 seconds) up_the_irons has joined #arpnetworks ChanServ sets mode: +o up_the_irons | [23:51] |
↑back Search ←Prev date Next date→ Show only urls | (Click on time to select a line by its url) |