As discussed on Discord, a feature which will return the servers on one node to their power state before a potential crash of the Daemon or an unplanned reboot / crash of the host system will reduce the stress on an admin to remember the correct state of each server before.
This could be further improved by allowing the following three settings upon a daemon coming online:
- Power on all servers on this node
- Return all servers to their previous power state
- Power on all servers with the selected option to power on with daemon (has to be added to the servers settings)
- Keep all servers powered off
To avoid load spikes, a defineable delay between starting the servers will be beneficial. (30 seconds should be a good value to start with).
Let me know if this fit's here or should be more a daemon feature.
BentHaase
All 13 comments
Since there have been so many requests for this. Mind rethinking about adding this?
Wqrld
on 19 Jun 2018
Why rethink? It's still open isn't it?
schrej
on 20 Jun 2018
This was opened a long time ago and i thought i'd bump it as it kinda disappeared.
Wqrld
on 20 Jun 2018
When is this going to be done?
BLEEPBLOOPforLife
on 13 Nov 2018
Eventually. Its not a trivial task with the current state of the daemon.
DaneEveritt
on 14 Nov 2018
why has this been open for nearly 3 years? This is a very useful and basic feature of even docker itself.
Doonut
on 20 May 2019
It's still open because no one implemented it so far, feel free to do so.
We might be able to leverage dockers restart policy, but that would probably break the current crash detection that only tries to restart a container a few times instead of forever.
schrej
on 20 May 2019
Age of an issue does not determine the priority of implementation. In addition, I've already given this a swing once and it was significantly more difficult to properly implement than imagined, which is why it is still here.
DaneEveritt
on 20 May 2019
This really needs implementing. +1
YeapGuy
on 14 Sep 2019
closed for now in https://github.com/pterodactyl/wings/commit/85762ba4b990c12653ac1753e1de5b1ffa67a41b
DaneEveritt
on 25 Nov 2019
The return to the previous state only works in some containers (ex: minecraft), in the custom containers or Voice Server containers do not work. I don't know if it's my fault but it doesn't seem to be.
alekitopi
on 21 Jun 2020
So what are we supposed to do in case of a an unexpected shutdown? Re-start manually all servers? Genuinely confused
Fieel
on 29 Jul 2020
The issue is closed. It's implemented in the 1.0 betas.
So what are we supposed to do in case of a an unexpected shutdown? Re-start manually all servers? Genuinely confused
On stable, yes.
schrej
on 29 Jul 2020
Related issues
CoolJWB
路
4Comments
TRYTIG
路
3Comments
TylerBurr
路
4Comments
zKoz210
路
4Comments
schrej
路
3Comments
Most helpful comment
why has this been open for nearly 3 years? This is a very useful and basic feature of even docker itself.