NUT Package (2.8.1 and above)

rarlup

@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 start

And 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]

Gertjan

@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.

dennypage

@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.

dennypage

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.

Gertjan

@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 ^^

rarlup

@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 A

0 - lacp to switch B
1 - lacp to switch B
2 - not used
3 - not used

Checked the UPS logs and no new events. Guess that & fixed it.

rarlup

@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?

Gertjan

@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 ^^

rarlup

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

dennypage

@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.