| Author |
Message |
caker
Joined: 15 Apr 2003
Posts: 2392
Location: Galloway, NJ
|
| Posted: Fri Jan 09, 2004 7:41 pm Post subject: Linodes on Host3 restarted |
|
|
At 3:15 EST, Linodes on host 3 were restarted shortly after I noticed they were in a locked-up state. Reboots might have been difficult via the control panel because UML didn't exit correctly and kept the filesystem locked. I terminated the remaining UML process for each Linode and issued a boot command.
-Chris |
|
| Back to top |
|
griffinn
Joined: 09 Sep 2003
Posts: 47
|
| Posted: Sat Jan 10, 2004 9:24 pm Post subject: |
|
|
My linode at host8 locked up at around January 9 13:54 EST. Did a reboot and it's been running fine since.
I didn't notice this announcement until now. Might this be related? |
|
| Back to top |
|
caker
Joined: 15 Apr 2003
Posts: 2392
Location: Galloway, NJ
|
| Posted: Sat Jan 10, 2004 9:46 pm Post subject: |
|
|
I don't think so -- whatever it was affected most, if not all of the Linodes on the machine. I'm still running some tests to determine the cause.
On a different topic than host1/3 issue, I believe the following symptoms are because the Out Of Memory Killer (OOM Killer) has been removed in 2.4.23 (and 2.4.24):
:arrow: Linodes Crashing
:arrow: Attempt to reboot, but won't come back online, "Filesystem Locked" error (requiring my assistance)
:arrow: page_alloc messages on console/output of "dmesg" <-- dead give-away
I'll look into patching the OOM killer back into the kernel (or wait for it to be re-included in 2.4.25?).
-Chris |
|
| Back to top |
|
| |
