Situation:
Dedicated server runs 24/7, with a separate process monitoring it.
Whenever the server process ends/stops (Either via a timed/programmed/scripted end, or a crash), the monitoring makes sure the -server is being restarted.
(Steam client is not running, as there's no need for it running anymore.)
This works fine, except for one situation, where the server reports 'Connection to steam lost. Exiting.'
The way this error is being reported is in a dialog box, that will wait forever for an operator to click the 'Ok' button. So, without operator input, the server will not end, and thus will not be restarted.
Request:
Could this error message be changed? So it no longer needs operator input? Put a timer in the box that closes it after some seconds?
Or, leave it out completely? The logs can show it occurred maybe?
Additional comment: This issue is being dealt with beautifully when using the ClodWatchdog client. It monitors steam as well and somehow it manages to suppress the error message, or silently click it.
All nice and cool, but as have the -server running without steam and without the watchdog...
Thanks!
Bookmarks