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
  1. #1
    Join Date
    October 2010
    Location
    Chile
    Posts
    2

    Server Shutdown sporadically

    Code:
    2010-10-15 10:18:19.364102|INFO    |ServerMain    |   | Received signal SIGTERM, shutting down.
    2010-10-22 22:32:46.146775|ERROR   |              |   | read invalid packet size size
    2010-10-23 00:37:51.864220|DEVELOP |              |   | TS3ANetwork::Connect failed error: 110
    2010-10-23 19:26:35.174861|INFO    |ServerMain    |   | Received signal SIGTERM, shutting down.
    2010-10-23 19:26:41.149511|INFO    |VirtualServer |  1| stopped
    2010-10-23 19:26:41.291497|INFO    |VirtualServer |  2| stopped
    2010-10-23 19:26:41.685525|INFO    |VirtualServer |  5| stopped
    2010-10-23 19:26:41.887245|INFO    |VirtualServer |  6| stopped
    2010-10-23 19:26:42.085842|INFO    |VirtualServer |  7| stopped
    2010-10-23 21:02:41.326631|WARNING |ServerParser  |   | DEV-CHECK-1 PLEASE REPORT THIS LINE TO THE DEVELOPERS
    2010-10-23 21:41:59.528514|INFO    |ServerMain    |   | Received signal SIGINT, shutting down.
    2010-10-23 21:43:14.204058|ERROR   |              |   | read invalid packet size size
    2010-10-23 21:43:14.204937|ERROR   |Accounting    |   | Accounting server error
    2010-10-23 21:43:14.224603|ERROR   |ServerLibPriv |   | Server() error while starting servermanager, error: accounting server error
    Server shutdown sporadically, all clients timeout and reconnects after 30 seconds.
    Linux Centos 5.5 x86_64
    Intel Quad Core
    Chipset Intel

  2. #2
    Join Date
    February 2006
    Location
    Texas, USA
    Posts
    4,143
    Have you forwarded the accounting server port 2008?

  3. #3
    Join Date
    October 2010
    Location
    Chile
    Posts
    2
    All ports by Default,
    may be because the international link from my provider goes down?

  4. #4
    Join Date
    May 2010
    Posts
    6,310
    Hello

    Ask to your provider and compare with the time in your server log.

  5. #5
    Join Date
    July 2005
    Location
    SK
    Posts
    44

    TS3ANetwork::Connect failed error: 110

    I just upgraded my TS3-server from beta28 to beta29, and suddenly it does not work. Anytime clients try to connect, they are kicked out. I have found these messages in ts.log:

    2010-10-27 16:52:52.461236|INFO |ServerLibPriv | | Server Version: 3.0.0-beta29 [Build: 12473], Linux
    2010-10-27 16:52:52.461496|INFO |DatabaseQuery | | dbPlugin name: SQLite3 plugin, Version 2, (c)TeamSpeak Systems GmbH
    2010-10-27 16:52:52.461525|INFO |DatabaseQuery | | dbPlugin version: 3.6.21
    2010-10-27 16:52:52.461761|INFO |DatabaseQuery | | checking database integrity (may take a while)
    2010-10-27 16:52:52.497924|INFO |SQL | | pruning old database log entries where timestamp is older than 90 days
    2010-10-27 16:52:52.527794|INFO |SQL | | updated permissions to version 7
    2010-10-27 16:52:52.539496|INFO |SQL | | updated permissions to version 8
    2010-10-27 16:52:52.580937|WARNING |Accounting | | Unable to find valid license key, falling back to limited functionality
    2010-10-27 16:52:52.598809|INFO |FileManager | | listening on xx.xx.xx.xx:30033
    2010-10-27 16:52:52.693959|INFO |VirtualServer | 1| listening on xx.xx.xx.xx:9987
    2010-10-27 16:52:52.694522|INFO |CIDRManager | | updated query_ip_whitelist ips: 127.0.0.1,
    2010-10-27 16:52:52.694753|INFO |Query | | listening on xx.xx.xx.xx:10011
    2010-10-27 16:53:03.047836|INFO |VirtualServer | 1| client connected 'Test'(id:22) from xx.xx.xx.xx:2618
    2010-10-27 16:56:12.832396|DEVELOP | | | TS3ANetwork::Connect failed error: 110
    2010-10-27 16:56:12.832537|WARNING |ServerParser | | DEV-CHECK-1 PLEASE REPORT THIS LINE TO THE DEVELOPERS
    2010-10-27 16:56:12.940585|INFO |VirtualServer | 1| client disconnected 'Test'(id:22) reason 'reasonmsg=connection lost'

    As I have found in this forum, probably it is because some connection to accounting server is necessary, so firewall rule must be created. I have a few questions:

    1. Why should TS-server connect to some accounting server, if all I am using is free version, without license? beta28 worked without any problem, and now without any warning, beta29 suddenly does not work in the very same conditions...

    2. How can I use TS now in case I do not have any internet connection? I used to use TS in our lan-parties, and they are generally on closed separated lan. We have been using TS (2, and now 3beta) for many years, with full satisfaction. I would find it very sad to be forced to use some other voice-comm solution...

    3. (and this is more serious) Why was this not mentioned in CHANGELOG??? I carefully read it, and there is absolutelly nothing about it. The same for FAQ. So how are we supposed to configure TS if we do not know even such a basic info, which inbound/outbound connections are necessary, and which ports have to be opened?

    BTW, opening new outbound connection from server has a serious security implications! I can not believe devs consider this change so unimportant that it was not worth to mention it in changelog...

  6. #6
    Join Date
    February 2010
    Location
    Ireland
    Posts
    2

    Can't ping accounting.teamspeak.com.

    SO my server will no longer start up, I got this error message:


    2010-11-03 09:11:25.426664|DEVELOP | | | TS3ANetwork::Connect failed error: 110
    2010-11-03 09:11:25.426809|ERROR |Accounting | | Unable to connect to accounting server
    2010-11-03 09:11:25.426848|ERROR |ServerLibPriv | | Server() error while starting servermanager, error: unable to connect to accounting server



    Following what I saw on these forums I pinged accounting.teamspeak.com and found that my server could not ping it. The only firewall I have installed is iptables and even when it is shut down I still can't connect. I can ping other sites outside of my server fine.


    Anyone know what I need to do to fix this?

  7. #7
    Join Date
    December 2009
    Posts
    237
    Hi, first try to ping 62.146.63.84 (IP of accounting).
    If this works, restart your DNS service or if you dont know how to restart your DNS service simply restart your server and try again.
    If it still does not work after this you may have to look into your servers (not the TS3server) log to see if there is a problem with the DNS configuration.
    But seeing as it already worked once that should not be the case

  8. #8
    Join Date
    February 2010
    Location
    Ireland
    Posts
    2
    Quote Originally Posted by TheMinz View Post
    Hi, first try to ping 62.146.63.84 (IP of accounting).
    If this works, restart your DNS service or if you dont know how to restart your DNS service simply restart your server and try again.
    If it still does not work after this you may have to look into your servers (not the TS3server) log to see if there is a problem with the DNS configuration.
    But seeing as it already worked once that should not be the case
    Perhaps its some kind of uk wide based issue because...

    I couldn't ping it from my home.
    I couldnt ping it from my computer science lab at university.
    I couldn't ping it from my server.

    I tried testing by pinging several other sites and it worked fine so idk what the issue could be...

  9. #9
    Join Date
    July 2005
    Location
    SK
    Posts
    44
    Quote Originally Posted by 00phelanchr View Post
    Perhaps its some kind of uk wide based issue because...

    I couldn't ping it from my home.
    I couldnt ping it from my computer science lab at university.
    I couldn't ping it from my server.

    I tried testing by pinging several other sites and it worked fine so idk what the issue could be...
    Perhaps icmp is blocked somewhere on the way. Try traceroute, and if you see icmp-reply is not comming from some host, try again with different protocol (udp, or tcp).

  10. #10
    Join Date
    September 2012
    Posts
    6,079
    You're blocking vital traffic. See https://support.teamspeakusa.com/ind...rticle/View/44 for necessary ports and communication.
    When sending PMs please make sure to include a reference link to the thread in question in the body of your message.

  11. #11
    Join Date
    October 2016
    Posts
    0

    TeamSpeak 3 server shuts down in every 2 hours.

    Hi people, I hope that you can help me resolve this issue.

    I have DELL PowerEdge R430 server:
    System Info

    CPU Model: Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz
    CPU Details: 1 Core (2397 MHz)
    Distro Name: CentOS release 6.8 (Final)
    Kernel Version: 2.6.32-642.6.1.el6.x86_64
    Platform: x86_64 [xenxen-hvm]

    Application Version

    Apache version: Apache/2.2.27
    PHP version: 5.5.38 [PHP Switcher]
    MySQL version: 5.6.34
    FTP version: 1.0.36
    And I install TeamSpeak 3 Server 3.0.13.4. I made clean install several times and I got same result. When I start server it runs ok for 2 hours and then dies. I restart server, it runs ok for 2 hours and again dies...

    Here is my ts3server_2016-10-13__21_17_15.131083_0.log after server des:
    2016-10-13 21:17:15.131148|INFO |ServerLibPriv | |TeamSpeak 3 Server 3.0.13.4 (2016-08-29 12:39:04)
    2016-10-13 21:17:15.131238|INFO |ServerLibPriv | |SystemInformation: Linux 2.6.32-642.6.1.el6.x86_64 #1 SMP Wed Oct 5 00:36:12 UTC 2016 x86_64 Binary: 64bit
    2016-10-13 21:17:15.131259|INFO |ServerLibPriv | |Using hardware aes
    2016-10-13 21:17:15.131775|INFO |DatabaseQuery | |dbPlugin name: SQLite3 plugin, Version 3, (c)TeamSpeak Systems GmbH
    2016-10-13 21:17:15.131800|INFO |DatabaseQuery | |dbPlugin version: 3.11.1
    2016-10-13 21:17:15.131950|INFO |DatabaseQuery | |checking database integrity (may take a while)
    2016-10-13 21:18:18.149106|ERROR | | |TS3ANetwork::Connect failed error: 110
    2016-10-13 21:18:18.149194|ERROR | | |Unable to connect to primary address, trying secondary
    2016-10-13 21:19:21.153153|ERROR | | |TS3ANetwork::Connect failed error: 110
    2016-10-13 21:19:21.155015|ERROR |Accounting | |Unable to connect to accounting server
    2016-10-13 21:19:21.155037|INFO |Accounting | |Licensing Information
    2016-10-13 21:19:21.155061|INFO |Accounting | |type : Non-profit
    2016-10-13 21:19:21.155086|INFO |Accounting | |starting date : Tue Aug 23 00:00:00 2016
    2016-10-13 21:19:21.155099|INFO |Accounting | |ending date : Thu Feb 23 00:00:00 2017
    2016-10-13 21:19:21.155109|INFO |Accounting | |max virtualservers: 2
    2016-10-13 21:19:21.155118|INFO |Accounting | |max slots : 512
    2016-10-13 21:19:22.409562|INFO | | |Puzzle precompute time: 1237
    2016-10-13 21:19:22.409790|INFO |FileManager | |listening on 0.0.0.0:30033, :::30033
    2016-10-13 21:19:22.432347|INFO |CIDRManager | |updated query_ip_whitelist ips: 127.0.0.1/32, ::1/128,
    2016-10-13 21:19:22.432492|INFO |Query | |listening on 0.0.0.0:10011, :::10011
    2016-10-13 21:20:25.469149|ERROR | | |TS3ANetwork::Connect failed error: 110
    2016-10-13 21:20:25.469227|ERROR | | |Unable to connect to primary address, trying secondary
    2016-10-13 21:21:28.473139|ERROR | | |TS3ANetwork::Connect failed error: 110
    2016-10-13 21:24:22.575375|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 21:24:22.575487|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 21:24:24.077730|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 21:24:24.077764|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 21:24:26.081087|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 21:24:26.081206|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 21:34:22.593413|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 21:34:22.593504|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 21:34:24.115800|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 21:34:24.115835|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 21:34:26.018976|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 21:34:26.019102|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 21:44:22.659879|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 21:44:22.659927|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 21:44:24.061415|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 21:44:24.061458|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 21:44:26.079896|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 21:44:26.079987|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 21:54:22.771821|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 21:54:22.771919|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 21:54:24.074158|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 21:54:24.074252|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 21:54:26.077449|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 21:54:26.077547|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 22:04:22.954903|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 22:04:22.954952|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 22:04:24.056828|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 22:04:24.056861|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 22:04:26.060117|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 22:04:26.060149|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 22:14:23.035376|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 22:14:23.035423|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 22:14:25.038720|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 22:14:25.038752|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 22:14:27.042201|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 22:14:27.042279|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 22:22:34.329149|ERROR | | |TS3ANetwork::Connect failed error: 110
    2016-10-13 22:22:34.329241|ERROR | | |Unable to connect to primary address, trying secondary
    2016-10-13 22:23:37.347148|ERROR | | |TS3ANetwork::Connect failed error: 110
    2016-10-13 22:24:23.089601|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 22:24:23.089696|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 22:24:25.120871|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 22:24:25.120950|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 22:24:27.024127|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 22:24:27.024205|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 22:34:23.119998|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 22:34:23.120060|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 22:34:25.023164|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 22:34:25.023232|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 22:34:27.046072|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 22:34:27.046189|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 22:44:23.108756|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 22:44:23.108803|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 22:44:25.012008|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 22:44:25.012117|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 22:44:27.015280|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 22:44:27.015360|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 22:54:23.141803|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 22:54:23.141851|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 22:54:25.045047|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 22:54:25.045092|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 22:54:27.048483|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 22:54:27.048562|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 23:04:23.237870|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 23:04:23.237967|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 23:04:25.057583|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 23:04:25.057626|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 23:04:27.060975|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 23:04:27.061027|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 23:14:23.208085|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 23:14:23.208166|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 23:14:25.011250|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 23:14:25.011341|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 23:14:27.030648|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 23:14:27.030683|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 23:24:23.375779|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 23:24:23.375895|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 23:24:25.078628|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 23:24:25.078725|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 23:24:27.081890|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 23:24:27.081923|ERROR | | |TS3ANetwork::Send failed error: 1
    2016-10-13 23:24:44.464152|ERROR | | |TS3ANetwork::Connect failed error: 110
    2016-10-13 23:24:44.464242|ERROR | | |Unable to connect to primary address, trying secondary
    2016-10-13 23:25:47.483116|ERROR | | |TS3ANetwork::Connect failed error: 110
    2016-10-13 23:25:47.483173|ERROR |Accounting | |Could not connect to accounting server after multiple attempts, shutting down server
    Last edited by dante696; October 14th, 2016 at 11:27 AM. Reason: merged

Thread Information

Users Browsing this Thread

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

Similar Threads

  1. [Resolved] TS3ANetwork::Connect failed error: 111
    By djdiper in forum Server Support
    Replies: 68
    Last Post: August 22nd, 2018, 06:07 AM
  2. TS3ANetwork::Connect failed error: 110
    By gpcore in forum Server Support
    Replies: 36
    Last Post: March 9th, 2018, 02:55 AM
  3. TS3ANetwork::Connect failed error: 60
    By Kenneth M in forum macOS
    Replies: 2
    Last Post: November 12th, 2012, 09:05 PM
  4. TS3ANetwork::Connect failed error: 101 ??
    By Mikebazz in forum Linux / FreeBSD
    Replies: 0
    Last Post: April 15th, 2012, 04:43 PM

Tags for this Thread

Posting Permissions

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