For some reason, when I press "sync time with Time Server" in WHM, it's always off by one hour :eek: How do I go about fixing this? The funny thing is that the time was off after the server crashed and rebooted. any help would be appreciated.
Printable View
For some reason, when I press "sync time with Time Server" in WHM, it's always off by one hour :eek: How do I go about fixing this? The funny thing is that the time was off after the server crashed and rebooted. any help would be appreciated.
Sounds like you need to set the hardware clock.
This page has helped me in the past:
http://www.linuxsa.org.au/tips/time.html
Thanks but is there a way to sync the time instead of manually inputting the time?
You probably just have the wrong time zone set. Select the correct time zone from WHM and save your changes.
- Matt
Well, I haven't used these before, but at that bottom of that page it notes two programs:You might wanna try checking them out :)Quote:
# rdate - get the current time from a remote machine; can be used to set the system time.
# xntpd - like rdate, but it's extremely accurate and you need a permanent 'net connection. xntpd runs continuously and accounts for things like network delay and clock drift, but there's also a program (ntpdate) included that just sets the current time like rdate does.
but the hardware and system clock are the same (off by one hour)... I tried to change to a different time zone but to no avail. :(Quote:
Originally posted by mainarea
You probably just have the wrong time zone set. Select the correct time zone from WHM and save your changes.
- Matt
My system already have rdate installed.Quote:
Originally posted by shockuk
Well, I haven't used these before, but at that bottom of that page it notes two programs:You might wanna try checking them out :)
I typed rdate -s time.nist.gov
and then it outputs:
"Alarm clock"
:confused: :confused:
Try syncing the time through WHM, and then do what the website said to sync the hardware clock - see if that works.Quote:
Setting the hardware clock
To set the hardware clock, my favourite way is to set the system clock first, and then set the hardware clock to the current system clock by typing ``/sbin/hwclock --systohc'' (or ``/sbin/hwclock --systohc --utc'' if you are keeping the hardware clock in UTC). To see what the hardware clock is currently set to, run hwclock with no arguments. If the hardware clock is in UTC and you want to see the local equivalent, type ``/sbin/hwclock --utc''
- Matt
Sync time through whm didn't work. Finally, I gave up with syncing and manually changed the time with the date command.
In the process, I inadvertantly changed the year incorrectly (ahead some years), is there anything it would affect that should be a concern? The cookies on my forum already got screwed because of this, it shows all topics from the 24th up until present as UNREAD even though they have been read. :( :confused:
Yes, your date would be wrong for everything.... just correct it.Quote:
In the process, I inadvertantly changed the year incorrectly (ahead some years), is there anything it would affect that should be a concern?
- Matt
Yes, I corrected it less than a minute afterwards... just paranoid that it might have screwed up other things on the server.
Well, if your server was live at the time, you could've presented some problems in forum scripts (and similar), but it shouldn't be too bad.
For example, if someone posts in a forum it would enter the wrong date into MySQL. This shouldn't really affect anything but showing a strange post time on any new posts - unless you have strange forum software that drags the post list out of the DB descending by date (which would cause your "future" posts to stay at the top of the topic list untill the date has past), but most popular ones (vB, phpBB, IPB, etc) drag the topics out in descending order of ID.
In other words, it more than likely did not affect much, but this depends on the scripts you are running on your server...