Teamspeak RC2 daemon fails to start

[Toff]

Hi!

I trying to get the new RC2 to work. I'm using Redhat Linux 8.0 with kernel 2.4.20.

When I start either the teamspeak server directly or with the script I end up with following error message:

Error starting daemon. Aborted

The log-file looks like this:
---------------------------------------------------------------
-------------- log started at 03-03-03 00:19 -------------
---------------------------------------------------------------
03-03-03 00:19:52,ALL,Info,server, Server init initialized
03-03-03 00:19:52,ALL,Info,server, Server version: 2.0.19.16 Linux
----------------------------------------------------------
---------------------------------------------------------------
--------------- log ended at 03-03-03 00:19 --------------
---------------------------------------------------------------
03-03-03 00:20:04,ALL,Info,server, Starting server with port: 8767
03-03-03 00:20:04,ERROR,All,SERVER, can not initialise udp communication wit
h port 8767
(END)

After a couple of seconds, I get the following message inside the terminal:

Runtime error 231 at 08058CF1

Right now I'm not using a single iptables-roule.

Can you help?

Thanks
Christoph

[rhoekstra]

I am having a similar problem . . .

Also using RH 8.0 with kernel 2.4.20..

I have configured the server.ini to bind itself to a certain IP, which solves the 'ERROR,All,SERVER, can not initialise udp communication with port 8767' problem..

But still the daemon startup seems to fail.

Doing ps -ax I see it running, but the new client (windows client) keeps telling me that the server is giving a bad response...

Anyone?

[Toff]

Hi!

I think this must be somehow related to Redhat 8.0. I tried to install teamspeak2 rc1, which ran pretty fine under Suse Linux 8.0.

But here too, I get the message:

---------------------------------------------------------------
-------------- log started at 03-03-03 01:13 -------------
---------------------------------------------------------------
03-03-03 01:13:12,ALL,Info,server, Server startup initialized
03-03-03 01:13:12,ALL,Info,server, Server version: 2.0.18.32 Linux
OK
03-03-03 01:13:12,ALL,Info,server, Starting server with port: 8767
03-03-03 01:13:13,ERROR,All,SERVER, can not initialise udp communication with port 8767

Any ideas?

Thanks,
Toff

[rhoekstra]

Have you tried to bind the server to a specific interface (IP address) ?? I don't seem to have that particular error message (I do get a runtime error message though)

Have you checked that all 'server_linux' processes are stopped before trying to start them again?

[Toff]

Yes, you were right. There was still a server_linux running, which I overlooked.

But still I get the following error:

Error starting daemon. Aborted

and the log looks like this:

---------------------------------------------------------------
-------------- log started at 03-03-03 01:37 -------------
---------------------------------------------------------------
03-03-03 01:37:11,ALL,Info,server, Server init initialized
03-03-03 01:37:11,ALL,Info,server, Server version: 2.0.19.16 Linux
03-03-03 01:37:15,ALL,Info,server, Starting server with port: 8767
----------------------------------------------------------
---------------------------------------------------------------
--------------- log ended at 03-03-03 01:37 --------------
---------------------------------------------------------------
03-03-03 01:37:22,ALL,Info,server, Server init finished
03-03-03 01:37:22,WARNING,Info,server, TeamSpeak Server daemon activated

It look like the server is running, but e.g. i can't log into the web surface.

CU
Toff

[Toff]

OK. It seems to work.

I still get the message, but i can log into the server via the client software as well via the web.

I didn't changed a thing, i just ignored the message

CU
Toff

[rhoekstra]

With me the problem is gone as well.. a network problem prevented me to connect to the server....

[Stebs]

I have also the "Error starting daemon. Aborted" Error but everything seems to work. But sadly the CPU "workload" is always at 100%.
I´m using the rather special fli4l distribution (it is a very tiny linux tailored for routers and has a 2.2.22 kernel)
Rc1 is running fine and only older versions of the Web-Frontend did the 100% CPU-thing (only when enabled).
Strange is, the first time I started with HTTPServer Enabled=0, I had no Error, then after enabling it (for Configuration) there was the error and 100 % CPU, a 3. start with the HTTPServer disabled again produced nevertheless the error and 100% CPU?

Hope this helps to find the bug
Thierry