Detected incorrectly running system clock (<)

Hi Guys,

i have a problem since i updated my Teamspeak Server to Version 3.11.0. (3.11.0 (13.01.2020 09:12:37) on Linux )

When i create a channel, the Teamspeakserver dropps clients out of the Server and post this message:
2020-02-18 08:08:24.471380|WARNING |PktHandler | |detected incorrectly running system clock (<)
2020-02-18 08:08:24.471426|WARNING |PktHandler | |detected incorrectly running system clock (<)
2020-02-18 08:08:24.492075|WARNING |PktHandler | |detected incorrectly running system clock (<)
2020-02-18 08:08:24.492170|WARNING |PktHandler | |detected incorrectly running system clock (<)
2020-02-18 08:08:24.492209|WARNING |PktHandler | |detected incorrectly running system clock (<)

2020-02-18 08:08:24.516892|INFO |PktHandler |1 |Terminating connection because of > 255 resends
2020-02-18 08:08:24.516980|INFO |PktHandler |1 |Dropping client 10 because of resend timeout
2020-02-18 08:08:24.518331|INFO |PktHandler |1 |Terminating connection because of > 255 resends
2020-02-18 08:08:24.518363|INFO |PktHandler |1 |Dropping client 19 because of resend timeout
2020-02-18 08:08:24.522346|INFO |PktHandler |1 |Terminating connection because of > 255 resends
2020-02-18 08:08:24.522392|INFO |PktHandler |1 |Dropping client 16 because of resend timeout

2020-02-18 08:08:24.551363|INFO |VirtualServerBase|1 |client disconnected ‘Oasis’(id:2103) reason ‘reasonmsg=connection lost’
2020-02-18 08:08:24.551775|INFO |VirtualServerBase|1 |client disconnected ‘Aspho’(id:132) reason ‘reasonmsg=connection lost’
2020-02-18 08:08:24.552090|INFO |VirtualServerBase|1 |client disconnected ‘[Kill] Clesory’(id:2235) reason ‘reasonmsg=connection lost’

i found in the old Forum a post: https://forum.teamspeak.com/threads/56320-Server-crash-quot-detected-incorrectly-running-system-clock-quot

i’m a bit confused…
my Servertime is: Tue Feb 18 09:13:16 CET 2020
and the Logfiletime is: 2020-02-18 08:08:24

how can this happen ? or better question, how can I synchronize the Teamspeak server again? unfortunately it does not work with a restart.

Illu

The problem is not the server. The problem is the system where the server is running on.

Your system clock jumps back in time when measured from the server and this is why you get these warnings. Could be caused by emulation of the system you use or when hardware is broken.

And the thread you linked there explains exactly what is happening.
If that does not help this may be a hardware problem.


The server log time is in UTC. This is why you see 1 hour difference.

3 Likes

Hi ChrisR,

“The server log time is in UTC. This is why you see 1 hour difference.”
can this be a problem ? or is this no problem for the Server ?

i checked my whole server… there is no script that changes time. The time is corret set on the server.

No the log is not the problem. That’s normal.

The system clock issue can be within a second where time jumps around. So you might not see it by watching/requesting the current time on your clock.

1 Like

i just observed that only people who are not in the same timezone as the rest are kicked off the server.

If your server is low on resources (virtual servers sometimes have this issue), your system clock may not be running in real time. Linux servers usually run ntpd as a system service which is responsible for adjusting the time.

If the system clock is too far off, ntpd may decide to set the time to the correct value rather than “smoothing out” the time difference by speeding up or slowing down the clock accordingly.

This can cause problems such as TeamSpeak thinking that a connection timed out even though it has not, simply because the system time it compares against is too far off.

You need to find out why your system clock keeps doing that and you should probably take this issue to a Linux forum. Your TeamSpeak issues are merely a side effect of your system doing weird things.

If this is a dedicated server, this may actually be a hardware failure. I think hardware clock failure is a rather rare issue these days but it could still happen.

2 Likes

@RandomHost Can your post be related to that?

This depends on how TeamSpeak built their software but I’d say that unreliable system time can cause all sorts of issues, including timezone conversion.

The only weird thing is your claim that these issues started after updating to 3.11.0 because it implies that something has changed in that version which makes it more prone to fluctuations in system time.

Oh, look:

  • Made further improvements to timeout and latency handling for larger servers.

You might have had the issue for longer but these “improvements” may actually be the reason why it causes timeouts now.

3 Likes

The problem always could cause timeouts for users. This must have happen before 3.11.0.
This happens when clock jumps backwards (asked dev again). Can happen when system you use is emulated or there is a small chance that hardware is broken.

The changes @RandomHost mentioned are not related to this. These timeouts happened because server was to busy with changes we made in versions before 3.11.0.

4 Likes

Thanks for the Reply,

i will check the whole server and may the problem with the clock.
if i solved it i will come back.

Use comand date then hwclock. If you see different time it is necessary changes hwclock.
How to change hwclock you can use this instructions hwclock

Please don’t remember write whether it helped

moved by moderator

Problem: All clients lose the connection to our Ts3 server at least 1x per day.

Error from the log:

detected incorrectly running system clock (<)

Fix it!
See post #2

But i would not count that the timeouts are related to this issue.

2 Likes
twitch instagram twitter facebook