Results 1 to 2 of 2
06-07-2011, 13:38 #1-= TeamSpeak Team =-
- Join Date
- Jul 2002
"Detected incorrectly running system clock" log message
This is for all people that find messages like this in their Log files:
2010-04-09 21:58:22.019663|WARNING |PktHandler | | detected incorrectly running system clock
What does this message mean?
"detected incorrectly running system clock" means we queried for the current time
once, got some value A, then later queried again, got B, but:
i) B signified an earlier point in time than A, so in effect the clock warped into the past, or
ii) B is too far past A to make sense (when we know the two queries are not far apart), in this case the time warped into the future.
On unix systems we use "gettimeofday" to query the system clock, on windows we use timeGetTime.
Why does it occur?
On Unix Systems any change of the system time can be the cause, scripts running ntpdate or ntpd obviously alter the system time. Make sure you use ntpd since it adjusts the time in small delecate steps that do not cause this problem. Some users have reported problems even with ntpd:
Originally Posted by Teddy
Of course there is also a Hardware component here. The operating system uses the system time source to provide the time to us, if the system clock is behaving badly, there is nothing the operating system or TS3 can do.
Also we have done some changes to the ways we handle time problems to be more robust to all but the nastiest time inconsistencies. The current 3.0.0-rc1 server already contains some of these fixes, the soon to be released 3.0.0 server will contain some more. We advise you to upgrade to it.
Last edited by Peter; 11-10-2011 at 08:13.
08-07-2011, 10:02 #2-= TeamSpeak Fanatic =-
- Join Date
- Dec 2004
For Linux, especially Debian-based systems, the problem could be not the NTPD running (It does not cause time leaps at all), but a stupid script in /etc/network/if-up.d/ called ntpdate.
THAT is what WILL cause time leaps each time any of your network interfaces going up.
Lower the executable bit on that file, and make sure your NTPD is correctly configured. ( "ntpq -p" should list your peers, not empty list and not some strange abuse )
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)
By meliorus in forum Linux / FreeBSDReplies: 54Last Post: 02-11-2012, 14:55
By mralaskaman in forum Linux / FreeBSDReplies: 7Last Post: 10-06-2011, 16:33
By meliorus in forum Bug ReportsReplies: 43Last Post: 03-02-2011, 13:10
By SeToY in forum Linux / FreeBSDReplies: 2Last Post: 03-01-2011, 22:52
By aix59 in forum WindowsReplies: 8Last Post: 26-12-2009, 09:26