NUT package (2.8.0 and below)
-
@kevindd992002 It's either the host end or the UPS end. On the host end, it can be hardware (bridge controller) or software (kernel driver). On the UPS end it would just be a flakey USB implementation.
What I generally recommend to people having these types of issues:
- Try a different port on the host that uses a different bridge chip. Favor ports that are USB 2 as USB 3 ports usually have more problems.
- If you have a USB hub between the host and the UPS, try removing it.
- If you don't have a USB hub between the host and the UPS, try adding one.
- Try a different USB hub that uses a different bridge chip.
- Try a different UPS model.
- Try a different host model.
Regarding the apu2c4, you might find this an interesting read.
Bonne chance
-
@dennypage I'm seeing the following log entries under 2.4.5, anything to be concerned about?
Apr 16 07:09:28 upsmon 92379 Communications with UPS UPS established Apr 16 07:09:28 upsd 33793 User local-monitor@127.0.0.1 logged into UPS [UPS] Apr 16 07:09:23 upsmon 92379 Communications with UPS UPS lost Apr 16 07:09:23 upsmon 92379 Poll UPS [UPS] failed - Write error: Permission denied Apr 16 07:09:21 nginx 2020/04/16 07:09:21 [crit] 11971#100993: *62736 SSL_write() failed (13: Permission denied) while processing HTTP/2 connection, client: 192.168.20.115, server: 0.0.0.0:4433 Apr 16 07:08:43 upsmon 92379 Communications with UPS UPS established Apr 16 07:08:43 upsd 33793 User local-monitor@127.0.0.1 logged into UPS [UPS] Apr 16 07:08:38 upsmon 92379 Communications with UPS UPS lost Apr 16 07:08:38 upsmon 92379 Poll UPS [UPS] failed - Write error: Permission denied -
@q54e3w Can you provide information on your NUT configuration please?
-
UPS is a network connected Eaton 9PX with Network Card 2.
UPS Type: Remote SNMP
UPS Name: UPS
Notifications: EnabledDriver Settings
Remote IP: 192.168.10.42
Extra args:
mibs = pw
pollfreq = 15
ignorelbAdvanced Settings
FINALDELAY 180
Addition configuration lines for ups.conf = LISTEN 192.168.10.1
Additional ups.users
[remoteuser]
password = mysupersecretpassword
upsmon slaveThis provides the following status
UPS Status
Name: UPS@localhost
Summary status: On line
Runtime (H:M:S): 5:17:00
UPS Load:
36.00%
Battery charge:
100.00%
Battery voltage: 52.00
Input frequency: 60.00 -
@q54e3w said in NUT package:
Poll UPS [UPS] failed - Write error: Permission denied
Is there anything that precedes this entry in the log? Perhaps something similar to this?
-
@dennypage said in NUT package:
Is there anything that precedes this entry in the log? Perhaps something similar to this?
No, no other errors or messages from upsd/upsmon above or below that one. First sign of trouble is the Poll UPS failed.
-
@q54e3w said in NUT package:
@dennypage said in NUT package:
Is there anything that precedes this entry in the log? Perhaps something similar to this?
No, no other errors or messages from upsd/upsmon above or below that one. First sign of trouble is the Poll UPS failed.
I wasn’t asking about other upsd/upsmon messages, rather I was asking about messages associated with links flapping, DHCP activities, etc. Similar to the logs in the link above.
-
ahhhh, gotcha. There was another issue with UPnP that I resolved and thats when I noticed these entries. I'll keep an eye on it but as I haven't seen a repeat maybe it was related. Thank you.
-
@dennypage Why is it that in the NUT GUI I see different set of parameters shown between my two pfsense boxes (same version of pfsense, same hardware, same NUT version, different UPS but both USB):
I'm missing battery voltage and last test result on the second one. Is this normal?
-
@kevindd992002 said in NUT package:
@dennypage Why is it that in the NUT GUI I see different set of parameters shown between my two pfsense boxes (same version of pfsense, same hardware, same NUT version, different UPS but both USB):
I'm missing battery voltage and last test result on the second one. Is this normal?
Not unusual. NUT only reports what what the UPS reports.
-
True.
This wouldn't be very assuring :
( image is fake of course )
-
Ok, that makes sense.
Any idea what can causes a UPS battery low notification even though I don't see a UPS on battery message first? Here's what I get in the system logs:
I've noticed this come and go since a few days ago and I don't know why. I was receiving email notifications about a batt low condition even without an on batt notification first. These are the settings I have:
I don't see the charge.warning and charge.low that high. But what do you think?
Also, how can I set the UPS (after a shutdown condition) to wait for a few minutes before it turns everything back on? Sort of a delay?
-
@kevindd992002 said in NUT package:
causes a UPS battery low notification even though I don't see a UPS on battery message first?
If a battery was a perfect device, it couldn't be low. But they are not. They always die .... which start with the tension that starts dropping. It isn't needed to be on battery to see that happen.
It could also be the charging electronics that adapts it's loading tension, because the load current start to rise for some reason.Also, the "UPS battery low notification" could also be a generic message from the UPS that is shown "as is" by NUT.
@kevindd992002 said in NUT package:
Also, how can I set the UPS (after a shutdown condition) to wait for a few minutes before it turns everything back on? Sort of a delay?
You should add a question to your question :
Does my UPS supports this ?
And if the answer is yes, ask another yourself another question : Is it possible with NUT and the UPS driver to communicate such a setting ?
If yes, then yes, it can be done.
How ? Dono. Up to you to search for it.Btw : the pfSense widget is nice to see the situation.
But UPS's (batteries) should be observed over (very long) time spans. Use tools like this to see more info. -
@Gertjan said in NUT package:
@kevindd992002 said in NUT package:
causes a UPS battery low notification even though I don't see a UPS on battery message first?
If a battery was a perfect device, it couldn't be low. But they are not. They always die .... which start with the tension that starts dropping. It isn't needed to be on battery to see that happen.
It could also be the charging electronics that adapts it's loading tension, because the load current start to rise for some reason.Also, the "UPS battery low notification" could also be a generic message from the UPS that is shown "as is" by NUT.
That's the answer I'm expecting. I completely know that batteries tend to die, especially in hot climates. I just thought there's an issue with NUT or something because it was fine a few days ago. There was just a blackout a few weeks ago where the battery was fully depleted in about 10 minutes so I knew it was working fine.
@kevindd992002 said in NUT package:
Also, how can I set the UPS (after a shutdown condition) to wait for a few minutes before it turns everything back on? Sort of a delay?
You should add a question to your question :
Does my UPS supports this ?
And if the answer is yes, ask another yourself another question : Is it possible with NUT and the UPS driver to communicate such a setting ?
If yes, then yes, it can be done.
How ? Dono. Up to you to search for it.Btw : the pfSense widget is nice to see the situation.
But UPS's (batteries) should be observed over (very long) time spans. Use tools like this to see more info.Yes, I have to search if my UPS supports it. And yes, I'm sure NUT and the USB ups driver can communicate this setting. I read about it somewhere but cannot find that specific post anymore. This is why I posted here. I guess I have to search harder.
What is that pfsense widget you've linked? Is it a package or something? I'm not seeing such a widget in the available widgets section.
-
@kevindd992002 said in NUT package:
I guess I have to search harder.
Or being lucky : someone knows what you're asking, and has the same UPS as you (APC SUA750).
I advise you to put chances on your side ;)@kevindd992002 said in NUT package:
package or something?
Munin.
It exists as a native FreeBSD package. To install it, the traditional FreeBSD CLI commands are needed.
You also need a web server 'some where' that will be hosting the Munin RRD-to-Images.
This means a Munin-client on pfSense, and a Munin server somewhere else.
I have multiple servers, so it somewhat pays of for me to use such a graph service. It reveals a lot of info over time. -
@Gertjan said in NUT package:
@kevindd992002 said in NUT package:
I guess I have to search harder.
Or being lucky : someone knows what you're asking, and has the same UPS as you (APC SUA750).
I advise you to put chances on your side ;)That's one of my UPS'es. I also have APC BR1500GI and Eaton 5E2000i.
@kevindd992002 said in NUT package:
package or something?
Munin.
It exists as a native FreeBSD package. To install it, the traditional FreeBSD CLI commands are needed.
You also need a web server 'some where' that will be hosting the Munin RRD-to-Images.
This means a Munin-client on pfSense, and a Munin server somewhere else.
I have multiple servers, so it somewhat pays of for me to use such a graph service. It reveals a lot of info over time.I see, I'll look into that. I can spin up a docker container that will serve as a web server real quick too. Thanks for the idea.
-
@dennypage Do you have any ideas why this would happen in a Synology NAS when it is connected to the pfsense NUT server?
So what happened there was:
- 12:00:24 AM -> blackout
- 12:02:45 AM -> FSD issued by NUT server and Syno went to safe shutdown (expected)
- 12:27:05 AM -> power went back on and everything started to boot up (expected)
- 12:27:59 AM -> Syno went to safe shutdown again (unexpected and I don't why it did that). I know that the NUT server thinks that the UPS is still in Low Battery state but I don't think it issued another FSD but I can't say for sure.
- 12:30:07 AM -> server back online which means it detected that AC was restored to the UPS already (unexpected because I would've thought that this message should've logged around the same time as #3 above when power really went back on)
- 12:31:40 AM -> RAID got reassemble which is the most disturbing part and what I'm trying to fix here.
My pfsense "ups*" logs around that time:
Apr 22 23:30:02 upsd 29008 User monuser@192.168.10.10 logged into UPS [ups] Apr 22 23:25:38 upsd 29008 User monuser@192.168.10.10 logged into UPS [ups] Apr 22 23:25:37 upsmon 21716 UPS ups battery is low Apr 22 23:25:37 upsmon 21716 Communications with UPS ups established Apr 22 23:25:34 upsd 29008 Connected to UPS [ups]: usbhid-ups-ups Apr 22 23:25:32 upsmon 21716 Communications with UPS ups lost Apr 22 23:25:32 upsmon 21716 Poll UPS [ups] failed - Driver not connected Apr 22 23:25:32 upsd 29008 User local-monitor@::1 logged into UPS [ups] Apr 22 23:25:30 upsd 28190 Can't connect to UPS [ups] (usbhid-ups-ups): No such file or directory Apr 22 23:25:28 upsd 12714 User monuser@192.168.10.10 logged into UPS [ups] Apr 22 23:25:27 upsd 12000 Can't connect to UPS [ups] (usbhid-ups-ups): No such file or directory Apr 22 23:25:25 upsd 78256 User local-monitor@::1 logged out from UPS [ups] Apr 22 23:25:24 upsmon 68274 Communications with UPS ups lost Apr 22 23:25:24 upsmon 68274 Poll UPS [ups] failed - Driver not connected Apr 22 23:25:24 upsd 78256 User local-monitor@::1 logged into UPS [ups] Apr 22 23:25:21 upsd 78160 Can't connect to UPS [ups] (usbhid-ups-ups): No such file or directory Apr 22 23:25:20 upsmon 22145 Communications with UPS ups lost Apr 22 23:25:20 upsmon 22145 Poll UPS [ups] failed - Driver not connected Apr 22 23:25:20 upsd 82186 User local-monitor@::1 logged into UPS [ups] Apr 22 23:25:18 upsd 80149 Can't connect to UPS [ups] (usbhid-ups-ups): No such file or directory Apr 22 23:25:17 upsd 60464 User local-monitor@::1 logged out from UPS [ups] Apr 22 23:25:10 upsmon 1149 UPS ups battery is low Apr 22 23:25:10 upsmon 1149 Communications with UPS ups established Apr 22 23:25:07 upsd 60464 Connected to UPS [ups]: usbhid-ups-ups Apr 22 23:25:05 upsd 60464 User monuser@192.168.10.10 logged into UPS [ups] Apr 22 23:25:05 upsmon 1149 UPS ups is unavailable Apr 22 23:25:05 upsmon 1149 Poll UPS [ups] failed - Driver not connected Apr 22 23:25:00 upsmon 1149 Communications with UPS ups lost Apr 22 23:25:00 upsmon 1149 Poll UPS [ups] failed - Driver not connected Apr 22 23:25:00 upsd 60464 User local-monitor@::1 logged into UPS [ups] Apr 22 23:24:58 upsd 59485 Can't connect to UPS [ups] (usbhid-ups-ups): No such file or directory Apr 22 23:24:55 upsd 23672 Can't connect to UPS [ups] (usbhid-ups-ups): No such file or directory Apr 22 23:18:33 upsd 31647 Client local-monitor@::1 set FSD on UPS [ups] Apr 22 23:18:33 upsmon 31178 UPS ups battery is low Apr 22 23:15:32 upsmon 31178 UPS ups on battery Apr 22 23:14:52 upsmon 31178 Communications with UPS ups established Apr 22 23:14:51 upsd 31647 UPS [ups] data is no longer stale Apr 22 23:14:47 upsmon 31178 Poll UPS [ups] failed - Data stale Apr 22 23:14:42 upsmon 31178 Poll UPS [ups] failed - Data stale Apr 22 23:14:37 upsmon 31178 Poll UPS [ups] failed - Data stale Apr 22 23:14:32 upsmon 31178 Poll UPS [ups] failed - Data stale Apr 22 23:14:27 upsmon 31178 Poll UPS [ups] failed - Data stale Apr 22 23:14:22 upsmon 31178 Poll UPS [ups] failed - Data stale Apr 22 23:14:17 upsmon 31178 Poll UPS [ups] failed - Data stale Apr 22 23:14:12 upsmon 31178 Poll UPS [ups] failed - Data stale Apr 22 23:14:07 upsmon 31178 Poll UPS [ups] failed - Data stale Apr 22 23:14:02 upsmon 31178 Poll UPS [ups] failed - Data staleI've had the same occurrence for about 2 or 3 times now. Can you help? Thanks.
-
@kevindd992002 said in NUT package:
@dennypage Do you have any ideas why this would happen in a Synology NAS when it is connected to the pfsense NUT server?
It's not related to the pfSense NUT package itself. It could be a result of how Synology manages NUT, or how Synology manages boot up. Either way, the best place to seek help would be the Synology forums.
One question comes to mind to prime the pump... did the Synology actually complete its shutdown? Did it remove the POWERDOWNFLAG?
-
@dennypage said in NUT package:
@kevindd992002 said in NUT package:
@dennypage Do you have any ideas why this would happen in a Synology NAS when it is connected to the pfsense NUT server?
It's not related to the pfSense NUT package itself. It could be a result of how Synology manages NUT, or how Synology manages boot up. Either way, the best place to seek help would be the Synology forums.
One question comes to mind to prime the pump... did the Synology actually complete its shutdown? Did it remove the POWERDOWNFLAG?
It wasn't really acting up this way before, so I'm not sure what changed.
I wouldn't really know because Synology doesn't provide logs regarding the complete shutdown but what I do know is that it will only go to safe mode with all the lights in the NAS itself lit up but with no activity (unmounted volumes, stopped services, etc.) which it did reach. If it was an improper shutdown, it would tell in the logs too. How would I confirm if it did remove the POWERDOWNFLAG?
-
@kevindd992002 said in NUT package:
I wouldn't really know because Synology doesn't provide logs regarding the complete shutdown but what I do know is that it will only go to safe mode with all the lights in the NAS itself lit up but with no activity (unmounted volumes, stopped services, etc.) which it did reach. If it was an improper shutdown, it would tell in the logs too. How would I confirm if it did remove the POWERDOWNFLAG?
These questions are best explored in the Synology forums.
