
Originally Posted by
Schlumpi
As far as I know, such thing happens if the server is started with a machine_id= option differently to what it was before. That means, if you previously started your server with machine_id=something, and now you use machine_id=someotherthing or no machine_id at all, or vice versa, this will happen. This is an option either directly on the server start command line or an option in the *.ini file if you use an ini file at server start.
Thanks for getting back to me. I have copied the same ts3server.ini and altered the IP addresses to meet the new server. I both .ini files it is 1. When I log in as root and start the minimized startup script, it does work with the proper virtualserver. As wel as the normal startup script as root. When i configure systemctl it starts with the created ts3user and then uses the seconde new virtualserver 2.
it is in systemctl somehow. I tried al service config from the web, but all fail to give the results, as where is started manually.
Code:
[Unit]
Description=Team Speak 3 Server
After=network.target
[Service]
WorkingDirectory=/home/ts3user/teamspeak3-server
User=ts3user
Group=ts3user
Type=forking
ExecStart=/home/ts3user/teamspeak3-server/ts3server_startscript.sh start inifile=/home/ts3user/teamspeak3-server/ts3server.ini
ExecStop=/home/ts3user/teamspeak3-server/ts3server_startscript.sh stop
PIDFile=/home/ts3user/teamspeak3-server/ts3server.pid
RestartSec=15
Restart=always
[Install]
WantedBy=multi-user.target
Code:
machine_id=1
default_voice_port=9987
voice_ip=1.1.1.1
licensepath=
filetransfer_port=30033
filetransfer_ip=1.1.1.1
query_port=10011
query_ip=1.1.1.1
query_ip_whitelist=query_ip_whitelist.txt
query_ip_blacklist=query_ip_blacklist.txt
dbplugin=ts3db_sqlite3
dbpluginparameter=
dbsqlpath=sql/
dbsqlcreatepath=create_sqlite/
dbconnections=10
logpath=logs
logquerycommands=0
dbclientkeepdays=30
logappend=0
query_skipbruteforcecheck=0