←back to thread

Show HN: Multi UPS SNMP based shutdown

(nupst.serve.zone)
25 points PhilKunz | 3 comments | 29 Mar 25 01:02 UTC | HN request time: 0.59s | source
Show context
windsurfer ◴[29 Mar 25 03:25 UTC] No.43512461[source]▶
Automatic updates? Node.js? Why would one want to use this over the tried-and-tested Network UPS Tools that already ships with most Linux distributions?
replies(6): >>43512823 #>>43512874 #>>43512945 #>>43513097 #>>43513462 #>>43528550 #
cyberax ◴[29 Mar 25 05:00 UTC] No.43512874[source]▶
Have you used these tools? Your main option is NUT, and it's not a great product. It crashes, it can't tolerate one of the UPSes being down, etc.

For my homelab, I ended up connecting my UPS via a USB cable to a Synology NAS and adding automation to shut down the rest of the servers to it.

replies(2): >>43512958 #>>43514457 #
1. cjk ◴[29 Mar 25 05:17 UTC] No.43512958[source]▶
I hadn’t realized this about NUT. I just started using it as part of TrueNAS’ built-in UPS monitoring support and haven’t had any issues thus far, but this gives me pause.

I buy that there is room for an alternative tool regardless of how crashy NUT is, but the technology choices for this are a huge turn-off IMO.

replies(2): >>43513493 #>>43513675 #
2. PhilKunz ◴[29 Mar 25 07:15 UTC] No.43513493[source]▶
Then use some rust file where you trust that the compiled file matches the source.
3. cyberax ◴[29 Mar 25 08:01 UTC] No.43513675[source]▶
I'd just stick the server into a docker container, and firewall it from the public Internet. NodeJS is not something that I'd use for these kinds of tools, but it's not inherently bad.