***: jcv has joined #arpnetworks
sjackso has joined #arpnetworks 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 :) ***: staticsafe has quit IRC (Ping timeout: 248 seconds)
Lucifer333 has joined #arpnetworks 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.) up_the_irons: Yeah I never knew there was an alternative to reboot ***: staticsafe has joined #arpnetworks up_the_irons: I think kvr18 just crashed 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 ***: brycec[m] has joined #arpnetworks -: brycec wonders why it's still down 20 minutes after it was acknowledged down up_the_irons: brycec: i see everything up now; are you still having problems? brycec: my vps hasn't phoned-home yet and isn't pinging. 1s while I check console
manual fsck >:(
(thanks for the prodding) up_the_irons: :) brycec: up_the_irons: thoughts/clues on what happened to kvr18?
(just curious) 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. brycec: Huh, weird. -: brycec ticks the "blame up_the_irons" reason tickbox
up_the_irons cries mercutio: i'm not sure zombie reaping is helpful up_the_irons: mercutio: VM wouldn't start until I reaped the zombie; then it started fine mercutio: it used to be when things started zombieing that it was due to memory management etc bugs iirc up_the_irons: I have no idea why all it's resources (tap, disk , etc...) were still held by the zombie mercutio: hmm
was that the same vps that got stuck? up_the_irons: yup, got stuck 3 times mercutio: weird. t's still strange. why that host, why that vm up_the_irons: exactly mercutio: it may be some weird race condition that hardly ever happens
that broke something that made it break again ***: toddf_ is now known as toddf
hazardous has quit IRC (Ping timeout: 245 seconds)
hazardous has joined #arpnetworks
Lucifer333 has quit IRC (Quit: Leaving) up_the_irons: yeah ***: Nahual has joined #arpnetworks
Nahual has quit IRC (Quit: Leaving.) nathani: whats a zombie? mercutio: when a process state says Z in top
it's basically a stuck process mike-burns: It's a child process that is not properly detached, right? mercutio: https://en.wikipedia.org/wiki/Zombie_process 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... mike-burns: Yeah, that. ***: 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
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