Beta test of new NUT UPS package

dennypage

I am looking for some volunteers to help with testing a new NUT UPS package.

Please note that in order to install the beta nut package, you must be comfortable using the command line interface. If you are not comfortable with the command line, please wait for the ga version of the package.

Please PM me if interested.

dennypage

Here are instructions for installing the beta:

PM me with an email address and I will send you a copy of the current beta package.

Before installing the beta package, please backup your current config file. You will want your prior config handy if you need to revert to the prior package.

IMPORTANT: Before installing the beta package, you MUST remove the existing nut package. If you fail to remove the prior package, you will end up with a non-functional nut package. Please use the pfSense package manager to remove the existing nut package.

To begin, copy the beta package to the system. Then log into the system as root and use the FreeBSD package manager to to install the package. The install command is:

pkg install pfSense-pkg-nut-2.7.4b1.txz

After the package is installed, goto Services -> UPS in the pfSense gui to configure settings for your UPS.

If you need to revert to the prior version, you must first remove the beta package via the pfSense package manager or the FreeBSD package manger. The command to remove the package via the FreeBSD package manager is:

pkg delete pfSense-pkg-nut

After the beta package has been removed, you can re-install nut via the pfSense package manager in the normal way. After you have reinstalled the prior nut package, you can either reconfigure nut via the package gui in Services -> NUT, or you can restore your prior config using the file you saved above. A config restore will cause a reboot, so it might be preferable to simply reconfigure via the GUI.

Thank you for your help!

dennypage

One last thing… if it takes me a while to respond, please be patient with me. I have a lot going on right now. :)

w0w

Did you created github pull request already?
What's new coming?
It would be good if NUT can get a new option like "keep service alive" fixing this bug — https://redmine.pfsense.org/issues/6571
Currently I'am using CRON to run the script that checks if NUT is running and starts it if not.

dennypage

It is a completely new version of the nut package, written from scratch. It brings an all new gui and alignment with current NUT architecture. PR will follow some initial testing.

Starrbuck

Denny, the new package is very nice! Great work! It installed cleanly and ran great the first time. I love the more easy to understand options and the status screen looks great.

I did find an issue. Following a reboot, it was unable to chdir to /var/db/nut as I have my /var in a ramdisk because I am running on mirrored SSDs for system drives.

dennypage

Thanks Ben. I actually have code to fix up a missing /var/db/nut, but it's currently only run at install time to fix a problem with the prior nut package. It's easy enough to move the fix up check to be executed at each config sync. I'll have it for you when I get back in a day or two.

@Starrbuck:

I did find an issue. Following a reboot, it was unable to chdir to /var/db/nut as I have my /var in a ramdisk because I am running on mirrored SSDs for system drives.

dennypage

Btw, do you mind posting the ups type and driver that you are testing with?

johnabbot

Hi,

I'm running a generic asian ups with the following

(Various USB)
UPSilon 2000 software blazer_usb langid_fix=0x409

It installed perfectly, looks great, unfortunately it gives me

"Failed to retrieve status"

Starrbuck

@dennypage:

Thanks Ben. I actually have code to fix up a missing /var/db/nut, but it's currently only run at install time to fix a problem with the prior nut package. It's easy enough to move the fix up check to be executed at each config sync. I'll have it for you when I get back in a day or two.

Awesome, that should be a rather easy fix!

@dennypage:

Btw, do you mind posting the ups type and driver that you are testing with?

I will have to check this evening after I get home with access to the server.

dennypage

Several questions:

What messages are in the system log? Look for messages from upsd, upsmon, upsdrvctl, blazer*.
What are the contents of /usr/local/etc/nut/ups.conf and upsd.conf?
What nut processes are running? (ps -axuwww | grep ups)
Does anything change if you restart the nut service via the nut status page or the services page?
Have you successfully tested this specific ups model with nut previously?

@johnabbot:

I'm running a generic asian ups with the following

(Various USB)
UPSilon 2000 software blazer_usb langid_fix=0x409

It installed perfectly, looks great, unfortunately it gives me

"Failed to retrieve status"

Starrbuck

USB type: Local USB
Driver: usbhid

dennypage

Hey Starrbuck, I sent you an update that should address your ram disk issue. Please let me know that it works for you. Thanks.

Starrbuck

Got it, thanks!

Starrbuck

@dennypage:

Hey Starrbuck, I sent you an update that should address your ram disk issue. Please let me know that it works for you. Thanks.

The ramdisk issue is corrected. Upon rebooting the package started up normally and the status looks fine.

dennypage

Good to hear. Thanks again for testing.

dennypage

w0w, I may have an approach that will address the SNMP unreachable on startup issue issue. Give me a couple of days, and I'll let you know. In the mean time, please test the existing beta2 version. Thanks.

w0w

UPS Status — OFF, but displayed battery charge and load are OK.
Fixed with an extra argument for driver.
mibs=ietf
Looks much better now :)
Good job!

P.S. Don't look at I/O Voltage at first picture, it's Powercom firmware bug that could not be fixed anyway.

nut1.jpg_thumb

nut2.jpg_thumb

w0w

Can I request some features for package? (lowest priority in your list) :)
1. I want shutdown pfsense before battery get LOW condition, for example after running 5 minutes on battery, I have seen some implementations using internal nut scripting, but not for pfsense. Feature is very similar to what APCUPSD already have for years.
2. It would be good to kill UPS power, sending command to shutdown UPS, like APCUPSD doing it.

BTW I am using APCUPSD on windows for the same UPS.

johnabbot

@dennypage:

Several questions:

What messages are in the system log? Look for messages from upsd, upsmon, upsdrvctl, blazer*.

upsmon 73821 Poll UPS [sunpac] failed - Driver not connected
upsd 71207 Can't connect to UPS [sunpac] (blazer_usb-sunpac): No such file or directory

What are the contents of /usr/local/etc/nut/ups.conf and upsd.conf?

sunpac]
driver=blazer_usb
port=auto
langid_fix=0x4095
subdriver=krauler
productid=1234
vendorid=0925

LISTEN 127.0.0.1
LISTEN ::1

What nut processes are running? (ps -axuwww | grep ups)

ps -axuwww | grep ups
root 71207 0.0 0.0 20712 2368 - Ss 6:10PM 0:00.24 /usr/local/sbin/upsd -u root
root 72651 0.0 0.0 16612 2308 - Is 6:10PM 0:00.00 /usr/local/sbin/upsmon
uucp 73821 0.0 0.0 16612 2340 - S 6:10PM 0:00.20 /usr/local/sbin/upsmon
root 58229 0.0 0.0 18740 2240 0 S+ 9:44PM 0:00.00 grep ups

Does anything change if you restart the nut service via the nut status page or the services page?

No

Have you successfully tested this specific ups model with nut previously?

No

@johnabbot:

I'm running a generic asian ups with the following

(Various USB)
UPSilon 2000 software blazer_usb langid_fix=0x409

It installed perfectly, looks great, unfortunately it gives me

"Failed to retrieve status"