runtime error while starting , Teamspeak doesn't works

[j0hann]

I'm using a red hat distribution ... when i'm starting teamspeak there is a :

[root@asciQ tss2]# ./tss.minimal_startscript start
Runtime error 0 at BF7FFADC
Runtime error 221 at B804DD34
Error stating daemon. Aborted

thats my server.ini

[Main Config]
HTTPServer Port=0
HTTPServer Enabled=1
DateTimeFormat=dd-mm-yyyy hh:nn:ss
TCPQueryPort=51234
BoundToIp=
[WebPost]
AdminEmail=na
ISPLinkURL=na
ISPName=Private
ISPCountry=Earth
PostURL=localhost

[server_cfg Default]
ServerName=TS Server
ServerType=1
ServerWelcomeMessage=[Welcome to TeamSpeak, check www.teamspeak.org]
ServerMaxUsers=12
ServerUDPPort=8767
ServerPassword=TS4ever
ServerFlags=2
AllowCodecCelp51=1

AllowCodecCelp63=1
AllowCodecGSM148=1
AllowCodecGSM164=1
AllowCodecWindowsCELP52=1
WebPost_LinkURL=

[Servers]
0=server_cfg Default


I've edited a lot of shit so correct me please and maybe you can tell me how to start my ts server I would very happy

[j0hann]

oh and i've read the other thread but there the roundtime errors are shown when ts has been started and not on starting

[Nomalz]

I got the same problem ;

When launching the ./server_linux or the ./tss.minimal_startscript, i got :

sh-2.04$ ./server_linux
Error stating daemon. Aborted


Need help please

[j0hann]

oh I forgot to say that there is the old teamspeak server version on the server. It doesn't matter, does it ?

[Nomalz]

I don't think so...

It's my first installation of a TeamSpeak server.

[j0hann]

oh ok but maybe it isn't the same problem

Hey Johann I had this issue. Its really quite simple. When you do a kill server_linux it doesn't fully kill all the tss2 server processes. The most effective way to do this is to do:
killall -s 9 server_linux

This will kill all the tss processes.

[j0hann]

there is no teamspeak process running anymorge but there is still the same thing

Have you tried a "ps aux" to make sure there are no processes left?

[j0hann]

oh how fucking damed you think I am or you just want to get more posts ?

[j0hann]

here is some thing out of my log:

27-08-02 20:56:11,ERROR,All,SERVER, can not initialise udp communication with port 8767

Whenever I start the server I also get the Error stating daemon. Aborted error but find that TS does start. Sometimes it won't and I have to stop it and try starting again and usually after a few tries it does catch and start, though still giving the error. If I can't get it to start and check the log, I find I get the error about not being able to communicate with the UDP port, so I just do what daxmax suggested and do a killall on it and try starting again and find it works. I'll still get the daemon error, but it starts. It seems that when you stop it or restart it, that it gets stuck and hangs on to that UDP port, so the killall seems to work well and then start it again.

[lt_bob]

Originally posted by Nomalz
When launching ./tss.minimal_startscript, i got :

sh-2.04$ ./server_linux
Error stating daemon. Aborted

Same issue here.

$ ./tss.minimal_startscript start
Error stating daemon. Aborted
$

Some more facts. It apppears to work fine. I can connect to it in TS2 and get to the Web interface. I can see nine PID's with ps -ef when it is up. netstat -anp shows the three ports listneing with the top level pocess. I do notice that is takes 7-10 seconds for the last four PID's to be created, IE the first 5 are there when the startup script exits and the last four show up a while later. The log file looks fine.

Bob

-------------- log started at 28-08-02 15:59 -------------
---------------------------------------------------------------
28-08-02 15:59:48,ALL,Info,server, Server startup initialized
28-08-02 15:59:48,ALL,Info,server, Starting server with port: 8767
----------------------------------------------------------
---------------------------------------------------------------
--------------- log ended at 28-08-02 15:59 --------------
---------------------------------------------------------------
28-08-02 16:00:01,ALL,Info,server, Server startup finished
28-08-02 16:00:01,WARNING,Info,server, TeamSpeak Server daemon activated

[lt_bob]

Originally posted by j0hann
there is no teamspeak process running anymorge but there is still the same thing

Try running

netstat -anp

and look to see if there is anything that has already opened the ports you are looking for. I have seen these messages a couple of times and it was always due to the port being in use.


Bob

[firefly]

@Nomalz did you want to run ts2 on ah fli4l router??

If yes so you could download the opt_glibc225 from http://www.fli4l.de/german/extern/opt/index.pl?pid=41

this solves all my start probs with ts2