Forum

Page 2 of 4 FirstFirst 1234 LastLast
Results 16 to 30 of 53
  1. #16
    Join Date
    February 2006
    Location
    Texas, USA
    Posts
    4,143

  2. #17
    Join Date
    October 2010
    Location
    Australia
    Posts
    3

    Teamspeak stopped working

    I'm using a copy of teamspeak that was installed using cPanel's gameserver addon. It was working great until an hour or so ago. Now, it'll start and we can connect but then it immediately crashes. A few minutes later, it restarts itself and crashs again 30 seconds later. cPanel's log view shows the following logs.

    ###################[ Beginning first 1000 lines from log ]##############

    [Sat Oct 30 12:20:02 2010] Launching server with the following commandline:
    # /home/<snip>/.gameservers/ts3_0//ts3server_linux_x86 query_port=8767


    TeamSpeak Server 3.0.0-beta27 [Build: 12002]
    (c)TeamSpeak Systems GmbH

    Logging started
    2010-10-30 04:20:02.962690|INFO |ServerLibPriv | | Server Version: 3.0.0-beta27 [Build: 12002], Linux
    2010-10-30 04:20:02.977450|INFO |DatabaseQuery | | dbPlugin name: SQLite3 plugin, Version 2, (c)TeamSpeak Systems GmbH
    2010-10-30 04:20:02.991119|INFO |DatabaseQuery | | dbPlugin version: 3.6.21
    2010-10-30 04:20:03.002169|INFO |DatabaseQuery | | checking database integrity (may take a while)
    2010-10-30 04:20:03.283759|INFO |SQL | | pruning old database log entries where timestamp is older than 90 days
    2010-10-30 04:20:03.698828|WARNING |Accounting | | Unable to find valid license key, falling back to limited functionality
    2010-10-30 04:20:03.762468|INFO |FileManager | | listening on <ipsnip>:30033
    2010-10-30 04:20:04.109958|INFO |VirtualServer | 1| listening on <ipsnip>:8767
    2010-10-30 04:20:04.130489|INFO |CIDRManager | | updated query_ip_whitelist ips: 127.0.0.1,
    2010-10-30 04:20:04.131670|INFO |Query | | listening on <snip>:8767
    2010-10-30 04:23:18.784141|DEVELOP | | | TS3ANetwork::Connect failed error: 110
    2010-10-30 04:23:18.800653|WARNING |PktHandler | | detected incorrectly running system clock
    2010-10-30 04:23:18.801512|WARNING |PktHandler | | detected incorrectly running system clock
    2010-10-30 04:23:18.802383|WARNING |PktHandler | | detected incorrectly running system clock
    2010-10-30 04:23:18.803084|WARNING |PktHandler | | detected incorrectly running system clock
    2010-10-30 04:23:18.803903|WARNING |PktHandler | | detected incorrectly running system clock
    2010-10-30 04:23:18.804610|WARNING |PktHandler | | detected incorrectly running system clock
    2010-10-30 04:23:18.805315|WARNING |PktHandler | | detected incorrectly running system clock
    2010-10-30 04:23:18.805995|WARNING |PktHandler | | detected incorrectly running system clock
    2010-10-30 04:23:18.806696|WARNING |PktHandler | | detected incorrectly running system clock
    2010-10-30 04:23:18.822340|WARNING |PktHandler | | detected incorrectly running system clock
    2010-10-30 04:26:32.784340|DEVELOP | | | TS3ANetwork::Connect failed error: 110
    2010-10-30 04:26:32.803429|WARNING |PktHandler | | detected incorrectly running system clock
    2010-10-30 04:26:32.804290|WARNING |PktHandler | | detected incorrectly running system clock
    2010-10-30 04:26:32.805123|WARNING |PktHandler | | detected incorrectly running system clock
    2010-10-30 04:26:32.805821|WARNING |PktHandler | | detected incorrectly running system clock
    2010-10-30 04:26:32.806522|WARNING |PktHandler | | detected incorrectly running system clock
    2010-10-30 04:26:32.807343|WARNING |PktHandler | | detected incorrectly running system clock
    2010-10-30 04:26:32.808040|WARNING |PktHandler | | detected incorrectly running system clock
    2010-10-30 04:26:32.808741|WARNING |PktHandler | | detected incorrectly running system clock
    2010-10-30 04:26:32.809566|WARNING |PktHandler | | detected incorrectly running system clock
    2010-10-30 04:26:32.810387|WARNING |PktHandler | | detected incorrectly running system clock
    2010-10-30 04:26:33.138518|DEVELOP | | | TS3ANetwork::Send failed error: 1
    2010-10-30 04:26:33.138750|DEVELOP | | | TS3ANetwork::Send failed error: 1
    2010-10-30 04:26:35.038446|DEVELOP | | | TS3ANetwork::Send failed error: 1
    2010-10-30 04:26:35.038698|DEVELOP | | | TS3ANetwork::Send failed error: 1
    2010-10-30 04:26:37.038354|DEVELOP | | | TS3ANetwork::Send failed error: 1
    2010-10-30 04:26:37.038599|DEVELOP | | | TS3ANetwork::Send failed error: 1
    2010-10-30 04:29:44.861606|DEVELOP | | | TS3ANetwork::Connect failed error: 110
    2010-10-30 04:29:44.877595|WARNING |PktHandler | | detected incorrectly running system clock
    2010-10-30 04:29:44.878603|WARNING |PktHandler | | detected incorrectly running system clock
    2010-10-30 04:29:44.879442|WARNING |PktHandler | | detected incorrectly running system clock
    2010-10-30 04:29:44.887255|WARNING |PktHandler | | detected incorrectly running system clock


    ###################[ End of log ]#########################
    I'm not sure why it's whining about the system clock because there's nothing wrong with the clock, but I don't think that'd cause TS to do what it's doing.

    Anyone able to help?

  3. #18
    Join Date
    May 2010
    Posts
    6,310
    Hello

    Quote Originally Posted by Bomyne
    2010-10-30 04:20:02.962690|INFO |ServerLibPriv | | Server Version: 3.0.0-beta27 [Build: 12002], Linux
    An update (Beta-29) of your server should solve the problem.
    And think to open the 2008 TCP port (licence. Same without licence).

  4. #19
    Join Date
    October 2010
    Location
    Australia
    Posts
    3
    Quote Originally Posted by florian_fr40 View Post
    Hello



    An update (Beta-29) of your server should solve the problem.
    And think to open the 2008 TCP port (licence. Same without licence).
    Is there any automated way to update the server, either through teamspeak itself or CPGS, or will I have to do this manually?

  5. #20
    Join Date
    May 2010
    Posts
    6,310
    Manually :

    - Stop your teamspeak server
    - Download the latest version
    - Unzip and overwrite (in your server folder)
    - Start your teamspeak server.

  6. #21
    Join Date
    December 2009
    Location
    Germany, Cologne
    Posts
    1,363
    + Make a BackUp before you overwrite it.

  7. #22
    Join Date
    October 2010
    Location
    Australia
    Posts
    3
    I did that and it worked for a while then it crashed again. Server log shows this.

    ###################[ Beginning first 1000 lines from log ]##############

    [Sun Oct 31 10:33:09 2010] Launching server with the following commandline:
    # /home/<snip>/.gameservers/ts3_0//ts3server_linux_x86 query_port=8767

    TeamSpeak Server 3.0.0-beta29 [Build: 12473]
    (c)TeamSpeak Systems GmbH

    Logging started
    2010-10-31 02:33:09.889748|INFO |ServerLibPriv | | Server Version: 3.0.0-beta29 [Build: 12473], Linux
    2010-10-31 02:33:09.890170|INFO |DatabaseQuery | | dbPlugin name: SQLite3 plugin, Version 2, (c)TeamSpeak Systems GmbH
    2010-10-31 02:33:09.890262|INFO |DatabaseQuery | | dbPlugin version: 3.6.21
    2010-10-31 02:33:09.890647|INFO |DatabaseQuery | | checking database integrity (may take a while)
    2010-10-31 02:33:09.916665|INFO |SQL | | pruning old database log entries where timestamp is older than 90 days
    2010-10-31 02:33:09.967807|INFO |SQL | | updated permissions to version 7
    2010-10-31 02:33:09.986920|INFO |SQL | | updated permissions to version 8
    2010-10-31 02:33:10.383753|WARNING |Accounting | | Unable to find valid license key, falling back to limited functionality
    2010-10-31 02:33:10.449894|INFO |FileManager | | listening on <snipIP>
    2010-10-31 02:33:10.705473|INFO |VirtualServer | 1| listening on <snipIP>
    2010-10-31 02:33:10.706362|INFO |CIDRManager | | updated query_ip_whitelist ips: 127.0.0.1,
    2010-10-31 02:33:10.706980|INFO |Query | | listening on <snip>:8767
    2010-10-31 02:38:10.702899|DEVELOP | | | TS3ANetwork::Send failed error: 1
    2010-10-31 02:38:10.703141|DEVELOP | | | TS3ANetwork::Send failed error: 1
    2010-10-31 02:38:12.002843|DEVELOP | | | TS3ANetwork::Send failed error: 1
    2010-10-31 02:38:12.003080|DEVELOP | | | TS3ANetwork::Send failed error: 1
    2010-10-31 02:38:14.002774|DEVELOP | | | TS3ANetwork::Send failed error: 1
    2010-10-31 02:38:14.003020|DEVELOP | | | TS3ANetwork::Send failed error: 1
    2010-10-31 02:48:10.767836|DEVELOP | | | TS3ANetwork::Send failed error: 1
    2010-10-31 02:48:10.768079|DEVELOP | | | TS3ANetwork::Send failed error: 1
    2010-10-31 02:48:12.068765|DEVELOP | | | TS3ANetwork::Send failed error: 1
    2010-10-31 02:48:12.069009|DEVELOP | | | TS3ANetwork::Send failed error: 1
    2010-10-31 02:48:14.068707|DEVELOP | | | TS3ANetwork::Send failed error: 1
    2010-10-31 02:48:14.068950|DEVELOP | | | TS3ANetwork::Send failed error: 1
    2010-10-31 02:58:10.807787|DEVELOP | | | TS3ANetwork::Send failed error: 1
    2010-10-31 02:58:10.808029|DEVELOP | | | TS3ANetwork::Send failed error: 1
    2010-10-31 02:58:12.007727|DEVELOP | | | TS3ANetwork::Send failed error: 1
    2010-10-31 02:58:12.007967|DEVELOP | | | TS3ANetwork::Send failed error: 1
    2010-10-31 02:58:14.007666|DEVELOP | | | TS3ANetwork::Send failed error: 1
    2010-10-31 02:58:14.007914|DEVELOP | | | TS3ANetwork::Send failed error: 1
    2010-10-31 03:08:10.855755|DEVELOP | | | TS3ANetwork::Send failed error: 1
    2010-10-31 03:08:10.856004|DEVELOP | | | TS3ANetwork::Send failed error: 1
    2010-10-31 03:08:12.056680|DEVELOP | | | TS3ANetwork::Send failed error: 1
    2010-10-31 03:08:12.056923|DEVELOP | | | TS3ANetwork::Send failed error: 1
    2010-10-31 03:08:14.057610|DEVELOP | | | TS3ANetwork::Send failed error: 1
    2010-10-31 03:08:14.057851|DEVELOP | | | TS3ANetwork::Send failed error: 1
    2010-10-31 03:18:10.942704|DEVELOP | | | TS3ANetwork::Send failed error: 1
    2010-10-31 03:18:10.942947|DEVELOP | | | TS3ANetwork::Send failed error: 1
    2010-10-31 03:18:12.042666|DEVELOP | | | TS3ANetwork::Send failed error: 1
    2010-10-31 03:18:12.042907|DEVELOP | | | TS3ANetwork::Send failed error: 1
    2010-10-31 03:18:14.043566|DEVELOP | | | TS3ANetwork::Send failed error: 1
    2010-10-31 03:18:14.043803|DEVELOP | | | TS3ANetwork::Send failed error: 1
    2010-10-31 03:24:45.440710|DEVELOP | | | TS3ANetwork::Connect failed error: 110
    2010-10-31 03:24:45.440879|WARNING |ServerParser | | DEV-CHECK-1 PLEASE REPORT THIS LINE TO THE DEVELOPERS
    2010-10-31 03:24:45.467922|WARNING |PktHandler | | detected incorrectly running system clock
    2010-10-31 03:24:45.468917|WARNING |PktHandler | | detected incorrectly running system clock
    2010-10-31 03:24:45.469702|WARNING |PktHandler | | detected incorrectly running system clock
    2010-10-31 03:24:45.470448|WARNING |PktHandler | | detected incorrectly running system clock
    2010-10-31 03:24:45.471188|WARNING |PktHandler | | detected incorrectly running system clock
    2010-10-31 03:24:45.471942|WARNING |PktHandler | | detected incorrectly running system clock
    2010-10-31 03:24:45.472683|WARNING |PktHandler | | detected incorrectly running system clock
    2010-10-31 03:24:45.473405|WARNING |PktHandler | | detected incorrectly running system clock
    2010-10-31 03:24:45.474147|WARNING |PktHandler | | detected incorrectly running system clock
    2010-10-31 03:24:45.475029|WARNING |PktHandler | | detected incorrectly running system clock
    2010-10-31 03:24:45.476055|WARNING |PktHandler | | detected incorrectly running system clock
    2010-10-31 03:24:45.476816|WARNING |PktHandler | | detected incorrectly running system clock


    ###################[ End of log ]#########################

  8. #23
    Join Date
    December 2009
    Location
    Localhost
    Posts
    30
    No, this problem still is and will continue with the tire. How have the kernel
    2.6.33-grsec # 1 SMP Thu Mar 11 3:01:57 p.m. EST 2010 x86_64 GNU / Linux

  9. #24
    Join Date
    November 2006
    Location
    USA
    Posts
    55
    I am also getting this ERROR issue. I was getting this a few versions back and with an update it was solved. This has now shown up again since server version 29 was installed.

    11/1/2010 1:03:56 PM PktHandler Warning detected incorrectly running system clock

    I am reverting back to version 28 for a few days to verify that its the new version 29 causing it.
    Last edited by BobBart; November 1st, 2010 at 05:11 PM.

  10. #25
    Join Date
    November 2006
    Location
    USA
    Posts
    55
    Well its beyond a doubt related to server version 29. We have had absolutely no issues with drops, restarts, connection issues or the system clock error.

    Since reverting back to version 28

  11. #26
    Join Date
    July 2005
    Location
    SK
    Posts
    44
    Quote Originally Posted by BobBart View Post
    Well its beyond a doubt related to server version 29. We have had absolutely no issues with drops, restarts, connection issues or the system clock error.

    Since reverting back to version 28
    Well, I doubt. I have the same problem even with beta28. The same messages about incorrectly running system clock, and random crashes. But I'm pretty sure my system clock is correct, it is being syncronised by ntpd for more than half year. I checked logs, and there have been really minimal corrections, my delay is constantly about 7-8 miliseconds when comparing time with a few of stratum-1 servers...

    Strange is, I have never had this issue, until last week. It is just 2 or 3 days, that my TS3/beta28 keeps crashing...

  12. #27
    Join Date
    November 2006
    Location
    USA
    Posts
    55
    Strange that reverting solved it for me.

    I wonder if it had anything to do with the EU / US Daylight Savings times. EU changes there clocks before the US.
    Is there not data going back and forth from our servers to a master server? Perhaps that has something to do with it?

    I don't remember when EU clocks changed but I will look it up and check my logs. As i think about this I dont think it could be. My logs showed this error back to Sept. 29th I think and I dont think they changed there clocks that long ago, but I will keep this post up in case it gives someone another idea.

  13. #28
    Join Date
    July 2005
    Location
    SK
    Posts
    44
    I can definitelly confirm this problem is causing a lot of disconnects and server crashes. I temporary stopped time-syncronizing on my server, and beta28 is running without a problem for more than week.

    After I started ntpd, again I got a lot of messages:
    ...TS3ANetwork::Send failed error: 1
    ...detected incorrectly running system clock

    All users got kicked quite frequently, and TS3 server needed some time to "recover" till we were again allowed to log-in. Stopping ntpd again "fixed" the problem...

    BTW, I checked my ntpd.log, those time-adjustments are always very small, somewhere in order of 1-10ms or so. I think time-checking routine in TS3-server is somehow paranoid: it checkes time very frequently and gets mad if it discoveres a very minimal change. I think devs should reconsider this. Time-syncing is quite often used, actually a "must" on any serious server! TS3-server should accept it, and not consider every small time-change as cracking/cheating or whatever...

  14. #29
    Join Date
    November 2010
    Location
    Germany
    Posts
    18
    I also had this problem today for the first time. Server is always running. I'm using:
    Code:
    Server Version: 3.0.0-beta29 [Build: 12473], Linux
    dbPlugin name:    SQLite3 plugin, Version 2, (c)TeamSpeak Systems GmbH
    dbPlugin version: 3.6.21
    My log file looks like this:
    Code:
    [...nothing unusual...]
    2010-11-09 17:37:01.445705|INFO    |VirtualServer |  1| client connected 'USER_C'(id:280) from XXX.YYY.93.19:1044
    2010-11-09 18:04:09.247045|INFO    |VirtualServer |  1| client connected 'USER_B (-.-')'(id:161) from XXX.YYY.253.75:63975
    2010-11-09 18:22:41.550539|INFO    |VirtualServer |  1| client connected 'USER_A'(id:18) from XXX.YYY.131.9:54537
    2010-11-09 18:22:41.716720|INFO    |VirtualServer |  1| client connected 'USER_A1'(id:18) from XXX.YYY.131.9:60751
    2010-11-09 18:23:06.541253|INFO    |VirtualServer |  1| client disconnected 'USER_A'(id:18) reason 'reasonmsg=connection lost'
    2010-11-09 18:23:27.408166|INFO    |VirtualServer |  1| client disconnected 'USER_A1'(id:18) reason 'reasonmsg=Verlassen'
    2010-11-09 18:23:27.429959|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-11-09 18:23:28.735613|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-11-09 18:23:28.736722|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-11-09 18:23:28.737441|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-11-09 18:23:28.738153|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-11-09 18:23:28.738882|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-11-09 18:23:28.739625|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-11-09 18:23:28.740350|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-11-09 18:23:28.741142|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-11-09 18:23:28.744085|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-11-09 18:23:28.745055|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-11-09 18:23:28.763485|INFO    |VirtualServer |  1| client disconnected 'USER_SA'(id:2) reason 'reasonmsg=connection lost'
    2010-11-09 18:23:28.764642|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-11-09 18:23:28.765176|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-11-09 18:23:28.772419|INFO    |VirtualServer |  1| client connected 'USER_A'(id:18) from XXX.YYY.131.9:64503
    2010-11-09 18:23:28.776935|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-11-09 18:23:28.784078|INFO    |VirtualServer |  1| client disconnected 'USER_B (-.-')'(id:161) reason 'reasonmsg=connection lost'
    2010-11-09 18:23:28.790225|INFO    |VirtualServer |  1| client disconnected 'USER_C'(id:280) reason 'reasonmsg=connection lost'
    2010-11-09 18:23:28.796297|INFO    |VirtualServer |  1| client disconnected 'USER_A'(id:18) reason 'reasonmsg=connection lost'
    After this, the TS3 server died.

  15. #30
    Join Date
    November 2006
    Location
    USA
    Posts
    55
    I stand corrected.

    The server has failed with this error again and again since the rollback to v28

    PLEASE can support comment on this so we know they are looking into it.

Thread Information

Users Browsing this Thread

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

Similar Threads

  1. [Resolved] "Detected incorrectly running system clock" log message
    By Peter in forum Linux / FreeBSD
    Replies: 21
    Last Post: February 24th, 2019, 09:54 PM
  2. Replies: 1
    Last Post: August 19th, 2012, 12:30 AM
  3. Replies: 7
    Last Post: June 10th, 2011, 05:33 PM
  4. "detected incorrectly running system clock"
    By meliorus in forum Bug Reports [EN/DE]
    Replies: 43
    Last Post: February 3rd, 2011, 02:10 PM
  5. Replies: 8
    Last Post: December 26th, 2009, 10:26 AM

Posting Permissions

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