NUT package (2.8.0 and below)

dennypage · Sep 26, 2016, 4:05 PM

When the UPS enters a low battery state NUT initiates a shutdown.

McFuzz · Oct 7, 2016, 4:42 AM

Hello!

Is there a tutorial to get email notifications to work? I have the checkbox ticked, but when I tested by putting the UPS on battery power (yanking power cord), it did not produce any notifications… I had it all working before upgrading to 2.3.2_1 and NUT upgrading to 2.4.7_2... but seems like things are a whole lot different now.

dennypage · Oct 7, 2016, 5:21 AM

Have you sucessfully tested emails in System Advanced / Notifications / E-Mail following the upgrade?

McFuzz · Oct 7, 2016, 6:42 AM

@dennypage:

Have you sucessfully tested emails in System Advanced / Notifications / E-Mail following the upgrade?

Yes I have - and indeed they are coming through. I have not done any additional configurations in the UPS Settings -> Advanced Settings section… am I supposed to configure anything there aside from ticking the checkbox?

dennypage · Oct 7, 2016, 6:47 AM

You did a save of the NUT settings after ticking the checkbox, yes?

Please post the contents of /usr/local/etc/nut/upsmon.conf.

McFuzz · Oct 7, 2016, 6:51 AM

@dennypage:

You did a save of the NUT settings after ticking the checkbox, yes?

Please post the contents of /usr/local/etc/nut/upsmon.conf.

Yup - I did.

Here are the contents of upsmon.conf - I did not modify it yet; want to first get the defaults working:


MONITOR BX1300G 1 monuser a620bdded832fb08439a master
SHUTDOWNCMD "/sbin/shutdown -p +0"
POWERDOWNFLAG /etc/killpower
NOTIFYCMD /usr/local/pkg/nut/nut_email.php
NOTIFYFLAG ONLINE   SYSLOG+WALL+EXEC
NOTIFYFLAG ONBATT   SYSLOG+WALL+EXEC
NOTIFYFLAG LOWBATT  SYSLOG+WALL+EXEC
NOTIFYFLAG FSD	  SYSLOG+WALL+EXEC
NOTIFYFLAG COMMOK   SYSLOG+WALL+EXEC
NOTIFYFLAG COMMBAD  SYSLOG+WALL+EXEC
NOTIFYFLAG SHUTDOWN SYSLOG+WALL+EXEC
NOTIFYFLAG REPLBATT SYSLOG+WALL+EXEC
NOTIFYFLAG NOCOMM   SYSLOG+WALL+EXEC
NOTIFYFLAG NOPARENT SYSLOG+WALL+EXEC

Naturally, I browsed through nut_email.php and noticed that it is referencing to a file called notices.inc:


require_once("notices.inc");

However - can't find that file anywhere…

dennypage · Oct 7, 2016, 7:01 AM

@McFuzz:

Naturally, I browsed through nut_email.php and noticed that it is referencing to a file called notices.inc:
require_once("notices.inc");
However - can't find that file anywhere…

You should find this as /etc/inc/notices.inc.

The contents of upsmon.conf look fine. Please run the following:

echo "hello" | /usr/local/pkg/nut/nut_email.php

What happens?

McFuzz · Oct 7, 2016, 7:03 AM

@dennypage:

@McFuzz:
Naturally, I browsed through nut_email.php and noticed that it is referencing to a file called notices.inc:
require_once("notices.inc");
However - can't find that file anywhere…
You should find this as /etc/inc/notices.inc.

The contents of upsmon.conf look fine. Please run the following:
echo "hello" | /usr/local/pkg/nut/nut_email.php
What happens?

Yup - notices.inc is in /etc/inc

Attempted to execute the command - all I got was an email that simply had a timestamp; nothing else… was I supposed to see "hello" in the body?

dennypage · Oct 7, 2016, 7:11 AM

Sorry, my bad. It should have been:

/usr/local/pkg/nut/nut_email.php hello

And yes, the content of the email should be like this:

Fri, 07 Oct 2016 00:09:55 -0700
hello

If you receive this, it means that your email notifications are working.

McFuzz · Oct 7, 2016, 7:13 AM

@dennypage:

Sorry, my bad. It should have been:
/usr/local/pkg/nut/nut_email.php hello
And yes, the content of the email should be like this:
Fri, 07 Oct 2016 00:09:55 -0700
hello
If you receive this, it means that your email notifications are working.

Yup - that worked; got an email with "hello" in it.

So what's wrong with the automatic notifications? :(

I just tried it again (saved the settings, for a good measure) - yanked the power off the UPS so it goes on battery power… got the notification within the shell session, but no email :(

dennypage · Oct 7, 2016, 7:13 AM

Assuming that your email notifications are working…

When you pulled the cord, how long did you wait? If you were logged into pfSense, did you see a wall announcement?

When you go to Services / UPS / Status with the cord pulled, what do you see?

dennypage · Oct 7, 2016, 7:24 AM

Are you affected by this bug?

https://forum.pfsense.org/index.php?topic=115349.msg646251#msg646251
https://forum.pfsense.org/index.php?topic=115349.msg646466#msg646466

McFuzz · Oct 7, 2016, 7:24 AM

@dennypage:

Assuming that your email notifications are working…

When you pulled the cord, how long did you wait? If you were logged into pfSense, did you see a wall announcement?

When you go to Services / UPS / Status with the cord pulled, what do you see?

I just gave it another shot:

Disconnected power
pfsense shell session indicated the UPS being on battery
UI dashboard as well as Services -> UPS both indicated the UPS needed attention (and showed it discharging)
Waited a minute and plugged back in
Shell session indicated the UPS was back on line power practically right away
UI dashboard reflected power restoration and shows the UPS as charging.

McFuzz · Oct 7, 2016, 7:28 AM

@dennypage:

Are you affected by this bug?

https://forum.pfsense.org/index.php?topic=115349.msg646251#msg646251
https://forum.pfsense.org/index.php?topic=115349.msg646466#msg646466

Hooray! That worked!!!!!

Thank you :)

