NUT notifications not working on pfsense+

dennypage

@austin-0 said in NUT notifications not working on pfsense+:

Does it need to hit a certain battery percentage to send the notification?

Initial notification that the UPS is on battery should be immediate.

FWIW, you can just disconnect the USB connection (assuming that is what you are using), and you should receive an immediate notification that the UPS is unavailable. On most UPSs you can also run a self test, which should also produce an "on battery" notification.

Call me old school, but I generally prefer pulling the USB connection, doing a self test, or even popping the breaker instead of pulling the mains cord. The reason for this is that pulling the mains cord also disconnects the ground.

FSC830

May be a dump question: was it possible, that the outage disconnects the line to the mail server?
I am using NUT at my SG-3100 and as far as I remember I did not configure anything else than the SMTP settings.

The UPS is scheduled for a self-test every two weeks an I get an e-mail immediately when UPS is on battery.

Regards

Austin 0

@fsc830 Thank you. Yes I was talking to my co-worker, and I realized that I don't currently know what the ONT is plugged into. So it 100% possible that the ONT went offline, which would explain the lack of emails. Something else I will have to look into Friday when I go up there.

Austin 0

I have double checked and the ont was on a battery backup. I unplugged the USB cable and still there was no notification sent. I did verify that the UPS status in nut changed. It just did not send a notification. I found a interesting message in the log though. ups_status_set: seems that UPS [OfficeUPS] is in OL+DISCHRG state now. Is it calibrating or do you perhaps want to set 'onlinedischarge' option? Some UPS models (e.g. CyberPower UT series) emit OL+DISCHRG when offline.

dennypage

@austin-0 said in NUT notifications not working on pfsense+:

I unplugged the USB cable and still there was no notification sent. I did verify that the UPS status in nut changed. It just did not send a notification.

This is puzzling.

Were you logged in on the console (ssh) when you disconnected the USB cable? Was there a notice there?

Austin 0

@dennypage I just tested it, and yes it does give a notification in the ssh connection.

dennypage

@austin-0 said in NUT notifications not working on pfsense+:

I just tested it, and yes it does give a notification in the ssh connection.

That's good--it means NUT itself is working.

Still very puzzling. I'd like to verify the contents of the pfSense NUT package. Can you please execute the following:

ls -l `pkg info --list-files pfSense-pkg-nut`

and

sha1sum `pkg info --list-files pfSense-pkg-nut`

