-
@jonlecroy said in NUT Package (2.8.1 and above):
The UPS regular maintenance sending an 'administrative off' which triggers a pfsense immediate halt when it shouldn't.
I believe this is addressed, yes.
-
D dennypage referenced this topic on
-
For what it's worth, I just did a pkg-static remove nut-devel and pfsense nut 2.8.2_1 blah blah. Cleaned it all out. Did a pkg-static update made sure repo is current. Installed the latest 2 packages from pfsense web gui, and tripplite USB is still broken.
pkg install -f nut-devel-2023.10.07_1.pkg
And it's fixed again.
-
@incith The next release is expected switch over to the 2.8.2 production release of NUT.
-
Not sure if you guys are aware but there is a bug with 2.8.2_4 and PPPoE as in when WAN goes down UPS states it's on battery (usbhid driver) and this causes unexpected shutdowns with internet offline, obviously.
pfSense+
24.11-RELEASE (amd64)
built on Sat Jan 11 18:11:00 EET 2025
FreeBSD 15.0-CURRENT -
@rarlup said in NUT Package (2.8.1 and above):
Not sure if you guys are aware but there is a bug with 2.8.2_4 and PPPoE as in when WAN goes down UPS states it's on battery (usbhid driver) and this causes unexpected shutdowns with internet offline, obviously.
Whenever an interface changes state, all packages are restarted. Expected, not particular to PPPoE.
Seems like you might be encountering an issue with the ups driver. What model of ups? And do you have anything in the Additional arguments to driver section? Or in any of the Advanced sections?
-
Whenever an interface changes state, all packages are restarted. Expected, not particular to PPPoE.
Why does this happen? Why does it need to happen? Seems extremely disruptive for benign events
-
@michmoor said in NUT Package (2.8.1 and above):
Whenever an interface changes state, all packages are restarted. Expected, not particular to PPPoE.
Why does this happen? Why does it need to happen? Seems extremely disruptive for benign events
It is required because pfSense does not have a view into what happens inside a package. Using NUT as an example, pfSense itself has no idea if NUT is using a remote connection, or what interface it may depend upon. Similar situations exist for all packages.
Package restart is the only current way to address this.
-
@dennypage I might since I have no idea if I need any extra arguments.
UPS is a CyberPower BR1200ELCD
Here is a screenshot of current config:
I have some Asustor NASes and due to their network ups default/unchangeable config UPS Name/username/password has to remain like this to keep it visible for them. -
@rarlup does it happen when you restart nut by itself? Or only when the automates restart happens?
What ups messages to you see in the system logs?
-
@dennypage
When restarting the service it goes from
to
directly.
Please find below all relevant logs but the last PPPoE down event was at 00:48 ish(not really last one, unplugged it a few minutes ago to replicate the issue but the UPS Status didn't change)
But these lines stands out:
Feb 14 12:29:24 upsmon 29260 UPS asustor on battery
...
Feb 14 12:29:44 upsmon 35718 UPS asustor on battery
...
Feb 16 00:49:20 upsmon 58827 UPS asustor on battery
And yes, I did find everything powered off couple of days ago when there was another wan down event. Today was the 2nd time.
And I'm 100% sure the AC power was never lost during this timeframe (have other UPSes in the house and all the buzzer sounds is enough to wake up anyone).Older logs (part 1):
Feb 13 23:24:50 upsmon 55586 UPS asustor is unavailable Feb 13 23:24:55 upsmon 55586 Poll UPS [asustor] failed - Driver not connected Feb 13 23:24:56 usbhid-ups 80525 Startup successful Feb 13 23:24:57 upsd 55007 Connected to UPS [asustor]: usbhid-ups-asustor Feb 13 23:25:00 upsmon 55586 Communications with UPS asustor established Feb 14 06:07:08 upsmon 55586 Signal 15: exiting Feb 14 06:07:08 upsd 55007 User local-monitor@127.0.0.1 logged out from UPS [asustor] Feb 14 06:07:08 upsd 55007 mainloop: Interrupted system call Feb 14 06:07:08 upsd 55007 Signal 15: exiting Feb 14 06:07:08 upsd 30801 listening on 127.0.0.1 port 3493 Feb 14 06:07:08 upsd 30801 listening on ::1 port 3493 Feb 14 06:07:08 upsd 30801 listening on 192.168.x.1 port 3493 Feb 14 06:07:08 upsd 30801 listening on 10.x.x.1 port 3493 Feb 14 06:07:08 upsd 30801 Connected to UPS [asustor]: usbhid-ups-asustor Feb 14 06:07:08 upsd 30801 Found 1 UPS defined in ups.conf Feb 14 06:07:08 upsd 32292 Startup successful Feb 14 06:07:08 upsd 32292 Can't connect to UPS [asustor] (usbhid-ups-asustor): Connection refused Feb 14 06:07:09 upsmon 37424 Startup successful Feb 14 06:07:09 upsd 32292 User local-monitor@127.0.0.1 logged into UPS [asustor] Feb 14 06:07:09 upsmon 37432 Poll UPS [asustor] failed - Driver not connected Feb 14 06:07:09 upsmon 37432 Communications with UPS asustor lost Feb 14 06:07:11 upsd 38934 listening on 127.0.0.1 port 3493 Feb 14 06:07:11 upsd 38934 listening on ::1 port 3493 Feb 14 06:07:11 upsd 38934 listening on 192.168.x.1 port 3493 Feb 14 06:07:11 upsd 38934 listening on 10.x.x.1 port 3493 Feb 14 06:07:11 upsd 38934 Can't connect to UPS [asustor] (usbhid-ups-asustor): Connection refused Feb 14 06:07:11 upsd 38934 Found 1 UPS defined in ups.conf Feb 14 06:07:11 upsd 39491 Startup successful Feb 14 06:07:12 upsmon 39925 Startup successful Feb 14 06:07:12 upsd 39491 User local-monitor@127.0.0.1 logged into UPS [asustor] Feb 14 06:07:12 upsmon 40059 Poll UPS [asustor] failed - Driver not connected Feb 14 06:07:12 upsmon 40059 Communications with UPS asustor lost Feb 14 06:07:17 upsmon 40059 Poll UPS [asustor] failed - Driver not connected Feb 14 06:07:17 upsmon 40059 UPS asustor is unavailable Feb 14 06:07:18 usbhid-ups 40977 Startup successful Feb 14 06:07:18 upsd 39491 Connected to UPS [asustor]: usbhid-ups-asustor Feb 14 06:07:22 upsmon 40059 Communications with UPS asustor established Feb 14 12:29:20 upsmon 40059 Signal 15: exiting Feb 14 12:29:20 upsd 39491 User local-monitor@127.0.0.1 logged out from UPS [asustor] Feb 14 12:29:20 upsd 39491 mainloop: Interrupted system call Feb 14 12:29:20 upsd 39491 Signal 15: exiting Feb 14 12:29:20 upsd 8379 listening on 127.0.0.1 port 3493 Feb 14 12:29:20 upsd 8379 listening on ::1 port 3493 Feb 14 12:29:20 upsd 8379 listening on 192.168.x.1 port 3493 Feb 14 12:29:20 upsd 8379 listening on 10.x.x.1 port 3493 Feb 14 12:29:20 upsd 8379 Connected to UPS [asustor]: usbhid-ups-asustor Feb 14 12:29:20 upsd 8379 Found 1 UPS defined in ups.conf Feb 14 12:29:20 upsd 9219 Startup successful Feb 14 12:29:20 upsd 9219 Can't connect to UPS [asustor] (usbhid-ups-asustor): Connection refused Feb 14 12:29:21 upsmon 13661 Startup successful Feb 14 12:29:21 upsd 9219 User local-monitor@127.0.0.1 logged into UPS [asustor] Feb 14 12:29:21 upsmon 13937 Poll UPS [asustor] failed - Driver not connected Feb 14 12:29:21 upsmon 13937 Communications with UPS asustor lost Feb 14 12:29:23 upsd 27918 listening on 127.0.0.1 port 3493 Feb 14 12:29:23 upsd 27918 listening on ::1 port 3493 Feb 14 12:29:23 upsd 27918 listening on 192.168.x.1 port 3493 Feb 14 12:29:23 upsd 27918 listening on 10.x.x.1 port 3493 Feb 14 12:29:23 upsd 27918 Can't connect to UPS [asustor] (usbhid-ups-asustor): Connection refused Feb 14 12:29:23 upsd 27918 Found 1 UPS defined in ups.conf Feb 14 12:29:23 upsd 28340 Startup successful Feb 14 12:29:23 usbhid-ups 28703 Startup successful Feb 14 12:29:24 upsmon 28984 Startup successful Feb 14 12:29:24 upsd 28340 Connected to UPS [asustor]: usbhid-ups-asustor Feb 14 12:29:24 upsd 28340 User local-monitor@127.0.0.1 logged into UPS [asustor] Feb 14 12:29:24 upsmon 29260 UPS asustor on battery Feb 14 12:29:30 upsmon 29260 Signal 15: exiting Feb 14 12:29:30 upsd 28340 User local-monitor@127.0.0.1 logged out from UPS [asustor] Feb 14 12:29:30 upsd 28340 mainloop: Interrupted system call Feb 14 12:29:30 upsd 28340 Signal 15: exiting Feb 14 12:29:30 usbhid-ups 28703 Signal 15: exiting Feb 14 12:29:30 upsd 94688 listening on 127.0.0.1 port 3493 Feb 14 12:29:30 upsd 94688 listening on ::1 port 3493 Feb 14 12:29:30 upsd 94688 listening on 192.168.x.1 port 3493 Feb 14 12:29:30 upsd 94688 listening on 10.x.x.1 port 3493 Feb 14 12:29:30 upsd 94688 Can't connect to UPS [asustor] (usbhid-ups-asustor): No such file or directory Feb 14 12:29:30 upsd 94688 Found 1 UPS defined in ups.conf Feb 14 12:29:30 upsd 96189 Startup successful Feb 14 12:29:31 upsmon 8313 Startup successful Feb 14 12:29:31 upsd 96189 User local-monitor@127.0.0.1 logged into UPS [asustor] Feb 14 12:29:31 upsmon 8341 Poll UPS [asustor] failed - Driver not connected Feb 14 12:29:31 upsmon 8341 Communications with UPS asustor lost Feb 14 12:29:33 upsd 23386 listening on 127.0.0.1 port 3493 Feb 14 12:29:33 upsd 23386 listening on ::1 port 3493 Feb 14 12:29:33 upsd 23386 listening on 192.168.x.1 port 3493 Feb 14 12:29:33 upsd 23386 listening on 10.x.x.1 port 3493 Feb 14 12:29:33 upsd 23386 Can't connect to UPS [asustor] (usbhid-ups-asustor): No such file or directory Feb 14 12:29:33 upsd 23386 Found 1 UPS defined in ups.conf Feb 14 12:29:33 upsd 24104 Startup successful Feb 14 12:29:34 upsmon 35461 Startup successful Feb 14 12:29:34 upsd 24104 User local-monitor@127.0.0.1 logged into UPS [asustor] Feb 14 12:29:34 upsmon 35718 Poll UPS [asustor] failed - Driver not connected Feb 14 12:29:34 upsmon 35718 Communications with UPS asustor lost Feb 14 12:29:39 upsmon 35718 Poll UPS [asustor] failed - Driver not connected Feb 14 12:29:39 upsmon 35718 UPS asustor is unavailable Feb 14 12:29:40 usbhid-ups 52006 Startup successful Feb 14 12:29:40 upsd 24104 Connected to UPS [asustor]: usbhid-ups-asustor Feb 14 12:29:44 upsmon 35718 Communications with UPS asustor established Feb 14 12:29:44 upsmon 35718 UPS asustor on battery Feb 14 12:30:24 upsmon 35718 Signal 15: exiting Feb 14 12:30:24 upsd 24104 User local-monitor@127.0.0.1 logged out from UPS [asustor] Feb 14 12:30:24 upsd 24104 mainloop: Interrupted system call Feb 14 12:30:24 upsd 24104 Signal 15: exiting Feb 14 12:30:24 usbhid-ups 52006 Signal 15: exiting Feb 14 12:30:24 upsd 82503 listening on 127.0.0.1 port 3493 Feb 14 12:30:24 upsd 82503 listening on ::1 port 3493 Feb 14 12:30:24 upsd 82503 listening on 192.168.x.1 port 3493 Feb 14 12:30:24 upsd 82503 listening on 10.x.x.1 port 3493 Feb 14 12:30:24 upsd 82503 Can't connect to UPS [asustor] (usbhid-ups-asustor): No such file or directory Feb 14 12:30:24 upsd 82503 Found 1 UPS defined in ups.conf Feb 14 12:30:24 upsd 83576 Startup successful Feb 14 12:30:25 upsmon 5940 Startup successful Feb 14 12:30:25 upsd 83576 User local-monitor@127.0.0.1 logged into UPS [asustor] Feb 14 12:30:25 upsmon 6162 Poll UPS [asustor] failed - Driver not connected Feb 14 12:30:25 upsmon 6162 Communications with UPS asustor lost Feb 14 12:30:27 upsd 8056 listening on 127.0.0.1 port 3493 Feb 14 12:30:27 upsd 8056 listening on ::1 port 3493 Feb 14 12:30:27 upsd 8056 listening on 192.168.x.1 port 3493 Feb 14 12:30:27 upsd 8056 listening on 10.x.x.1 port 3493 Feb 14 12:30:27 upsd 8056 Can't connect to UPS [asustor] (usbhid-ups-asustor): No such file or directory Feb 14 12:30:27 upsd 8056 Found 1 UPS defined in ups.conf Feb 14 12:30:27 upsd 8590 Startup successful Feb 14 12:30:28 upsmon 8990 Startup successful Feb 14 12:30:28 upsd 8590 User local-monitor@127.0.0.1 logged into UPS [asustor] Feb 14 12:30:28 upsmon 9123 Poll UPS [asustor] failed - Driver not connected Feb 14 12:30:28 upsmon 9123 Communications with UPS asustor lost Feb 14 12:30:33 upsmon 9123 Poll UPS [asustor] failed - Driver not connected Feb 14 12:30:33 upsmon 9123 UPS asustor is unavailable Feb 14 12:30:38 upsmon 9123 Poll UPS [asustor] failed - Driver not connected Feb 14 12:30:39 usbhid-ups 59354 Startup successful Feb 14 12:30:39 upsd 8590 Connected to UPS [asustor]: usbhid-ups-asustor Feb 14 12:30:44 upsmon 9123 Communications with UPS asustor established Feb 14 12:30:54 upsmon 9123 Signal 15: exiting Feb 14 12:30:54 upsd 8590 User local-monitor@127.0.0.1 logged out from UPS [asustor] Feb 14 12:30:54 upsd 8590 mainloop: Interrupted system call Feb 14 12:30:54 upsd 8590 Signal 15: exiting Feb 14 12:30:54 usbhid-ups 59354 Signal 15: exiting Feb 14 12:30:54 upsd 59480 listening on 127.0.0.1 port 3493 Feb 14 12:30:54 upsd 59480 listening on ::1 port 3493 Feb 14 12:30:54 upsd 59480 listening on 192.168.x.1 port 3493 Feb 14 12:30:54 upsd 59480 listening on 10.x.x.1 port 3493 Feb 14 12:30:54 upsd 59480 Can't connect to UPS [asustor] (usbhid-ups-asustor): No such file or directory Feb 14 12:30:54 upsd 59480 Found 1 UPS defined in ups.conf Feb 14 12:30:54 upsd 60478 Startup successful Feb 14 12:30:55 upsmon 83342 Startup successful Feb 14 12:30:55 upsd 60478 User local-monitor@127.0.0.1 logged into UPS [asustor] Feb 14 12:30:55 upsmon 83669 Poll UPS [asustor] failed - Driver not connected Feb 14 12:30:55 upsmon 83669 Communications with UPS asustor lost Feb 14 12:30:57 upsd 5973 listening on 127.0.0.1 port 3493 Feb 14 12:30:57 upsd 5973 listening on ::1 port 3493 Feb 14 12:30:57 upsd 5973 listening on 192.168.x.1 port 3493 Feb 14 12:30:57 upsd 5973 listening on 10.x.x.1 port 3493 Feb 14 12:30:57 upsd 5973 Can't connect to UPS [asustor] (usbhid-ups-asustor): No such file or directory Feb 14 12:30:57 upsd 5973 Found 1 UPS defined in ups.conf Feb 14 12:30:57 upsd 6118 Startup successful Feb 14 12:30:58 upsmon 11030 Startup successful Feb 14 12:30:58 upsd 6118 User local-monitor@127.0.0.1 logged into UPS [asustor] Feb 14 12:30:58 upsmon 11214 Poll UPS [asustor] failed - Driver not connected Feb 14 12:30:58 upsmon 11214 Communications with UPS asustor lost Feb 14 12:31:03 upsmon 11214 Poll UPS [asustor] failed - Driver not connected Feb 14 12:31:03 upsmon 11214 UPS asustor is unavailable Feb 14 12:31:08 upsmon 11214 Poll UPS [asustor] failed - Driver not connected Feb 14 12:31:09 usbhid-ups 22013 Startup successful Feb 14 12:31:09 upsd 6118 Connected to UPS [asustor]: usbhid-ups-asustor Feb 14 12:31:09 upsmon 11214 Signal 15: exiting Feb 14 12:31:09 upsd 6118 User local-monitor@127.0.0.1 logged out from UPS [asustor] Feb 14 12:31:09 upsd 6118 mainloop: Interrupted system call Feb 14 12:31:09 upsd 6118 Signal 15: exiting Feb 14 12:31:09 usbhid-ups 22013 Signal 15: exiting Feb 14 12:31:09 upsd 28649 listening on 127.0.0.1 port 3493 Feb 14 12:31:09 upsd 28649 listening on ::1 port 3493 Feb 14 12:31:09 upsd 28649 listening on 192.168.x.1 port 3493 Feb 14 12:31:09 upsd 28649 listening on 10.x.x.1 port 3493 Feb 14 12:31:09 upsd 28649 Can't connect to UPS [asustor] (usbhid-ups-asustor): No such file or directory Feb 14 12:31:09 upsd 28649 Found 1 UPS defined in ups.conf Feb 14 12:31:09 upsd 28778 Startup successful Feb 14 12:31:10 upsmon 39526 Startup successful Feb 14 12:31:10 upsd 28778 User local-monitor@127.0.0.1 logged into UPS [asustor] Feb 14 12:31:10 upsmon 39743 Poll UPS [asustor] failed - Driver not connected Feb 14 12:31:10 upsmon 39743 Communications with UPS asustor lost Feb 14 12:31:11 usbhid-ups 70270 Startup successful Feb 14 12:31:12 upsd 28778 Connected to UPS [asustor]: usbhid-ups-asustor Feb 14 12:31:12 upsd 76065 listening on 127.0.0.1 port 3493 Feb 14 12:31:12 upsd 76065 listening on ::1 port 3493 Feb 14 12:31:12 upsd 76065 listening on 192.168.x.1 port 3493 Feb 14 12:31:12 upsd 76065 listening on 10.x.x.1 port 3493 Feb 14 12:31:12 upsd 76065 Can't connect to UPS [asustor] (usbhid-ups-asustor): Connection refused Feb 14 12:31:12 upsd 76065 Found 1 UPS defined in ups.conf Feb 14 12:31:12 upsd 76434 Startup successful Feb 14 12:31:13 upsmon 80839 Startup successful Feb 14 12:31:13 upsd 76434 User local-monitor@127.0.0.1 logged into UPS [asustor] Feb 14 12:31:13 upsmon 81172 Poll UPS [asustor] failed - Driver not connected Feb 14 12:31:13 upsmon 81172 Communications with UPS asustor lost Feb 14 12:31:14 usbhid-ups 85849 Startup successful Feb 14 12:31:14 upsd 76434 Connected to UPS [asustor]: usbhid-ups-asustor Feb 14 12:31:18 upsmon 81172 Communications with UPS asustor established Feb 14 12:34:55 upsmon 81172 Signal 15: exiting Feb 14 12:34:55 upsd 76434 User local-monitor@127.0.0.1 logged out from UPS [asustor] Feb 14 12:34:55 upsd 76434 mainloop: Interrupted system call Feb 14 12:34:55 upsd 76434 Signal 15: exiting Feb 14 12:34:55 upsd 19955 listening on 127.0.0.1 port 3493 Feb 14 12:34:55 upsd 19955 listening on ::1 port 3493 Feb 14 12:34:55 upsd 19955 listening on 192.168.x.1 port 3493 Feb 14 12:34:55 upsd 19955 listening on 10.x.x.1 port 3493 Feb 14 12:34:55 upsd 19955 Connected to UPS [asustor]: usbhid-ups-asustor Feb 14 12:34:55 upsd 19955 Found 1 UPS defined in ups.conf Feb 14 12:34:55 upsd 21038 Startup successful Feb 14 12:34:55 upsd 21038 Can't connect to UPS [asustor] (usbhid-ups-asustor): Connection refused Feb 14 12:34:56 upsmon 27436 Startup successful Feb 14 12:34:56 upsd 21038 User local-monitor@127.0.0.1 logged into UPS [asustor] Feb 14 12:34:56 upsmon 27469 Poll UPS [asustor] failed - Driver not connected Feb 14 12:34:56 upsmon 27469 Communications with UPS asustor lost Feb 14 12:34:58 upsd 44878 listening on 127.0.0.1 port 3493 Feb 14 12:34:58 upsd 44878 listening on ::1 port 3493 Feb 14 12:34:58 upsd 44878 listening on 192.168.x.1 port 3493 Feb 14 12:34:58 upsd 44878 listening on 10.x.x.1 port 3493 Feb 14 12:34:58 upsd 44878 Can't connect to UPS [asustor] (usbhid-ups-asustor): Connection refused Feb 14 12:34:58 upsd 44878 Found 1 UPS defined in ups.conf Feb 14 12:34:58 upsd 46248 Startup successful Feb 14 12:34:59 upsmon 77936 Startup successful Feb 14 12:34:59 upsd 46248 User local-monitor@127.0.0.1 logged into UPS [asustor] Feb 14 12:34:59 upsmon 77986 Poll UPS [asustor] failed - Driver not connected Feb 14 12:34:59 upsmon 77986 Communications with UPS asustor lost Feb 14 12:35:04 upsmon 77986 Poll UPS [asustor] failed - Driver not connected Feb 14 12:35:04 upsmon 77986 UPS asustor is unavailable Feb 14 12:35:05 usbhid-ups 2764 Startup successful Feb 14 12:35:06 upsd 46248 Connected to UPS [asustor]: usbhid-ups-asustor Feb 14 12:35:09 upsmon 77986 Communications with UPS asustor established Feb 14 12:35:12 upsmon 77986 Signal 15: exiting Feb 14 12:35:12 upsd 46248 User local-monitor@127.0.0.1 logged out from UPS [asustor] Feb 14 12:35:12 upsd 46248 mainloop: Interrupted system call Feb 14 12:35:12 upsd 46248 Signal 15: exiting Feb 14 12:35:12 usbhid-ups 2764 Signal 15: exiting Feb 14 12:35:12 upsd 87683 listening on 127.0.0.1 port 3493 Feb 14 12:35:12 upsd 87683 listening on ::1 port 3493 Feb 14 12:35:12 upsd 87683 listening on 192.168.x.1 port 3493 Feb 14 12:35:12 upsd 87683 listening on 10.x.x.1 port 3493 Feb 14 12:35:12 upsd 87683 Can't connect to UPS [asustor] (usbhid-ups-asustor): No such file or directory Feb 14 12:35:12 upsd 87683 Found 1 UPS defined in ups.conf Feb 14 12:35:12 upsd 88747 Startup successful Feb 14 12:35:13 upsmon 95512 Startup successful Feb 14 12:35:13 upsd 88747 User local-monitor@127.0.0.1 logged into UPS [asustor] Feb 14 12:35:13 upsmon 95709 Poll UPS [asustor] failed - Driver not connected Feb 14 12:35:13 upsmon 95709 Communications with UPS asustor lost Feb 14 12:35:15 upsd 10318 listening on 127.0.0.1 port 3493 Feb 14 12:35:15 upsd 10318 listening on ::1 port 3493 Feb 14 12:35:15 upsd 10318 listening on 192.168.x.1 port 3493 Feb 14 12:35:15 upsd 10318 listening on 10.x.x.1 port 3493 Feb 14 12:35:15 upsd 10318 Can't connect to UPS [asustor] (usbhid-ups-asustor): No such file or directory Feb 14 12:35:15 upsd 10318 Found 1 UPS defined in ups.conf Feb 14 12:35:15 upsd 10692 Startup successful Feb 14 12:35:16 upsmon 18330 Startup successful Feb 14 12:35:16 upsd 10692 User local-monitor@127.0.0.1 logged into UPS [asustor] Feb 14 12:35:16 upsmon 18582 Poll UPS [asustor] failed - Driver not connected Feb 14 12:35:16 upsmon 18582 Communications with UPS asustor lost Feb 14 12:35:21 upsmon 18582 Poll UPS [asustor] failed - Driver not connected Feb 14 12:35:21 upsmon 18582 UPS asustor is unavailable Feb 14 12:35:26 upsmon 18582 Poll UPS [asustor] failed - Driver not connected Feb 14 12:35:31 upsmon 18582 Poll UPS [asustor] failed - Driver not connected Feb 14 12:35:36 upsmon 18582 Poll UPS [asustor] failed - Driver not connected Feb 14 12:35:41 upsmon 18582 Poll UPS [asustor] failed - Driver not connected Feb 14 12:35:47 upsmon 18582 Poll UPS [asustor] failed - Driver not connected Feb 14 12:35:52 upsmon 18582 Poll UPS [asustor] failed - Driver not connected Feb 14 12:35:57 upsmon 18582 Poll UPS [asustor] failed - Driver not connected Feb 14 12:36:02 upsmon 18582 Poll UPS [asustor] failed - Driver not connected Feb 14 12:36:07 upsmon 18582 Poll UPS [asustor] failed - Driver not connected Feb 14 12:36:12 upsmon 18582 Poll UPS [asustor] failed - Driver not connected Feb 14 12:36:17 upsmon 18582 Poll UPS [asustor] failed - Driver not connected Feb 14 12:36:22 upsmon 18582 Poll UPS [asustor] failed - Driver not connected Feb 14 12:36:27 upsmon 18582 Poll UPS [asustor] failed - Driver not connected Feb 14 12:36:32 upsmon 18582 Poll UPS [asustor] failed - Driver not connected Feb 14 12:36:37 upsmon 18582 Poll UPS [asustor] failed - Driver not connected Feb 14 12:36:42 upsmon 18582 Poll UPS [asustor] failed - Driver not connected Feb 14 12:36:47 upsmon 18582 Poll UPS [asustor] failed - Driver not connected Feb 14 12:36:52 upsmon 18582 Poll UPS [asustor] failed - Driver not connected Feb 14 12:36:57 upsmon 18582 Poll UPS [asustor] failed - Driver not connected Feb 14 12:37:02 upsmon 18582 Poll UPS [asustor] failed - Driver not connected Feb 14 12:37:07 upsmon 18582 Poll UPS [asustor] failed - Driver not connected Feb 14 12:37:12 upsmon 18582 Poll UPS [asustor] failed - Driver not connected Feb 14 12:37:17 upsmon 18582 Poll UPS [asustor] failed - Driver not connected Feb 14 12:37:22 upsmon 18582 Poll UPS [asustor] failed - Driver not connected Feb 14 12:37:28 upsmon 18582 Poll UPS [asustor] failed - Driver not connected Feb 14 12:37:33 upsmon 18582 Poll UPS [asustor] failed - Driver not connected Feb 14 12:37:38 upsmon 18582 Poll UPS [asustor] failed - Driver not connected Feb 14 12:37:43 upsmon 18582 Poll UPS [asustor] failed - Driver not connected Feb 14 12:37:48 upsmon 18582 Poll UPS [asustor] failed - Driver not connected Feb 14 12:37:53 upsmon 18582 Poll UPS [asustor] failed - Driver not connected Feb 14 12:37:58 upsmon 18582 Poll UPS [asustor] failed - Driver not connected Feb 14 12:38:03 upsmon 18582 Poll UPS [asustor] failed - Driver not connected Feb 14 12:38:08 upsmon 18582 Poll UPS [asustor] failed - Driver not connected Feb 14 12:38:13 upsmon 18582 Poll UPS [asustor] failed - Driver not connected Feb 14 12:38:18 upsmon 18582 Poll UPS [asustor] failed - Driver not connected Feb 14 12:38:23 upsmon 18582 Poll UPS [asustor] failed - Driver not connected Feb 14 12:38:28 upsmon 18582 Poll UPS [asustor] failed - Driver not connected Feb 14 12:38:33 upsmon 18582 Poll UPS [asustor] failed - Driver not connected Feb 14 12:38:38 upsmon 18582 Poll UPS [asustor] failed - Driver not connected Feb 14 12:38:43 upsmon 18582 Poll UPS [asustor] failed - Driver not connected Feb 14 12:38:49 upsmon 18582 Poll UPS [asustor] failed - Driver not connected Feb 14 12:38:53 upsmon 18582 Signal 15: exiting Feb 14 12:38:53 upsd 10692 User local-monitor@127.0.0.1 logged out from UPS [asustor] Feb 14 12:38:53 upsd 10692 mainloop: Interrupted system call Feb 14 12:38:53 upsd 10692 Signal 15: exiting Feb 14 12:38:53 upsd 44381 listening on 127.0.0.1 port 3493 Feb 14 12:38:53 upsd 44381 listening on ::1 port 3493 Feb 14 12:38:53 upsd 44381 listening on 192.168.x.1 port 3493 Feb 14 12:38:53 upsd 44381 listening on 10.x.x.1 port 3493 Feb 14 12:38:53 upsd 44381 Can't connect to UPS [asustor] (usbhid-ups-asustor): No such file or directory Feb 14 12:38:53 upsd 44381 Found 1 UPS defined in ups.conf Feb 14 12:38:53 upsd 45560 Startup successful Feb 14 12:38:54 upsmon 50001 Startup successful Feb 14 12:38:54 upsd 45560 User local-monitor@127.0.0.1 logged into UPS [asustor] Feb 14 12:38:54 upsmon 50095 Poll UPS [asustor] failed - Driver not connected Feb 14 12:38:54 upsmon 50095 Communications with UPS asustor lost Feb 14 12:38:56 upsd 66496 listening on 127.0.0.1 port 3493 Feb 14 12:38:56 upsd 66496 listening on ::1 port 3493 Feb 14 12:38:56 upsd 66496 listening on 192.168.x.1 port 3493 Feb 14 12:38:56 upsd 66496 listening on 10.x.x.1 port 3493 Feb 14 12:38:56 upsd 66496 Can't connect to UPS [asustor] (usbhid-ups-asustor): No such file or directory Feb 14 12:38:56 upsd 66496 Found 1 UPS defined in ups.conf Feb 14 12:38:56 upsd 67052 Startup successful Feb 14 12:38:57 upsmon 68081 Startup successful Feb 14 12:38:57 upsd 67052 User local-monitor@127.0.0.1 logged into UPS [asustor] Feb 14 12:38:57 upsmon 68189 Poll UPS [asustor] failed - Driver not connected Feb 14 12:38:57 upsmon 68189 Communications with UPS asustor lost Feb 14 12:39:02 upsmon 68189 Poll UPS [asustor] failed - Driver not connected Feb 14 12:39:02 upsmon 68189 UPS asustor is unavailable Feb 14 12:39:07 upsmon 68189 Poll UPS [asustor] failed - Driver not connected 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 -
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.
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.