 Major problems after fixing time. [message #65123] |
Sun, 17 May 2009 23:09  |
 kev888 
Messages: 36
Registered: October 2006 |
Member |
|
|
We had some issues with a major time offset of about 8 hours on one of our Xen machines. After updating the time with ntp, Xen domains crashed upon entry with xm console #, and VMs showed 9999% cpu usage for all processes. The server crashed shortly afterwords and had to be reset.
After rebooting, it kept crashing after roughly 5-15 minutes of running. After killing hypervm, it lasted for a few more hours before any other issues.
My question is, what would cause fixing time to make a perfectly stable server go nuts?
Any help would be greatly appreciated.....
[Updated on: Sun, 17 May 2009 23:19] Report message to a moderator |
|
|
| Re: Major problems after fixing time. [message #65142 is a reply to message #65123] |
Mon, 18 May 2009 02:12  |
lxbhargava 
Messages: 597
Registered: May 2009 |
Master |
|
|
Hello,
Check dmesg.
On Mon, May 18, 2009 at 03:09:45AM -0000, Kevin Bauer wrote:
>
>
> We had some issues with a major time offset of about 8 hours on one of our Xen machines. After updating the time with ntp, Xen domains crashed upon entry with xm console #, and VMs showed 9999% cpu usage for all processes. The server crashed shortly afterwards and had to be reset.
>
> After rebooting, it kept crashing after roughly 5-15 minutes of running. After killing hypervm, it lasted for a few moure hours before any other issues.
>
> My question is, what would cause fixing time to make a perfectly stable server go nuts?
>
> Any help would be greatly appreciated.....
>
>
>
Thanks and Regards
S Bhargava
Lxlabs Support
|
|
|
|
| Re: Major problems after fixing time. [message #65185 is a reply to message #65123] |
Mon, 18 May 2009 16:31 |
kev888
Messages: 36
Registered: October 2006 |
Member |
|
|
Another problem that has popped up AFTER changing just the time (Was off about 8 hours).
Disk I/O is horrendous. A simple yum update on one VM will bring the node to 4.0+ load average, and cause i/o wait problems on all the other VMs. It only started after the time update as well. I'm about ready to change the time back to the bad number, and just have people run ntpd on their VM's, but I doubt it'll work and I'm guessing it'll just cause more problems. I'm not 100% sure if the problem is the disks, or something acting up.
[Updated on: Mon, 18 May 2009 16:50] Report message to a moderator |
|
|
HyperVM & Kloxo Support
Members
Search
Help
Register
Login
Home