[don't worry about the no such file or directory error for pfSense-pkg-nut-2.8.0_2]

Austin 0

@dennypage

ls: pfSense-pkg-nut-2.8.0_2:: No such file or directory
-rw-r--r--  1 root  wheel   1225 Feb 17 10:43 /etc/inc/priv/nut.priv.inc
-rw-r--r--  1 root  wheel   1692 Feb 17 10:43 /usr/local/pkg/nut.xml
-rwxr-xr-x  1 root  wheel   1007 Feb 17 10:43 /usr/local/pkg/nut/nut_email.php
-rw-r--r--  1 root  wheel  12255 Feb 17 10:43 /usr/local/pkg/nut/nut.inc
-rw-r--r--  1 root  wheel  10173 Feb 17 10:43 /usr/local/share/licenses/pfSense-pkg-nut-2.8.0_2/APACHE20
-rw-r--r--  1 root  wheel    164 Feb 17 10:43 /usr/local/share/licenses/pfSense-pkg-nut-2.8.0_2/catalog.mk
-rw-r--r--  1 root  wheel     66 Feb 17 10:43 /usr/local/share/licenses/pfSense-pkg-nut-2.8.0_2/LICENSE
-rw-r--r--  1 root  wheel    357 Feb 17 10:43 /usr/local/share/pfSense-pkg-nut/info.xml
-rw-r--r--  1 root  wheel  22284 Feb 17 10:43 /usr/local/www/nut_settings.php
-rw-r--r--  1 root  wheel   4720 Feb 17 10:43 /usr/local/www/nut_status.php
-rw-r--r--  1 root  wheel    193 Feb 17 10:43 /usr/local/www/shortcuts/pkg_nut.inc
-rw-r--r--  1 root  wheel     96 Feb 17 10:43 /usr/local/www/widgets/include/nut_status.inc
-rw-r--r--  1 root  wheel   3152 Feb 17 10:43 /usr/local/www/widgets/widgets/nut_status.widget.php

sha1sum: pfSense-pkg-nut-2.8.0_2:: No such file or directory
8c24e4933087b1174c821e66f940d0318a6e9b7e  /etc/inc/priv/nut.priv.inc
fe967ea9e93cd309d4b74a61e469bef85e4c4da9  /usr/local/pkg/nut.xml
efc07713dccf6f8bd43305a897437e11df769aa4  /usr/local/pkg/nut/nut.inc
7fa23e54c2f5f81125acf6ffd2f3d3df55db208a  /usr/local/pkg/nut/nut_email.php
a6a5418b4d67d9f3a33cbf184b25ac7f9fa87d33  /usr/local/share/licenses/pfSense-pkg-nut-2.8.0_2/APACHE20
6bea4964bbc2176ec94a06684a226b5813d94c0d  /usr/local/share/licenses/pfSense-pkg-nut-2.8.0_2/LICENSE
b26b9ab861e0d5b418b5e57021d768bd97a07915  /usr/local/share/licenses/pfSense-pkg-nut-2.8.0_2/catalog.mk
1ccd0187b82cd6c552aa34a776fa6cee31d76c19  /usr/local/share/pfSense-pkg-nut/info.xml
fe4c2381a6c4a51124ba3ed3a7c68c8935d58284  /usr/local/www/nut_settings.php
9f8e451e4300a77f89695004a5e8d33c4b4aade6  /usr/local/www/nut_status.php
cd553d2cfee28ef76482153f4a11b6fa3cc34f71  /usr/local/www/shortcuts/pkg_nut.inc
1d48164e283d9e320ac8bc81704a11b8949e3448  /usr/local/www/widgets/include/nut_status.inc
d33250c0811051d2fb43a77a3c3300d1595a06ca  /usr/local/www/widgets/widgets/nut_status.widget.php

dennypage

@austin-0 That is all correct. I'm not seeing anything wrong from a NUT pov.

Let's try the notification again and check the system log to see if there is any indication of the issue. Run this:

php-cgi /usr/local/pkg/nut/nut_email.php this is a test

followed by this:

tail /var/log/system.log

There should be a line in the system log for the php-cgi command referring to notify_monitor. What does it say?

dennypage

@austin-0 While we're at it, we might as well just do this:

grep notify_monitor /var/log/system.log

This will include the prior attempts as well.

Austin 0

@dennypage

Apr 22 12:29:23 WhatAreRoutes kernel: ugen1.2: <CPS ST Series> at usbus1
Apr 22 12:29:25 WhatAreRoutes upsmon[2348]: Poll UPS [OfficeUPS] failed - Driver not connected
Apr 22 12:29:30 WhatAreRoutes php-cgi[74564]: notify_monitor.php: Message sent to ----- OK
Apr 22 12:29:30 WhatAreRoutes upsmon[2348]: Poll UPS [OfficeUPS] failed - Driver not connected
Apr 22 12:29:30 WhatAreRoutes kernel: ugen1.2: <CPS ST Series> at usbus1 (disconnected)
Apr 22 12:29:34 WhatAreRoutes kernel: ugen1.2: <CPS ST Series> at usbus1
Apr 22 12:29:35 WhatAreRoutes upsmon[2348]: Poll UPS [OfficeUPS] failed - Driver not connected
Apr 22 12:29:40 WhatAreRoutes upsmon[2348]: Poll UPS [OfficeUPS] failed - Driver not connected
Apr 22 12:29:41 WhatAreRoutes php-cgi[74564]: notify_monitor.php: Message sent to ----- OK
Apr 22 12:29:42 WhatAreRoutes kernel: ugen1.2: <CPS ST Series> at usbus1 (disconnected)

I replaced the email address with ----- in the output for privacy reasons. It was the correct email though. I also did get the notification email when running this test.

Austin 0

Actually now it is spamming the email with the "this is a test" message.

dennypage

@austin-0 said in NUT notifications not working on pfsense+:

I also did get the notification email when running this test.

Meaning you received a notification from NUT saying that the UPS was not available? There are two successful indications in there.

Austin 0

And it was failing to get the UPS status until reseated the cable, and restarted the nut service.

Austin 0

@dennypage Yes however last time we tried that I also got the notifications when running the command. I just don't get them when I disconnect the UPS, or it switches to battery.

dennypage

@austin-0 said in NUT notifications not working on pfsense+:

Actually now it is spamming the email with the "this is a test" message.

Ah... there we go. See this Redmine entry for a patch.

Austin 0

@dennypage Thank you. We are currently live streaming. So it's not a good time to be installing patches, but once that is done I will try out the patch.

dennypage

@austin-0 said in NUT notifications not working on pfsense+:

We are currently live streaming. So it's not a good time to be installing patches, but once that is done I will try out the patch.

After installing the patch, you may also need to remove the existing notification files. And if a process is hung processing notifications, either kill it or reboot pfSense.

Austin 0

@dennypage Okay so I have never done this before, but from what I can tell I correctly entered th commit ID, but it is telling me it is invalid. What am I doing wrong here?

dennypage

@austin-0 Not sure, but you can try it in URL format:

https://github.com/pfsense/pfsense/commit/c5faa351c1ef6d4555478a7f50b3a16ece7e0b2a.patch