Page 1 of 1

[0.17.17] Dedicated Server no longer shutting down

Posted: Mon Mar 25, 2019 10:26 am
by pingger
Hi,

TLDR:
- Server keeps running after "/quit" and only saves+unloads the map, no way to stop except SIGINT.

Long:
I have an automatic update checker and installer, which (upon finding an update) automatically closes any running Factorio Server on my Server Machine (Windows Server 2012). Until 0.16 the Server would save and exit when sending the "/quit" command to the server.

But since 0.17 (don't the exact update, but 0.17.17 is affected) the Server no longer exits, but only saves the World and unloads it.

After that the Server is in a state in which no longer accepts any clients or commands. Only way to close is SIGINT, which is a fairly bad way since it usually involves a human interacting with a console window. But when the normally the server is started without any console window.


Greetings
Pingger

Re: [0.17.17] Dedicated Server no longer shutting down

Posted: Mon Mar 25, 2019 1:33 pm
by Rseding91
Thanks for the report. Are you running the server on Windows or Linux?

Re: [0.17.17] Dedicated Server no longer shutting down

Posted: Mon Mar 25, 2019 2:22 pm
by posila
Thanks for the report.
It should be fixed for the next release.

Re: [0.17.17] Dedicated Server no longer shutting down

Posted: Mon Mar 25, 2019 5:49 pm
by pingger
Rseding91 wrote:
Mon Mar 25, 2019 1:33 pm
Thanks for the report. Are you running the server on Windows or Linux?
As already described in the first post a Windows Server 2012

Re: [0.17.17] Dedicated Server no longer shutting down

Posted: Mon Mar 25, 2019 9:03 pm
by Hiekie
What kind of tool do you use to automatic update your Windows headless server?

Re: [0.17.17] Dedicated Server no longer shutting down

Posted: Thu Jan 09, 2020 3:05 pm
by neo130288
i am still running in to this problem in 0.17.79

any news on a fix?

Re: [0.17.17] Dedicated Server no longer shutting down

Posted: Thu Jan 09, 2020 7:52 pm
by Rseding91
neo130288 wrote:
Thu Jan 09, 2020 3:05 pm
i am still running in to this problem in 0.17.79

any news on a fix?
You'll need to make a new report with new steps to reproduce because it doesn't happen for us.