-
@incith
I have the same thing happen lately. (23.05.1)
It works fine for a while but then says unavailable. I restart service and all works again. Sometimes for weeks, sometimes it quits the next day.
Also use a cyberpower 1500
Hardware is a Dell R210-II -
@DurUser My UPS.status is always blank. So it does not work even for a little bit for me. It thinks the ups is offline 100%.
-
@DurUser I think FreeBSD/pfSense/NUT has a somewhat general issue with USB based UPS’s.
IT’s well known Cyberpower UPS’es suffer very badly from this, but also several other units - fairly vendor agnostic - shows the same disconnect issues. I have two Eaton S5 UPS’s that suffer the same problem (and I have thoroughly tested its not the USB cable).
Common for all of them is that if you connect the same UPS to a Linux or Windows host they suffer no disconnect issues - so it’s likely something to do with either the USB UPS driver or the whole USB subsystem in pfSense.Up until 23.01 it was not a catastrophe because NUT would just reconnect to the UPS. But after 23.01 it no longer does that and a disconnect now means loss of UPS status/communication. I think work is being done on getting a never USB driver for NUT that attempts to reconnect again, but it will take a while - it will likely not cure the temporary disconnect issue though. That seems to be a deeper rooted issue.
-
@keyser agree with you observation. I have same problem with TrippLite disconnecting using usb driver. @dennypage (intel) and @Maltz (arm) have posted drivers to temporarily help with disconnects. @incith is using snmp driver and seems to never connect, which sounds like a different problem altogether.
-
@ghound yeah I literally had 0 problems at all on 2.6 pfSense using snmp. It always reported 100% correctly.
-
@keyser Sure, but it was working great before. Never had an issue until recent updates to pfsense. So something got screwed up that wasn't screwed up before. And yes, I did see those disconnects/reconnects happen before the update. That worked for me. Now it no longer reconnects I guess.
-
@incith Did you not have disconnects/reconnects ? Or never noticed it ?
-
@DurUser I did not have any disconnects. SNMP worked flawlessly.
-
@incith Wait, so you didn't have the ups directly connected to your pfsense box?
I am not sure I understand your snmp setup. -
Found the fix? Not sure why this hasn't been merged into pfSense 2.7. this is old it seems. pfSense using mib v0.51 and this is 0.52 to fix the issue
https://github.com/networkupstools/nut/commit/6a6888e9b5fd995e79e3db335ff4c9c524f31b51
https://redmine.pfsense.org/issues/13972
-
@DurUser correct....that's kind of the point of SNMP lol. CyberPower PowerPanel software does SNMP server. A windows server is the primary host for the snmp data. pfSense is a slave.
It'd be nice to see pfSense have an option for choosing master or slave in the snmp driver.
-
@incith said in NUT package:
I did not have any disconnects. SNMP worked flawlessly.
You likely had disconnects. You would not have noticed, because it immediately reconnected. When this happens, there is no notification.
-
@dennypage ...ok?
-
@incith Your prior post referred to an adjustment in polling interval. FWIW, I do not see any polling interval in the configuration you posted.
As to your actual problem, it is discussed here. Assuming that you are on an Intel or AMD based platform, you use the updated snmp-ups driver posted in that thread.
-
@incith huh ? So your master is a windows machine ?
We're talking about the pfsense machine being the master. It does show disconnects. Windows likely does not.
I have a completely seperate workstation running windows with a different cyberpower 1500 ups and it never notifies me of disconnects... ever. That could mean 2 things. It has a better driver OR it doesn't show any disconnects if it's quickly reconnected.
The pfsense machine is a whole different story. I would repeatedly see disconnects in the console output. -
@DurUser cyberpower ups USB cable -> Windows server -> PowerPanel business software -> enable SNMP.
pfSense -> remote-snmp driver -> IP of windows server.
pfSense is not the master in my setup. It is an SNMP client.
-
@dennypage Thanks, I'll give that a shot here shortly!
I did a completely clean install and wiped my config from /conf for <nut> and rm /temp/config.cache etc etc. And removed the /usr/local/etc/nut folder to give you a clean configuration. That is why you are noticing discrepancies. I had tried poll interval as it was mentioned somewhere else this helped but I assumed this was going to be driver related from the start.
-
@incith said in NUT package:
Found the fix? Not sure why this hasn't been merged into pfSense 2.7. this is old it seems. pfSense using mib v0.51 and this is 0.52 to fix the issue
https://github.com/networkupstools/nut/commit/6a6888e9b5fd995e79e3db335ff4c9c524f31b51
It's not a question of being merged into pfSense. A version of NUT with that fix has not actually been released yet. The most recent release of NUT is 2.8.0, in April 2022. We have been waiting for 2.8.1 for some time. I'm sure that when 2.8.1 is released, it will be in FreeBSD Ports, and the pfSense repo, shortly thereafter.
As it sits, the only way to get a fully functional build for the various Cyberpower UPS units is to build against NUT's development (master) branch. Unfortunately, this is a moving target.
-
@dennypage Hmm, that sucks! Thanks for the information.
Unfortunately the linked snmp-ups driver will not load. It's an Intel xeon e3 v3 so should be compatible I'd have thought. Perhaps it needs rebuilt for pfSense 2.7?
-
@incith said in NUT package:
Unfortunately the linked snmp-ups driver will not load.
Need more information. Please start the driver by hand as described in the other thread. and report the actual errors encountered.
FWIW, this description:
pfSense -> remote-snmp driver -> IP of windows server.Doesn't make sense. You are using the snmp driver, so you should be talking directly to the UPS using the IP address of the UPS rather than a Windows server.
