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 11 of 11

Thread: TS3 is closing.

  1. #1
    Join Date
    February 2013
    Posts
    10

    Question TS3 server instance is closing.

    Hey guys.
    My Teamspeak server process is closing randomly.

    2013-02-16 01:07:35.626898|INFO |VirtualServer | 1| client disconnected 'Ganjaman'(id:7) reason 'reasonmsg=Server Shutdown!'
    2013-02-16 01:07:35.627200|INFO |VirtualServer | 1| client disconnected 'UNSTERN'(id:15) reason 'reasonmsg=Server Shutdown!'
    2013-02-16 01:07:35.809099|INFO |VirtualServer | 1| stopped
    2013-02-14 22:15:12.093307|INFO |VirtualServer | 1| client disconnected 'schoschy'(id:2) reason 'reasonmsg=Server Shutdown!'
    2013-02-14 22:15:12.093597|INFO |VirtualServer | 1| client disconnected 'Ganjaman'(id:7) reason 'reasonmsg=Server Shutdown!'
    2013-02-14 22:15:12.220305|INFO |VirtualServer | 1| stopped
    Now we come to the point: why is the server closing, while i'm asleep? :D

    Someone got an idea, how to figure out the problem?

    The current ts is running under Ubuntu 12.04.2 LTS (GNU/Linux 3.2.0-37-generic x86_64), with all updates. The server is nearly blank.

    Version of Teamspeak:
    3.0.6.1 (29.06.2012 09:59:05) on Linux
    License:
    Non-profit license

    Thanks for help and a good morning to everyone,
    SCHoschY.

    Edit 1: "I'm actually thinking of an problem with my license.
    I had TS3 running without an license for about 2 weeks and put it on than. ~ 5 days ago.
    This fits with the problem, in my opinion.

    Is TS3 server shutting down, if the license packages get blocked by the firewall in some way?"

    Edit 2: #9
    I actually figured out the problem, but I don't know, how to fix that.
    So if I set my Linux Firewall INPUT to drop all, with the TS3 ports allowed, than the sid=1 is closing. ->200 slots. with 32 slots it isn't.
    If I set that INPUT to Accept all, than it is not closing, while its running on 200 slots.

    What i have noticed is, that if i Drop the INPUT, it needs several seconds to connect.
    <08:35:26> Trying to resolve hostname x
    <08:35:30> Trying to connect to server on x
    <08:35:30> Connected to Server: y
    looks like 4 seconds.

    with Accept INPUT:
    <08:41:57> Trying to resolve hostname x
    <08:41:57> Trying to connect to server on x
    <08:41:57> Connected to Server: y
    looks like instant.

    So should i try a new firewall, or is that a known thing, whit a short fixable way?

    SCHoschY

    E: here is the log:
    2013-02-16 02:49:15.229961|INFO |ServerLibPriv | | TeamSpeak 3 Server 3.0.6.1 (2012-06-29 07:59:05)
    2013-02-16 02:49:15.230562|INFO |DatabaseQuery | | dbPlugin name: SQLite3 plugin, Version 2, (c)TeamSpeak Systems GmbH
    2013-02-16 02:49:15.230627|INFO |DatabaseQuery | | dbPlugin version: 3.7.3
    2013-02-16 02:49:15.231138|INFO |DatabaseQuery | | checking database integrity (may take a while)
    2013-02-16 02:49:15.403062|INFO |Accounting | | Licensing Information
    2013-02-16 02:49:15.403142|INFO |Accounting | | type : Non-profit
    2013-02-16 02:49:15.403238|INFO |Accounting | | starting date : Wed Nov 21 00:00:00 2012
    2013-02-16 02:49:15.403340|INFO |Accounting | | ending date : Sat May 25 00:00:00 2013
    2013-02-16 02:49:15.403391|INFO |Accounting | | max virtualservers: 10
    2013-02-16 02:49:15.403434|INFO |Accounting | | max slots : 512
    2013-02-16 02:49:15.422257|INFO |FileManager | | listening on 0.0.0.0:30033
    2013-02-16 02:49:15.475360|INFO |CIDRManager | | updated query_ip_whitelist ips: 127.0.0.1,
    2013-02-16 02:49:15.476300|INFO |Query | | listening on 0.0.0.0:10011
    2013-02-16 03:50:01.545698|ERROR | | | TS3ANetwork::ResolveHostName failed error: -3 (Temporary failure in name resolution) 11
    2013-02-16 03:51:04.699466|ERROR | | | TS3ANetwork::Connect failed error: 110
    2013-02-16 04:51:50.698696|ERROR | | | TS3ANetwork::ResolveHostName failed error: -3 (Temporary failure in name resolution) 11
    2013-02-16 04:52:53.819553|ERROR | | | TS3ANetwork::Connect failed error: 110
    2013-02-16 05:53:39.823741|ERROR | | | TS3ANetwork::ResolveHostName failed error: -3 (Temporary failure in name resolution) 11
    2013-02-16 05:54:42.939559|ERROR | | | TS3ANetwork::Connect failed error: 110
    2013-02-16 06:55:28.919189|ERROR | | | TS3ANetwork::ResolveHostName failed error: -3 (Temporary failure in name resolution) 11
    2013-02-16 06:56:32.059562|ERROR | | | TS3ANetwork::Connect failed error: 110
    2013-02-16 07:57:18.036070|ERROR | | | TS3ANetwork::ResolveHostName failed error: -3 (Temporary failure in name resolution) 11
    2013-02-16 07:58:21.179524|ERROR | | | TS3ANetwork::Connect failed error: 110
    2013-02-16 08:59:07.127736|ERROR | | | TS3ANetwork::ResolveHostName failed error: -3 (Temporary failure in name resolution) 11
    2013-02-16 09:00:10.235567|ERROR | | | TS3ANetwork::Connect failed error: 110
    2013-02-16 10:00:56.210341|ERROR | | | TS3ANetwork::ResolveHostName failed error: -3 (Temporary failure in name resolution) 11
    2013-02-16 10:01:59.291557|ERROR | | | TS3ANetwork::Connect failed error: 110
    2013-02-16 11:02:45.285720|ERROR | | | TS3ANetwork::ResolveHostName failed error: -3 (Temporary failure in name resolution) 11
    2013-02-16 11:03:48.411498|ERROR | | | TS3ANetwork::Connect failed error: 110
    2013-02-16 12:04:34.405630|ERROR | | | TS3ANetwork::ResolveHostName failed error: -3 (Temporary failure in name resolution) 11
    2013-02-16 12:05:37.531555|ERROR | | | TS3ANetwork::Connect failed error: 110
    2013-02-16 13:06:23.506128|ERROR | | | TS3ANetwork::ResolveHostName failed error: -3 (Temporary failure in name resolution) 11
    2013-02-16 13:07:26.587567|ERROR | | | TS3ANetwork::Connect failed error: 110
    2013-02-16 14:08:12.576050|ERROR | | | TS3ANetwork::ResolveHostName failed error: -3 (Temporary failure in name resolution) 11
    2013-02-16 14:09:15.707563|ERROR | | | TS3ANetwork::Connect failed error: 110
    2013-02-16 15:10:01.701470|ERROR | | | TS3ANetwork::ResolveHostName failed error: -3 (Temporary failure in name resolution) 11
    2013-02-16 15:11:04.827556|ERROR | | | TS3ANetwork::Connect failed error: 110
    2013-02-16 16:11:50.808547|ERROR | | | TS3ANetwork::ResolveHostName failed error: -3 (Temporary failure in name resolution) 11
    2013-02-16 16:12:53.947486|ERROR | | | TS3ANetwork::Connect failed error: 110
    2013-02-16 17:13:39.859562|ERROR | | | TS3ANetwork::ResolveHostName failed error: -3 (Temporary failure in name resolution) 11
    2013-02-16 17:14:43.003557|ERROR | | | TS3ANetwork::Connect failed error: 110
    2013-02-16 18:15:28.969644|ERROR | | | TS3ANetwork::ResolveHostName failed error: -3 (Temporary failure in name resolution) 11
    2013-02-16 18:16:32.123455|ERROR | | | TS3ANetwork::Connect failed error: 110
    2013-02-16 19:17:18.110077|ERROR | | | TS3ANetwork::ResolveHostName failed error: -3 (Temporary failure in name resolution) 11
    2013-02-16 19:18:21.243530|ERROR | | | TS3ANetwork::Connect failed error: 110
    2013-02-16 20:19:07.229261|ERROR | | | TS3ANetwork::ResolveHostName failed error: -3 (Temporary failure in name resolution) 11
    2013-02-16 20:20:10.363560|ERROR | | | TS3ANetwork::Connect failed error: 110
    2013-02-16 21:20:56.360963|ERROR | | | TS3ANetwork::ResolveHostName failed error: -3 (Temporary failure in name resolution) 11
    2013-02-16 21:21:59.483453|ERROR | | | TS3ANetwork::Connect failed error: 110
    2013-02-16 22:22:45.465777|ERROR | | | TS3ANetwork::ResolveHostName failed error: -3 (Temporary failure in name resolution) 11
    2013-02-16 22:23:48.603561|ERROR | | | TS3ANetwork::Connect failed error: 110
    2013-02-16 23:24:34.579066|ERROR | | | TS3ANetwork::ResolveHostName failed error: -3 (Temporary failure in name resolution) 11
    2013-02-16 23:25:37.723554|ERROR | | | TS3ANetwork::Connect failed error: 110
    2013-02-17 00:26:23.708519|ERROR | | | TS3ANetwork::ResolveHostName failed error: -3 (Temporary failure in name resolution) 11
    2013-02-17 00:27:26.843555|ERROR | | | TS3ANetwork::Connect failed error: 110
    2013-02-17 01:28:12.808069|ERROR | | | TS3ANetwork::ResolveHostName failed error: -3 (Temporary failure in name resolution) 11
    2013-02-17 01:29:15.899562|ERROR | | | TS3ANetwork::Connect failed error: 110
    2013-02-17 02:30:01.885605|ERROR | | | TS3ANetwork::ResolveHostName failed error: -3 (Temporary failure in name resolution) 11
    2013-02-17 02:31:05.019562|ERROR | | | TS3ANetwork::Connect failed error: 110
    2013-02-17 03:31:50.995009|ERROR | | | TS3ANetwork::ResolveHostName failed error: -3 (Temporary failure in name resolution) 11
    2013-02-17 03:32:54.139565|ERROR | | | TS3ANetwork::Connect failed error: 110
    2013-02-17 04:33:00.113658|ERROR |Accounting | | not started, shutting down!
    2013-02-17 07:35:24.432654|ERROR |ParamParser | | Protocol mismatch, old client or old server?
    2013-02-17 07:35:28.960799|ERROR |ParamParser | | Protocol mismatch, old client or old server?
    2013-02-17 07:35:46.872999|INFO |VirtualSvrMgr | | startServer() VirtualServer(1) started
    2013-02-17 07:36:34.283200|ERROR | | | TS3ANetwork::ResolveHostName failed error: -3 (Temporary failure in name resolution) 11
    2013-02-17 07:37:37.403502|ERROR | | | TS3ANetwork::Connect failed error: 110
    Last edited by SCHoschKOPP; February 17th, 2013 at 09:05 AM.

  2. #2
    Join Date
    April 2011
    Location
    Germany
    Posts
    1,266
    There might be many possibilities. The server which runs your teamspeak is rebooting or the server is going into sleep mode. With that little information it is quite difficult to find the right answer. Have to tried to check the system logs of any event occurs at that time?

  3. #3
    Join Date
    February 2013
    Posts
    10
    Quote Originally Posted by Barungar View Post
    There might be many possibilities. The server which runs your teamspeak is rebooting or the server is going into sleep mode. With that little information it is quite difficult to find the right answer. Have to tried to check the system logs of any event occurs at that time?
    already did that, without finding something.

    I'm actually thinking of an problem with my license.
    I had TS3 running without an license for about 2 weeks and put it on than. ~ 5 days ago.
    This fits with the problem, in my opinion.

    Is TS3 server shutting down, if the license packages get blocked by the firewall in some way?

    Thanks,
    SCHoschY

  4. #4
    Join Date
    April 2011
    Location
    Germany
    Posts
    1,266
    If it is an issue with the licensing server then you should find some errors in the teamspeak server's log just before shutting down.

  5. #5
    Join Date
    February 2013
    Posts
    10
    Quote Originally Posted by Barungar View Post
    If it is an issue with the licensing server then you should find some errors in the teamspeak server's log just before shutting down.
    I didn't get any errors at all. all i got before the server shut down, you can see in #1

    The server process is running, only the VS is getting closed (also seen in the log on #1). -> that why i thought, the license is the problem.

  6. #6
    Join Date
    April 2011
    Location
    Germany
    Posts
    1,266
    Could it be that someone issued the "serverstop" comand?!

  7. #7
    Join Date
    February 2013
    Posts
    10
    Thought i'm the only admin here, no?

  8. #8
    Join Date
    April 2009
    Location
    Germany
    Posts
    173
    Have you tried running the TS3 Server without Firewall? Or with an Configurated Firewall with TS3 Open ports ?

    http://support.teamspeakusa.com/inde...k-3-server-use

    Still the same Problem ?
    And/ore is your Hoster changing his Rules for TS3 Using?

  9. #9
    Join Date
    February 2013
    Posts
    10
    I actually figured out the problem, but I don't know, how to fix that.
    So if I set my Linux Firewall INPUT to drop all, with the TS3 ports allowed, than the sid=1 is closing. ->200 slots. with 32 slots it isn't.
    If I set that INPUT to Accept all, than it is not closing, while its running on 200 slots.

    What i have noticed is, that if i Drop the INPUT, it needs several seconds to connect.
    <08:35:26> Trying to resolve hostname x
    <08:35:30> Trying to connect to server on x
    <08:35:30> Connected to Server: y
    looks like 4 seconds.

    with Accept INPUT:
    <08:41:57> Trying to resolve hostname x
    <08:41:57> Trying to connect to server on x
    <08:41:57> Connected to Server: y
    looks like instant.

    So should i try a new firewall, or is that a known thing, whit a short fixable way?

    SCHoschY

    E: here is the log:
    2013-02-16 02:49:15.229961|INFO |ServerLibPriv | | TeamSpeak 3 Server 3.0.6.1 (2012-06-29 07:59:05)
    2013-02-16 02:49:15.230562|INFO |DatabaseQuery | | dbPlugin name: SQLite3 plugin, Version 2, (c)TeamSpeak Systems GmbH
    2013-02-16 02:49:15.230627|INFO |DatabaseQuery | | dbPlugin version: 3.7.3
    2013-02-16 02:49:15.231138|INFO |DatabaseQuery | | checking database integrity (may take a while)
    2013-02-16 02:49:15.403062|INFO |Accounting | | Licensing Information
    2013-02-16 02:49:15.403142|INFO |Accounting | | type : Non-profit
    2013-02-16 02:49:15.403238|INFO |Accounting | | starting date : Wed Nov 21 00:00:00 2012
    2013-02-16 02:49:15.403340|INFO |Accounting | | ending date : Sat May 25 00:00:00 2013
    2013-02-16 02:49:15.403391|INFO |Accounting | | max virtualservers: 10
    2013-02-16 02:49:15.403434|INFO |Accounting | | max slots : 512
    2013-02-16 02:49:15.422257|INFO |FileManager | | listening on 0.0.0.0:30033
    2013-02-16 02:49:15.475360|INFO |CIDRManager | | updated query_ip_whitelist ips: 127.0.0.1,
    2013-02-16 02:49:15.476300|INFO |Query | | listening on 0.0.0.0:10011
    2013-02-16 03:50:01.545698|ERROR | | | TS3ANetwork::ResolveHostName failed error: -3 (Temporary failure in name resolution) 11
    2013-02-16 03:51:04.699466|ERROR | | | TS3ANetwork::Connect failed error: 110
    2013-02-16 04:51:50.698696|ERROR | | | TS3ANetwork::ResolveHostName failed error: -3 (Temporary failure in name resolution) 11
    2013-02-16 04:52:53.819553|ERROR | | | TS3ANetwork::Connect failed error: 110
    2013-02-16 05:53:39.823741|ERROR | | | TS3ANetwork::ResolveHostName failed error: -3 (Temporary failure in name resolution) 11
    2013-02-16 05:54:42.939559|ERROR | | | TS3ANetwork::Connect failed error: 110
    2013-02-16 06:55:28.919189|ERROR | | | TS3ANetwork::ResolveHostName failed error: -3 (Temporary failure in name resolution) 11
    2013-02-16 06:56:32.059562|ERROR | | | TS3ANetwork::Connect failed error: 110
    2013-02-16 07:57:18.036070|ERROR | | | TS3ANetwork::ResolveHostName failed error: -3 (Temporary failure in name resolution) 11
    2013-02-16 07:58:21.179524|ERROR | | | TS3ANetwork::Connect failed error: 110
    2013-02-16 08:59:07.127736|ERROR | | | TS3ANetwork::ResolveHostName failed error: -3 (Temporary failure in name resolution) 11
    2013-02-16 09:00:10.235567|ERROR | | | TS3ANetwork::Connect failed error: 110
    2013-02-16 10:00:56.210341|ERROR | | | TS3ANetwork::ResolveHostName failed error: -3 (Temporary failure in name resolution) 11
    2013-02-16 10:01:59.291557|ERROR | | | TS3ANetwork::Connect failed error: 110
    2013-02-16 11:02:45.285720|ERROR | | | TS3ANetwork::ResolveHostName failed error: -3 (Temporary failure in name resolution) 11
    2013-02-16 11:03:48.411498|ERROR | | | TS3ANetwork::Connect failed error: 110
    2013-02-16 12:04:34.405630|ERROR | | | TS3ANetwork::ResolveHostName failed error: -3 (Temporary failure in name resolution) 11
    2013-02-16 12:05:37.531555|ERROR | | | TS3ANetwork::Connect failed error: 110
    2013-02-16 13:06:23.506128|ERROR | | | TS3ANetwork::ResolveHostName failed error: -3 (Temporary failure in name resolution) 11
    2013-02-16 13:07:26.587567|ERROR | | | TS3ANetwork::Connect failed error: 110
    2013-02-16 14:08:12.576050|ERROR | | | TS3ANetwork::ResolveHostName failed error: -3 (Temporary failure in name resolution) 11
    2013-02-16 14:09:15.707563|ERROR | | | TS3ANetwork::Connect failed error: 110
    2013-02-16 15:10:01.701470|ERROR | | | TS3ANetwork::ResolveHostName failed error: -3 (Temporary failure in name resolution) 11
    2013-02-16 15:11:04.827556|ERROR | | | TS3ANetwork::Connect failed error: 110
    2013-02-16 16:11:50.808547|ERROR | | | TS3ANetwork::ResolveHostName failed error: -3 (Temporary failure in name resolution) 11
    2013-02-16 16:12:53.947486|ERROR | | | TS3ANetwork::Connect failed error: 110
    2013-02-16 17:13:39.859562|ERROR | | | TS3ANetwork::ResolveHostName failed error: -3 (Temporary failure in name resolution) 11
    2013-02-16 17:14:43.003557|ERROR | | | TS3ANetwork::Connect failed error: 110
    2013-02-16 18:15:28.969644|ERROR | | | TS3ANetwork::ResolveHostName failed error: -3 (Temporary failure in name resolution) 11
    2013-02-16 18:16:32.123455|ERROR | | | TS3ANetwork::Connect failed error: 110
    2013-02-16 19:17:18.110077|ERROR | | | TS3ANetwork::ResolveHostName failed error: -3 (Temporary failure in name resolution) 11
    2013-02-16 19:18:21.243530|ERROR | | | TS3ANetwork::Connect failed error: 110
    2013-02-16 20:19:07.229261|ERROR | | | TS3ANetwork::ResolveHostName failed error: -3 (Temporary failure in name resolution) 11
    2013-02-16 20:20:10.363560|ERROR | | | TS3ANetwork::Connect failed error: 110
    2013-02-16 21:20:56.360963|ERROR | | | TS3ANetwork::ResolveHostName failed error: -3 (Temporary failure in name resolution) 11
    2013-02-16 21:21:59.483453|ERROR | | | TS3ANetwork::Connect failed error: 110
    2013-02-16 22:22:45.465777|ERROR | | | TS3ANetwork::ResolveHostName failed error: -3 (Temporary failure in name resolution) 11
    2013-02-16 22:23:48.603561|ERROR | | | TS3ANetwork::Connect failed error: 110
    2013-02-16 23:24:34.579066|ERROR | | | TS3ANetwork::ResolveHostName failed error: -3 (Temporary failure in name resolution) 11
    2013-02-16 23:25:37.723554|ERROR | | | TS3ANetwork::Connect failed error: 110
    2013-02-17 00:26:23.708519|ERROR | | | TS3ANetwork::ResolveHostName failed error: -3 (Temporary failure in name resolution) 11
    2013-02-17 00:27:26.843555|ERROR | | | TS3ANetwork::Connect failed error: 110
    2013-02-17 01:28:12.808069|ERROR | | | TS3ANetwork::ResolveHostName failed error: -3 (Temporary failure in name resolution) 11
    2013-02-17 01:29:15.899562|ERROR | | | TS3ANetwork::Connect failed error: 110
    2013-02-17 02:30:01.885605|ERROR | | | TS3ANetwork::ResolveHostName failed error: -3 (Temporary failure in name resolution) 11
    2013-02-17 02:31:05.019562|ERROR | | | TS3ANetwork::Connect failed error: 110
    2013-02-17 03:31:50.995009|ERROR | | | TS3ANetwork::ResolveHostName failed error: -3 (Temporary failure in name resolution) 11
    2013-02-17 03:32:54.139565|ERROR | | | TS3ANetwork::Connect failed error: 110
    2013-02-17 04:33:00.113658|ERROR |Accounting | | not started, shutting down!
    2013-02-17 07:35:24.432654|ERROR |ParamParser | | Protocol mismatch, old client or old server?
    2013-02-17 07:35:28.960799|ERROR |ParamParser | | Protocol mismatch, old client or old server?
    2013-02-17 07:35:46.872999|INFO |VirtualSvrMgr | | startServer() VirtualServer(1) started
    2013-02-17 07:36:34.283200|ERROR | | | TS3ANetwork::ResolveHostName failed error: -3 (Temporary failure in name resolution) 11
    2013-02-17 07:37:37.403502|ERROR | | | TS3ANetwork::Connect failed error: 110
    Last edited by SCHoschKOPP; February 17th, 2013 at 09:04 AM.

  10. #10
    Join Date
    April 2011
    Location
    Germany
    Posts
    1,266
    The problem is clearly that your TeamSpeak Server loses the connection to the licensing server. You might want to check the firewall settings for outgoing rules and/or your dns configuration on your server (because of "Temporary failure in name resolution").

  11. #11
    Join Date
    February 2013
    Posts
    10
    looks like there are some ports more than only 9987 10011 and 30033
    Thanks Barungar for that tip.
    missing was:
    Default weblist port (UDP out): 2010
    Default tsdns port (TCP in): 41144
    Default accounting port (TCP out): 2008

Thread Information

Users Browsing this Thread

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

Similar Threads

  1. Teamspeak closing
    By lupine1990 in forum Windows
    Replies: 0
    Last Post: April 10th, 2014, 10:50 PM
  2. Server keeps closing...
    By karimali831 in forum Linux / FreeBSD
    Replies: 1
    Last Post: April 21st, 2010, 08:31 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
  •