4 ms·

Looks great! The one issue i have is my Proxmox server runs OPNsense and all my hosted apps. It has an APC UPS. Some of the apps gracefully close down when UPS

by spants 2y ago

Looks great! The one issue i have is my Proxmox server runs OPNsense and all my hosted apps. It has an APC UPS. Some of the apps gracefully close down when UPS is low and power is lost. If UPS power fails completely, then PC is obviously off. Is there a foolproof way that the server will restart when UPS receives power again?. I see a "restart on power loss" in BIOS but is this the proper way to do it?

MaKey 2y ago
> I see a "restart on power loss" in BIOS but is this the proper way to do it? Yes, it is.
swinglock 2y ago
Server class hardware will let you choose. Other varies. Some will let you choose to always start on power, some won't. "Restart on power loss" should cover your use case, since you don't shut down the computer gracefully on low power.
themoonisachees 2y ago
That's what you should use, yes. It's a bit different in enterprise because you want to stagger the restarts of all your servers to avoid browning out the recently restored power, but for an at-home system that's fine.
k8sToGo 2y ago
That option works, but only if the UPS was truly off and no power on the socket.
Brian_K_White 2y ago
If it was a pikvm instead of proprietary, you could script it to do anything you want if some other user with the same common wish didn't already build it in. Restart on power loss in the bios is usually the right way if the machine is a server that you know you always want it to be on or trying. It only gets complicated when you have say, a full backup clone of that machine that you actually want to be a cold spare not a hot spare. So it exists, is plugged in, but turned off, and you want it to stay off unless you explicitly turn it on because it would conflict with the primary, and yet want to be able to do that remotely or even automatically but by some more complex logic than merely the fact that power went from off to on. That's not super common, but it would take something weird like that to not want simple bios always-on. Usually it should be easy enough to have a machine always try to turn on, and decide for itself that it should shut back down.

by spants 2y ago

MaKey 2y ago

> I see a "restart on power loss" in BIOS but is this the proper way to do it? Yes, it is.

swinglock 2y ago

Server class hardware will let you choose. Other varies. Some will let you choose to always start on power, some won't. "Restart on power loss" should cover your use case, since you don't shut down the computer gracefully on low power.

themoonisachees 2y ago

That's what you should use, yes. It's a bit different in enterprise because you want to stagger the restarts of all your servers to avoid browning out the recently restored power, but for an at-home system that's fine.

k8sToGo 2y ago

That option works, but only if the UPS was truly off and no power on the socket.

Brian_K_White 2y ago

If it was a pikvm instead of proprietary, you could script it to do anything you want if some other user with the same common wish didn't already build it in. Restart on power loss in the bios is usually the right way if the machine is a server that you know you always want it to be on or trying. It only gets complicated when you have say, a full backup clone of that machine that you actually want to be a cold spare not a hot spare. So it exists, is plugged in, but turned off, and you want it to stay off unless you explicitly turn it on because it would conflict with the primary, and yet want to be able to do that remotely or even automatically but by some more complex logic than merely the fact that power went from off to on. That's not super common, but it would take something weird like that to not want simple bios always-on. Usually it should be easy enough to have a machine always try to turn on, and decide for itself that it should shut back down.