UPS Configuration - Service won't start?

[cobalt]

I am trying to get the UPS service running. My UPS worked great with Freenas 7, so I would think my APC back ups es 725 should still be supported.

I am running 8.2-r8971-amd64. IS there a guide to go by to get this service working?


When I try to turn on the UPS service, I get the following:

Dec 11 12:28:05 bilnas notifier[1981]: Executing: /usr/sbin/service ix-ups quietstart
Dec 11 12:28:05 bilnas notifier[1981]: Executing: /usr/sbin/service nut restart
Dec 11 12:28:05 bilnas notifier: nut not running? (check /var/db/nut/upsd.pid).
Dec 11 12:28:06 bilnas notifier: Network UPS Tools - Generic HID driver 0.35 (2.6.1)
Dec 11 12:28:06 bilnas notifier: USB communication driver 0.31
Dec 11 12:28:06 bilnas notifier: No matching HID UPS found
Dec 11 12:28:06 bilnas notifier: Driver failed to start (exit status=1)
Dec 11 12:28:06 bilnas notifier: Network UPS Tools - UPS driver controller 2.6.1
Dec 11 12:28:06 bilnas root: /usr/local/etc/rc.d/nut: WARNING: failed precmd routine for nut
Dec 11 12:28:06 bilnas notifier: /usr/local/etc/rc.d/nut: WARNING: failed precmd routine for nut
Dec 11 12:28:06 bilnas notifier[1981]: Executing: /usr/sbin/service nut_upsmon restart
Dec 11 12:28:06 bilnas notifier: nut_upsmon not running? (check /var/db/nut/upsmon.pid).
Dec 11 12:28:06 bilnas notifier: Starting nut_upsmon.
Dec 11 12:28:06 bilnas notifier: UPS: ups (master) (power value 1)
Dec 11 12:28:06 bilnas notifier[1981]: Executing: /usr/sbin/service nut_upslog restart
Dec 11 12:28:06 bilnas upsmon[6027]: UPS [ups]: connect failed: Connection failure: Connection refused
Dec 11 12:28:06 bilnas upsmon[6027]: Communications with UPS ups lost
Dec 11 12:28:06 bilnas notifier: nut_upslog not running? (check /var/db/nut/upslog.pid).
Dec 11 12:28:06 bilnas notifier: Starting nut_upslog.
Dec 11 12:28:06 bilnas notifier: Warning: initial connect failed: Connection failure: Connection refused
Dec 11 12:28:06 bilnas notifier[1981]: Executing: /bin/pgrep -F /var/db/nut/upsd.pid upsd
Dec 11 12:28:06 bilnas notifier[1981]: Executing: /usr/sbin/service nut_upslog stop
Dec 11 12:28:06 bilnas notifier: Stopping nut_upslog.
Dec 11 12:28:06 bilnas notifier[1981]: Executing: /usr/sbin/service nut_upsmon stop
Dec 11 12:28:07 bilnas notifier: Stopping nut_upsmon.
Dec 11 12:28:07 bilnas upsmon[6026]: upsmon parent: read
Dec 11 12:28:07 bilnas notifier[1981]: Executing: /usr/sbin/service nut stop
Dec 11 12:28:07 bilnas notifier: Will not 'stop' nut because nut_enable is NO.
Dec 11 12:28:07 bilnas notifier[1981]: Executing: /bin/pgrep -F /var/db/nut/upsd.pid upsd

 

[Milhouse]

Which USB port is your UPS using? It should be reported on the console or in dmesg (eg. /dev/ugen0.2) whenever you connect/disconnect it.

 

[cobalt]

Shutdown Loop

The good news - I was able to find a port and driver combination that recognized the UPS.

The bad news - Freenas is now stuck in a shutdown loop.

My setup is 8.2-r8971-amd64 running on VMware Fusion 4 on a Hakintosh. The port /dev/cuau1 and driver was set to genericups upstyle=12 was a setting that allowed the UPS service to be turned on. Unfortunately the connected and operational UPS or disconnected UPS cause Freenas to sense a shutdown condition.

I created a new virtual machine and loaded FreeNAS-8.0.3-BETA1-amd.iso. After the main configurations were adjusted, I tried a different port/driver configuration of port /dev/cuau0 and driver was set to APC Back-UPS Pro USB USB (usbhid-ups). This combination seems to work.

I am brand new to VMware, so this process is challenging to say the least. I had made some changes to the way the VM connects to the recognized UPS. So now I am trying to figure out what settings are the correct ones to have my original Freenas operational.

The first thing I need to accomplish with the original VM is to break the shutdown loop. I do not have enough time to stop it from the GUI, so I am hoping that I can do it from the shell on the machine that is running Freenas. What command will interrupt the UPS service?

Millhouse - to answer your question, when I unplug the UPS cable, ugen0.4 at usbus0 is what appears in the console of the Freenas machine.

 

[cobalt]

UPS issues

I was able to break the loop by logging on locally. I was able to get the services open in the GUI and turn off the UPS service.

There seems to be issues with the 8.2-r8971-amd64 build as related to UPS service. The 8.0.3-BETA version does a better job with UPS service.

The upsc UPS@localhost does not work with the 8.2-r8971-amd64 build, but does work with the .3 BETA. It lists the APC unit as it should.