>> Eventually, after restarting the server over and over, the problem goes
>> away
>> and people can connect and play fine. I talked to octohd and
>> FLOOR_MASTER
>> and they said they are getting the same problem.
Also, lest Valve think the problem just magically disappears and fixes
itself after a random number of times rebooting the server, and never
comes back again once players can successfully spawn --
The first time I got our 24/7 2Fort Fast Respawn server to successfully
spawn a player without the connection problem, I was still running the
server OUTSIDE of its usual screen session, so I could easily scroll back
and look at console messages.
I then reattached ("screen -rd") to the screen session the gameserver
normally runs in and restarted the server. Voila. Players can't spawn.
So whatever the problem is, it doesn't magically disappear. I would
venture to guess that it is subject to come back after ANY server reboot.
This sucks because many/most of us reboot our games daily to "reset" the
game's memory allocations.
It's going to take an update to fix it, IMO.
So Valve, when you fix the fix for the string table and startup crash
problems, how about leaving the damn dedicated server alone until you are
SURE
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please
visit:
http://list.valvesoftware.com/mailman/listinfo/hlds_linux
