Hi,
I just discovered that my linode was inaccessible and the Linode Manager graphs were showing 100% CPU. I attempted to get in using SSH and the AJAX console but didn't even get a prompt. So I rebooted.
The system appears to have come back up fine, with no problems. I looked in /var/log/messages and found the following:
Code:
May 10 22:20:03 mail kernel: c030030e
May 10 22:20:03 mail kernel: Modules linked in:
May 10 22:20:03 mail kernel: EIP: 0061:[<c030030e>] Not tainted VLI
May 10 22:20:03 mail kernel: EFLAGS: 00010213 (2.6.18.8-linode19 #1)
May 10 22:20:03 mail kernel: [<c02ffcb4>] key_cleanup+0x84/0xe0
May 10 22:20:03 mail kernel: [<c012e752>] run_workqueue+0x72/0xf0
May 10 22:20:03 mail kernel: [<c02ffc30>] key_cleanup+0x0/0xe0
May 10 22:20:03 mail kernel: [<c012ef57>] worker_thread+0x127/0x150
May 10 22:20:03 mail kernel: [<c0117100>] default_wake_function+0x0/0x10
May 10 22:20:03 mail kernel: [<c012ee30>] worker_thread+0x0/0x150
May 10 22:20:03 mail kernel: [<c0131bb6>] kthread+0xf6/0x100
May 10 22:20:03 mail kernel: [<c0131ac0>] kthread+0x0/0x100
May 10 22:20:03 mail kernel: [<c0102b95>] kernel_thread_helper+0x5/0x10
May 10 22:22:07 mail kernel: <7>[FW_SSH_DENIED]: IN=eth0 OUT= MAC=fe:fd:61:6b:86:a5:00:0e:39:6f:48:00:08:00 SRC=97.107.33.179 DST=97.107.134.165 LEN=48 TOS=0x00 PREC=0x00 TTL=115 ID=15755 DF PROTO=TCP SPT=3406 DPT=135 WINDOW=65535 RES=0x00 SYN URGP=0
May 10 22:35:02 mail kernel: c0337f07
May 10 22:35:02 mail kernel: Modules linked in:
May 10 22:35:02 mail kernel: EIP: 0061:[<c0337f07>] Not tainted VLI
May 10 22:35:02 mail kernel: EFLAGS: 00010296 (2.6.18.8-linode19 #1)
May 10 22:35:02 mail kernel: [<c0338047>] rb_insert_color+0x77/0xe0
May 10 22:35:02 mail kernel: [<c02ff9a0>] key_alloc+0x260/0x370
May 10 22:35:02 mail kernel: [<c0300af0>] keyring_alloc+0x30/0x80
May 10 22:35:02 mail kernel: [<c03026a4>] alloc_uid_keyring+0x54/0xd0
May 10 22:35:02 mail kernel: [<c0127f84>] alloc_uid+0xe4/0x1b0
May 10 22:35:02 mail kernel: [<c012bd4b>] set_user+0xb/0xa0
May 10 22:35:02 mail kernel: [<c012d708>] sys_setreuid+0x1c8/0x1e0
May 10 22:35:02 mail kernel: [<c010547f>] syscall_call+0x7/0xb
Anyone know what this is/what could have caused it? Maybe an upgrade/glitch on the host?
As an aside, this is the first problem I've had and I'm coming up to a 1 year member in a couple of weeks. Well done to Linode for the excellent service!
Thanks,
Dan Scott
http://danieljamesscott.org
FAQ
Search
Members
Register
Login [ Anonymous ]
