@cobordism said:

yum update --disablerepo=* --enablerepo=xcp-ng-base,xcp-ng-updates

It's currently in testing and will move to updates if everything (not only nut) is ok:

yum install --disablerepo=* \
   --enablerepo=xcp-ng-base,xcp-ng-updates,xcp-ng-testing  nut

# yum update --disablerepo=* --enablerepo=xcp-ng-base,xcp-ng-updates 
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
Excluding mirror: updates.xcp-ng.org
 * xcp-ng-base: mirrors.xcp-ng.org
Excluding mirror: updates.xcp-ng.org
 * xcp-ng-updates: mirrors.xcp-ng.org
Resolving Dependencies
--> Running transaction check
---> Package net-snmp.x86_64 1:5.7.2-52.1.xcpng8.3 will be updated
---> Package net-snmp.x86_64 1:5.9.3-8.1.xcpng8.3 will be an update
---> Package net-snmp-agent-libs.x86_64 1:5.7.2-52.1.xcpng8.3 will be updated
---> Package net-snmp-agent-libs.x86_64 1:5.9.3-8.1.xcpng8.3 will be an update
---> Package net-snmp-libs.x86_64 1:5.7.2-52.1.xcpng8.3 will be updated
--> Processing Dependency: libnetsnmp.so.31()(64bit) for package: OpenIPMI-2.0.23-2.el7.x86_64
---> Package net-snmp-libs.x86_64 1:5.9.3-8.1.xcpng8.3 will be an update
--> Finished Dependency Resolution
Error: Package: OpenIPMI-2.0.23-2.el7.x86_64 (@xcp-ng-base)
           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)

https://xcp-ng.org/forum/topic/9964/xcp-ng-8-3-updates-announcements-and-testing/432

Then please confirm the issue is gone by editing post topic with "[SOLVED]" prefix

@FritzGerald said:

@rzr Just for curiosity.

As far as I understand you assess the risk as low for the nut package - and only for that - to use ci-repo. I am fine with that for my personal servers.

• Would you consider to integrate this into "stable" branch?

