[oopscheck] KERNEL Oops

[mikelegg]

For about the last week I've been receiving KERNEL Oops notifications every night on one of my VPSs. The emails are generated a minute or two after scripts/upcp runs.

I've had advice not to worry about them, but obviously there is something wrong and it is occurring every time the cPanel update runs.

Does anyone have any thoughts about this or should I just open a support ticket with cPanel?

IMPORTANT: Do not ignore this email.
Your kernel had an Oops!

This is the result of bad hardware or a kernel bug.
Your system may continue to function as normal, however
there is a good chance bad things are happening right now.
Bad things include: files disappearing, daemons crashing,
complete server crashs, disk corruption and many others.

You might want to check your RAM with memtest86 as this is
usually the cause of the problem.
Memtest86.com - Memory Diagnostic

The Oops is below:
EIP: 0060:[<c0403be1>] CPU: 1
EIP is at default_idle+0x31/0x59
EFLAGS: 00000246 Not tainted (2.6.18-164.15.1.el5 #1)
EAX: 00000000 EBX: 00000001 ECX: c0403bb0 EDX: f7c96000
ESI: 00000000 EDI: 00000000 EBP: 00000000 DS: 007b ES: 007b
CR0: 8005003b CR2: 001dc120 CR3: 363af000 CR4: 000006d0
[<c0403ca8>] cpu_idle+0x9f/0xb9
=======================
TCP: Treason uncloaked! Peer 202.124.75.238:49323/80 shrinks window 1358195100:1358204900. Repaired.
TCP: Treason uncloaked! Peer 202.124.75.238:49323/80 shrinks window 1358195100:1358204900. Repaired.
TCP: Treason uncloaked! Peer 121.200.0.203:1339/80 shrinks window 1961057390:1961058140. Repaired.
TCP: Treason uncloaked! Peer 121.200.0.203:1339/80 shrinks window 1961092488:1961093948. Repaired.

[WiredTree Joe]

This is not a cPanel issue. It is most likely bad hardware on the parent hardware node that is kicking out errors in your VPS. You should contact your provider to fix it for you as there isn't much that cPanel can do to help you.

[Al-Ra3eD.CoM]

Hello

I get This In One Of My Customer Dedicated Server ..

The Problem Was With Ram in the Server And I change it ..

You Can Call Your Hosting Provider to fix This Problem ..

[mikelegg]

This is apparently a controversial issue with no clear cause or a solution that works in every case.

The message literally means that a client connecting to the web server is shrinking the TCP window size inappropriately.

Treason Uncloaked | KernelTrap

TCP Treason Uncloaked - Informed Banking Wiki

What intrigues me is that on my machine it's the same two IP addresses every night and it always coincides with the running of upcp.

I'll try blocking those two IP's and see what happens.

[UNIXy]

This is apparently a controversial issue with no clear cause or a solution that works in every case.

The message literally means that a client connecting to the web server is shrinking the TCP window size inappropriately.

The critical message here is the Oops not the TCP Treason one. The two entries are distinct and report different issues. Here's the kernel error you'd need to investigate:

EIP: 0060:[<c0403be1>] CPU: 1
EIP is at default_idle+0x31/0x59
EFLAGS: 00000246 Not tainted (2.6.18-164.15.1.el5 #1)
EAX: 00000000 EBX: 00000001 ECX: c0403bb0 EDX: f7c96000
ESI: 00000000 EDI: 00000000 EBP: 00000000 DS: 007b ES: 007b
CR0: 8005003b CR2: 001dc120 CR3: 363af000 CR4: 000006d0
[<c0403ca8>] cpu_idle+0x9f/0xb9

Be sure to ask your provider to run a hardware check.

Regards
Joe / UNIXY

[mikelegg]

The critical message here is the Oops not the TCP Treason one. The two entries are distinct and report different issues. Here's the kernel error you'd need to investigate:

EIP: 0060:[<c0403be1>] CPU: 1
EIP is at default_idle+0x31/0x59
EFLAGS: 00000246 Not tainted (2.6.18-164.15.1.el5 #1)
EAX: 00000000 EBX: 00000001 ECX: c0403bb0 EDX: f7c96000
ESI: 00000000 EDI: 00000000 EBP: 00000000 DS: 007b ES: 007b
CR0: 8005003b CR2: 001dc120 CR3: 363af000 CR4: 000006d0
[<c0403ca8>] cpu_idle+0x9f/0xb9

Be sure to ask your provider to run a hardware check.

Regards
Joe / UNIXY

Thanks Joe

I'll do that.

[mikelegg]

Used VMotion to migrate the VM to another host machine and also rebooted the VM and didn't get the Oops email tonight.

Have to wait and see what happens tomorrow night.