[Nut-upsuser] [nut-upsusers] NUT 2.8.0r3 | NUT-clients are loosing connection to UPS over SNMP-driver

Andre Mueller andre.mueller at himmel-blau.com
Wed Oct 26 15:57:01 BST 2022


Hello

Becoming somewhat "desperate" I configured and tested (for hours) to get 
a NUT-Server/Client 2.8.0r3 installation to work together with a 
CyberPower OLS1500 UPS over SNMP v3.

As NUT-packages for  ubuntu are still at version 2.7.4 and this 
NUT-SNMP-driver does not report very much information from the 
CyberPower UPS, I decided to compile/install from source the 2.8.0r3 
version with the following configure settings:


./configure --with-snmp --with-cgi --with-scanner  -with-docs 
--with-user=root --with-group=nut  --sysconfdir=/etc/nut/


now with version 2.8.0r3 I get over upsc full information from my ups 
(named ups00) over SNMP. Also NUT-cgi reports full information and is 
refreshed accordingly.


/usr/local/ups/bin/upsc ups00
battery.charge: 100
battery.current: 1
battery.runtime: 2880
battery.runtime.elapsed: 0
battery.voltage: 54.60
battery.voltage.nominal: 48
device.contact: Administrator
device.description: UPS SNMP Card
device.location: Server Room
device.mfr: CYBERPOWER
device.model: OLS1500ERT2UA
device.serial: 3003070Z30000042
device.type: ups
driver.name: snmp-ups
driver.parameter.pollinterval: 1
driver.parameter.port: 192.168.1.10
driver.parameter.secLevel: authPriv
driver.parameter.snmp_version: v3
driver.parameter.synchronous: auto
driver.version: 2.8.0-rc3
driver.version.data: cyberpower MIB 0.51
driver.version.internal: 1.21
input.frequency: 49.90
input.voltage: 232.50
output.current: 1
output.frequency: 49.90
output.voltage: 232.50
ups.delay.reboot: 0
ups.delay.shutdown: 180
ups.delay.start: 0
ups.firmware: OS02RV07
ups.load: 17
ups.mfr: CYBERPOWER
ups.model: OLS1500ERT2UA
ups.serial: 3003070Z30000042
ups.status:


Also the NUT-Server (v2.8.0r3) seems to works correct and 3 NUT-clients 
(1 local, 2 remote) can login correctly to the NUT-Server and to the ups00.


nut-server[1069]: User upsmon at 127.0.0.1 logged into UPS [ups00]
upsd[1069]: User upsmon at 127.0.0.1 logged into UPS [ups00]
nut-server[1069]: User upsmon at 192.168.1.211 logged into UPS [ups00]
upsd[1069]: User upsmon at 192.168.1.211 logged into UPS [ups00]
nut-server[1069]: User upsmon at 192.168.1.11 logged into UPS [ups00]
upsd[1069]: User upsmon at 192.168.1.11 logged into UPS [ups00]


Unfortunately all NUT-clients (also the local NUT-client) are reporting 
directly after the first refresh and then continuously, that they have 
lost connenctions to the ups00 but they are still loggedin to the 
NUT-Server.

...
nut-monitor[1078]: UPS ups00 at localhost is unavailable
nut-monitor[29503]: Network UPS Tools upsmon 2.8.0-rc3
...

So my question is, what could be "wrong" in configuration and/or 
installation, that all clients (local or remote) are reporting that they 
have lost connection to the ups00 and that it is not unavailable?


Many thanks in advance for any hint, best










More information about the Nut-upsuser mailing list