Forum

Results 1 to 6 of 6
  1. #1
    Join Date
    July 2014
    Posts
    24

    Server dropping Clients frequently

    Hey,

    In the last 2 Days my Teamspeak Server is dropping a lot of clients very often.
    I dont understand the reason, here are some parts of the logs:

    Code:
    2019-08-07 09:31:43.545738|INFO    |PktHandler    |1  |Terminating connection because of > 255 resends
    2019-08-07 09:31:43.545760|INFO    |PktHandler    |1  |Dropping client 26 because of resend timeout
    2019-08-07 09:31:43.545894|INFO    |PktHandler    |1  |Terminating connection because of > 255 resends
    2019-08-07 09:31:43.545913|INFO    |PktHandler    |1  |Dropping client 2 because of resend timeout
    2019-08-07 09:31:43.546139|INFO    |PktHandler    |1  |Terminating connection because of > 255 resends
    2019-08-07 09:31:43.546162|INFO    |PktHandler    |1  |Dropping client 40 because of resend timeout
    2019-08-07 09:32:36.975353|INFO    |PktHandler    |1  |Cleaning up connection because of 4 resends of COMMAND packet
    2019-08-07 09:32:36.975413|INFO    |PktHandler    |1  |Dropping client 39 because of resend timeout
    2019-08-07 09:32:59.073813|INFO    |PktHandler    |1  |Cleaning up connection because of 9 resends of COMMAND packet
    2019-08-07 09:32:59.073872|INFO    |PktHandler    |1  |Dropping client 50 because of resend timeout
    2019-08-07 09:48:07.200142|INFO    |PktHandler    |1  |Dropping client 41 because of ping timeout 19 0 0
    2019-08-07 09:54:19.878028|INFO    |PktHandler    |1  |Cleaning up connection because of 1 resends of COMMAND packet
    2019-08-07 09:54:19.878097|INFO    |PktHandler    |1  |Dropping client 28 because of resend timeout
    2019-08-07 10:01:36.011625|INFO    |PktHandler    |1  |Dropping client 13 because of ping timeout 19 0 0
    2019-08-07 12:04:19.121157|INFO    |PktHandler    |1  |Cleaning up connection because of 1 resends of COMMAND packet
    2019-08-07 12:04:19.135938|INFO    |PktHandler    |1  |Dropping client 32 because of resend timeout
    2019-08-07 12:04:39.555697|INFO    |PktHandler    |1  |Cleaning up connection because of 8 resends of COMMAND packet
    2019-08-07 12:04:39.555767|INFO    |PktHandler    |1  |Dropping client 33 because of resend timeout
    2019-08-07 12:10:15.914491|INFO    |PktHandler    |1  |Dropping client 57 because of ping timeout 19 0 0
    2019-08-07 12:47:57.784371|INFO    |PktHandler    |1  |Dropping client 52 because of ping timeout 19 0 0
    2019-08-07 12:47:57.790081|INFO    |PktHandler    |1  |Dropping client 59 because of ping timeout 19 0 0
    2019-08-07 13:09:49.697377|INFO    |PktHandler    |1  |Cleaning up connection because of 13 resends of COMMAND packet
    2019-08-07 13:09:49.697443|INFO    |PktHandler    |1  |Dropping client 6 because of resend timeout
    2019-08-07 15:04:14.286687|INFO    |PktHandler    |1  |Dropping client 88 because of ping timeout 19 0 0
    2019-08-07 15:26:08.191783|INFO    |PktHandler    |1  |Dropping client 83 because of ping timeout 19 0 0
    2019-08-07 15:26:08.192704|INFO    |PktHandler    |1  |Dropping client 84 because of ping timeout 19 0 0
    2019-08-07 16:17:42.627305|INFO    |PktHandler    |1  |Dropping client 47 because of ping timeout 19 0 0
    2019-08-07 16:44:18.361303|INFO    |PktHandler    |1  |Dropping client 45 because of ping timeout 19 0 0
    2019-08-07 16:44:18.369695|INFO    |PktHandler    |1  |Dropping client 48 because of ping timeout 19 0 0
    2019-08-07 16:51:17.940691|INFO    |PktHandler    |1  |Dropping client 18 because of ping timeout 19 0 0
    2019-08-07 17:01:35.562574|INFO    |PktHandler    |1  |Terminating connection because of > 255 resends
    2019-08-07 17:01:35.570645|INFO    |PktHandler    |1  |Dropping client 63 because of resend timeout
    2019-08-07 17:01:35.599632|INFO    |PktHandler    |1  |Terminating connection because of > 255 resends
    2019-08-07 17:01:35.599695|INFO    |PktHandler    |1  |Dropping client 105 because of resend timeout
    2019-08-07 17:01:35.644240|INFO    |PktHandler    |1  |Terminating connection because of > 255 resends
    2019-08-07 17:01:35.644298|INFO    |PktHandler    |1  |Dropping client 103 because of resend timeout
    2019-08-07 17:01:35.675946|INFO    |PktHandler    |1  |Terminating connection because of > 255 resends
    2019-08-07 17:01:35.676011|INFO    |PktHandler    |1  |Dropping client 72 because of resend timeout
    2019-08-07 17:01:35.730256|INFO    |PktHandler    |1  |Terminating connection because of > 255 resends
    2019-08-07 17:01:35.730329|INFO    |PktHandler    |1  |Dropping client 99 because of resend timeout

    Sometimes the logs getting filled with that as well:
    Code:
    2019-08-05 18:27:46.832259|WARNING |PktHandler    |   |detected incorrectly running system clock (<)
    2019-08-05 18:27:46.832321|WARNING |PktHandler    |   |detected incorrectly running system clock (<)
    2019-08-05 18:27:46.832351|WARNING |PktHandler    |   |detected incorrectly running system clock (<)
    2019-08-05 18:27:46.832374|WARNING |PktHandler    |   |detected incorrectly running system clock (<)
    2019-08-05 18:27:46.832422|WARNING |PktHandler    |   |detected incorrectly running system clock (<)
    2019-08-05 18:27:46.832446|WARNING |PktHandler    |   |detected incorrectly running system clock (<)
    2019-08-05 18:27:46.832471|WARNING |PktHandler    |   |detected incorrectly running system clock (<)
    2019-08-05 18:27:46.832493|WARNING |PktHandler    |   |detected incorrectly running system clock (<)
    2019-08-05 18:27:46.832518|WARNING |PktHandler    |   |detected incorrectly running system clock (<)
    2019-08-05 18:27:46.832543|WARNING |PktHandler    |   |detected incorrectly running system clock (<)
    2019-08-05 18:27:46.832574|WARNING |PktHandler    |   |detected incorrectly running system clock (<)
    2019-08-05 18:27:46.832600|WARNING |PktHandler    |   |detected incorrectly running system clock (<)
    2019-08-05 18:27:46.832624|WARNING |PktHandler    |   |detected incorrectly running system clock (<)
    2019-08-05 18:27:46.832645|WARNING |PktHandler    |   |detected incorrectly running system clock (<)
    2019-08-05 18:27:46.832670|WARNING |PktHandler    |   |detected incorrectly running system clock (<)
    2019-08-05 18:27:46.832692|WARNING |PktHandler    |   |detected incorrectly running system clock (<)
    2019-08-05 18:27:46.832716|WARNING |PktHandler    |   |detected incorrectly running system clock (<)
    What can be the reason for this? How to solve this?

  2. #2
    Join Date
    January 2017
    Location
    Switzerland
    Posts
    451
    This issue is possibly caused by your server...
    Try to check the server connection/bandwidth/traffic or contact your server provider.

    Otherwiese, someone is crashing it - make sure to update your server to the latest version: currently 3.9.1
    Last edited by MCG; August 8th, 2019 at 02:02 PM. Reason: typo

  3. #3
    Join Date
    February 2019
    Location
    Germany, Stuttgart
    Posts
    9
    Same issue here.
    Checked my server, ddos protection by provider, latest teamspeak version,
    reinstalled the teamspeak server. And so on...
    Unforgently still no fix
    HTML Code:
    2019-07-13 18:31:19.762641|INFO    |VirtualServer |1  |listening on 0.0.0.0:9987, [::]:9987
    2019-07-13 19:03:17.104975|INFO    |VirtualServer |1  |client (id:262) was removed from servergroup 'Server Admin'(id:9) by client 'Vxrious'(id:5)
    2019-07-13 19:03:27.309216|INFO    |VirtualServer |1  |client (id:262) was added to servergroup 'Server Admin'(id:9) by client 'Vxrious'(id:5)
    2019-07-13 19:41:44.803414|INFO    |PktHandler    |1  |Cleaning up connection because of 10 resends of COMMAND packet
    2019-07-13 19:41:44.803505|INFO    |PktHandler    |1  |Dropping client 28 because of resend timeout
    2019-07-13 19:41:46.489334|INFO    |PktHandler    |1  |Cleaning up connection because of 10 resends of COMMAND packet
    2019-07-13 19:41:46.489405|INFO    |PktHandler    |1  |Dropping client 1 because of resend timeout
    2019-07-13 19:41:46.490039|INFO    |PktHandler    |1  |Cleaning up connection because of 11 resends of COMMAND packet
    2019-07-13 19:41:46.490078|INFO    |PktHandler    |1  |Dropping client 2 because of resend timeout

  4. #4
    Join Date
    January 2017
    Location
    Switzerland
    Posts
    451
    daaamn... I've also seen some big servers today where the clients just timed out, like a hundred clients in 3 seconds. - well that's confirmed now, it's not caused by our servers/versions.

    Maybe cloudflare? @Staff - statement?

    I also can't explain that to myself, since I've seen this

    Name:  zz4aECx.png
