q4base Dedicated Server Crash:

Post by **GODLIKE** » Mon Jul 24, 2006 9:17 pm

Frankly, I'm expecting to simply wait this one out till PR 1.3, but:

Anybody seen this before:

-- idRenderModelManagerLocal::EndLevelLoad --
17 models purged from previous level, 229 models kept.
---------------------------------------------
---------------------------------------------
506 msec to load mp/q4dm3
WARNING: idSoundSystemLocal::SetMute: not paused
------------ Game Map Shutdown --------------
---------------------------------------------
client 0 Server has shut down.
Server has shut down.
client 1 Server has shut down.
Server has shut down.
client 2 Server has shut down.
Server has shut down.
client 3 Server has shut down.
Server has shut down.
------------ Game Map Shutdown --------------
---------------------------------------------
********************
ERROR: idPVS::FreeCurrentPVS: invalid handle
********************
PunkBuster Server: Lost Connection (slot #1) [PlayerIP] : [PlayerGUID] (-) LifeShye
PunkBuster Server: Lost Connection (slot #2) [PlayerIP]:[PlayerGUID](-) shaD^7
PunkBuster Server: Lost Connection (slot #3) [PlayerIP]:[PlayerGUID](-) Mrpsychology
PunkBuster Server: Lost Connection (slot #4) [PlayerIP]:[PlayerGUID](-) sLeeK-
WARNING: idSession: triggering mainmenu watchdog
PunkBuster Server: Master Query Sent to (MASTER8.EVENBALANCE.COM) 66.180.170.20
PunkBuster Server: Received Master Security Information
(PB updates continue until log ends, but the server is clearly NOT running.)

Post by **GODLIKE** » Mon Jul 24, 2006 10:14 pm

Glah... But at least it's not just mine... I'll just schedule some tasks to kill the server and restart it periodically..

taskkill /f /im quake4ded.exe oughta work okay. :icon26:

Post by **GODLIKE** » Mon Jul 24, 2006 10:31 pm

Lo, PR 1.3 cometh.. Let us not be bitter. :icon31:

Post by **iluvquake4** » Mon Jul 24, 2006 11:15 pm

A known PunkBuster issue.

Post by **kleeks** » Mon Jul 24, 2006 11:19 pm

ERROR: idPVS::FreeCurrentPVS: invalid handle

This was a nice little treat introduced with the 1.1 pr (well that is to say i only really noticed it after the pr - it could be that before the servers were so flakey this one went unheeded)
I can minimise its occurance if i reboot the servers daily - but even then i see the error cropping up maybe once a week. Annoyingly the server doesn't shut down fully, so process restarting doesn't help
As this is the only thing that does seem to bring things grinding to a halt, i have come to live with it - but hopefully the 1.3 pr will fix it

I've been unable to isolate the cause, but afaik the others are aware and have been looking at it ...

Post by **GODLIKE** » Tue Jul 25, 2006 12:10 am

iluvquake4 wrote:A known PunkBuster issue.

Can you source that? Everything I've seen seems to point to it being a baseq4 issue..

Post by **iluvquake4** » Tue Jul 25, 2006 1:02 am

Nope. Just another admin I've talked with has the same issues, people just disconnect via PB.

Post by **iluvquake4** » Tue Jul 25, 2006 3:13 am

Ah, nevermind, the PB bug is a different story. Sorry.

Post by **Hex** » Tue Jul 25, 2006 3:23 am

this error is mentioned in the q4max changelog for their latest release - you running q4max? (although it appears to be a vq4 issue)
http://www.q4max.com/wiki/index.php/Changelog

Kleeks posted about it at the q4max forums. http://www.q4max.com/forums/viewtopic.p ... 3c2a9f04a0

I haven't seen the error on my servers since the 1.2.1 ded linux release.

Post by **kleeks** » Tue Jul 25, 2006 4:56 pm

Hex wrote: I haven't seen the error on my servers since the 1.2.1 ded linux release.

Now that is interesting - only our ctf and mod servers run on linux, and although i have seen this error therin, its certainly a lot less frequent.
In the main the error crops up on our baseq4 dm servers (win) - although its worth noting here that these servers are busy most of the time, I had put it down to busier servers producing the error more frequently.

Post by **GODLIKE** » Wed Jul 26, 2006 1:12 am

I can support the "busy" notion.. My server seems to only do this when it's full... I've had 2-3 players on it for ages with no crash, but if the maploop rotates often enough with a full player loadout.. That's when I tend to see the error.

Post by KO » Fri Jul 28, 2006 12:03 am

Q4 servers just don't stay up :S

Post by **Hex** » Wed Aug 09, 2006 2:13 am

OK, I'm coming back around to support also the 'busy' notion. After the 1.3 patch this ded linux server has been 'busier' and I'm also seeing these crashes frequently.

ERROR: idPVS::FreeCurrentPVS: invalid handle

bah.

(haven't installed the 1.32 yet...)

Post by **GODLIKE** » Wed Aug 09, 2006 2:21 am

There's a 1.32? or are you being witty?

Post by **Hex** » Wed Aug 09, 2006 2:32 am

Thats what I thought when I first saw it. But it appears to be for real.

1.3-2 for linux only, not for win. Not sure what the reasoning was. (downloading now)

Post by **niko** » Wed Aug 09, 2006 7:55 pm

1.3 works nice on linux...
no prob.s for now...

Post by **kleeks** » Wed Aug 09, 2006 9:30 pm

Hex wrote:OK, I'm coming back around to support also the 'busy' notion. After the 1.3 patch this ded linux server has been 'busier' and I'm also seeing these crashes frequently.

ERROR: idPVS::FreeCurrentPVS: invalid handle

bah.

(haven't installed the 1.32 yet...)

I've not seen this error until today under 1.3 - although it is the first day i have let the servers run overnight without a reboot.

was hoping it was fixed, but alas :icon23: