Weird TS3 status change

[Palletje]

I have some weird issues with the status of my TS3 server runnign on UBUNTU 11.10.

Sometime when i am viewing the status of it with the command
./ts3server_startscript.sh status
the status is: Server seems to have died

But I can in fact log in to the Teamspeak from my client, so I would say The server is lying to me

The logs also don't show a problem,
2012-03-21 13:15:15.826982|INFO |ServerLibPriv | | TeamSpeak 3 Server 3.0.3 (2012-03-17 06:12:11)
2012-03-21 13:15:15.945894|INFO |DatabaseQuery | | dbPlugin name: SQLite3 plugin, Version 2, (c)TeamSpeak Systems GmbH
2012-03-21 13:15:15.945934|INFO |DatabaseQuery | | dbPlugin version: 3.7.3
2012-03-21 13:15:15.946124|INFO |DatabaseQuery | | checking database integrity (may take a while)
2012-03-21 13:15:16.351250|INFO |Accounting | | Licensing Information
2012-03-21 13:15:16.351294|INFO |Accounting | | type : Non-profit
2012-03-21 13:15:16.351333|INFO |Accounting | | starting date : Mon Aug 22 00:00:00 2011
2012-03-21 13:15:16.351355|INFO |Accounting | | ending date : Wed Aug 22 00:00:00 2012
2012-03-21 13:15:16.351374|INFO |Accounting | | max virtualservers: 10
2012-03-21 13:15:16.351392|INFO |Accounting | | max slots : 512
2012-03-21 13:15:16.600420|INFO |FileManager | | listening on 0.0.0.0:30033
2012-03-21 13:15:16.959226|INFO |CIDRManager | | updated query_ip_whitelist ips: 127.0.0.1,
2012-03-21 13:15:16.959723|INFO |Query | | listening on 0.0.0.0:10011

root@server:/opt/ts3/logs# cat ts3server_2012-03-21__13_15_15.826768_1.log
2012-03-21 13:15:16.939323|INFO |VirtualServer | 1| listening on 0.0.0.0:9987


ps -aux | grep ts3 tells me the service is indeed running
1001 997 0.2 0.1 135128 8068 ? Sl 14:15 1:00 ./ts3server_linux_amd64

but when i do the status view again with ./ts3server_startscript.sh status it says
Server is running

ewald@server:/opt/ts3$ ls -l
totaal 6868
-rw-r--r-- 1 teamspeak teamspeak 36373 2012-03-17 07:20 CHANGELOG
drwxr-xr-x 2 teamspeak teamspeak 4096 2012-03-17 07:20 doc
drwx------ 3 teamspeak teamspeak 4096 2012-03-19 12:27 files
-rwxr-xr-x 1 teamspeak teamspeak 216952 2012-03-17 07:20 libts3db_mysql.so
-rwxr-xr-x 1 teamspeak teamspeak 1056152 2012-03-17 07:20 libts3db_sqlite3.so
-rw-r--r-- 1 teamspeak teamspeak 24099 2012-03-17 07:20 LICENSE
-rw-r--r-- 1 teamspeak teamspeak 878 2012-03-19 12:29 licensekey.dat
drwx------ 2 teamspeak teamspeak 4096 2012-03-21 14:15 logs
-rw-r--r-- 1 teamspeak teamspeak 1 2012-03-19 12:27 query_ip_blacklist.txt
-rw-r--r-- 1 teamspeak teamspeak 10 2012-03-19 12:27 query_ip_whitelist.txt
-rw-r--r-- 1 teamspeak teamspeak 112 2012-03-19 12:30 serverkey.dat
drwxr-xr-x 2 teamspeak teamspeak 4096 2012-03-17 07:20 serverquerydocs
drwxr-xr-x 4 teamspeak teamspeak 4096 2012-03-17 07:20 sql
-rwxr-xr-x 1 teamspeak teamspeak 5441960 2012-03-17 07:20 ts3server_linux_amd64
-rwxr-xr-x 1 teamspeak teamspeak 432 2012-03-17 07:20 ts3server_minimal_runscript.sh
-rw-r--r-- 1 teamspeak teamspeak 4 2012-03-21 14:15 ts3server.pid
-rw-r--r-- 1 teamspeak teamspeak 197632 2012-03-21 21:23 ts3server.sqlitedb
-rwxr-xr-x 1 teamspeak teamspeak 2842 2012-03-17 07:20 ts3server_startscript.sh
drwxr-xr-x 2 teamspeak teamspeak 4096 2012-03-17 07:20 tsdns

This is not the first time, this happens a lot.

The problem is that sometimes I cannot log into teamspeak and sometimes I can. Sometimes when i reboot the service it is not being started up on boot and sometimes it is. It makes absolutley no sense to me. Does anyone have a possible explanation to me or a solution would even be better

[Palletje]

Well after doing a lot of googling and doing a lot of trying out i found the answer of my problem.
the answer to what went wrong is the command: sudo ./ts3server_startscript.sh stop/start.
What this does is restarting the server, but also making the ts3server.pid change owner to root, causing 2 fails.

First fail is that when you try to reboot your machine by doing sudo reboot, it is failing to listen to that command, because it cannot shut down ts3server.pid. I am not sure if it should or not, but it just doesn't. so having an ssh connection open to the ubuntu machine will give me the warning; "The system is going for reboot now" however it keeps in that state without actually rebooting

Second fail is that it also will not automaticly start the teamspeak service upon startup. ts3server.pid is still owned by root and it wants to start it as root, but with the user teamspeak priveleges, causing it to fail.

This is easily fixed by first using sudo chown -R teamspeak.teamspeak /opt/ts3. Ofcourse if you have installed it on a different location then /opt/ts3 should be changed to the right location

and second and this is very IMPORTANT! start and stop teamspeak by typing; "service teamspeak stop/start/status" and please do not use the sudo ./ts3startscript.sh start/stop/status version.

The only thing i have not found out is why the status script still says the server seem to have died, when i can now always connect to it, restart the ubuntu machine and automaticly start teamspeak at startup *edit: even the status script works very good at the moment*

[ARCHI]

Solution is very easy actually.

You can change your startup script from service teamspeak start to file ./ts3server_minimal_runscript.sh, and change your stop script to signal SIGINT ts3server_linux_x86/amd64.

Reboot command sends SIGINT to every running process, also teamspeak process. Service doesn't work like this.


My startup script located in rc.local looks like this:

su myusername -c 'screen -d -m -S ts3 /home/myusername/teamspeak/ts3server_minimal_runscript.sh inifile=ts3server.ini'

su myusername -c executes command as myusername. Screen is optional, you can use '/path/to/teamspeak/ts3serevr_minimal_runscript.sh' It loads teamspeak as myusername and it's working all time as myusername. Kill script just sends SIGINT to process instead of trying to stop service.

It works fine with rebooting the machine, at least with my Debian "Wheezy" 7.0 64-bit with such configuration.

Good Luck.

[Palletje]

So there are a lot of ways to fix this, very good imo. However since it works like a charm now i see no reason to try out your version, but perhaps other visitors find your method better than mine so all tips regarding this problem are welcome