TS keeps stopping

[bigern75]

Ive got a game server from insomnia365.com and TS is installed just fine, works good, but every few days it just stops. 70.85.135.10:14534
Does it need its own dedicated ip with NO games playing on that ip?
Whats some does and donts?
And any ideas why it might keep stopping?

Thanx

[guldi]

if it's a dynamic IP address you might want to read the lower part of the FAQ thread dealign with DynDNS (the disadvantages of DynDNS).
Or does the server proeccess gets stoped (hangs up,..) on that PC ? Pls be more specific.

Add. servers (like game servers) should not prevent TS from running correct. Maybe some TS hosters which host as well game servers could give here some more clues ?

[bigern75]

if it's a dynamic IP address you might want to read the lower part of the FAQ thread dealign with DynDNS (the disadvantages of DynDNS).
Or does the server proeccess gets stoped (hangs up,..) on that PC ? Pls be more specific.

I'll have to double check the DynDNS.

But it TS is the only thing that keeps stopping. The games and the cortex software keeps runs fine. Ive just gotta go into ssh and restart TS every couple of days.

I'll look at that thread about the DynDNS and get back with ya.

Thanx

[guldi]

I'm still not entirely sure if it's due to the server not answering on the network layer (in this case th server should still be accessible from the LAN) or if the server process itselfs dies and has to be restarted ?

[bigern75]

on the lan, u can pull up the login page and thats it. u cant login.
I then goto ssh and do a ./teamspeak2-server_startscript restart and everything stats back up and u can login.

[bigern75]

The process it self seems to be dieing. There is no record of it crashing anywhere that I can find. Secondly, I do not need to use DynDNS.org since this is NOT a dynamic IP and has no relevence to this present issue.

[bigern75]

bump

Still having issues
Clients seems to think its a Linux issue

[Naked Ape]

bump

Still having issues
Clients seems to think its a Linux issue

Not sure what is happening to your server but I doubt it's a Linux problem. I have run a TS2 server for a few years on Debian Unstable and the only thing stopping it is power outages.

If you've ruled out coredumps and things like the network configuration changing you might want to llok into adminstrative control scripts and user process limits. Most of these usually result in a process getting killed which seems isn't the case for you but you never know.

[bigern75]

we think it was getting overloaded. It would just stop. Since the overloading client left, weve had no more problems. But we'll see.
Thanx