So yeah - I guess I am affected :x

dennypage · Oct 7, 2016, 7:29 AM

You're welcome. I'm glad it worked for you.

endy66 · Oct 13, 2016, 9:56 AM

Since yesterday, i have also an brand new UPS, one from CyberPower. I installed the nut package and everything is working as expected. Thanks to this thread, i could set the override.battery.charge.low to shutdown my pfsense earlier.
But now i have one question, i don't know, if this is the rigt Forum to ask this: I want to shutdown a Linux/Debian Server, which should get the data from the pfsense. So i have added in the upsd.users inside the box of the nut Settings the following:


[client]
password = mypass
upsmon slave

And in the upsd.conf box


LISTEN 192.168.1.1

On the Server i installed the nut-Client package (apt-get install nut-Client). With this command


upsc CyberPower_USV@192.168.1.1

i can get all the data from the pfsense (UPS)

But how can i make, that the Server also shuts down, when the pfsense box is shutting down?

EDIT// Everything is working now, i had to set the MODE=netclient on the Server.

But i found a Problem with the override values. As i said above, i have set the following to the additional ups.conf field in pfSense:


ignorelb
override.battery.charge.low = 50
override.battery.runtime.low = 1200

BUT These values are added on top of the ups.conf file, which means in my case, they are ignored. When i edit the ups.conf manually from ssh / Shell, and set thes override values at the bottom of the file and restart the daemon, the everything works and also the Monitoring in pfsense Show the new values. Is this a bug? Problem is, after reboot or restart the daemon, These values are not the anymore…

Best Regards

alanper · Oct 13, 2016, 1:53 PM

Firstly, thanks for a great and extremely useful package.
I'm having a problem with the NUT package on my pfSense deployment. When I click on Services->UPS I get an alert "Status Alert: The UPS requires attention". The NUT service is setup as a Remote NUT Server. The service is connecting fine to the UPS as I can see values and graphs being populated (correctly). The service is working as expected as well, as when I drop power to the UPS, NUT detects it and does what it is setup to do. Yet I still get the "Status Alert: The UPS requires attention" every time I go to Services->UPS. Any ideas?

dennypage · Oct 13, 2016, 8:53 PM

@endy66:

But i found a Problem with the override values. As i said above, i have set the following to the additional ups.conf field in pfSense:
ignorelb
override.battery.charge.low = 50
override.battery.runtime.low = 1200
BUT These values are added on top of the ups.conf file, which means in my case, they are ignored. When i edit the ups.conf manually from ssh / Shell, and set thes override values at the bottom of the file and restart the daemon, the everything works and also the Monitoring in pfsense Show the new values. Is this a bug? Problem is, after reboot or restart the daemon, These values are not the anymore…

The section entitled "Additional configuration lines for ups.conf" in Advanced settings is for global directives. The values you are trying to set are UPS specific arguments. UPS specific arguments should be entered in the section above that says "Extra Arguments to driver"

Sorry this isn't clear. I'll have a look at clarifying.

dennypage · Oct 13, 2016, 9:04 PM

@alanper:

When I click on Services->UPS I get an alert "Status Alert: The UPS requires attention". The NUT service is setup as a Remote NUT Server. The service is connecting fine to the UPS as I can see values and graphs being populated (correctly). The service is working as expected as well, as when I drop power to the UPS, NUT detects it and does what it is setup to do. Yet I still get the "Status Alert: The UPS requires attention" every time I go to Services->UPS.

Can you clarify some things please?

What do you mean by "The NUT service is setup as a Remote NUT Server"? Is the UPS attached to the pfSense host or to another host?

When you say "I can see values and graphs", are you seeing this on the Services / UPS / Status page?

If present, can you post the content of the UPS Detail section of Services / UPS / Status?

Thanks

endy66 · Oct 14, 2016, 5:06 AM

@dennypage:

@alanper:

When I click on Services->UPS I get an alert "Status Alert: The UPS requires attention". The NUT service is setup as a Remote NUT Server. The service is connecting fine to the UPS as I can see values and graphs being populated (correctly). The service is working as expected as well, as when I drop power to the UPS, NUT detects it and does what it is setup to do. Yet I still get the "Status Alert: The UPS requires attention" every time I go to Services->UPS.

Can you clarify some things please?

What do you mean by "The NUT service is setup as a Remote NUT Server"? Is the UPS attached to the pfSense host or to another host?

When you say "I can see values and graphs", are you seeing this on the Services / UPS / Status page?

If present, can you post the content of the UPS Detail section of Services / UPS / Status?

Thanks

Thank you very much for the help, it works perfectly! :)

One last question i have:

When my UPS reaches the Limit which i set, my Server (slave) and my pfsense box are shutting down. But when do they (especally the pfsense box), boot again? Does the UPS Needs to dischagre completely to cut the power from the devices and then after power restore they get the power and boot again (with bios Setting ac restore)?

Best Regards