Forum

Results 1 to 12 of 12
  1. #1
    Join Date
    December 2004
    Location
    RF
    Posts
    3,000

    ToDo List TS3 (upstart,systemd) general setup for Debian based distro

    1. Install TS3 into /opt/teamspeak. Make sure the permissions on a directory are sensible.
    2. Create a system user named "teamspeak" with home directory /var/lib/teamspeak
    3. Copy ts3.ini from distribution to the user home directory.
    4. Uncomment and adjust the following lines exactly as shown:
    Code:
    query_ip=127.0.0.1
    query_port=10011
    logpath=/var/log/teamspeak
    dbsqlpath=/opt/teamspeak/sql/
    dbsqlcreatepath=create_sqlite
    licensepath=/var/lib/teamspeak/
    query_ip_whitelist=/var/lib/teamspeak/query_ip_whitelist.txt
    query_ip_blacklist=/var/lib/teamspeak/query_ip_blacklist.txt
    query_skipbruteforcecheck=1
    logquerycommands=1
    Pay close attention to "dbsql*" and "licensepath" settings, they are most backwards and most important. The presense/absence of starting/trailing directory separators is important.

    5. Create /var/log/teamspeak directory.
    6.
    Code:
    chown teamspeak:adm /var/log/teamspeak
    7a. For upstart users: install /etc/init/teamspeak3.conf from attachment.
    7b. For systemd users: install /etc/systemd/system/teamspeak3.service from attachment.
    8.
    Code:
    service teamspeak3 start
    9. Enjoy.
    Attached Files Attached Files
    Last edited by ANR Daemon; November 9th, 2018 at 04:33 PM.

  2. #2
    Join Date
    March 2009
    Location
    Germany
    Posts
    40
    Since you are stating "upstart script" it seems you are using upstart which is used primarily on Ubuntu.

    Debian will most likely move over to systemd in the future and is currently using SysV.
    So for anyone out there. If that stuff up there is not working for your system you should consider checking which init-system your distro and or distro-release is using.

    For sysV see:
    https://wiki.debian.org/Daemon

    For systemd see:
    https://wiki.debian.org/systemd

  3. #3
    Join Date
    December 2004
    Location
    RF
    Posts
    3,000
    I do not want to touch systemd at all. It just doesn't work. Why Debian is moving to it is a mystery.
    Probably something is fundamentally broken in a Linux community. Linux was always a bunch of programs, each good at something, and together they were bringing excellent results.
    But systemd is trying to be everything at once, and is below mediocre at that.

  4. #4
    Join Date
    January 2010
    Location
    Germany
    Posts
    2

    Thanks

    Thanks for this cool guide!

    Remark: Usage of the licensekey.dat will only work correct when ts3.ini containts:

    licensepath=/var/lib/teamspeak/

  5. #5
    Join Date
    December 2004
    Location
    RF
    Posts
    3,000
    Quote Originally Posted by Powie View Post
    Thanks for this cool guide!

    Remark: Usage of the licensekey.dat will only work correct when ts3.ini containts:

    licensepath=/var/lib/teamspeak/
    What?… ooookay… guide updated, but this is below understandable.

  6. #6
    Join Date
    May 2010
    Location
    Germany
    Posts
    6
    I have a script to generate a .deb for the Teamspeak server for Debian Jessie+ (it uses systemd): https://github.com/pschichtel/ts3server-package

    I would be equally easy to create a package using upstart, but I have no need for that.

  7. #7
    Join Date
    December 2004
    Location
    RF
    Posts
    3,000
    I'm not sure about redistribution of TS3.
    If I would have done it myself, it'd be a download script that retrieves the necessary TS3 version directly to the user's system.

  8. #8
    Join Date
    May 2010
    Location
    Germany
    Posts
    6
    It's not redistributing the server. It's a script that downloads the server from the official source and builds a package from the files.
    That way I can easily deliver it automatically through our infrastructure automation. And in general I always prefer a package over manual installation because updates will be easier, safer and faster

  9. #9
    Join Date
    December 2004
    Location
    RF
    Posts
    3,000
    Err, well, that could work for local updates.
    However, distributing such package to a wider audience is a no-go, I'm afraid.

  10. #10
    Join Date
    December 2004
    Location
    RF
    Posts
    3,000
    Updated for 3.0.12

  11. #11
    Join Date
    August 2005
    Location
    UK
    Posts
    7
    Doesn't seem to work on Debian 8 or Ubuntu 15.04 or higher as they have both moved away from Upstart.
    Any chance this could be updated?
    Or at least update the the original post with some version numbers so others don't waste their time trying to make this work?

  12. #12
    Join Date
    December 2004
    Location
    RF
    Posts
    3,000

    Thumbs down

    No chances. I do not support systemd, it's inherently broken and can not be repaired.
    It thinks too much, expects too much, limit everything around it and last of all, has BINARY LOGS.
    If you want support, use distribution with sane, supported INIT daemon.

Thread Information

Users Browsing this Thread

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

Similar Threads

  1. Debian package (and possibly other distro's as well?)
    By rommyappus in forum Linux / FreeBSD
    Replies: 2
    Last Post: January 21st, 2014, 07:15 AM
  2. Possible to setup whitelist based on Forum Membership?
    By kbassil in forum Permission System
    Replies: 4
    Last Post: April 15th, 2013, 09:26 AM
  3. Replies: 0
    Last Post: May 31st, 2012, 10:43 PM
  4. Upstart Script for Ubuntu Upstart
    By rubinho in forum Linux / FreeBSD
    Replies: 0
    Last Post: December 21st, 2010, 04:44 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
  •