You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The !restart command often results in a "hung process" where Torch refuses to actually restart (but is no longer online and joinable) and needs to have its process manually terminated via Task Manager. My server has 6 restarts a day and I usually come across this issue 1-2 out of the 6 times. No errors appear in the log.
I've been advised this is a long-standing issue and the only work around is to run external batch files to monitor and forcibly kill the process. Is there anything that can be done to make the restart process more reliable though?
I have experienced this issue while running both fresh and old worlds.
The text was updated successfully, but these errors were encountered:
From what I have seen, you either have to setup a script to check if process is running or run an additional plugin. I run the ALE-RestartWatchdog plugin to get consistent restarts.
The !restart command often results in a "hung process" where Torch refuses to actually restart (but is no longer online and joinable) and needs to have its process manually terminated via Task Manager. My server has 6 restarts a day and I usually come across this issue 1-2 out of the 6 times. No errors appear in the log.
I've been advised this is a long-standing issue and the only work around is to run external batch files to monitor and forcibly kill the process. Is there anything that can be done to make the restart process more reliable though?
I have experienced this issue while running both fresh and old worlds.
The text was updated successfully, but these errors were encountered: