Beta test of new NUT UPS package
-
I believe NUT already handles this. Have a look at the man page for the apcsmart driver. Pretty rich configuration options for power handling in there.
@w0w:
It would be good to kill UPS power, sending command to shutdown UPS, like APCUPSD doing it.
-
Hey John, just wondering if you had a chance to dump the usb config to check the vendor and product id?
driver=blazer_usb
port=auto
langid_fix=0x4095
subdriver=krauler
productid=1234
vendorid=0925 -
dennypage
Thanks, looks like b3 works. UPS reconnects if no connection at startup or if it lost.I believe NUT already handles this. Have a look at the man page for the apcsmart driver. Pretty rich configuration options for power handling in there.
@w0w:
It would be good to kill UPS power, sending command to shutdown UPS, like APCUPSD doing it.
I don't use apcsmart driver, I use SNMP. I think I'll try
something like " /usr/local/ups/sbin/upsdrvctl shutdown" later to check if this works.
Thanks again about tip for ups.conf, shame on me. :)
-
w0w
If that works to kill the UPS, you can add this to rc.shutdown and it will send the command if NUT shuts down the system
I use the system patches package to keep it there across updates.if (test -f /etc/killpower) then echo "Shutting down UPS power..." /usr/local/sbin/upsdrvctl shutdown fi -
Glad it works. No shame btw, it wasn't possible to do in beta 2. Both config and script changes were needed to support it.
@w0w:
Thanks, looks like b3 works. UPS reconnects if no connection at startup or if it lost.
Thanks again about tip for ups.conf, shame on me. :)
-
Pull request created: https://github.com/pfsense/FreeBSD-ports/pull/155
-
Hey John, just wondering if you had a chance to dump the usb config to check the vendor and product id?
Hi Denny,
There was an attempt to reverse engineer this back in 3013 that seems to have come to nothing.
http://lists.alioth.debian.org/pipermail/nut-upsdev/2013-January/006390.html
my understanding is they won't do any more work on supporting it. I've wasted enough time on getting it to work I think I will wait to see what works well with NUT on the pfsense and buy one of those.
John
driver=blazer_usb
port=auto
langid_fix=0x4095
subdriver=krauler
productid=1234
vendorid=0925 -
If you are looking for a new UPS, pretty much anything that is supported by NUT 2.7.4 should work fine with the new nut package under pfSense. To ensure compatibility with NUT, it would be a good idea to choose a ups that operates with a publicly available protocol. You can find these on the NUT hardware compatibility list by selecting "***" as the minimum Support Level.
-
sorry, wrong thread
-
I got a Eaton 5E2000iUSB and it seems to work perfectly.
I still have to add the Nut Clients (debian servers & a NAS) and test it properly but looking good.
Thanks a million for your work, this is one thing about Pfsense that has been really bugging me.
-
Thanks John. I'm glad it worked for you. I really appreciate your help with testing the new package.
-
let me know if I can test for you too.
Does this NUT update support reporting on enviromentals via an APC 9631 and sensors? -
The UPS Detail section on the Status page will display all variables reported by the NUT driver, however I don't personally know what variables are reported by the driver for the 9631 card.
If you would like a copy of the beta package, please pm me with an email address. Thanks.
@irj972:
Does this NUT update support reporting on enviromentals via an APC 9631 and sensors?
-
Does the Beta package properly support the connection to Apcupsd ? Now I use a workaround with the old package, but I'd rather use something that can be configured through the pfsense webui.
-
Yes, the package supports configuration of remote apcupsd.
-
Thanks for letting me join the Beta Phase.
Here's my feedback:
I use a remote APC UPS which is hooked up on one of my Synology NAS.
After removing the current package i installed the beta via cmdline and was very happy that my Config Data has been found :)
I had to re-enable these by saving them and i got every value from the APC now shown in pfSense. That's cool!
There is also a new widget. The new one seems to be a little bigger. There i have to say, that i liked the older one a little more.
As i remember there where colored texts in it and it was, yes smaller.I keep up looking if there is any bug left :)
Thank you! -
Thanks for the feedback renegade. Much appreciated. Glad it worked for you.
The new widget is intended to fit with pfSense's new Bootstrap model. Line it up with the System Information widget and you'll see what I mean. Surprisingly, when not in alert state, the size of the new widget is about the same size as the old widget. It's smaller if there is an alert. :)
The new widget is intended to provide a highly distinctive visual indication of UPS alerts. The alert combines a large shaded color band and bolded alert text, which fits with the Bootstrap model. You can see what it looks like by disconnecting your UPS or by killing the driver. The multicolored text of the prior widget really was not sufficiently distinctive, particularly for color blind administrators.
No, I'm not color blind, but I have worked with admins that are.
-
Just installed the beta package without any problems. Connected to my APC SmartUPS 1500 usb through Apcupsd on my ubuntu server to which the UPS is physically connected. Worked without a hitch. Also the widget works without any issues.
Do you need logfiles or more info ?
-
Glad it worked for you justmie. No log files necessary. Thank you again for your help.
-
I found a strange bug. If I call Services >> UPS, it brings up https://192.168.1.1/nut_status.php properly. However, if I go to Services >> Snort, and then to Services >> UPS, it tries to call https://192.168.1.1/snort/nut_status.php.
