-
And here are the most recent logs - hard to post since I'm a new forum user and my content gets marked as spam
Feb 14 12:39:08 usbhid-ups 3654 Startup successful Feb 14 12:39:09 upsd 67052 Connected to UPS [asustor]: usbhid-ups-asustor Feb 14 12:39:12 upsmon 68189 Communications with UPS asustor established Feb 16 00:48:30 upsmon 68189 Signal 15: exiting Feb 16 00:48:30 upsd 67052 User local-monitor@127.0.0.1 logged out from UPS [asustor] Feb 16 00:48:30 upsd 67052 mainloop: Interrupted system call Feb 16 00:48:30 upsd 67052 Signal 15: exiting Feb 16 00:48:30 upsd 45026 listening on 127.0.0.1 port 3493 Feb 16 00:48:30 upsd 45026 listening on ::1 port 3493 Feb 16 00:48:30 upsd 45026 listening on 192.168.x.1 port 3493 Feb 16 00:48:30 upsd 45026 listening on 10.x.x.1 port 3493 Feb 16 00:48:30 upsd 45026 Connected to UPS [asustor]: usbhid-ups-asustor Feb 16 00:48:30 upsd 45026 Found 1 UPS defined in ups.conf Feb 16 00:48:30 upsd 46128 Startup successful Feb 16 00:48:30 upsd 46128 Can't connect to UPS [asustor] (usbhid-ups-asustor): Connection refused Feb 16 00:48:31 upsmon 52643 Startup successful Feb 16 00:48:31 upsd 46128 User local-monitor@127.0.0.1 logged into UPS [asustor] Feb 16 00:48:31 upsmon 52810 Poll UPS [asustor] failed - Driver not connected Feb 16 00:48:31 upsmon 52810 Communications with UPS asustor lost Feb 16 00:48:33 upsd 62460 listening on 127.0.0.1 port 3493 Feb 16 00:48:33 upsd 62460 listening on ::1 port 3493 Feb 16 00:48:33 upsd 62460 listening on 192.168.x.1 port 3493 Feb 16 00:48:33 upsd 62460 listening on 10.x.x.1 port 3493 Feb 16 00:48:33 upsd 62460 Can't connect to UPS [asustor] (usbhid-ups-asustor): Connection refused Feb 16 00:48:33 upsd 62460 Found 1 UPS defined in ups.conf Feb 16 00:48:33 upsd 62759 Startup successful Feb 16 00:48:34 upsmon 77057 Startup successful Feb 16 00:48:34 upsd 62759 User local-monitor@127.0.0.1 logged into UPS [asustor] Feb 16 00:48:34 upsmon 77403 Poll UPS [asustor] failed - Driver not connected Feb 16 00:48:34 upsmon 77403 Communications with UPS asustor lost Feb 16 00:48:39 upsmon 77403 Poll UPS [asustor] failed - Driver not connected Feb 16 00:48:39 upsmon 77403 UPS asustor is unavailable Feb 16 00:48:39 usbhid-ups 90094 Startup successful Feb 16 00:48:40 upsd 62759 Connected to UPS [asustor]: usbhid-ups-asustor Feb 16 00:48:44 upsmon 77403 Communications with UPS asustor established Feb 16 00:49:06 upsmon 77403 Signal 15: exiting Feb 16 00:49:06 upsd 62759 User local-monitor@127.0.0.1 logged out from UPS [asustor] Feb 16 00:49:06 upsd 62759 mainloop: Interrupted system call Feb 16 00:49:06 upsd 62759 Signal 15: exiting Feb 16 00:49:06 usbhid-ups 90094 Signal 15: exiting Feb 16 00:49:06 upsd 35986 listening on 127.0.0.1 port 3493 Feb 16 00:49:06 upsd 35986 listening on ::1 port 3493 Feb 16 00:49:06 upsd 35986 listening on 192.168.x.1 port 3493 Feb 16 00:49:06 upsd 35986 listening on 10.x.x.1 port 3493 Feb 16 00:49:06 upsd 35986 Can't connect to UPS [asustor] (usbhid-ups-asustor): No such file or directory Feb 16 00:49:06 upsd 35986 Found 1 UPS defined in ups.conf Feb 16 00:49:06 upsd 37101 Startup successful Feb 16 00:49:07 upsmon 43021 Startup successful Feb 16 00:49:07 upsd 37101 User local-monitor@127.0.0.1 logged into UPS [asustor] Feb 16 00:49:07 upsmon 43028 Poll UPS [asustor] failed - Driver not connected Feb 16 00:49:07 upsmon 43028 Communications with UPS asustor lost Feb 16 00:49:09 upsd 57673 listening on 127.0.0.1 port 3493 Feb 16 00:49:09 upsd 57673 listening on ::1 port 3493 Feb 16 00:49:09 upsd 57673 listening on 192.168.x.1 port 3493 Feb 16 00:49:09 upsd 57673 listening on 10.x.x.1 port 3493 Feb 16 00:49:09 upsd 57673 Can't connect to UPS [asustor] (usbhid-ups-asustor): No such file or directory Feb 16 00:49:09 upsd 57673 Found 1 UPS defined in ups.conf Feb 16 00:49:09 upsd 57948 Startup successful Feb 16 00:49:10 upsmon 58606 Startup successful Feb 16 00:49:10 upsd 57948 User local-monitor@127.0.0.1 logged into UPS [asustor] Feb 16 00:49:10 upsmon 58827 Poll UPS [asustor] failed - Driver not connected Feb 16 00:49:10 upsmon 58827 Communications with UPS asustor lost Feb 16 00:49:15 usbhid-ups 81890 Startup successful Feb 16 00:49:15 upsd 57948 Connected to UPS [asustor]: usbhid-ups-asustor Feb 16 00:49:15 upsmon 58827 Poll UPS [asustor] failed - Driver not connected Feb 16 00:49:15 upsmon 58827 UPS asustor is unavailable Feb 16 00:49:20 upsmon 58827 Communications with UPS asustor established Feb 16 00:49:20 upsmon 58827 UPS asustor on battery Feb 16 01:15:24 upsmon 58827 Signal 15: exiting Feb 16 01:15:24 upsd 57948 User local-monitor@127.0.0.1 logged out from UPS [asustor] Feb 16 01:15:24 upsd 57948 mainloop: Interrupted system call Feb 16 01:15:24 upsd 57948 Signal 15: exiting Feb 16 01:15:24 usbhid-ups 81890 Signal 15: exiting Feb 16 01:15:24 upsd 57162 listening on 127.0.0.1 port 3493 Feb 16 01:15:24 upsd 57162 listening on ::1 port 3493 Feb 16 01:15:24 upsd 57162 listening on 192.168.x.1 port 3493 Feb 16 01:15:24 upsd 57162 listening on 10.x.x.1 port 3493 Feb 16 01:15:24 upsd 57162 Can't connect to UPS [asustor] (usbhid-ups-asustor): No such file or directory Feb 16 01:15:24 upsd 57162 Found 1 UPS defined in ups.conf Feb 16 01:15:24 upsd 58023 Startup successful Feb 16 01:15:25 upsmon 65579 Startup successful Feb 16 01:15:25 upsd 58023 User local-monitor@127.0.0.1 logged into UPS [asustor] Feb 16 01:15:25 upsmon 65876 Poll UPS [asustor] failed - Driver not connected Feb 16 01:15:25 upsmon 65876 Communications with UPS asustor lost Feb 16 01:15:27 upsd 79675 listening on 127.0.0.1 port 3493 Feb 16 01:15:27 upsd 79675 listening on ::1 port 3493 Feb 16 01:15:27 upsd 79675 listening on 192.168.x.1 port 3493 Feb 16 01:15:27 upsd 79675 listening on 10.x.x.1 port 3493 Feb 16 01:15:27 upsd 79675 Can't connect to UPS [asustor] (usbhid-ups-asustor): No such file or directory Feb 16 01:15:27 upsd 79675 Found 1 UPS defined in ups.conf Feb 16 01:15:27 upsd 79793 Startup successful Feb 16 01:15:29 upsmon 80326 Startup successful Feb 16 01:15:29 upsd 79793 User local-monitor@127.0.0.1 logged into UPS [asustor] Feb 16 01:15:29 upsmon 80422 Poll UPS [asustor] failed - Driver not connected Feb 16 01:15:29 upsmon 80422 Communications with UPS asustor lost Feb 16 01:15:34 upsmon 80422 Poll UPS [asustor] failed - Driver not connected Feb 16 01:15:34 upsmon 80422 UPS asustor is unavailable Feb 16 01:15:34 usbhid-ups 3026 Startup successful Feb 16 01:15:35 upsd 79793 Connected to UPS [asustor]: usbhid-ups-asustor Feb 16 01:15:39 upsmon 80422 Communications with UPS asustor established Feb 16 04:31:17 upsmon 80422 Signal 15: exiting Feb 16 04:31:17 upsd 79793 User local-monitor@127.0.0.1 logged out from UPS [asustor] Feb 16 04:31:17 upsd 79793 mainloop: Interrupted system call Feb 16 04:31:17 upsd 79793 Signal 15: exiting Feb 16 04:31:17 upsd 31604 listening on 127.0.0.1 port 3493 Feb 16 04:31:17 upsd 31604 listening on ::1 port 3493 Feb 16 04:31:17 upsd 31604 listening on 192.168.x.1 port 3493 Feb 16 04:31:17 upsd 31604 listening on 10.x.x.1 port 3493 Feb 16 04:31:17 upsd 31604 Connected to UPS [asustor]: usbhid-ups-asustor Feb 16 04:31:17 upsd 31604 Found 1 UPS defined in ups.conf Feb 16 04:31:17 upsd 31697 Startup successful Feb 16 04:31:17 upsd 31697 Can't connect to UPS [asustor] (usbhid-ups-asustor): Connection refused Feb 16 04:31:18 upsmon 32274 Startup successful Feb 16 04:31:18 upsd 31697 User local-monitor@127.0.0.1 logged into UPS [asustor] Feb 16 04:31:18 upsmon 32557 Poll UPS [asustor] failed - Driver not connected Feb 16 04:31:18 upsmon 32557 Communications with UPS asustor lost Feb 16 04:31:24 upsmon 32557 Poll UPS [asustor] failed - Driver not connected Feb 16 04:31:24 upsmon 32557 UPS asustor is unavailable Feb 16 04:31:25 usbhid-ups 40263 Startup successful Feb 16 04:31:26 upsd 31697 Connected to UPS [asustor]: usbhid-ups-asustor Feb 16 04:31:29 upsmon 32557 Communications with UPS asustor established Feb 16 04:33:49 upsmon 32557 Signal 15: exiting Feb 16 04:33:49 upsd 31697 User local-monitor@127.0.0.1 logged out from UPS [asustor] Feb 16 04:33:49 upsd 31697 mainloop: Interrupted system call Feb 16 04:33:49 upsd 31697 Signal 15: exiting Feb 16 04:33:49 usbhid-ups 40263 Signal 15: exiting Feb 16 04:33:49 upsd 16956 listening on 127.0.0.1 port 3493 Feb 16 04:33:49 upsd 16956 listening on ::1 port 3493 Feb 16 04:33:49 upsd 16956 listening on 192.168.x.1 port 3493 Feb 16 04:33:49 upsd 16956 listening on 10.x.x.1 port 3493 Feb 16 04:33:49 upsd 16956 Can't connect to UPS [asustor] (usbhid-ups-asustor): No such file or directory Feb 16 04:33:49 upsd 16956 Found 1 UPS defined in ups.conf Feb 16 04:33:49 upsd 17200 Startup successful Feb 16 04:33:50 upsmon 17746 Startup successful Feb 16 04:33:50 upsd 17200 User local-monitor@127.0.0.1 logged into UPS [asustor] Feb 16 04:33:50 upsmon 17789 Poll UPS [asustor] failed - Driver not connected Feb 16 04:33:50 upsmon 17789 Communications with UPS asustor lost Feb 16 04:33:55 upsmon 17789 Poll UPS [asustor] failed - Driver not connected Feb 16 04:33:55 upsmon 17789 UPS asustor is unavailable Feb 16 04:33:55 usbhid-ups 71842 Startup successful Feb 16 04:33:57 upsd 17200 Connected to UPS [asustor]: usbhid-ups-asustor Feb 16 04:34:00 upsmon 17789 Communications with UPS asustor established Feb 16 04:47:29 upsmon 17789 Signal 15: exiting Feb 16 04:47:29 upsd 17200 User local-monitor@127.0.0.1 logged out from UPS [asustor] Feb 16 04:47:29 upsd 17200 mainloop: Interrupted system call Feb 16 04:47:29 upsd 17200 Signal 15: exiting Feb 16 04:47:29 upsd 21251 listening on 127.0.0.1 port 3493 Feb 16 04:47:29 upsd 21251 listening on ::1 port 3493 Feb 16 04:47:29 upsd 21251 listening on 192.168.x.1 port 3493 Feb 16 04:47:29 upsd 21251 listening on 10.x.x.1 port 3493 Feb 16 04:47:29 upsd 21251 Connected to UPS [asustor]: usbhid-ups-asustor Feb 16 04:47:29 upsd 21251 Found 1 UPS defined in ups.conf Feb 16 04:47:29 upsd 22338 Startup successful Feb 16 04:47:29 upsd 22338 Can't connect to UPS [asustor] (usbhid-ups-asustor): Connection refused Feb 16 04:47:30 upsmon 28745 Startup successful Feb 16 04:47:30 upsd 22338 User local-monitor@127.0.0.1 logged into UPS [asustor] Feb 16 04:47:30 upsmon 29046 Poll UPS [asustor] failed - Driver not connected Feb 16 04:47:30 upsmon 29046 Communications with UPS asustor lost Feb 16 04:47:32 upsd 44171 listening on 127.0.0.1 port 3493 Feb 16 04:47:32 upsd 44171 listening on ::1 port 3493 Feb 16 04:47:32 upsd 44171 listening on 192.168.x.1 port 3493 Feb 16 04:47:32 upsd 44171 listening on 10.x.x.1 port 3493 Feb 16 04:47:32 upsd 44171 Can't connect to UPS [asustor] (usbhid-ups-asustor): Connection refused Feb 16 04:47:32 upsd 44171 Found 1 UPS defined in ups.conf Feb 16 04:47:32 upsd 44733 Startup successful Feb 16 04:47:33 upsmon 45169 Startup successful Feb 16 04:47:33 upsd 44733 User local-monitor@127.0.0.1 logged into UPS [asustor] Feb 16 04:47:33 upsmon 45467 Poll UPS [asustor] failed - Driver not connected Feb 16 04:47:33 upsmon 45467 Communications with UPS asustor lost Feb 16 04:47:38 upsmon 45467 Poll UPS [asustor] failed - Driver not connected Feb 16 04:47:38 upsmon 45467 UPS asustor is unavailable Feb 16 04:47:38 usbhid-ups 66387 Startup successful Feb 16 04:47:40 upsd 44733 Connected to UPS [asustor]: usbhid-ups-asustor Feb 16 04:47:43 upsmon 45467 Communications with UPS asustor established -
Way back, I thought the following : interfaces that are physically connected can go down, but there 's one that actually doesn't get downed ... the local host : 127.0.0.1.
And guess what :
The NUT service always listens to 127.0.0.1 and every other interface you specify.
Like :
So, me thinking being smart (and probably also seeing this proposed in the documentation ) :
I added a NAT rule on my LAN for the devices that want to connect to NUT on pfSense :
But no, NUT still get restarted upon any interface event. The fact that it uses only the internal 127.0.0.1 doesn't matter ...
I was able to exclude NUT from restarting, but this needed some pfSense script editing ....
Anyway, for me, interfaces going down is a very rare event (ditched pppoe years ago as it was a meant to be used with modems and stuff like that, and these will be phased out anyway) as my main switches and ISP router are also UPS fed. -
@Gertjan - kinda smart thinking but since it's an OR between interfaces it was indeed pointless...
I'm not happy with PPPoE either but that is all my ISP can provide. Can't complain however $8.5 for 1G down/0.5G up bandwidth and no cap on any traffic is great value compared to others. -
@rarlup said in NUT Package (2.8.1 and above):
Can't complain however $8.5 for 1G down/0.5G up bandwidth and no cap on any traffic is great value compared to others
I agree. pppoe it will be ^^
-
@rarlup Sorry for the delayed response -- I've been traveling.
Couple of things I noticed looking at your logs. First, you have a lot of pogo. I assume that this is from your WAN connection, but I can't tell without more logs. I would definitely check to see if there are other sources of restart occurring, such as a local client plugged directly into a port on the firewall.
Secondly, I note that it is taking quite a long time for your UPS driver to start. As an experiment, you might remove the ampersand from the start of upsdrvctl in /usr/local/etc/rc.d/nut.sh and see if that helps the startup.
As to the shutdown, I'm guessing that you may have had a brief power outage just before your WAN reset. If NUT looses connection with the UPS, and the last known state was on battery, the default behavior of NUT is to initiate a shutdown.
-
@dennypage said in NUT Package (2.8.1 and above):
Sorry for the delayed response -- I've been traveling
No worries - hope it was for pleasure :)
And please forgive me for not thanking you sooner for your help, and especially on a Saturday - greatly appreciated.@dennypage said in NUT Package (2.8.1 and above):
you have a lot of pogo
what do you mean? bouncing back and forth / up and down?
@dennypage said in NUT Package (2.8.1 and above):
Secondly, I note that it is taking quite a long time for your UPS driver to start. As an experiment, you might remove the ampersand from the start of upsdrvctl in /usr/local/etc/rc.d/nut.sh and see if that helps the startup.
Will try later today/tmr. Currently under business hours.
@dennypage said in NUT Package (2.8.1 and above):
As to the shutdown
Devices (mostly Asustor NASes, as I mentioned before) are scheduled to gracefully shutdown 5min after the On Battery event (without a corresponding On A/C event). The thing is it didn't lose the connection with the UPS it just showed On Battery after WAN down event and stayed with that status. I'm 100% convinced there was no power outage since there was no relay click (comes instantly, talking few milliseconds) and as I was standing right by it.
Why was I standing right by it?
Because I was the one that cut(literally) the wan cable. This may have caused a few ms short - I do agree it may have caused pfSense to do weird things.
I cut it since the wiring was damaged and I wanted to redo the connection. Previously, just breathing near the cable could cause a WAN down event so this may be the actual cause - faulty wiring on one of the pfSense interfaces can/will cause weird UPS status? -
@dennypage said in NUT Package (2.8.1 and above):
Secondly, I note that it is taking quite a long time for your UPS driver to start. As an experiment, you might remove the ampersand from the start of upsdrvctl in /usr/local/etc/rc.d/nut.sh and see if that helps the startup.
Removed the &
/usr/local/sbin/upsdrvctl start &/usr/local/sbin/upsdrvctl startAnd restarted the service.
Seems like it helped - no more poll ups failures and connections being refused. Not sure if this is related to edited file.Feb 19 03:07:45 upsmon 17987 Signal 15: exiting Feb 19 03:07:45 upsd 17183 User local-monitor@127.0.0.1 logged out from UPS [asustor] Feb 19 03:07:45 upsd 17183 mainloop: Interrupted system call Feb 19 03:07:45 upsd 17183 Signal 15: exiting Feb 19 03:07:45 usbhid-ups 19139 Signal 15: exiting Feb 19 03:07:52 usbhid-ups 26744 Startup successful Feb 19 03:07:52 upsd 26874 listening on 127.0.0.1 port 3493 Feb 19 03:07:52 upsd 26874 listening on ::1 port 3493 Feb 19 03:07:52 upsd 26874 listening on 192.168.x.1 port 3493 Feb 19 03:07:52 upsd 26874 listening on 10.x.x.1 port 3493 Feb 19 03:07:52 upsd 26874 Connected to UPS [asustor]: usbhid-ups-asustor Feb 19 03:07:52 upsd 26874 Found 1 UPS defined in ups.conf Feb 19 03:07:52 upsd 27039 Startup successful Feb 19 03:07:53 upsmon 27550 Startup successful Feb 19 03:07:53 upsd 27039 User local-monitor@127.0.0.1 logged into UPS [asustor] -
@rarlup said in NUT Package (2.8.1 and above):
faulty wiring on one of the pfSense interfaces can/will cause weird UPS status?
A faulty network cable, WAN, LAN, whatever, will cause system network event. One of the effects will be that that interface is taken down (and/or up if the connections returns).
Software that is bound (uses) to a (any !) interface will get restarted, even if that interface wasn't the one triggering the event.
Instead of a weird behavior, look at the logs again : it gets stopped, and restarted again.
The monitoring process will re open the USB port, if that's your UPS connection, re contact the UPS, signal the obtained stated to the local NUT process, etc.
Even the localhost or 127.0.0.1 is no exception, it's probably not the interface that can be taken down by a bad cable, as it has no cable ^^ but processes using it will also get restarted.No "help me" PM's please. Use the forum, the community will thank you.
Edit : and where are the logs ?? -
@rarlup said in NUT Package (2.8.1 and above):
you have a lot of pogo
what do you mean? bouncing back and forth / up and down?Yes.
@rarlup said in NUT Package (2.8.1 and above):
The thing is it didn't lose the connection with the UPS it just showed On Battery after WAN down event and stayed with that status.
There was a persistent connection loss in the logs you posted. Feb 14 12:35:26.
@rarlup said in NUT Package (2.8.1 and above):
Previously, just breathing near the cable could cause a WAN down event so this may be the actual cause - faulty wiring on one of the pfSense interfaces can/will cause weird UPS status?
Yes, this could be the cause of the pogo.
-
A common mistake people make is to directly connect a PC or Mac to a port on pfSense rather than through a switch. The frequent sleep/wake cycles of these systems, which bring link down/up on their ports, wreak havoc on the pfSense.
-
@dennypage said in NUT Package (2.8.1 and above):
A common mistake people make is to directly connect a PC or Mac to a port on pfSense rather than through a switch. The frequent sleep/wake cycles of these systems, which bring link down/up on their ports, wreak havoc on the pfSense.
Yeah ... big +1 that one.
No excuse if they have an UPS : the upstream ISP device (router, modem, powered ONT, whatever, pfSense itself, and all the LAN attached switch(es) should be powered by the same - or linked - UPS.
This solves a load of potential pitfalls.
(admin) Live is so easy ones you reached this conclusion / setup ^^ -
@dennypage
Not the case - that pfsense box has 9 interfaces (5 rj45 and 4 sfp+)
0 - wan pppoe
1 - another pfsense box
2 - not used yet
3 - not used
4 - switch A0 - lacp to switch B
1 - lacp to switch B
2 - not used
3 - not usedChecked the UPS logs and no new events. Guess that & fixed it.
-
@dennypage said in NUT Package (2.8.1 and above):
There was a persistent connection loss in the logs you posted. Feb 14 12:35:26.
So WAN glitched, triggered package restart and somehow it detected the UPS as on battery before losing connection to it?
-
@rarlup said in NUT Package (2.8.1 and above):
detected the UPS as on battery
If that state was known at the moment, then it is because NUT got that state from the UPS.
An UPS on battery, yeah, something has glitched - and the WAN agrees ^^ -
I see and it makes sense. Thank you both!
Looking to purchase a few more UPSes - any particular model that is 100% compatible with NUT and you can truly recommend?
min 700VA, cheap (<$200) and rack mountable would be ideal -
@rarlup said in NUT Package (2.8.1 and above):
Looking to purchase a few more UPSes - any particular model that is 100% compatible with NUT and you can truly recommend?
NUT is compatible with a wide variety of UPSs. That said, some UPSs have more quirks than others.
Specific recommendations are difficult, but I would generally stay with usb-hid capable units from one of the big manufacturers such as APC, Cyber Power or Tripp Lite.
My personal preference is for APC, but they tend to be a bit more expensive.
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.