Freenas 11.3 UPS Monitoring not working

longshot006

Cadet
Joined
Feb 18, 2020
Messages
2
Hello,

I ´ve just updated to Freenas 11.3 but the UPS monitoring is broken now.

if i issue the command:

upsdrvctl -DDD start

i get back:


Code:
root@lin01-fs01:/var/log # upsdrvctl -DDD start
Network UPS Tools - UPS driver controller 2.7.4
   0.000000
If you're not a NUT core developer, chances are that you're told to enable debugging
to see why a driver isn't working for you. We're sorry for the confusion, but this is
the 'upsdrvctl' wrapper, not the driver you're interested in.

Below you'll find one or more lines starting with 'exec:' followed by an absolute
path to the driver binary and some command line option. This is what the driver
starts and you need to copy and paste that line and append the debug flags to that
line (less the 'exec:' prefix).

   0.000098     Starting UPS: lin01-ups01.xts.int
   0.000112     1 remaining attempts
   0.000116     exec:  /usr/local/libexec/nut/snmp-ups -a lin01-ups01.xts.int
Network UPS Tools - Generic SNMP UPS driver 0.97 (2.7.4)
Duplicate driver instance detected! Terminating other driver!
No matching MIB found for sysOID '.1.3.6.1.4.1.318.1.3.27'!
Please report it to NUT developers, with an 'upsc' output for your device.
Going back to the classic MIB detection method.
Detected Smart-UPS 750 on host 192.168.26.138 (mib: apcc 1.2)
[lin01-ups01.xts.int] Warning: excessive poll failures, limiting error reporting (OID = .1.3.6.1.4.1.318.1.1.1.9.2.3.1.5.1.1.3)
[lin01-ups01.xts.int] Warning: excessive poll failures, limiting error reporting (OID = .1.3.6.1.4.1.318.1.1.1.9.3.3.1.6.1.1.1)


i am using an APC Smart-UPS with an ebedded AP9630 Network-Card.

Following Configuration Parameters are used:
(See attachment)

What can i do to tackle down this issue?

In the 11.2-Release, everything worked well.

Regards
Sebastian
 

Attachments

  • 19.02.jpg
    19.02.jpg
    59.8 KB · Views: 344
Joined
Feb 19, 2020
Messages
6
HI,

The same here.

Updated from 11.2 U6 via 11.2 U8 to 11.3 today
Using APC Smart-UPS750

See attached screenshot

Regards

Herman
 

Attachments

  • Screenshot_UPS_error.png
    Screenshot_UPS_error.png
    29.2 KB · Views: 340
Joined
Feb 19, 2020
Messages
6
With support of iX Systems, it turned out that the default NUT port 3493 has changed to the default APCUPSD port 3551.

iX Systems:
In 11.2 there's a bug where it defaults to listening to default port 3493
I am guessing it would be default which is 3493
So to correct this, you can set the value to 3493 either in the ups settings or pass the correct one in your connecting script (application).

To find the port you can issue the following command: midclt call ups.config | jq

Regards

Herman
 
Joined
Feb 19, 2020
Messages
6
Another add on remark from iX Systems:

FreeNAS does not change the value of remote port on it's own and it defaults to 3493, it must have been changed while you were configuring the ups service at some point ( either in 11.2 or 11.3 ).
 

longshot006

Cadet
Joined
Feb 18, 2020
Messages
2
Ok, i figured that one out:
i had to issue
midclt call ups.update '{"remoteport": 3493}'
to get it working again.

now i got a strange behavior even on a fresh install.

After a reboot i need to run


/usr/local/sbin/upsd
/usr/local/libexec/nut/snmp-ups -a lin01-ups01

to get everything running again. I didn´t get that one on the 11.2-Release so maybe this is a bug in the 11.3-Release?

Can i do something from my side to sort this out?

Regards
Sebastian
 
Joined
Feb 19, 2020
Messages
6
Hello Sebastian,

I solved it by changing the port in the remote application. I actually did not spend much time in checking FreeNAS side.

I suggest that you create a Jira ticket. You can do that by clicking" Report a Bug" at the top of this screen.

Regards
 
Top