Views: 209
Size:  36.5 KB

  5. #5
    Join Date
    July 2014
    Posts
    24
    I am on Server Version 3.9.1 and i am running a Gameserver on the exact same server that runs the Teamspeak Server.
    When the Client drop on Teamspeak happens, everything is still working on the gameserver.
    That means that the connection of the server is still working, but only for teamspeak its losing connection.

  6. #6
    Join Date
    August 2019
    Location
    Germany
    Posts
    1
    Hello Guys,

    We have the same Problem on our Server. But its a bit Strange.

    First of all, the Server has been updated AFTER the problem occured the first time to the newest Version (3.9.1).
    The Problem was that all Actions that handle rights in the Teamspeak were causing timeouts.(Before ive updated the Server.)
    Now, after the Update its different.

    If i want to give somebody talkpower im timing out. Same with editing rights.
    I have updated the complete Server, all pkgs etc. and the Protection (DDOS) seems not to make any difference. Its still happening all the time. Im from Germany so my English isnt the best, but i hope its understandable.

    Thanks a lot.

    If its making any difference i can attach a Video.

    ------------Merged

    Here is a Picture from the Log. I Hope you can see something on it.

    ------------Merged

    Just look at your hwclock. It has to be the right time. After i fixed it, its working.

    How to fix it:

    [email protected]:~# sudo hwclock
    Mi 21 Aug 2019 13:21:31 CEST -0.844034 seconds (Heres 12.30 -> Server thinks its 13.30 so the Server Time is wrong.)

    [email protected]:~# sudo timedatectl set-time 12:30 (Here im setting the time to 12.30)

    [email protected]:~# sudo hwclock --systohc (Here your setting the time to 12.30 on the Hardwareclock)



    -> NOW Restart your Server. And it should work.

    ------------------------------------------------------------------------------------------------------------------------------------------

    Actual it only fixed the Permission Issue.
    Sometimes the Server still dropps Clients.
    Cant figure more out, its Strange.


    It would be nice if somebody could help. I cant give somebody Talk Power, Change Channel Settings or Send text messages in the Channel Chat. Every time were doing that, the Server dropps us.
    Last edited by ReScUe; August 23rd, 2019 at 10:39 AM. Reason: Edited because of new Infos

Thread Information

Users Browsing this Thread

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

Similar Threads

  1. Replies: 1
    Last Post: August 29th, 2018, 07:48 PM
  2. Hosting TS3 server on a laptop, dropping clients.
    By Metabo in forum Server Support
    Replies: 1
    Last Post: October 20th, 2017, 02:09 AM
  3. Virtual Server dropping clients.
    By dbz28 in forum Linux / FreeBSD
    Replies: 4
    Last Post: November 15th, 2014, 12:48 AM
  4. [Resolved] Server randomly dropping all clients
    By quenoz in forum Linux / FreeBSD
    Replies: 3
    Last Post: March 24th, 2012, 11:50 AM
  5. Server randomly dropping all clients
    By quenoz in forum Bug Reports [EN/DE]
    Replies: 1
    Last Post: March 23rd, 2012, 07:49 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
  •