Performing automated shutdown during a power failure using a USB-UPS with NUT - XCP-ng 8.2

[odeawan]

Well I still don't think it is out of scope then for just the NUT client for enterprises or HomeLabs on XCP-NG.

SBCs are everywhere these days. Using a Raspberry Pi as the NUT Server in a homelab or a flavor of a more robust server for NUT seems like a solid choice. No USB passthrough to worry about, uptime on a 1500VA+ UPS, forget about it! There are a handful of guides how to get it running for a Pi or anything else (including this post).

As I think this though, I would still feel ok with another external device watching, waiting, and notifying me on a successful power off of any number of my hosts and VMs. Not all enterprises or homelabs can afford (even if their appetites want it) to get enterprise level power automations. We have our power. Break the chain. @olivierlambert

[olivierlambert]

Which chain? The development is open, if you want something, do it If you want to be the maintainer so we can have it updated, packaged and put in our repo (even if not bundled by default), go ahead! If we think there's people behind it, we are not against, since it's an extra package.

[dj423]

This post is deleted!

[nomad]

After NUT's grand reconfiguration there are a few things that you need to be aware of:

In order to run NUT as a monitor to shut down your XCP-ng hypervisors it is no longer sufficient to just install nut-client and enable nut-monitor.

You also need to install nut and enable nut.target or nut-monitor won't autostart. There won't be anything in journalctl either, since it isn't even trying to start - the thing that tells it to do so is the nut.target and if that's missing nothing will ever trigger.

yum install nut nut-client --enablerepo=epel

make your edits in nut.conf and upsmon.conf then

systemctl enable nut.target 
systemctl enable nut-monitor 
systemctl start nut-monitor

[CodeMercenary]

@nomad What do you mean by the grand reconfiguration? Is there a new version that changes how things work?

[samuelolavo]

Hello,

I’ve been configuring NUT on XCP-ng 8.3 and had some trouble finding proper documentation. However, after going through the messages in this forum, I created a document that I believe might help others set up the NUT client on XCP-ng 8.3:
https://github.com/samuel-olavo/xcp-ng-nutclient

This method worked for me — tested and confirmed.

Thanks everyone!

[Forza]

@samuelolavo, nice work! I wonder if it can be improved by using an independent machine/unit and login remotely via ssh and execute the script? This way we need no modification on xcp-ng dom0 itself.

[ph7]

@Forza
Yes it can
This is how I do it
https://xcp-ng.org/forum/topic/10834/apcupsd-install/9

[Strebor]

For people running XCP-ng, wanting to use NUT client to power down gracefully during longer power outages, it could be interesting to note that Unifi now has two very affordable UPS models that feature a built in NUT server. So no need to run your own NUT server.

[datacare]

I have been in the Network Enterprise business for 28 years. I live in Virginia which is heavily populated with Data Centers and adding more all the time.
However, we have quite a few customers especially municipalities which are saying NO to having anything hosted with cloud computing due to security and endless rising cost. We have been deploying xcp-ng in quite a few installations, on customer premise. I think VATES will find there is a whole other market in these areas they can reach.

That being said, Thanks to VATES and all who have worked on solutions for this! It truly benefits everyone!