Just FYI: current update seams to break NUT dependancies
-
@rzr
Hi, thank you for having a look.Regarding point 1.)
As it was written by Olivier Lambert in post https://xcp-ng.org/forum/topic/10250/what-os-is-xcp-ng-8-3-based-on/8?_=1773671654080 I understand that your focus is on datacenter usage. Nevertheless I still think - and in other posts users mention it as well - there are quite a lot small non-datacenter - installations in place that use xcp-ng in small office structures using and needing an USV, since it simply essential. I love using XCP-NG and believe it would be a goodie that would make a lot small open source supporters like me very happy.Regarding point 2.)
I am always careful when interfering with "mighty" tools like hypervisors. My experience is that my knowledge is unfortunately to small to see all caveats. -
This post is deleted! -
@FritzGerald workaround
yum update --exclude=net-snmp*This is dangerous.
@stormi Do you see any immediate threat? I am asking since it is working so far for me
-
You can install nut on a separate (small) machine and let it
sshto Your master and run a shutdown script.
That's how I do it since a while back when the NUT-package was temporarily removed from the extra repo -
Yes this "extra" tool was not (never?) supported ,
NUT has never been supported in XCP-ng, it has been asked about for a long time though and a lot of people handle XCP-ng not as an appliance but as any other Server/Desktop system and install packages because they aren't blocked from doing so
-
@rzr @stormi @olivierlambert Please consider this such a request. NUT's functionality at the small system/appliance level (i.e. not datacenter) of use is too useful to ignore but not enough to build a dedicated VM for on systems/appliances with limited resources.
-
I second this request.
-
https://xcp-ng.org/forum/topic/11967/gracefull-shutdown-of-host-when-ups-battery-runs-low
Not a great response, if this is really a need paying customers should go and put a request in on the ticketing side.
-
In case my experience can help with this problem:
The package causing compatibility issues is nut, but nut-client works and allows the xcp-ng hosts update.
I installed nut-client and defined the pool hosts as clients, with my nut server on a Truenas server.
This installation is working and has allowed me to continue using nut on my hosts.
-
Hi, I had a look at it and may have something to be tested soon (TBC https://github.com/xcp-ng-rpms/nut/pull/1 )
Is any of you volunteering for testing an extra (unsupported?) package ?
Or if the client is enough maybe we can put this on hold unless there is more traction?Reminder: https://docs.xcp-ng.org/management/additional-packages/
-
@rzr Hi. Thank you very much. I will be setting up a new server within the next 2 weeks and will definitely test it. Then I will give you feedback! Thank you again for picking it up!
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login