Server hardware?

Message

Wavesynck · #1 Post by **Wavesynck** » Thu Jul 15, 2010 2:29 pm

I noticed that often when there are a lot of players (and buildables) the server begins to lag altogether, I mean not certain people getting lag but everybody.
And recently at the time of such activity spike, the server dropped.
Time for some upgrade or it's just me not knowing something?

#2 Post by **Rotacak** » Thu Jul 15, 2010 4:36 pm

If there is builded VERY much buildables, then can happen this things. Yellow mountains on lagometer and everything unplayable. But that is not due to cheap server connection nor cheap server. Its just due to tremulous cannot handle so much buildings.

Next thing is - 1.2 is buggy. I reported three different crashs, but nobody fixed it yet. Dunno if these crashes are caused by many buildings but on 1.1 happen no crashs. I saw on 1.1 yellow mountains on lagometer and high ping for everyone when builders goes mad, but no crash.

1.2 crashing only when this scenario happen? (everyone lags and while next playing and building it will crash?)

Wavesynck · #3 Post by **Wavesynck** » Thu Jul 15, 2010 5:21 pm

Rotacak wrote: 1.2 crashing only when this scenario happen? (everyone lags and while next playing and building it will crash?)

Yes, everyone lags, warps, game gets unplayable and if there are more people connecting/more buildables constructing the servers drops and players get a message 'Server disconnected - signal caught'.
I don't recall crashes when the server isn't too crowded.
BTW, does that mean the UNIX sense of 'signal'?
P.S.: But as the server lags, there can happen some fun things, like being stuck in an armory cause of warping.

EDIT: Oh, and I also remember before the server shutdown there is something like a hang (Connection Interrupted message and all yellow lagometer for a few seconds).

#4 Post by **Rotacak** » Thu Jul 15, 2010 6:16 pm

Then we need !sd command for admins to prevent crash.

"BTW, does that mean the UNIX sense of 'signal'? "
i think that is global quake3 message.

Quarko · #5 Post by **Quarko** » Thu Jul 15, 2010 10:06 pm

Yes, if clients recieve signal error - that means that qvm crashed. When QVM crashes, tremserv tries to shut down nicely and disconnects all clients.

Wavesynck · #6 Post by **Wavesynck** » Fri Jul 16, 2010 8:20 am

Quarko wrote:Yes, if clients recieve signal error - that means that qvm crashed. When QVM crashes, tremserv tries to shut down nicely and disconnects all clients.

Ummm...SIGTERM?