[Nut-upsuser] NUT 2.8.0r3 | NUT-clients are loosing connection to UPS over SNMP-driver
Andre Mueller
andre.mueller at himmel-blau.com
Thu Oct 27 17:39:23 BST 2022
Hello Jim
Many thanks for your reply.
As I am on a Ubuntu system there are at that time no nut-packages for
version 2.8.0. And as I wanted to avoid to get a mess with dependencies
from the Debian nut 2.8.0-4 packages, I decided to compile from the
networkupstools.org nut source archive
(https://github.com/networkupstools/nut-source-archive/tree/master/2.8/)
where only version 2.8.0-rc3 (april 2022) is available.
Now I have installed the Debian nut 2.8.0-4 packages (bookworm) manually
to my Ubuntu system. So far the nut 2.8.0-4 services etc. are working
correctly, but the problem remains the same, that upsmon/nut-clients are
reporting, that they have lost connection to the ups they are already
logged in. I have installed those Debian packages manually:
libltdl7_2.4.7-4_amd64.deb
libnutscan2_2.8.0-4_amd64.deb
libsnmp40_5.9.3+dfsg-1+b1_amd64.deb
libupsclient6_2.8.0-4_amd64.deb
nut_2.8.0-4_all.deb
nut-cgi_2.8.0-4_amd64.deb
nut-client_2.8.0-4_amd64.deb
nut-monitor_2.8.0-4_all.deb
nut-server_2.8.0-4_amd64.deb
nut-snmp_2.8.0-4_amd64.deb
python3-nut_2.8.0-4_all.deb
Instead upsd is working correctly for the ups (named ups00), nut-cgi also:
nut-server[1132]: Connected to UPS [ups00]: snmp-ups-ups00
upsd[1132]: Connected to UPS [ups00]: snmp-ups-ups00
nut-server[1132]: Running as foreground process, not saving a PID file
nut-server[1132]: User upsmon at 127.0.0.1 logged into UPS [ups00]
upsd[1132]: Running as foreground process, not saving a PID file
upsd[1132]: User upsmon at 127.0.0.1 logged into UPS [ups00]
nut-server[1132]: User upsmon at 192.168.1.11 logged into UPS [ups00]
upsd[1132]: User upsmon at 192.168.1.11 logged into UPS [ups00]
nut-server[1132]: User upsmon at 192.168.1.211 logged into UPS [ups00]
upsd[1132]: User upsmon at 192.168.1.211 logged into UPS [ups00]
upsc -L
Init SSL without certificate database
ups00: upsmy.mydomain.net
upsc -c ups00
Init SSL without certificate database
192.168.1.211
192.168.1.11
127.0.0.1
upsc ups00
Init SSL without certificate database
battery.charge: 100
battery.current: 0.90
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: upsmy.mydomain.net
driver.parameter.secLevel: authPriv
driver.parameter.snmp_version: v3
driver.parameter.synchronous: auto
driver.version: 2.8.0
driver.version.data: cyberpower MIB 0.51
driver.version.internal: 1.21
input.frequency: 50
input.voltage: 233.50
output.current: 0.90
output.frequency: 50
output.voltage: 233.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:
status/log from upsmon is (still):
...
nut-monitor[1135]: UPS ups00 at localhost is unavailable
nut-monitor[2130]: Network UPS Tools upsmon 2.8.0
...
or detailed from upsmon -D -D -D:
upsmon -D -D -D
Network UPS Tools upsmon 2.8.0
0.000000 fopen /run/nut/upsmon.pid: No such file or directory
0.000614 Could not find PID file to see if previous upsmon instance
is already running!
0.001522 Using power down flag file /etc/killpower
0.002237 UPS: ups00 at localhost (primary) (power value 1)
0.002844 [D1] debug level is '3'
0.003441 [D1] debug level is '3'
0.004638 [D1] Saving PID 2295 into /run/nut/upsmon.pid
Init SSL without certificate database
0.008229 [D1] Trying to connect to UPS [ups00 at localhost]
0.009241 [D1] Logged into UPS ups00 at localhost
0.009427 [D2] pollups: ups00 at localhost
0.009456 [D3] get_var: ups00 at localhost / status
0.009579 [D2] parse_status: []
0.009603 [D2] do_notify: ntype 0x0005 (COMMBAD)
0.009621 Communications with UPS ups00 at localhost lost
0.009808 [D3] Current power value: 1
0.009892 [D3] Minimum power value: 1
Broadcast message from root at localhost (pts/1) (Thu Oct 27 18:35:07
Communications with UPS ups00 at localhost lost
Broadcast message from root at localhost (pts/1) (Thu Oct 27 18:35:07
Communications with UPS ups00 at localhost lost
5.010023 [D2] pollups: ups00 at localhost
5.010128 [D3] get_var: ups00 at localhost / status
5.010292 [D2] parse_status: []
5.010316 [D2] do_notify: ntype 0x0008 (NOCOMM)
5.010330 UPS ups00 at localhost is unavailable
5.010618 [D3] Current power value: 1
5.010690 [D3] Minimum power value: 1
Broadcast message from root at localhost (pts/1) (Thu Oct 27 18:35:12
UPS ups00 at localhost is unavailable
Broadcast message from root at localhost (pts/1) (Thu Oct 27 18:35:12
UPS ups00 at localhost is unavailable
10.010912 [D2] pollups: ups00 at localhost
10.010955 [D3] get_var: ups00 at localhost / status
10.011163 [D2] parse_status: []
10.011184 [D3] Current power value: 1
10.011216 [D3] Minimum power value: 1
15.011440 [D2] pollups: ups00 at localhost
15.011485 [D3] get_var: ups00 at localhost / status
15.011651 [D2] parse_status: []
15.011676 [D3] Current power value: 1
15.011691 [D3] Minimum power value: 1
...
above log flow is the same on other connected nut-clients.
Many thanks again
André
Am 26.10.2022 um 22:24 schrieb Jim Klimov:
> On the road now so gotta come back to main question later, but for now -
> why 2.8.0-rc3 (not "r3")? There is a newer final release, or current
> master... just asking.
>
> Notably, there was a fix in master last week or so that moght help woth
> some broken large queries for SNMPv2/v3... No idea if that's your case
> though. Error messages from clients might help.
>
> Jim
>
> On Wed, Oct 26, 2022, 17:57 Andre Mueller via Nut-upsuser
> <nut-upsuser at alioth-lists.debian.net
> <mailto:nut-upsuser at alioth-lists.debian.net>> wrote:
>
>
> 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 <http://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 <mailto:upsmon at 127.0.0.1>
> logged into UPS [ups00]
> upsd[1069]: User upsmon at 127.0.0.1 <mailto:upsmon at 127.0.0.1> logged
> into UPS [ups00]
> nut-server[1069]: User upsmon at 192.168.1.211
> <mailto:upsmon at 192.168.1.211> logged into UPS [ups00]
> upsd[1069]: User upsmon at 192.168.1.211 <mailto:upsmon at 192.168.1.211>
> logged into UPS [ups00]
> nut-server[1069]: User upsmon at 192.168.1.11
> <mailto:upsmon at 192.168.1.11> logged into UPS [ups00]
> upsd[1069]: User upsmon at 192.168.1.11 <mailto: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