On my MVM server, I have it autorestarting every 8 hours or so with cron executing sv_shutdown along with a high sv_shutdown_timeout_minutes value (to prevent it from restarting with anyone on it). Problem is, quite often the server thinks it still has players on it or something, so it doesn't actually restart when the command is executed. No one has been on the server for over an hour, no bots are on it, etc., and yet sv_shutdown doesn't shut it down.
Example console output: >sv_shutdown >sv_shutdown command received. >Server will shut down in 41922 seconds, or when it becomes empty. (as you can see, the shutdown request has already been received before) >status >hostname: >version : 1.2.4.9/23 5183 secure >udp/ip : >account : logged in >map : mvm_coaltown at: 0 x, 0 y, 0 z >players : 0 (32 max) > # userid name uniqueid connected ping loss state > adr Just a random guess about something that Valve might want to look into: perhaps this bug is also stopping matchmaking traffic from being sent to the server? All my other MVM instances are filled most of the time, and I notic that when an instance gets "bugged" like this, it seems to stop receiving players. Thanks. _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux
