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
If you start your server in an existing screen instance, systemd will refuse to monitor it. Currently, systemctl start newrun@whatever will report a timeout or configured resource limit exceeded, but systemctl status -l newrun@whatever will report the correct issue.
In this case, the service systemd is supposed to be monitoring does not belong to the cgroup systemd created for it, so it will always fail. There is no way around that.
You must instead configure unique screen sessions for each newrun-managed server. If the server crashes, the screen session will persist and have to be ended manually before restarting the server.
The text was updated successfully, but these errors were encountered:
If you start your server in an existing screen instance, systemd will refuse to monitor it. Currently,
systemctl start newrun@whatever
will report a timeout or configured resource limit exceeded, butsystemctl status -l newrun@whatever
will report the correct issue.In this case, the service systemd is supposed to be monitoring does not belong to the cgroup systemd created for it, so it will always fail. There is no way around that.
You must instead configure unique screen sessions for each newrun-managed server. If the server crashes, the screen session will persist and have to be ended manually before restarting the server.
The text was updated successfully, but these errors were encountered: