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 4 of 4
  1. #1
    Join Date
    September 2010
    Location
    Earth
    Posts
    2

    SIGTERM immediately on launch

    I just updated to server version 3.0.0_beta28 (from beta 25), and now I simply cannot get it to start. The log tells me that TS receives a SIGTERM signal.

    Things I have tried:
    • Downgrading to beta 25 (the version that used to work).
    • Deleting the database.
    • Uninstalling TS and deleting all TS-related files that were left over.
    • Installing TS (beta 28) on a completely different machine.

    None of these things made a difference; TS always fails, and the log claims that TS was killed by a SIGTERM.

    Some details:
    • The primary machine is a 2.4 GHz Pentium 4 with 1 GB RAM, running Gentoo Linux (x86). The kernel version was 2.6.35-r4, but there were supposedly some problems with that version so I reverted to 2.6.34-r6 (it did not help).
    • The other machine is a 2.4 GHz Core2Duo with 4 GB RAM, running Gentoo Linux (x64). It is running kernel 2.6.34-r1.


    As a test, I tried installing the Windows version on a Windows XP machine (a virtual machine actually). This worked flawlessly.

    Every time I try to start the TS server on Linux, it produces a log like this one (only the timestamps change each time):
    Code:
    2010-09-12 16:22:26.468670|INFO    |ServerLibPriv |   | Server Version: 3.0.0-beta28 [Build: 12264], Linux
    2010-09-12 16:22:26.471339|INFO    |DatabaseQuery |   | dbPlugin name:    SQLite3 plugin, Version 2, (c)TeamSpeak Systems GmbH
    2010-09-12 16:22:26.471872|INFO    |DatabaseQuery |   | dbPlugin version: 3.6.21
    2010-09-12 16:22:26.485924|INFO    |DatabaseQuery |   | checking database integrity (may take a while)
    2010-09-12 16:22:26.715380|INFO    |SQL           |   | pruning old database log entries where timestamp is older than 90 days
    2010-09-12 16:22:26.770759|WARNING |Accounting    |   | Unable to find valid license key, falling back to limited functionality
    2010-09-12 16:22:26.818337|INFO    |FileManager   |   | listening on 0.0.0.0:30033
    2010-09-12 16:22:26.960325|INFO    |VirtualServer |  1| listening on 0.0.0.0:9987
    2010-09-12 16:22:26.961385|INFO    |CIDRManager   |   | updated query_ip_whitelist ips: 127.0.0.1,
    2010-09-12 16:22:26.962490|INFO    |Query         |   | listening on 0.0.0.0:10011
    2010-09-12 16:22:27.832830|INFO    |ServerMain    |   | Received signal SIGTERM, shutting down.
    2010-09-12 16:22:27.919072|INFO    |VirtualServer |  1| stopped
    Is there anything else I can try, or should I just wait for a new version and hope that works better? It is not an important server, so having it offline for a while is not a huge deal, but it would still be nice to know what is wrong.

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

    What is your command line to start your server ?

  3. #3
    Join Date
    September 2010
    Location
    Earth
    Posts
    2

    [Solved] SIGTERM immediately on launch

    Quote Originally Posted by florian_fr40 View Post
    What is your command line to start your server ?
    I was reluctant to put a lot of effort into this issue, but your question made me think of one thing I had forgotten to try, and it actually turned out to be the solution.

    In short, the problem lies with the (sometimes broken) way Gentoo launches TS, not with TS itself.

    Longer version:
    In Gentoo, TS is usually launched through the script /etc/init.d/teamspeak3-server. This script sets up some variables and then runs the script /usr/sbin/ts3server as a daemon. That also sets up some stuff and then runs /opt/teamspeak3-server/ts3server-bin which is the actual executable.
    Earlier versions of the init-script were broken in that it did not set-up LD_LIBRARY_PATH the way TS requires, and you basically had to manually edit the script to fix it. The latest version fixes this, but it appears that there is a "fix" in both of the scripts, and at least one of them is broken (the one in /usr/sbin/ts3server looks weird). I circumvented the issue by changing the init script to launch the executable directly, thus bypassing the other script altogether. Now everything seems to be running fine.
    The reason why downgrading did not help is that the ebuild (Gentoo's installer script) for beta 25 did not overwrite the new scripts from beta 28.


    Thanks for the inspiration.

  4. #4
    Join Date
    May 2010
    Posts
    6,310
    Quote Originally Posted by vincer76
    I was reluctant to put a lot of effort into this issue, but your question made me think of one thing I had forgotten to try, and it actually turned out to be the solution.
    It is often the idea.

    Glad you solved your problem.

Thread Information

Users Browsing this Thread

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

Similar Threads

  1. Received signal SIGTERM, shutting down
    By Napster in forum Server Support
    Replies: 2
    Last Post: July 31st, 2015, 07:38 PM
  2. server crashing immediately upon launch
    By louig1 in forum Linux / FreeBSD
    Replies: 2
    Last Post: August 7th, 2014, 12:37 PM
  3. Received signal SIGTERM
    By deeGeee in forum Linux / FreeBSD
    Replies: 0
    Last Post: February 19th, 2012, 11:22 PM
  4. [Resolved] Sigterm
    By Bobbi in forum Linux / FreeBSD
    Replies: 0
    Last Post: July 31st, 2011, 02:05 PM
  5. Server shuts down often, SIGTERM
    By Hileksel in forum Server Support
    Replies: 1
    Last Post: July 25th, 2010, 11:41 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
  •