Servers version 3.0.1 -3.0.2-pre2

[hunterpl]

Hello today was a critical bug appear on the all servers come from version 3.0.1-3.0.2-pre2

not only I had that problem !

on the 3.0.0 works fine.

all server had packet loss and big large syslog + kern.log

here is a screenshots of 3 processes when egrep doing check log and that issue doing bigg loss of packets, i was on official teamspeak 3 server test public there was a same problem with packet loss on the "out box" same like the others servers.

http://oi41.tinypic.com/99466s.jpg

Processors was busy high, really high and load more 5.46 , the only one solution was that when i killed all processes with checking log after that was fine, my kernlog and syslog increases up to 40 GB

and log from teamspeak 3 only piece of logs:

2012-02-19 02:25:35.605279|INFO    |ServerLibPriv |   | TeamSpeak 3 Server 3.0.2-pre2 (2012-02-18 08:28:28)
2012-02-19 02:25:35.605734|INFO    |DatabaseQuery |   | dbPlugin name:    SQLite3 plugin, Version 2, (c)TeamSpeak Systems GmbH
2012-02-19 02:25:35.605777|INFO    |DatabaseQuery |   | dbPlugin version: 3.7.3
2012-02-19 02:25:35.606006|INFO    |DatabaseQuery |   | checking database integrity (may take a while)
2012-02-19 02:25:36.408480|INFO    |Accounting    |   | Licensing Information
2012-02-19 02:25:36.408531|INFO    |Accounting    |   | licensed to       : TS3 Bahu Legenda
2012-02-19 02:25:36.408551|INFO    |Accounting    |   | type              : Hoster
2012-02-19 02:25:36.408600|INFO    |Accounting    |   | starting date     : Sun Sep 11 00:00:00 2011
2012-02-19 02:25:36.408622|INFO    |Accounting    |   | ending date       : Tue Sep 11 00:00:00 2012
2012-02-19 02:25:36.408640|INFO    |Accounting    |   | max virtualservers: 10
2012-02-19 02:25:36.408657|INFO    |Accounting    |   | max slots         : 1000
2012-02-19 02:25:36.456159|INFO    |FileManager   |   | listening on 188.138.89.162:30033
2012-02-19 02:25:36.748524|INFO    |CIDRManager   |   | updated query_ip_blacklist ips: 178.33.37.133, 85.214.124.238, 
2012-02-19 02:25:36.748621|INFO    |CIDRManager   |   | updated query_ip_whitelist ips: 127.0.0.1, 188.138.89.162, 85.25.120.233, 208.167.0.0/16, 68.232.0.0/16, 194.97.114.3, 
2012-02-19 02:25:36.749117|INFO    |Query         |   | listening on 188.138.89.162:10011
2012-02-19 20:59:05.489213|WARNING |PktHandler    |   | detected incorrectly running system clock (>)
2012-02-19 20:59:06.393500|WARNING |PktHandler    |   | detected incorrectly running system clock (>)
2012-02-19 20:59:06.393581|WARNING |PktHandler    |   | detected incorrectly running system clock (>)
............
2012-02-21 15:13:32.882923|WARNING |PktHandler    |   | detected incorrectly running system clock (>)

of course is that doing conenction lost for clients on the server.

i think that information is really usefull for teamspeak 3 developers

Best Regards
Mateusz
TS3 Bahu

[dante696]

I changed your thread title! Are you sure, that this message does not appear on a 3.0.1 Server?

Please read this first

The warning "Detected incorrectly running system clock (>)" appears, when your clock does not run correctly.
This can happen, when a second timeserver is running on your server or when your hardware is broken.

Or when a script is running to get an higher FPs on game server. A user was telling me in that this was his problem, while i tried to find his lag on his server. We found out, that incorrectly tiem was spammed in his logs. He stopped that script and everything was fine again. It was a Linux-Debian server.

[Peter]

Hi,

everything is happening as expected, no bug here :-)





Ok to be more helpful, from the screenshot you send you can see that your CPU is being loaded heavily by 3 egrep commands (each taking one entire core CPU wise), and one perl script called "psad". These take care of overloading your machine, and the output TeamSpeak gives with regarding system clock errors is a RESULT of your machine being so overloaded. In effect, if TeamSpeak does not get enough CPU, this error can occur.

So, find out who or what runs this egrep scripts and this psad script and make sure they don't eat up the entire system cpu.

PS: It might very well be that the 3.0.0 server does not log the warning message, since it was recently added, the behavior will be the same anyhow.

[hunterpl]

thank you for your replay.

[dante696]

thank you for your replay.

Did you fix it? Or do you need tiem to solve it or Can this be closed??

[hunterpl]

yeah it was solved already, thank you.