Forum


Notice to all users

We are migrating towards a new forum system located at community.teamspeak.com, as such this forum will become read-only on January 29, 2020

Results 1 to 5 of 5
  1. #1
    Join Date
    June 2016
    Posts
    6

    "Connection Lost" for Multiple Clients

    Edit 3/8/17: The following was taken from the server logs:
    PktHandler |1 |Terminating connection because of > 255 resends
    PktHandler |1 |Dropping client * because of resend timeout
    Been experiencing this on and off over a period of several months, pretty fed up with not being able to solve it:
    <20:38:35> "Jaaryn" dropped (connection lost)
    <20:39:06> "Jaaryn" connected to channel "Staff"
    <20:42:41> "Iron Pichu" dropped (connection lost)
    <20:42:41> "ddReaper_666" dropped (connection lost)
    <20:42:41> "FlimFlamFanMan" dropped (connection lost)
    <20:42:41> "Ambrose/Malik" dropped (connection lost)
    <20:42:42> "Factor" dropped (connection lost)
    <20:42:42> "Jesus" dropped (connection lost)
    <20:42:42> "halomantis" dropped (connection lost)
    <20:42:42> "Mineymonkey" dropped (connection lost)
    <20:43:11> Connection to server lost
    <20:43:12> Trying to resolve hostname ts.arcticdoge.com
    <20:43:13> Trying to connect to server on ts.arcticdoge.com
    <20:43:14> www.arcticdoge.com
    <20:43:14> Connected to Server: "Arctic Doge (www.arcticdoge.com)"

    Server Host:
    Google Cloud Platform (virtual server running Ubuntu 16.04)
    Specs: 1 Ghz Intel processor, 1 GB RAM, (at least) 100 Mbps synchronous connection.

    I can't tell if it's the TeamSpeak configuration, Ubuntu configuration or a network problem, the only thing I'm able to identify is a small increase in CPU, Disk and Network usage during these events. I would greatly appreciate any suggestions on how to troubleshoot this issue.


    Thank you,
    Seathre
    Last edited by Seathre; March 8th, 2017 at 01:17 PM.

  2. #2
    Join Date
    June 2016
    Posts
    6
    Update: Still experiencing the same issue, some or all users will lose connection/timeout and reconnect a few seconds later. I haven't been able to identify any patterns, the system resource increase I mentioned in the first post doesn't appear to be related. Still leaning towards this being a network issue, but exploring all avenues.

    Update 2: Just saw this in my logs: http://pastebin.com/d1dpU8Br
    Last edited by Seathre; March 8th, 2017 at 12:40 AM.

  3. #3
    Join Date
    June 2016
    Posts
    6
    Issue still occurring. Working closely with engineers at Google Cloud to determine whether it is actually a network problem. I will continue to update this thread on the situation.

  4. #4
    Join Date
    June 2016
    Posts
    6
    So far, the issue does not seem to be network-related. I'm beginning to suspect it is a software issue, either with the Operating System configuration or the TeamSpeak server configuration. The issue has not happened for a few weeks, beginning to wonder if it'll reappear.

  5. #5
    Join Date
    June 2016
    Posts
    6
    It's looking to be NTP related:
    2017-04-13 03:51:49.553013|WARNING |PktHandler | |detected incorrectly running system clock (<)2017-04-13 03:51:49.553036|WARNING |PktHandler | |detected incorrectly running system clock (<)
    2017-04-13 03:51:49.553611|WARNING |PktHandler | |detected incorrectly running system clock (<)
    2017-04-13 03:51:49.553688|WARNING |PktHandler | |detected incorrectly running system clock (<)
    2017-04-13 03:51:49.554212|WARNING |PktHandler | |detected incorrectly running system clock (<)
    2017-04-13 03:51:49.554488|WARNING |PktHandler | |detected incorrectly running system clock (<)
    2017-04-13 03:51:49.554512|WARNING |PktHandler | |detected incorrectly running system clock (<)
    2017-04-13 03:51:49.554891|WARNING |PktHandler | |detected incorrectly running system clock (<)
    2017-04-13 03:51:49.554996|WARNING |PktHandler | |detected incorrectly running system clock (<)
    2017-04-13 03:51:49.590420|WARNING |PktHandler | |detected incorrectly running system clock (<)
    I've implemented a possible fixed, found here: http://forum.teamspeak.com/threads/1...ot-log-message
    Add "tinker step 0" to your NTP config.

    I do feel as though I have to give a lot of credit to the engineers at Google whom I've been going back and forth with. Without their help, I'd likely still be at square one on this.

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: November 9th, 2013, 11:36 AM
  2. Replies: 2
    Last Post: October 31st, 2013, 10:26 PM
  3. Replies: 1
    Last Post: July 2nd, 2011, 09:24 PM
  4. Replies: 5
    Last Post: June 29th, 2011, 11:51 PM
  5. [No Bug] Updated to "Beta Channel" version, reverted, "lost" my contacts
    By Nev0r in forum Client Support
    Replies: 3
    Last Post: March 21st, 2011, 01:02 PM

Posting Permissions

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