NUT Package (2.8.1 and above)
-
@dennypage I didn't update by hand, used the Package Manager. But, I think I know what may have happened: I was trying to update to CE 2.7.1-RC and changed the branch (even though I'm still on 2.7), and that may have caused the new NUT package to show up.
Now I'm unable to upgradeto 2.7.1, however. The Update page says I'm on the latest 2.7. Even if I change to 2.7.1-RC branch. May need to force-upgrade it.
-
@dmitri said in NUT Package (2.8.1 and above):
I've added "RUN_AS_USER root" to the upsmon.conf and "user=root" to ups.conf. But those didn't have any effect.
FYI, if you are using a remote nut connection, you are not running upsd.
-
@dmitri said in NUT Package (2.8.1 and above):
I didn't update by hand, used the Package Manager. But, I think I know what may have happened: I was trying to update to CE 2.7.1-RC and changed the branch (even though I'm still on 2.7), and that may have caused the new NUT package to show up.
Okay, now that makes more sense.
The upsmon from 2.8.1 isn't going to be able to start in a 2.7.0 system because libraries that it needs, such as OpenSSL 3, are not there.
-
@dennypage said in NUT Package (2.8.1 and above):
FYI, if you are using a remote nut connection, you are not running upsd.
Yeah, I guess I was just shooting in the dark at this point :). I've since removed those lines.
After upgrading to 2.7.1-RC the issues went away. Thanks for the help!
-
@dmitri said in NUT Package (2.8.1 and above):
After upgrading to 2.7.1-RC the issues went away.
Are you running NUT 2.8.1 there?
-
@dennypage Just double checked, yes 2.8.1 NUT package on 2.7.1-RC.
-
@dennypage I've done some additional testing. Initially when I tried the updated package I was receiving connection lost/established messages. I've restarted pfSense, removed all nut packages, reinstalled nut (pfsense-pkg-nut, and the nut package itself), removed nut, installed the nut-devel-2023.10.07_01 and restarted the service.
I then did some testing and grabbed some logs. So far I haven't received any more connection lost notices, but they were sporadic over an hour timeframe. Here are the logs/info, in case you see anything that jumps out. I do see no matching INFO_* value for OID listed for a bunch of different OID values (in the log).
[23.09-RELEASE][admin@netgate]/tmp/acme: upsc CyberPowerCP2200 battery.charge: 100 battery.current: 3.50 battery.date: 12/22/2022 battery.runtime: 3300 battery.runtime.elapsed: 0 battery.voltage: 81.10 battery.voltage.nominal: 72 device.contact: Shaun device.description: UPS SNMP Card device.location: Basement device.mfr: CYBERPOWER device.model: OL2200RTXL2U device.serial: WBGEP2000038 device.type: ups driver.debug: 0 driver.flag.allow_killpower: 0 driver.name: snmp-ups driver.parameter.pollinterval: 2 driver.parameter.port: 10.10.5.10 driver.parameter.synchronous: auto driver.state: quiet driver.version: 2.8.0.1 driver.version.data: cyberpower MIB 0.55 driver.version.internal: 1.30 input.frequency: 60 input.transfer.reason: noTransfer input.voltage: 123 output.current: 3.50 output.frequency: 60 output.voltage: 120.20 ups.delay.reboot: 0 ups.delay.shutdown: 180 ups.delay.start: 0 ups.firmware: S1A14 ups.id: CP2200 ups.load: 19 ups.mfr: CYBERPOWER ups.model: OL2200RTXL2U ups.serial: WBGEP2000038 ups.status: OL ups.temperature: 34 ups.test.date: 11/12/2023 ups.test.result: Ok
[23.09-RELEASE][admin@netgate]/tmp/acme: snmpwalk -v 1 -c public 10.10.5.10 SNMPv2-SMI::enterprises.3808.1.1.1 SNMPv2-SMI::enterprises.3808.1.1.1.1.1.1.0 = STRING: "OL2200RTXL2U" SNMPv2-SMI::enterprises.3808.1.1.1.1.1.2.0 = STRING: "CP2200" SNMPv2-SMI::enterprises.3808.1.1.1.1.2.1.0 = STRING: "S1A14" SNMPv2-SMI::enterprises.3808.1.1.1.1.2.3.0 = STRING: "WBGEP2000038" SNMPv2-SMI::enterprises.3808.1.1.1.1.2.4.0 = STRING: "1.4.0" SNMPv2-SMI::enterprises.3808.1.1.1.1.2.5.0 = NULL SNMPv2-SMI::enterprises.3808.1.1.1.1.2.6.0 = INTEGER: 2200 SNMPv2-SMI::enterprises.3808.1.1.1.1.2.7.0 = INTEGER: 1800 SNMPv2-SMI::enterprises.3808.1.1.1.1.2.8.0 = INTEGER: 180 SNMPv2-SMI::enterprises.3808.1.1.1.1.2.9.0 = NULL SNMPv2-SMI::enterprises.3808.1.1.1.2.1.1.0 = INTEGER: 2 SNMPv2-SMI::enterprises.3808.1.1.1.2.1.2.0 = Timeticks: (0) 0:00:00.00 SNMPv2-SMI::enterprises.3808.1.1.1.2.1.3.0 = STRING: "12/22/2022" SNMPv2-SMI::enterprises.3808.1.1.1.2.1.4.0 = INTEGER: 36 SNMPv2-SMI::enterprises.3808.1.1.1.2.2.1.0 = Gauge32: 100 SNMPv2-SMI::enterprises.3808.1.1.1.2.2.2.0 = Gauge32: 811 SNMPv2-SMI::enterprises.3808.1.1.1.2.2.3.0 = NULL SNMPv2-SMI::enterprises.3808.1.1.1.2.2.4.0 = Timeticks: (330000) 0:55:00.00 SNMPv2-SMI::enterprises.3808.1.1.1.2.2.5.0 = INTEGER: 1 SNMPv2-SMI::enterprises.3808.1.1.1.2.2.8.0 = INTEGER: 72 SNMPv2-SMI::enterprises.3808.1.1.1.2.2.9.0 = NULL SNMPv2-SMI::enterprises.3808.1.1.1.3.1.1.0 = INTEGER: 1 SNMPv2-SMI::enterprises.3808.1.1.1.3.2.1.0 = Gauge32: 1230 SNMPv2-SMI::enterprises.3808.1.1.1.3.2.2.0 = Gauge32: 1232 SNMPv2-SMI::enterprises.3808.1.1.1.3.2.3.0 = Gauge32: 1230 SNMPv2-SMI::enterprises.3808.1.1.1.3.2.4.0 = Gauge32: 600 SNMPv2-SMI::enterprises.3808.1.1.1.3.2.5.0 = INTEGER: 1 SNMPv2-SMI::enterprises.3808.1.1.1.3.2.6.0 = INTEGER: 1 SNMPv2-SMI::enterprises.3808.1.1.1.4.1.1.0 = INTEGER: 2 SNMPv2-SMI::enterprises.3808.1.1.1.4.1.2.0 = INTEGER: 1 SNMPv2-SMI::enterprises.3808.1.1.1.4.1.3.0 = STRING: "40~70 Hz" SNMPv2-SMI::enterprises.3808.1.1.1.4.2.1.0 = Gauge32: 1200 SNMPv2-SMI::enterprises.3808.1.1.1.4.2.2.0 = INTEGER: 600 SNMPv2-SMI::enterprises.3808.1.1.1.4.2.3.0 = Gauge32: 19 SNMPv2-SMI::enterprises.3808.1.1.1.4.2.4.0 = Gauge32: 35 SNMPv2-SMI::enterprises.3808.1.1.1.4.2.5.0 = Gauge32: 342 SNMPv2-SMI::enterprises.3808.1.1.1.4.2.6.0 = NULL SNMPv2-SMI::enterprises.3808.1.1.1.4.2.7.0 = NULL SNMPv2-SMI::enterprises.3808.1.1.1.5.1.1.0 = INTEGER: 24 SNMPv2-SMI::enterprises.3808.1.1.1.5.1.2.1.1.1 = INTEGER: 1 SNMPv2-SMI::enterprises.3808.1.1.1.5.1.2.1.1.2 = INTEGER: 2 SNMPv2-SMI::enterprises.3808.1.1.1.5.1.2.1.1.3 = INTEGER: 3 SNMPv2-SMI::enterprises.3808.1.1.1.5.1.2.1.1.4 = INTEGER: 4 SNMPv2-SMI::enterprises.3808.1.1.1.5.1.2.1.1.5 = INTEGER: 5 SNMPv2-SMI::enterprises.3808.1.1.1.5.1.2.1.1.6 = INTEGER: 6 SNMPv2-SMI::enterprises.3808.1.1.1.5.1.2.1.1.7 = INTEGER: 7 SNMPv2-SMI::enterprises.3808.1.1.1.5.1.2.1.1.8 = INTEGER: 8 SNMPv2-SMI::enterprises.3808.1.1.1.5.1.2.1.1.9 = INTEGER: 9 SNMPv2-SMI::enterprises.3808.1.1.1.5.1.2.1.1.10 = INTEGER: 10 SNMPv2-SMI::enterprises.3808.1.1.1.5.1.2.1.1.11 = INTEGER: 11 SNMPv2-SMI::enterprises.3808.1.1.1.5.1.2.1.1.12 = INTEGER: 12 SNMPv2-SMI::enterprises.3808.1.1.1.5.1.2.1.1.13 = INTEGER: 13 SNMPv2-SMI::enterprises.3808.1.1.1.5.1.2.1.1.14 = INTEGER: 14 SNMPv2-SMI::enterprises.3808.1.1.1.5.1.2.1.1.15 = INTEGER: 15 SNMPv2-SMI::enterprises.3808.1.1.1.5.1.2.1.2.1 = STRING: "Outlet1" SNMPv2-SMI::enterprises.3808.1.1.1.5.1.2.1.2.2 = STRING: "Outlet2" SNMPv2-SMI::enterprises.3808.1.1.1.5.1.2.1.2.3 = STRING: "Outlet3" SNMPv2-SMI::enterprises.3808.1.1.1.5.1.2.1.2.4 = STRING: "Outlet4" SNMPv2-SMI::enterprises.3808.1.1.1.5.1.2.1.2.5 = STRING: "Outlet5" SNMPv2-SMI::enterprises.3808.1.1.1.5.1.2.1.2.6 = STRING: "Outlet6" SNMPv2-SMI::enterprises.3808.1.1.1.5.1.2.1.2.7 = STRING: "Outlet7" SNMPv2-SMI::enterprises.3808.1.1.1.5.1.2.1.2.8 = STRING: "Outlet8" SNMPv2-SMI::enterprises.3808.1.1.1.5.1.2.1.2.9 = STRING: "Outlet9" SNMPv2-SMI::enterprises.3808.1.1.1.5.1.2.1.2.10 = STRING: "Outlet10" SNMPv2-SMI::enterprises.3808.1.1.1.5.1.2.1.2.11 = STRING: "Outlet11" SNMPv2-SMI::enterprises.3808.1.1.1.5.1.2.1.2.12 = STRING: "Outlet12" SNMPv2-SMI::enterprises.3808.1.1.1.5.1.2.1.2.13 = STRING: "Outlet13" SNMPv2-SMI::enterprises.3808.1.1.1.5.1.2.1.2.14 = STRING: "Outlet14" SNMPv2-SMI::enterprises.3808.1.1.1.5.1.2.1.2.15 = STRING: "Outlet15" SNMPv2-SMI::enterprises.3808.1.1.1.5.1.2.1.3.1 = INTEGER: 0 SNMPv2-SMI::enterprises.3808.1.1.1.5.1.2.1.3.2 = INTEGER: 0 SNMPv2-SMI::enterprises.3808.1.1.1.5.1.2.1.3.3 = INTEGER: 0 SNMPv2-SMI::enterprises.3808.1.1.1.5.1.2.1.3.4 = INTEGER: 0 SNMPv2-SMI::enterprises.3808.1.1.1.5.1.2.1.3.5 = INTEGER: 0 SNMPv2-SMI::enterprises.3808.1.1.1.5.1.2.1.3.6 = INTEGER: 0 SNMPv2-SMI::enterprises.3808.1.1.1.5.1.2.1.3.7 = INTEGER: 0 SNMPv2-SMI::enterprises.3808.1.1.1.5.1.2.1.3.8 = INTEGER: 0 SNMPv2-SMI::enterprises.3808.1.1.1.5.1.2.1.3.9 = INTEGER: 0 SNMPv2-SMI::enterprises.3808.1.1.1.5.1.2.1.3.10 = INTEGER: 0 SNMPv2-SMI::enterprises.3808.1.1.1.5.1.2.1.3.11 = INTEGER: 0 SNMPv2-SMI::enterprises.3808.1.1.1.5.1.2.1.3.12 = INTEGER: 0 SNMPv2-SMI::enterprises.3808.1.1.1.5.1.2.1.3.13 = INTEGER: 0 SNMPv2-SMI::enterprises.3808.1.1.1.5.1.2.1.3.14 = INTEGER: 0 SNMPv2-SMI::enterprises.3808.1.1.1.5.1.2.1.3.15 = INTEGER: 0 SNMPv2-SMI::enterprises.3808.1.1.1.5.1.2.1.4.1 = INTEGER: 2 SNMPv2-SMI::enterprises.3808.1.1.1.5.1.2.1.4.2 = INTEGER: 2 SNMPv2-SMI::enterprises.3808.1.1.1.5.1.2.1.4.3 = INTEGER: 2 SNMPv2-SMI::enterprises.3808.1.1.1.5.1.2.1.4.4 = INTEGER: 2 SNMPv2-SMI::enterprises.3808.1.1.1.5.1.2.1.4.5 = INTEGER: 2 SNMPv2-SMI::enterprises.3808.1.1.1.5.1.2.1.4.6 = INTEGER: 2 SNMPv2-SMI::enterprises.3808.1.1.1.5.1.2.1.4.7 = INTEGER: 2 SNMPv2-SMI::enterprises.3808.1.1.1.5.1.2.1.4.8 = INTEGER: 2 SNMPv2-SMI::enterprises.3808.1.1.1.5.1.2.1.4.9 = INTEGER: 2 SNMPv2-SMI::enterprises.3808.1.1.1.5.1.2.1.4.10 = INTEGER: 2 SNMPv2-SMI::enterprises.3808.1.1.1.5.1.2.1.4.11 = INTEGER: 2 SNMPv2-SMI::enterprises.3808.1.1.1.5.1.2.1.4.12 = INTEGER: 2 SNMPv2-SMI::enterprises.3808.1.1.1.5.1.2.1.4.13 = INTEGER: 2 SNMPv2-SMI::enterprises.3808.1.1.1.5.1.2.1.4.14 = INTEGER: 2 SNMPv2-SMI::enterprises.3808.1.1.1.5.1.2.1.4.15 = INTEGER: 2 SNMPv2-SMI::enterprises.3808.1.1.1.5.2.1.0 = INTEGER: 120 SNMPv2-SMI::enterprises.3808.1.1.1.5.2.4.0 = INTEGER: 2 SNMPv2-SMI::enterprises.3808.1.1.1.5.2.9.0 = Timeticks: (0) 0:00:00.00 SNMPv2-SMI::enterprises.3808.1.1.1.5.2.10.0 = Timeticks: (18000) 0:03:00.00 SNMPv2-SMI::enterprises.3808.1.1.1.5.2.11.0 = Timeticks: (18000) 0:03:00.00 SNMPv2-SMI::enterprises.3808.1.1.1.5.2.13.0 = INTEGER: 2 SNMPv2-SMI::enterprises.3808.1.1.1.5.2.14.0 = INTEGER: 0 SNMPv2-SMI::enterprises.3808.1.1.1.5.2.15.0 = INTEGER: 2 SNMPv2-SMI::enterprises.3808.1.1.1.5.2.16.0 = INTEGER: 0 SNMPv2-SMI::enterprises.3808.1.1.1.5.2.17.0 = INTEGER: 1 SNMPv2-SMI::enterprises.3808.1.1.1.5.2.18.0 = INTEGER: 20 SNMPv2-SMI::enterprises.3808.1.1.1.5.2.19.0 = NULL SNMPv2-SMI::enterprises.3808.1.1.1.5.2.20.0 = NULL SNMPv2-SMI::enterprises.3808.1.1.1.6.2.1.0 = INTEGER: 1 SNMPv2-SMI::enterprises.3808.1.1.1.6.2.2.0 = INTEGER: 1 SNMPv2-SMI::enterprises.3808.1.1.1.6.2.3.0 = INTEGER: 1 SNMPv2-SMI::enterprises.3808.1.1.1.6.2.5.0 = NULL SNMPv2-SMI::enterprises.3808.1.1.1.6.2.6.0 = INTEGER: 1 SNMPv2-SMI::enterprises.3808.1.1.1.7.2.2.0 = INTEGER: 1 SNMPv2-SMI::enterprises.3808.1.1.1.7.2.3.0 = INTEGER: 1 SNMPv2-SMI::enterprises.3808.1.1.1.7.2.4.0 = STRING: "11/12/2023" SNMPv2-SMI::enterprises.3808.1.1.1.7.2.6.0 = INTEGER: 1 SNMPv2-SMI::enterprises.3808.1.1.1.7.2.7.0 = NULL SNMPv2-SMI::enterprises.3808.1.1.1.7.2.8.0 = NULL SNMPv2-SMI::enterprises.3808.1.1.1.8.1.1.1.1.1 = INTEGER: 1 SNMPv2-SMI::enterprises.3808.1.1.1.8.1.1.1.1.2 = INTEGER: 2 SNMPv2-SMI::enterprises.3808.1.1.1.8.1.1.1.1.3 = INTEGER: 3 SNMPv2-SMI::enterprises.3808.1.1.1.8.1.1.1.1.4 = INTEGER: 4 SNMPv2-SMI::enterprises.3808.1.1.1.8.1.1.1.1.5 = INTEGER: 5 SNMPv2-SMI::enterprises.3808.1.1.1.8.1.1.1.2.1 = INTEGER: 4 SNMPv2-SMI::enterprises.3808.1.1.1.8.1.1.1.2.2 = INTEGER: 1 SNMPv2-SMI::enterprises.3808.1.1.1.8.1.1.1.2.3 = INTEGER: 3 SNMPv2-SMI::enterprises.3808.1.1.1.8.1.1.1.2.4 = INTEGER: 4 SNMPv2-SMI::enterprises.3808.1.1.1.8.1.1.1.2.5 = INTEGER: 2 SNMPv2-SMI::enterprises.3808.1.1.1.10.1.0 = INTEGER: 1 SNMPv2-SMI::enterprises.3808.1.1.1.10.2.0 = Gauge32: 34
Here is the file with the output (ran for about 100 seconds) from: /usr/local/libexec/nut/snmp-ups -a ups -DDDDDD 2>&1 | tee /tmp/out
output.txtI'm hoping the restart and reinstall of everything fixed whatever was causing the connection losts messages, but I'll update again if they reoccur.
Update about 2 hours later: The reboot and uninstall/reinstall of all NUT packages (to the devel package) seemed to do the trick. I haven't had a single connection lost notice since then. No idea why it was having issues after I tried the devel package, but it seems to be good now.
-
Upgraded to the new NUT package (2.8.2) and I'm happy to report that I was able to remove the
interruptonly
flag and now see no more disconnects on the USB connected Cyberpower UPS. Thanks @dennypage for all your hard work updating and maintaining this pfSense package. -
@tman222 said in NUT Package (2.8.1 and above):
Thanks @dennypage for all your hard work updating and maintaining this pfSense package.
You are most welcome
-
@dennypage said in NUT Package (2.8.1 and above):
Call for testing!
We are in a testing/feedback phase for the 2.8.1 pfSense NUT package. Many of you have experienced issues with the 2.8.0 version and are running custom builds. I would like to ask you to test the new package prior to a general release.
The 2.8.1 packages are available from the Redmine issue here. In order to install the package, you must be running 23.09. Be sure to select the correct package for your architecture.
Can you tell me where I can get the previous package? I'm on 23.05.1 and upgraded NUT to 2.8.2 yesterday. Package management let me do this, even though NUT 2.8.2 apparently doesn't work with 23.05.1. Result: a busted nut...
(I'll upgrade to 23.09 soon, but I can't do this during office hours) -
@Unoptanio said in NUT Package (2.8.1 and above):
maybe I found it, can you confirm?
nano /boot/loader.confNot that file, as pfSense can wipe / purge / empty / modify / do whatever it wants with the content.
Read System Tunables and you'll find the one you need : /boot/loader.conf.local
-
@evert said in NUT Package (2.8.1 and above):
@
Can you tell me where I can get the previous package? I'm on 23.05.1 and upgraded NUT to 2.8.2 yesterday. Package management let me do this, even though NUT 2.8.2 apparently doesn't work with 23.05.1. Result: a busted nut...
(I'll upgrade to 23.09 soon, but I can't do this during office hours)It shouldn’t show up in 23.05.1. Did you switch update streams? Best I can suggest is to remove the package and reinstall.
-
@dennypage I got prompted on package manager that 2.8.2 was available and upgraded. Since then, I've started receiving the communication lost and established. I'm running a CyberPower UPS. I tried to put the nut-devel-2023.10.07_1.pkg back on, but it doesn't seem to be working with the other portion of NUT that was installed with 2.8.2. Was 2.8.2 the fix or is that still a version that hasn't been patched yet?
What's my best bet to get this working again until a permanent fix is available? Thanks!
-
@sgnoc 2.8.2 of the pfSense package is the final release version.
The content of the underlying NUT package, nut-devel-2023.10.07_1, is the same as the prerelease test version. The only change in the new pfSense package (pfSense-pkg-nut-2.8.2) is that it states a dependency on nut-devel-2023.10.07_1 instead of nut-2.8.0.
A current install on 23.09 should show this:
[23.09-RELEASE][root@fw]/root: pkg info | grep nut nut-devel-2023.10.07_1 Network UPS Tools pfSense-pkg-nut-2.8.2 Network UPS Tools [23.09-RELEASE][root@fw]/root:
-
@dennypage I'm showing both of those packages, but oddly enough I'm now getting sporadic lost communication notices again, where I was not with the patch before this 2.8.2 update.
It's only happening a few times a day, but it is consistently a lost communication notice, exactly 3 seconds later a second lost communication notice and 5 seconds after that an established communication notice. I've already uninstalled and reinstalled to see if that would do it. I'll try and dig around to see why this may have happened from the patch to this update, since there shouldn't be a difference.
-
All working with 2.8.2 here with Eaton 9PX3000. Only change required was subdriver changing from
pw
toeaton_pw_nm2
. Thanks @dennypage for maintaining this package, super appreciated. -
@q54e3w I appreciate you saying that. Thanks.
-
@dennypage said in NUT Package (2.8.1 and above):
@evert said in NUT Package (2.8.1 and above):
@
Can you tell me where I can get the previous package? I'm on 23.05.1 and upgraded NUT to 2.8.2 yesterday. Package management let me do this, even though NUT 2.8.2 apparently doesn't work with 23.05.1. Result: a busted nut...
(I'll upgrade to 23.09 soon, but I can't do this during office hours)It shouldn’t show up in 23.05.1. Did you switch update streams? Best I can suggest is to remove the package and reinstall.
We are on the regular 'Latest Stable Version' branch. Ah well, I came in early today and updated the whole thing to 23.09 and that resolved my issues
And... Lo and behold! Our UPS is finally having a proper connection to the pfSense box
-
A bit confused by the versioning: pfSense now has nut 2.8.2, but the official NUT release is 2.8.1 if I interpret this page correctly.
What happens when the official NUT release hits 2.8.2?
-
@evert Yea, we had a little oops at the end, and a commit went in that should not have. The published version of the pfSense package itself shows as 2.8.2. By the time I discovered it, it was too late to change it.
It should stay 2.8.2 (2.8.2_1, 2.8.2_2, 2.8.2_3...) until 2.8.3 or 3.0.0 is released.