Time screwed up after Yum Update
Any way to prep for this sorta weird behavior in the future? Should I be using ntp to manually force my VPS to sync the correct time stamp?
5 Replies
Next time it happens, do "date" and "date -u" both before and after you fix it. That will help define what's going on. (Also, from the ntpq command line, "rl" and "peers" might be handy.)
Are you saying that the timezone on your machine is wrong? If that's the case then you may need to edit /etc/sysconfig/clock because that value is sometimes used to update /etc/localtime.
@hoopycat:
Define "messes up"…
Next time it happens, do "date" and "date -u" both before and after you fix it. That will help define what's going on. (Also, from the ntpq command line, "rl" and "peers" might be handy.) [02:47 AM] $ date
Tue Sep 27 02:47:24 EDT 2011
[02:47 AM] $ date -u
Tue Sep 27 06:47:26 UTC 2011
The current time is 11:49 PM, Sept. 26th, 2011
In other words, it's still wrong, even after relinking the correct timezone.. I don't know much about ntpq.
@sweh:
What do you mean "reset the /etc/localtime" ?
Are you saying that the timezone on your machine is wrong? If that's the case then you may need to edit /etc/sysconfig/clock because that value is sometimes used to update /etc/localtime. I'm saying for some reason a module updated with yum update always ruins my timezone information. It's annoying. And I'm not sure exactly how to fix it.
@superfastcars:
The current time is 11:49 PM, Sept. 26th, 2011
…."11:49 PM" in what time zone? As of when you posted, it's certainly not "11:49 PM" in either EDT (UTC-04:00), which your node is set to, or UTC.
~~![](<URL url=)http://drop.hoopycat.com/linode-forum-44092-1.png
You've gone through the RHEL time-zone-changing procedure