ts3server: The monitor service does not recognize the server running.

[dgibbs64]

Florian Henze says:
November 15, 2013 at 12:53 am (Edit)
The script is really great for an easy-to-go server. But I faced two issues.

1. The renaming of the folder is written as “ts3″ on the website, within the script it is required to have “serverfiles”.
2. The monitor service does not recognize the server running. As markezzz said in the comment before. The two lines in the script asking for ts3status are
   237 ts3status=${filesdir}/ts3server_startscript.sh status inifile=${ini}
   264 ts3status=${filesdir}/ts3server_startscript.sh status inifile=${ini} > /dev/null 2>&1

Replace line 264 with the same content of 237 or just remove ” > /dev/null 2>&1″ in the end and it will work.

Maybe a leftover from a debug session?

markezzz says:
November 4, 2013 at 3:51 pm (Edit)
Hello Daniel,
I started my ts3-server with the ts3server-script. Than i wanted to test the monitor-function from the script.
I get all time this error:

ts3server@GPR0067:~$ ./ts3server start
[ OK ] Starting ts3-server: Teamspeak 3 Server

ts3server@GPR0067:~$ ./ts3server monitor
[ WARN ] ts3-server: Monitor detected Teamspeak 3 Server had stopped!
[ INFO ] ts3-server: Teamspeak 3 Server Unknown error

[ OK ] Stopping ts3-server: Teamspeak 3 Server
[ OK ] Starting ts3-server: Teamspeak 3 Server

But i have started the server and it show all time the ts3-server has stopped.

What is my failure on this step?

[dgibbs64]

I have made a minor update to address the points that Florian Henze stated. When running my tests however (I run this on a live server) I have not experianced any issues. However I have updated the script to help fix the issue. I cannot confirm if this will help however.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.