Community Forums Today's Posts     Member List     Archive    
Page 1 of 4 123 ... LastLast
Results 1 to 15 of 58
  1. #1
    Join Date
    Dec 2009
    Location
    Localhost
    Posts
    30

    Solved Server 'crash', "detected incorrectly running system clock"

    Hello!
    My teamspeak server is on a MySQL database on a separate server when I was placed on the Teamspeak server database SQLite was not the problem just now started to happen so that the server then throws all the 3 seconds you can enter it again is very annoying. Below I've included a log of the server.

    2010-04-09 21:56:19.255568|INFO |VirtualServer | 1| query client disconnected 'TSViewer.com DBscan REG 915244'(id:323) reason 'reasonmsg=disconnecting'
    2010-04-09 21:56:29.791031|INFO |VirtualServer | 1| client disconnected 'xxSlayeRxx'(id:669) reason 'reasonmsg=leaving'
    2010-04-09 21:56:32.109854|INFO |VirtualServer | 1| client connected 'xxSlayeRxx'(id:669) from 194.146.218.83:1213
    2010-04-09 21:56:34.672161|INFO |VirtualServer | 1| client disconnected 'Nivalis'(id:171) reason 'reasonmsg=connection lost'
    2010-04-09 21:57:00.411943|INFO |VirtualServer | 1| client connected 'Nivalis'(id:171) from 213.241.66.57:3623
    2010-04-09 21:57:11.013971|INFO |VirtualServer | 1| client disconnected 'xxSlayeRxx'(id:669) reason 'reasonmsg=leaving'
    2010-04-09 21:57:12.801611|INFO |VirtualServer | 1| client connected 'xxSlayeRxx'(id:518) from 194.146.218.83:1213
    2010-04-09 21:57:29.447663|INFO |VirtualServer | 1| client disconnected 'invidia'(id:663) reason 'reasonmsg=connection lost'
    2010-04-09 21:58:19.637203|INFO |VirtualServer | 1| permission 'i_channel_join_power'(id:13683) was deleted by 'xxSlayeRxx'(id:518) from channel 'Mix 1'(id:65)
    2010-04-09 21:58:20.284236|WARNING |PktHandler | | detected incorrectly running system clock
    2010-04-09 21:58:20.332143|INFO |VirtualServer | 1| client disconnected 'xxSlayeRxx'(id:518) reason 'reasonmsg=connection lost'
    2010-04-09 21:58:20.392223|WARNING |PktHandler | | detected incorrectly running system clock
    2010-04-09 21:58:20.461169|INFO |VirtualServer | 1| client disconnected 'Yung'(id:405) reason 'reasonmsg=connection lost'
    2010-04-09 21:58:20.574236|WARNING |PktHandler | | detected incorrectly running system clock
    2010-04-09 21:58:20.628597|INFO |VirtualServer | 1| client disconnected 'Alarinius'(id:664) reason 'reasonmsg=connection lost'
    2010-04-09 21:58:21.291720|WARNING |PktHandler | | detected incorrectly running system clock
    2010-04-09 21:58:21.306531|INFO |VirtualServer | 1| client disconnected 'Gonsiorek'(id:394) reason 'reasonmsg=connection lost'
    2010-04-09 21:58:21.391184|WARNING |PktHandler | | detected incorrectly running system clock
    2010-04-09 21:58:21.812535|INFO |VirtualServer | 1| client connected 'xxSlayeRxx'(id:518) from 194.146.218.83:1213
    2010-04-09 21:58:21.869582|INFO |VirtualServer | 1| client disconnected 'Serek'(id:349) reason 'reasonmsg=connection lost'
    2010-04-09 21:58:21.931572|WARNING |PktHandler | | detected incorrectly running system clock
    2010-04-09 21:58:21.991524|INFO |VirtualServer | 1| client disconnected 'Luna'(id:604) reason 'reasonmsg=connection lost'
    2010-04-09 21:58:22.019663|WARNING |PktHandler | | detected incorrectly running system clock
    2010-04-09 21:58:22.057851|ERROR |VirtualServer | 1| connectionLost() invalid clientID: 0
    2010-04-09 21:58:22.107779|WARNING |PktHandler | | detected incorrectly running system clock
    2010-04-09 21:58:22.147774|INFO |VirtualServer | 1| client disconnected 'HONESTY'(id:26) reason 'reasonmsg=connection lost'
    2010-04-09 21:58:22.172878|WARNING |PktHandler | | detected incorrectly running system clock
    How do I fix this?
    Last edited by meliorus; 11-04-2010 at 23:38.

  2. #2
    Join Date
    Jul 2002
    Location
    Germany
    Posts
    2,829
    Well, this happens when the system clock "jumps" around (skips into the future, or into the past). Why it is doing this I do not know, there are many possible causes...your hardware might be broken, or your might be running some not so clever scripts that fool around with the time. Where the database runs should have no impact on this issue.
    You think my answer is stupid ? Read This:
    http://www.catb.org/~esr/faqs/smart-...ons.html#intro

    In a world without fences and walls - who needs windows and gates ?

  3. #3
    Join Date
    Dec 2009
    Location
    Localhost
    Posts
    30
    This is only one mistake which I leap at the opportunity with an error:
    [QUOTE]| ERROR | VirtualServer | 1 | connectionLost () invalid clientID: 0
    I am concerned about is that all users who are on my server is kicked and then again after 3 minutes may come.
    My Client Log throws me this error:
    2010-04-11 23:55:31.411328 Info Logging started, clientlib version: 3.0.0-beta18 [Build: 10609]
    2010-04-11 23:55:32.646347 ClientUI Info TeamSpeak 3 client version: 3.0.0-beta18 [Build: 10609]
    2010-04-11 23:55:32.646347 ClientUI Info Qt version: 4.6.2
    2010-04-11 23:55:32.646347 ClientUI Info Using configuration location: C: / Users/Ziom/AppData/Roaming/TS3Client/ts3clientui_qt.conf
    2010-04-11 23:55:33.118854 ClientUI Info Last update check you: N 11th April 2010 10:02:37
    2010-04-11 23:55:39.647962 PreProSpeex Info Speex version: speex-1.2beta3
    2010-04-11 23:59:28.942004 ClientUI Info updateClient (): clientID invalid
    2010-04-12 00:09:25.283681 ClientUI Info updateClient (): invalid clientID
    Please continue to help fix this problem
    this is my ts3server.ini:

    machine_id=
    default_voice_port=9987
    voice_ip=0.0.0.0
    liscensepath=
    filetransfer_port=30044
    filetransfer_ip=0.0.0.0
    query_port=12548
    query_ip=0.0.0.0
    dbplugin=ts3db_mysql
    dbpluginparameter=ts3db_mysql.ini
    dbsqlpath=sql/
    dbsqlcreatepath=create_mysql/
    logpath=logs
    logquerycommands=1
    Last edited by meliorus; 11-04-2010 at 23:37.

  4. #4
    Join Date
    Jun 2010
    Posts
    6
    Hey everyone

    We've got same problem and did you found any solution how to fix this damn issue? We just lookin forward to fix this somehow and it would be nice if anyone already know whats wrong.

    Code:
    2010-06-18 05:38:35 PktHandler Warning detected incorrectly running system clock

  5. #5
    Join Date
    Dec 2004
    Location
    RF
    Posts
    2,353
    How you are managing your system clock?
    If you just running ntpdate now and then to set correct time, make sure it is using time adjustment instead of time step.

  6. #6
    Join Date
    Jul 2002
    Location
    Germany
    Posts
    2,829
    "detected incorrectly running system clock" means we queried for the current time
    once, got some value A, then later queried again, got B, but B signified an earlier
    point in time than A, so in effect the clock warped into the past. On linux systems
    we use "gettimeofday" to query the system clock, on windows we use
    QueryPerformanceCounter.

    If you or some script you use changes the system time on UNIX this error can come
    up. For synchronizing your clock with a timeserver use ntpd and not ntpdate.

    If you are sure neither you nor some script is messing with the time, or if you are
    seeing this error on Windows there is some deeper problem at work.

    For windows systems, microsoft itself has a paragraph about possible causes
    for QueryPerformanceCounter to produce bad results, quoting msdn:
    On a multiprocessor computer, it should not matter which processor is called. However, you can get different results on different processors due to bugs in the basic input/output system (BIOS) or the hardware abstraction layer (HAL).
    So, bugs in the bios (maybe try a bios upgrade helps) or the kernel, or the hardware itself that is used to provide the system time can all cause the system time to misbehave. When running in some kind of a virtual machine there is yet annother layer between teamspeak and the hardware providing the system time, which can add problems too.
    You think my answer is stupid ? Read This:
    http://www.catb.org/~esr/faqs/smart-...ons.html#intro

    In a world without fences and walls - who needs windows and gates ?

  7. #7
    Join Date
    Jan 2010
    Location
    New England USA / Marnbach, Weilheim i.OB, Germany
    Posts
    443

    Solved [Fixed?] Server 'crash', "detected incorrectly running system clock"

    On my client, I received "Connection to server lost" so I continued on to check my connection, and realized that it was the server that had dropped everyone. In the log is what is posted below just before everyone lost their connection to the server.

    What I had done last before the server went down, was unchecked the check box in the logs tab when editing virtual server so that the log wouldn't log 'ServerQuery'. Before, I had the logs logging everything that they could log, all check boxes were checked. After editing the virtual server to NOT log ServerQuery, the "detected incorrectly running system clock" appears in log, and all clients lost their connection.

    Server Version: 3.0.0-beta26-pre [Build: 11624]

    Probably not a bug, what what is |WARNING |PktHandler | | detected incorrectly running system clock and would it cause a server to drop all clients connections?

    I have searched the forums and have seen other people get this similar warning. I just thought I would post it because it occurred only after editing the Virtual Server to not log ServerQuery and following it, the server went down and all clients lost their connection.

    Code:
    2010-07-10 01:47:21.969278|INFO    |VirtualServer |  1| server was edited by 'Gen.Skylab'(id:2)
    2010-07-10 01:47:21.969812|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-07-10 01:47:21.970712|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-07-10 01:47:21.971253|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-07-10 01:47:21.971796|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-07-10 01:47:21.972228|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-07-10 01:47:26.646284|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-07-10 01:47:26.647181|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-07-10 01:47:28.355656|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-07-10 01:47:28.357166|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-07-10 01:47:28.358320|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-07-10 01:47:28.360028|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-07-10 01:47:28.361758|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-07-10 01:47:28.362850|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-07-10 01:47:28.363306|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-07-10 01:47:28.363838|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-07-10 01:47:28.364419|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-07-10 01:47:28.365023|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-07-10 01:47:28.365468|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-07-10 01:47:28.366103|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-07-10 01:47:28.366604|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-07-10 01:47:28.367133|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-07-10 01:47:28.367732|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-07-10 01:47:28.368279|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-07-10 01:47:28.368813|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-07-10 01:47:28.369585|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-07-10 01:47:28.370169|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-07-10 01:47:28.395744|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-07-10 01:47:28.399787|WARNING |PktHandler    |   | detected incorrectly running system clock

  8. #8
    Join Date
    Jun 2008
    Posts
    9,377
    Please retry this, with the official beta 26 release. This crash should be fixed.
    http://ftp.4players.de/pub/hosted/ts3/releases/beta-26/
    The error won't dissapear, because your system clock sends something wrong.

  9. #9
    Join Date
    Jan 2010
    Location
    New England USA / Marnbach, Weilheim i.OB, Germany
    Posts
    443
    Already have servers updated to 11927 and so far this error has been fixed. I'll let you know if this crash occurs again, thanks!

  10. #10
    Join Date
    Nov 2006
    Location
    USA
    Posts
    55
    Its not fixed.. I never had this before but since updating the server build to the latest I am not getting this error in mass and then the server restarts.

    I hope there is an answer for this...

  11. #11
    Join Date
    Jan 2010
    Location
    New England USA / Marnbach, Weilheim i.OB, Germany
    Posts
    443
    Quote Originally Posted by BobBart View Post
    Its not fixed.. I never had this before but since updating the server build to the latest I am not getting this error in mass and then the server restarts.

    I hope there is an answer for this...
    Perhaps a snippet of server log?

  12. #12
    Join Date
    Dec 2009
    Location
    Iceland
    Posts
    14
    I have the exact same issue just started today at 03:00 or so GMT and now the server process has crashed twice due to it. i have force synched the ntpdate and we will wait and see what happens.

    edit.
    Every time somone is added removed or changes server or channel group the process crashes, and throws the exact same error you guys are having.

    edit
    I have force synchronised the system clock using ntpd but the issue continues to happen. I have had no issues like this prior to beta 27 and nothing on the limux server has changed at all.
    Last edited by VPope; 25-08-2010 at 11:27.

  13. #13
    Join Date
    May 2009
    Location
    London
    Posts
    16
    I guess this problem is unresolved then?

  14. #14
    Join Date
    Dec 2009
    Location
    Germany
    Posts
    8

    detected incorrectly running system clock (beta29)

    I have updated to the new version Beta29 and now I have connection problems. All people leave the server and can reconnect in next 5 minutes. This problem occurs at specific time intervals.

    System: Windows

    Code:
    ...
    2010-10-02 12:46:40.467625|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-10-02 12:46:40.467625|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-10-02 12:46:40.483250|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-10-02 12:46:40.483250|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-10-02 12:46:40.483250|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-10-02 12:46:40.498875|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-10-02 12:46:40.498875|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-10-02 12:46:40.514500|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-10-02 12:46:40.577000|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-10-02 12:46:40.577000|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-10-02 12:46:40.577000|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-10-02 12:46:40.577000|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-10-02 12:46:40.592625|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-10-02 12:46:40.592625|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-10-02 12:46:40.608250|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-10-02 12:46:40.608250|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-10-02 12:46:40.608250|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-10-02 12:46:40.623875|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-10-02 12:46:40.623875|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-10-02 12:46:40.623875|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-10-02 12:46:40.639500|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-10-02 12:46:40.686375|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-10-02 12:46:40.717625|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-10-02 12:46:40.733250|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-10-02 12:46:40.733250|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-10-02 12:46:40.733250|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-10-02 12:46:40.748875|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-10-02 12:46:40.780125|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-10-02 12:46:40.780125|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-10-02 12:46:40.795750|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-10-02 12:46:40.795750|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-10-02 12:46:40.795750|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-10-02 12:46:40.811375|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-10-02 12:46:40.811375|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-10-02 12:46:40.811375|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-10-02 12:46:40.827000|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-10-02 12:46:40.827000|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-10-02 12:46:40.827000|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-10-02 12:46:40.842625|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-10-02 12:46:40.842625|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-10-02 12:46:40.842625|WARNING |PktHandler    |   | detected incorrectly running system clock
    ...

  15. #15
    Join Date
    Dec 2009
    Location
    Germany
    Posts
    8
    but my system is windows and the problem appeared in the new beta29 version

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. Replies: 7
    Last Post: 10-06-2011, 16:33
  2. Detected incorrectly running system clock!
    By Cyberwolf. in forum Server Support
    Replies: 0
    Last Post: 18-04-2011, 15:12
  3. detected incorrectly running system clock
    By SeToY in forum Linux / FreeBSD
    Replies: 2
    Last Post: 03-01-2011, 22:52
  4. detected incorrectly running system clock (beta29)
    By Sponge-Manu in forum Bug Reports
    Replies: 3
    Last Post: 03-10-2010, 16:14
  5. detected incorrectly running system clock
    By YJeeper in forum Server Support
    Replies: 1
    Last Post: 02-03-2010, 22:24

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •