starred/LinuxGSM

Fork 0

mirror of https://github.com/GameServerManagers/LinuxGSM.git synced 2026-04-25 14:15:59 +03:00

[GH-ISSUE #246] [ts3server] Monitor fails if incorrect architecture version is installed #210

New issue

Closed

opened 2026-02-27 02:00:08 +03:00 by kerem · 16 comments

kerem commented

2026-02-27 02:00:08 +03:00

Owner

Originally created by @npd1124 on GitHub (Dec 17, 2014).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/246

I have set it in crontab so that it will run the monitor but for some reason it detects taht the server is offline when it is not and restarts it. Is there a way to fix this?

Originally created by @npd1124 on GitHub (Dec 17, 2014). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/246 I have set it in crontab so that it will run the monitor but for some reason it detects taht the server is offline when it is not and restarts it. Is there a way to fix this?

kerem

2026-02-27 02:00:08 +03:00

closed this issue
added the
type: feature
label

kerem commented

2026-02-27 02:00:09 +03:00

Author

Owner

@Scarsz commented on GitHub (Dec 17, 2014):

We need error logs to be able to fix this, try running the command manually and seeing if it does anything.

@Scarsz commented on GitHub (Dec 17, 2014): We need error logs to be able to fix this, try running the command manually and seeing if it does anything.

kerem commented

2026-02-27 02:00:09 +03:00

Author

Owner

@npd1124 commented on GitHub (Dec 17, 2014):

ts3server@vps33182:$ ./ts3server monitor
[ WARN ] ts3-server: Monitor detected FuZion Gaming Teamspeak had stopped!
[ INFO ] ts3-server: FuZion Gaming Teamspeak Unknown error
[ INFO ] Sent email notification to
[ OK ] Stopping ts3-server: FuZion Gaming Teamspeak
[ OK ] Starting ts3-server: FuZion Gaming Teamspeak
ts3server@vps33182:$

this is all I get when I run the monitor

@npd1124 commented on GitHub (Dec 17, 2014): ts3server@vps33182:~$ ./ts3server monitor [ WARN ] ts3-server: Monitor detected FuZion Gaming Teamspeak had stopped! [ INFO ] ts3-server: FuZion Gaming Teamspeak Unknown error [ INFO ] Sent email notification to [ OK ] Stopping ts3-server: FuZion Gaming Teamspeak [ OK ] Starting ts3-server: FuZion Gaming Teamspeak ts3server@vps33182:~$ this is all I get when I run the monitor

kerem commented

2026-02-27 02:00:09 +03:00

Author

Owner

@dgibbs64 commented on GitHub (Dec 17, 2014):

Thats looks like a pain.

Here is the code that s returning the error

if [ "$ts3status" = "Server seems to have died" ];then
    echo -en "[\e[0;36m INFO \e[0;39m] ${servicename}: ${servername} Server seems to have died"
    echo -e "$(date '+%b %d %H:%M:%S') ${servicename}: ${servername} Server seems to have died" >> ${scriptlog}

    failurereason="Server seems to have died"
    echo -en "[\e[0;36m INFO \e[0;39m] ${servicename}: ${servername} No server running (ts3server.pid is missing)"
    echo -e "$(date '+%b %d %H:%M:%S') ${servicename}: ${servername} No server running (ts3server.pid is missing)" >> ${scriptlog}
    failurereason="No server running (ts3server.pid is missing)"
else
    echo -en "[\e[0;36m INFO \e[0;39m] ${servicename}: ${servername} Unknown error"
    echo -e "$(date '+%b %d %H:%M:%S') ${servicename}: ${servername} Unknown error" >> ${scriptlog}
    failurereason="Unknown error"
fi

fn_status(){
    ts3status=$(${filesdir}/ts3server_startscript.sh status inifile=${ini})
}

Please can you run the following command.

serverfiles/ts3server_startscript.sh status inifile=(your ini file)

and tell me what it returns as it must be something other than "Server seems to have died".

I may have to look in to this further

@dgibbs64 commented on GitHub (Dec 17, 2014): Thats looks like a pain. Here is the code that s returning the error ``` if [ "$ts3status" = "Server seems to have died" ];then echo -en "[\e[0;36m INFO \e[0;39m] ${servicename}: ${servername} Server seems to have died" echo -e "$(date '+%b %d %H:%M:%S') ${servicename}: ${servername} Server seems to have died" >> ${scriptlog} failurereason="Server seems to have died" echo -en "[\e[0;36m INFO \e[0;39m] ${servicename}: ${servername} No server running (ts3server.pid is missing)" echo -e "$(date '+%b %d %H:%M:%S') ${servicename}: ${servername} No server running (ts3server.pid is missing)" >> ${scriptlog} failurereason="No server running (ts3server.pid is missing)" else echo -en "[\e[0;36m INFO \e[0;39m] ${servicename}: ${servername} Unknown error" echo -e "$(date '+%b %d %H:%M:%S') ${servicename}: ${servername} Unknown error" >> ${scriptlog} failurereason="Unknown error" fi fn_status(){ ts3status=$(${filesdir}/ts3server_startscript.sh status inifile=${ini}) } ``` Please can you run the following command. serverfiles/ts3server_startscript.sh status inifile=(your ini file) and tell me what it returns as it must be something other than "Server seems to have died". I may have to look in to this further

kerem commented

2026-02-27 02:00:09 +03:00

Author

Owner

@npd1124 commented on GitHub (Dec 17, 2014):

This is what it returned

-bash: syntax error near unexpected token `('

@npd1124 commented on GitHub (Dec 17, 2014): This is what it returned -bash: syntax error near unexpected token `('

kerem commented

2026-02-27 02:00:09 +03:00

Author

Owner

@Scarsz commented on GitHub (Dec 17, 2014):

Replace (your ini file) with the path to your teamspeak servers ini

@Scarsz commented on GitHub (Dec 17, 2014): Replace `(your ini file)` with the path to your teamspeak servers ini

kerem commented

2026-02-27 02:00:09 +03:00

Author

Owner

@npd1124 commented on GitHub (Dec 17, 2014):

so would it be like this
serverfiles/ts3server_startscript.sh status inifile=(/home/ts3server/serverfiles/ts3-server.ini)

@npd1124 commented on GitHub (Dec 17, 2014): so would it be like this serverfiles/ts3server_startscript.sh status inifile=(/home/ts3server/serverfiles/ts3-server.ini)

kerem commented

2026-02-27 02:00:09 +03:00

Author

Owner

@dgibbs64 commented on GitHub (Dec 17, 2014):

serverfiles/ts3server_startscript.sh status inifile=/home/ts3server/serverfiles/ts3-server.ini

@dgibbs64 commented on GitHub (Dec 17, 2014): ``` serverfiles/ts3server_startscript.sh status inifile=/home/ts3server/serverfiles/ts3-server.ini ```

kerem commented

2026-02-27 02:00:09 +03:00

Author

Owner

@npd1124 commented on GitHub (Dec 17, 2014):

Would it be because I have the x86 teamspeak server?

@npd1124 commented on GitHub (Dec 17, 2014): Would it be because I have the x86 teamspeak server?

kerem commented

2026-02-27 02:00:09 +03:00

Author

Owner

@npd1124 commented on GitHub (Dec 17, 2014):

It returned this
Do you have the right TS3 Server package for your system? You have: Linux x86_64, not Linux i386.
Server is running

@npd1124 commented on GitHub (Dec 17, 2014): It returned this Do you have the right TS3 Server package for your system? You have: Linux x86_64, not Linux i386. Server is running

kerem commented

2026-02-27 02:00:09 +03:00

Author

Owner

@dgibbs64 commented on GitHub (Dec 17, 2014):

If you are running a 64-bit distro you should run the 64-bit version :)

@dgibbs64 commented on GitHub (Dec 17, 2014): If you are running a 64-bit distro you should run the 64-bit version :)

kerem commented

2026-02-27 02:00:09 +03:00

Author

Owner

@npd1124 commented on GitHub (Dec 17, 2014):

I am running Ubuntu 12.04 64 bit with the Linux x86_64, does that have anything to do with why the monitor keeps restarting the server ?

@npd1124 commented on GitHub (Dec 17, 2014): I am running Ubuntu 12.04 64 bit with the Linux x86_64, does that have anything to do with why the monitor keeps restarting the server ?

kerem commented

2026-02-27 02:00:09 +03:00

Author

Owner

@dgibbs64 commented on GitHub (Dec 17, 2014):

Yeah I think thats probably the issue. You are running the wrong version of teamspeak for your server. Looks like the x86 version still runs.

The problem is that the script is looking for either the following to be returned:

Server is running

Server seems to have died

Instead the teamspeak server returns.

Do you have the right TS3 Server package for your system? You have: Linux x86_64, not Linux i386. Server is running

This is an "Unknown error" to the script as it does not match any of the other messages.

The only way to resolve this currently is for you to re install with the correct x64 bit version. I will however look at making a change to the script to take this problem in to account. For example the server would advise you are running the wrong version on start so you know right away and correct on first install.

@dgibbs64 commented on GitHub (Dec 17, 2014): Yeah I think thats probably the issue. You are running the wrong version of teamspeak for your server. Looks like the x86 version still runs. The problem is that the script is looking for either the following to be returned: ``` Server is running ``` or ``` Server seems to have died ``` Instead the teamspeak server returns. ``` Do you have the right TS3 Server package for your system? You have: Linux x86_64, not Linux i386. Server is running ``` This is an "Unknown error" to the script as it does not match any of the other messages. The only way to resolve this currently is for you to re install with the correct x64 bit version. I will however look at making a change to the script to take this problem in to account. For example the server would advise you are running the wrong version on start so you know right away and correct on first install.

kerem commented

2026-02-27 02:00:09 +03:00

Author

Owner

@npd1124 commented on GitHub (Dec 17, 2014):

Then which server would be the right one?

@npd1124 commented on GitHub (Dec 17, 2014): Then which server would be the right one?

kerem commented

2026-02-27 02:00:09 +03:00

Author

Owner

@dgibbs64 commented on GitHub (Dec 17, 2014):

http://dl.4players.de/ts/releases/3.0.11.2/teamspeak3-server_linux-amd64-3.0.11.2.tar.gz

@dgibbs64 commented on GitHub (Dec 17, 2014): http://dl.4players.de/ts/releases/3.0.11.2/teamspeak3-server_linux-amd64-3.0.11.2.tar.gz

kerem commented

2026-02-27 02:00:09 +03:00

Author

Owner

@npd1124 commented on GitHub (Dec 17, 2014):

Alright ill try that version and see if it fixes it.

@npd1124 commented on GitHub (Dec 17, 2014): Alright ill try that version and see if it fixes it.

kerem commented

2026-02-27 02:00:09 +03:00

Author

Owner

@lock[bot] commented on GitHub (Jul 20, 2018):

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.

@lock[bot] commented on GitHub (Jul 20, 2018): 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.