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
I'm using the torch on a Space Engineers server at Streamline Servers, copy the reboot example from the plugin's wiki.
The log informs that there was a timeout when saving and after that the company panel is in an Error state, as if waiting for a torch response that never arrived.
The server is brand new, less than 1 week, had almost no built, hardly any players, and the save internally in the game, via command, takes less than 2 seconds.
The solution that the company gave me was not to use the torch to restart the server... I think the problem may be in referencing the save instance folder for example... or some kind of permission... The question is that the logs are not straightforward as to why the save timeout and I don't see any material that mentions this error message. And the company has the torch as a possibility but support makes no effort to help.
The text was updated successfully, but these errors were encountered:
I'm using the torch on a Space Engineers server at Streamline Servers, copy the reboot example from the plugin's wiki.
The log informs that there was a timeout when saving and after that the company panel is in an Error state, as if waiting for a torch response that never arrived.
The server is brand new, less than 1 week, had almost no built, hardly any players, and the save internally in the game, via command, takes less than 2 seconds.
The solution that the company gave me was not to use the torch to restart the server... I think the problem may be in referencing the save instance folder for example... or some kind of permission... The question is that the logs are not straightforward as to why the save timeout and I don't see any material that mentions this error message. And the company has the torch as a possibility but support makes no effort to help.
The text was updated successfully, but these errors were encountered: