Just FYI: current update seams to break NUT dependancies

FritzGerald

Just a short informational update. Current xcp-ng update seems to break nut dependancies.

Error: Package: nut-2.8.0-2.el7.x86_64 (@epel)
           Requires: libnetsnmp.so.31()(64bit)
           Removing: 1:net-snmp-libs-5.7.2-52.1.xcpng8.3.x86_64 (@xcp-ng-updates)
               libnetsnmp.so.31()(64bit)
           Updated By: 1:net-snmp-libs-5.9.3-8.1.xcpng8.3.x86_64 (xcp-ng-updates)
              ~libnetsnmp.so.40()(64bit)
           Available: 1:net-snmp-libs-5.7.2-33.el7_5.2.x86_64 (xcp-ng-base)
               libnetsnmp.so.31()(64bit)
           Available: 1:net-snmp-libs-5.7.2-51.1.xcpng8.3.x86_64 (xcp-ng-base)
               libnetsnmp.so.31()(64bit)
           Available: 1:net-snmp-libs-5.7.2-51.2.xcpng8.3.x86_64 (xcp-ng-base)
               libnetsnmp.so.31()(64bit)
           Available: 1:net-snmp-libs-5.7.2-51.3.xcpng8.3.x86_64 (xcp-ng-base)
               libnetsnmp.so.31()(64bit)

Since NUT is an "external" package and everyone was warned about installing "3rd-party" packages, this is not an official xcp-ng problem. I have not yet found a workaround. Since the old repos EPEL 7 are not really updated, it could get tricky. I just wanted to let you know.

bogikornel

@FritzGerald workaround

yum update --exclude=net-snmp*

FritzGerald

@bogikornel said:

yum update --exclude=net-snmp*

You made my day. Works fine and I have learned something new. Thank you for your quick help!

Kajetan321

I'm having the same problem. I could never get NUT to work properly anyways. What's the best way to uinstal it?

Kajetan321

It looks like "yum remove nut" does the trick.

rzr

@Kajetan321 said:

It looks like "yum remove nut" does the trick.

Yes this "extra" tool was not (never?) supported ,

If you really need it, there are 2 options to consider:

1st is convince us to add it to the distro
2d rebuild it yourself (to link with updated dep, and also rebuild its deps like neon)

stormi

@bogikornel said:

@FritzGerald workaround
yum update --exclude=net-snmp*

This is dangerous.

FritzGerald

@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.

FritzGerald

This post is deleted!

FritzGerald

@stormi said:
@bogikornel said:

@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

ph7

You can install nut on a separate (small) machine and let it ssh to 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

DustinB

@rzr said:

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