More on 'Error starting daemon. Aborted'

[Lethe]

To recap my minor problem (running B22 on RH7.1 Linux).

I can start/restart TSRC2 and get this error produced at console:

'Error starting daemon. Aborted'

but server comes up and all operates perfectly :)

So...

...I have just done a load of tests, and as far as I am aware:

'Error starting daemon. Aborted'

actually doesn't mean - nor do anything.

Now in server.log, I noticed this very last line after activation of TS:

11-03-02 19:32:37,WARNING,Info,server, TeamSpeak Server daemon ativated

That warning in there intrigued me... but as you can see, the daemon started OK.

SO I reckon the actual wrong server message is being sent to stdout... it shouldn't be 'failed to activate' but Successful! Somehow the WARNING is passed the wrong text string to display.

I reckon ;)

Nick :)

[S41N7]

i got that error message too, but latly i got another problem on the server...
some people just cant get into the server with a error message saying something with "bad server response"

then, some other people can get into the server but I cant hear them speak although they can hear me, but when we use some other server everything works well, so its something with my tss2_rc2...

[bjorn]

i get the same error

[root@server tss2]# ./tss.minimal_startscript start
Error starting daemon. Aborted

and even though I can connect from my lan other users can not - but they can access the web interface and I have checked the firewall is configured for the right port...

im running linux red hat 8

.. any input form support ppl?

[Lethe]

Have you opened the port thru' firewall?

Nick

[bjorn]

Just double checked firwall configs, have opened udp 8767, tcp 14534 and tcp 54234.

However I just tried downloading a fresh copy and it ran without any problems - just restarted the box first ... could it have been a instance of RC1 not having stopped propperly causing it?

- anyway all is well!

edit:
Nooooo! I just tried restarting it and i got the same message? Ok doing it again and not stopping it this time!!

[Renegat3]

Originally posted by Lethe
SO I reckon the actual wrong server message is being sent to stdout... it shouldn't be 'failed to activate' but Successful! Somehow the WARNING is passed the wrong text string to display.

I reckon ;)

Nick :) Well, it is a wrong message, but not the way you think! It is a grammatical error. It should say "stating" instead!

Greets
R3

[Lethe]

Ah! 'Starting to activate!'. Yep, makes sense.

Nick :)

[madcat]

i have the same problem :/

not that there is anything wrong.. it all works well, but i also get the error at startup:

madcat:/usr/share/teamspeak/tss2_rc2# ./tss.minimal_startscript start
Error starting daemon. Aborted
madcat:/usr/share/teamspeak/tss2_rc2# tail server.log
---------------------------------------------------------------
26-09-03 01:18:29,ALL,Info,server, Server init initialized
26-09-03 01:18:29,ALL,Info,server, Server version: 2.0.19.46 Linux
26-09-03 01:18:31,ALL,Info,server, Starting VirtualServer id:1 with port:8767
----------------------------------------------------------
---------------------------------------------------------------
--------------- log ended at 26-09-03 01:18 --------------
---------------------------------------------------------------
26-09-03 01:18:52,ALL,Info,server, Server init finished
26-09-03 01:18:52,WARNING,Info,server, TeamSpeak Server daemon activated

[Android]

I have multiple servers running in my home, some at different versions. I've done some testing on this message tonight and discovered some interesting things which should be passed on to the dev team. (but I haven't found the FAQ/method of how yet...)

Anyways, this problem is actually kind of serious. What this error is reporting is that the server is not running in multi-thread mode. (or at least it's not spawning copies of itself)

I've tried this on a Slackware 9.1 box (I don't have the lib versions handy) and on two different Slackware 8 boxes (2.4 and a 2.6 kernel). The slackware 9.1 box gives this error message, the other two don't. What's the difference? Library versions.

In order for the server to support multiple versions of Linux (and since the dev team has decided not to release the source [this is their choice, and they're the ones doing the work...] ) this binary should be linked static.

Using shared libs where each distribution uses different versions and/or types of libs (I know of at least two or three different threads libs for example) is not going to work. Yes, it will lead to a bigger binary, but at least it will be guarenteed to work on ALL distributions.

My only option now is to downgrade my TeamSpeak box to Slackware 8, which isn't bad, but I just got the damn thing upgraded... :(