ET server stops responding

(BallsCutter) #1

Well, ET server on Linux, works fine several days but then abruptly stops
responding. Players can connect but can’t do a single step. All I see
via screen at console is an infinite loop of messages like this:

ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
ExitLevel: executed
quit
----- Server Shutdown -----
Sending heartbeat to etmaster.idsoftware.com
==== ShutdownGame ====
ShutdownGame:

Shutdown tty console

[screen is terminating]

:banghead:

(Rain) #2

[snip]
I’ve seen ET do things like this when whatever command is in the ‘nextcampaign’ cvar fails to actually load a new campaign. That’s the first thing I’d investigate, although it doesn’t seem likely since you say you manage several days before it actually borks.
Setting ‘developer’ to ‘1’ might provide some more insight into the problem, but it’ll also lot a lot more crap to the server console, which may not suit you well.

(BallsCutter) #3

Thank you, all I’ve found out is that it happens when voting for stopwatch passes.