Hi Toolguy, thank you for clarifying and I am checking out those logs now
What would be interesting is whether this crash (not blaming your tool) occurs when the launcher is not used, meaning the old style /organic way of running the Conan server through a manual command line and/or basic batch file. The aim being that when it does crash, does it give the same generic error about not responding.
I suspect it does.
I’ve been reading up more on using Powershell now and I’m close I think to a form of a watchdog, at least in the sense it queries any processes (or a specific PID) that is in a not responding state - say every ten minutes. If it finds one, it runs a KILL command
However upon testing this script it did not work as it doesn’t actually think the program is not responding. The Get-Process returns a result that the program is still operating.
So…this was one of my concerns and why I mentioned whether you’d built something into or aim to build something into the launcher to do this very thing, but a bit more heavy handed in that for example as soon as it sees the server crash and go down, it immediately stops the process, checks it’s not already running and then restarts the server.
So yes would very much like a watchdog and kill built into your launcher
And for anyone who doesn’t want this behavior, it could be a toggled option?
Also, let’s not forget I may be using poor terminology here in that “not responding” is not the same as “suspended” and I wonder whether at the time of the generic error, the sandbox executable is a suspended state.
Any thing I should be searching for in particular in the log? “Shutdown?”