Offline issue

[JoanFo1456]

Current Behavior

When restarting a server and clicking "kill", makes the server restart but as "Offline", unless you click start the server will appear as "Offline" but in reality is started.

Expected Behavior

It shouldn't happen this, after killing the status should be like normal, starting, running...

Steps to Reproduce

1. On a server started, click restart and then kill.

Panel Version

Canary 35ce1d3

Wings Version

"develop" (Latest)

Games and/or Eggs Affected

No response

Docker Image

No response

Error Logs

Is there an existing issue for this?

• I have searched the existing issues before opening this issue.
• I have provided all relevant details, including the specific game and Docker images I am using if this issue is related to running a server.
• I have checked in the Discord server and believe this is a bug with the software, and not a configuration issue with my specific system.

[JoanFo1456]

(Screenshot is from demo)

[Boy132]

Seems like a wings issue: https://paste.pelistuff.com/wexJ
Or it's a problem with the power buttons on the panel.

[mristau]

it reproducably happens happens if the kill is between the lines marked 1. and 2.
if kill is klicked after 2. then it will just shutdown

1. pelican@sparrow ~ Server marked as offline...
[pelican Daemon]: Updating process configuration files...
[pelican Daemon]: Ensuring file permissions are set correctly, this could take a few seconds...
2. pelican@sparrow ~ Server marked as starting...
[pelican Daemon]: Pulling Docker container image, this could take a few minutes to complete...
pelican@sparrow ~ Server marked as offline...
[pelican Daemon]: ---------- Detected server process in a crashed state! ----------
[pelican Daemon]: Exit code: 1
[pelican Daemon]: Out of memory: false
[pelican Daemon]: Server crash was detected but an error occurred while handling it.
Pulling from parkervcp/yolks
... Server starting logs

My Suggestion for at least reduce the issue, was to add a "double opt in" for killing, means klick kill -> "Do you really want to kill, it is not suggested, can lead to corrupt saves ..."

[JustTNE]

This is especially a problem when the server one is trying to stop refuses to stop normally. The only action that can be taken from the user interface to remedy the situation is to then kill the server.

This will then trigger the restart, but pelican doesn't seem to realize the restart is taking place and continues to offer only the start button, even beyond a reload of the page.

[notAreYouScared]

If this is still an issue with the latest beta, please mention it here for this issue to be reopened.

[JoanFo1456]

Still an issue, needs reopening @notAreYouScared