yes it's the plan, we usually test packages in ci repos for a couple of weeks and once we're happy of the packages set it goes to testing repo, then users can officially test it (and based on feedback (or absence of feedback) then everything lands in update repo after a week or more (it depends on risk or hurry)..

• What would be the next steps on our side to support this?

I think nothing should be done your side you did your job before the testing window, early feedback is always appreciated (as long people know what they are doing )

But If I were you, just to be safe i would keep trace of packages i have installed from ci or testing repo, in case anything is not going as expected, you can still reinstall those packages from update channel.

• How long would does that roughly take?

It depends usually a couple of weeks, but this next batch might be a bit longer because there is a long waited feature planned.

Check the future announcement in the forum.

Thank again!

thank you for the detailed howto, if there is traction for this feature maybe it worth documenting officially, I'll ask product managers.

As far as I understand you assess the risk as low for the nut package - and only for that - to use ci-repo. I am fine with that for my personal servers. In terms of staying as close to the stable version in order to avoid potential future upgrade issues, is there a chance to say something about:

• Would you consider to integrate this into "stable" branch?
• What would be the next steps on our side to support this?
• How long would does that roughly take?

Thank again!

Quick install procedure for anyone interested. I use a USB connected APC Smart-UPS 750 (SMT750RMI2U) on a completely patched test "XCP-ng 8.3" server. To install ci packages run:

yum install nut --enablerepo=xcp-ng-ci

Most important, check that your USV device is properly connected and found using

lsusb

it should show something like:

...
Bus 002 Device 002: ID 051d:0003 American Power Conversion UPS
...

Grab details then by:

lsusb -s 002:002 -v

which should give you something like

[12:53 xcp-test ~]# lsusb -s 002:002 -v

Bus 002 Device 002: ID 051d:0003 American Power Conversion UPS
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0        64
  idVendor           0x051d American Power Conversion
  idProduct          0x0003 UPS
  bcdDevice            1.06
  iManufacturer           1 American Power Conversion
  iProduct                2 Smart-UPS 750 FW:UPS 15.1 / ID=18
  iSerial                 3 SERIALXXXXXXXX
  bNumConfigurations      1
...
  Remote Wakeup Enabled

Based upon this data you can add this information to your ups.conf

nano /etc/ups/ups.conf

[apc]
        driver = "usbhid-ups"
        port = "auto"
        vendorid = "051D"
        productid = "0003"
        product = "Smart-UPS 750 FW:UPS 15.1 / ID=18"
        serial = "SERIALXXXXXXXX"
        vendor = "American Power Conversion"
        bus = "002"

Now add users in nano /etc/ups/upsd.users. "upsmon" is for slave connected devices.

[admin]
      password = PWXXXXXX
      actions = SET FSD
      instcmds = ALL
      upsmon master

[upsmon]
      password = SLAVEPW
      upsmon slave

Now add/enable via nano /etc/ups/upsd.conf the required lines. If you want other servers to listen, you need to listen to a non-localhost IP of course.

LISTEN 127.0.0.1 3493

Now enable in nano /etc/ups/upsmon.conf the relevant line:

MONITOR apc@localhost 1 admin PWXXXXXX master

Now restart services:

upsdrvctl start
systemctl start nut-server.service
systemctl start nut-monitor.service

and you should be able to see the USV data by calling:

upsc apc@localhost

It should show:

battery.charge: 100
battery.charge.low: 10
battery.charge.warning: 50
battery.runtime: 3900
battery.runtime.low: 120
battery.type: PbAc
battery.voltage: 27.3
battery.voltage.nominal: 24.0
device.mfr: American Power Conversion
device.model: Smart-UPS 750
device.serial: SERIALXXXXX
device.type: ups
driver.name: usbhid-ups
driver.parameter.bus: 002
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.parameter.product: Smart-UPS 750 FW:UPS 15.1 / ID=18
driver.parameter.productid: 0003
driver.parameter.serial: SERIALXXXXX
driver.parameter.synchronous: auto
driver.parameter.vendor: American Power Conversion
driver.parameter.vendorid: 051D
driver.version: 2.8.0
driver.version.data: APC HID 0.98
driver.version.internal: 0.47
driver.version.usb: libusb-0.1 (or compat)
ups.beeper.status: enabled
ups.delay.shutdown: 20
ups.firmware: UPS 15.1 / ID=18
ups.mfr: American Power Conversion
ups.mfr.date: 2015/08/14
ups.model: Smart-UPS 750
ups.productid: 0003
ups.serial: SERIALXXXXX
ups.status: OL
ups.timer.reboot: -1
ups.timer.shutdown: -1
ups.vendorid: 051d

HINT#1: I experienced that the bus id of the usb device sometimes changes after reboot. Watch out if you restart the server and adapt your ups.conf accordingly!!!

HINT#2: You need to open firewall port 3493 if you want to access it from a monitor!

@FritzGerald said:

@rzr: Sorry, first and foremost I totally forgot to say thank you very much. I really appreciate you work and effort for this "non-core" issue.

You're welcome !

Keep in mind using/enabling ci repo can be dangerous but for this nut update the risk is low.

Is there maybe anything particular you are interested in for me to test?

Nothing specific, the regular use case but feel free to share to community your experience with your hardware:

https://networkupstools.org/ddl/APC/Smart-UPS_750.html

Then others can compare with other devices supported by N.U.T. :

https://networkupstools.org/ddl/

This makes me think, I have scavenged an APC BE400 but it looks like an offline device, unsure I will make anything useful soon.

That said, I can say that it works on my test machines. I could successfully install and connected to a APC Smart-UPS 750 (SMT750RMI2UC) to my test server. Not a single problem whatsoever. I will now monitor it a bit and if I observe anything I will let you know.

Is there maybe anything particular you are interested in for me to test?

Since I have never installed this type of "dev" package, I just wanted to let others know how to install (please to so on a testing server). Besides that, just run:

yum install nut --enablerepo=xcp-ng-ci

That's it. At least installation on my newly setup and completely patched test "XCP-ng 8.3" server worked like a charme:

[22:41 xcp-test ~]# yum install nut --enablerepo=xcp-ng-ci
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
Excluding mirror: updates.xcp-ng.org
 * xcp-ng-base: mirrors.xcp-ng.org
Excluding mirror: updates.xcp-ng.org
 * xcp-ng-ci: mirrors.xcp-ng.org
Excluding mirror: updates.xcp-ng.org
 * xcp-ng-updates: mirrors.xcp-ng.org
xcp-ng-base/signature                                                                                                                                                                        |  473 B  00:00:00
xcp-ng-base/signature                                                                                                                                                                        | 3.0 kB  00:00:00 !!!
xcp-ng-ci/signature                                                                                                                                                                          |  473 B  00:00:00
xcp-ng-ci/signature                                                                                                                                                                          | 3.0 kB  00:00:00 !!!
xcp-ng-updates/signature                                                                                                                                                                     |  473 B  00:00:00
xcp-ng-updates/signature                                                                                                                                                                     | 3.0 kB  00:00:00 !!!
xcp-ng-ci/primary_db                                                                                                                                                                         | 168 kB  00:00:00
Resolving Dependencies
--> Running transaction check
---> Package nut.x86_64 0:2.8.0-2.1.xcpng8.3 will be installed
--> Processing Dependency: libfreeipmi.so.17()(64bit) for package: nut-2.8.0-2.1.xcpng8.3.x86_64
--> Processing Dependency: libipmimonitoring.so.6()(64bit) for package: nut-2.8.0-2.1.xcpng8.3.x86_64
--> Processing Dependency: libltdl.so.7()(64bit) for package: nut-2.8.0-2.1.xcpng8.3.x86_64
--> Processing Dependency: libupsclient.so.6()(64bit) for package: nut-2.8.0-2.1.xcpng8.3.x86_64
--> Processing Dependency: libusb-0.1.so.4()(64bit) for package: nut-2.8.0-2.1.xcpng8.3.x86_64
--> Running transaction check
---> Package freeipmi.x86_64 0:1.5.7-2.el7 will be installed
---> Package libtool-ltdl.x86_64 0:2.4.2-22.el7_3 will be installed
---> Package libusb.x86_64 1:0.1.4-3.el7 will be installed
---> Package nut-client.x86_64 0:2.8.0-2.1.xcpng8.3 will be installed
--> Finished Dependency Resolution

Dependencies Resolved

====================================================================================================================================================================================================================
 Package                                            Arch                                         Version                                                    Repository                                         Size
====================================================================================================================================================================================================================
Installing:
 nut                                                x86_64                                       2.8.0-2.1.xcpng8.3                                         xcp-ng-ci                                         2.2 M
Installing for dependencies:
 freeipmi                                           x86_64                                       1.5.7-2.el7                                                xcp-ng-base                                       2.0 M
 libtool-ltdl                                       x86_64                                       2.4.2-22.el7_3                                             xcp-ng-base                                        48 k
 libusb                                             x86_64                                       1:0.1.4-3.el7                                              xcp-ng-base                                        19 k
 nut-client                                         x86_64                                       2.8.0-2.1.xcpng8.3                                         xcp-ng-ci                                         203 k

Transaction Summary
====================================================================================================================================================================================================================
Install  1 Package (+4 Dependent packages)

Total download size: 4.5 M
Installed size: 20 M
Is this ok [y/d/N]: y
Downloading packages:
(1/5): libtool-ltdl-2.4.2-22.el7_3.x86_64.rpm                                                                                                                                                |  48 kB  00:00:00
(2/5): freeipmi-1.5.7-2.el7.x86_64.rpm                                                                                                                                                       | 2.0 MB  00:00:01
(3/5): libusb-0.1.4-3.el7.x86_64.rpm                                                                                                                                                         |  19 kB  00:00:00
(4/5): nut-client-2.8.0-2.1.xcpng8.3.x86_64.rpm                                                                                                                                              | 203 kB  00:00:00
(5/5): nut-2.8.0-2.1.xcpng8.3.x86_64.rpm                                                                                                                                                     | 2.2 MB  00:00:01
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Total                                                                                                                                                                               1.7 MB/s | 4.5 MB  00:00:02
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
  Installing : nut-client-2.8.0-2.1.xcpng8.3.x86_64                                                                                                                                                             1/5
  Installing : freeipmi-1.5.7-2.el7.x86_64                                                                                                                                                                      2/5
  Installing : libtool-ltdl-2.4.2-22.el7_3.x86_64                                                                                                                                                               3/5
  Installing : 1:libusb-0.1.4-3.el7.x86_64                                                                                                                                                                      4/5
  Installing : nut-2.8.0-2.1.xcpng8.3.x86_64                                                                                                                                                                    5/5
  Verifying  : nut-2.8.0-2.1.xcpng8.3.x86_64                                                                                                                                                                    1/5
  Verifying  : 1:libusb-0.1.4-3.el7.x86_64                                                                                                                                                                      2/5
  Verifying  : libtool-ltdl-2.4.2-22.el7_3.x86_64                                                                                                                                                               3/5
  Verifying  : freeipmi-1.5.7-2.el7.x86_64                                                                                                                                                                      4/5
  Verifying  : nut-client-2.8.0-2.1.xcpng8.3.x86_64                                                                                                                                                             5/5

Installed:
  nut.x86_64 0:2.8.0-2.1.xcpng8.3

Dependency Installed:
  freeipmi.x86_64 0:1.5.7-2.el7                    libtool-ltdl.x86_64 0:2.4.2-22.el7_3                    libusb.x86_64 1:0.1.4-3.el7                    nut-client.x86_64 0:2.8.0-2.1.xcpng8.3

Complete!

I will let you know once I got some impressions.

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/

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.

Not a great response, if this is really a need paying customers should go and put a request in on the ticketing side.

@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

@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

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.

@bogikornel said:

@FritzGerald workaround

yum update --exclude=net-snmp*

This is dangerous.

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