APC BR1500G UPS - How do I get it working?

[RichTJ99]

Hi,

I have a BR1500G APC UPS (http://www.amazon.com/dp/B003Y24DEU/?tag=ozlp-20) I have the it connected by the USB to Catx cable that comes with the unit. I hit the services, UPS to turn it on & get this message:

Any idea how to get this working?

Thanks,
Rich

Code:

Jan 21 15:54:17 freenas notifier: Can't start /usr/local/libexec/nut/(null): No such file or directory
Jan 21 15:54:17 freenas notifier: Network UPS Tools - UPS driver controller 2.7.3
Jan 21 15:54:17 freenas root: /usr/local/etc/rc.d/nut: WARNING: failed precmd routine for nut
Jan 21 15:54:17 freenas notifier: /usr/local/etc/rc.d/nut: WARNING: failed precmd routine for nut
Jan 21 15:54:17 freenas notifier: Starting nut_upsmon.
Jan 21 15:54:17 freenas notifier: kill: No such process
Jan 21 15:54:17 freenas notifier: UPS: ups (master) (power value 1)
Jan 21 15:54:17 freenas notifier: Using power down flag file /etc/nokillpower
Jan 21 15:54:17 freenas upsmon[8871]: UPS [ups]: connect failed: Connection failure: Connection refused
Jan 21 15:54:17 freenas upsmon[8871]: Communications with UPS ups lost
Jan 21 15:54:17 freenas notifier: Starting nut_upslog.
Jan 21 15:54:18 freenas notifier: Warning: initial connect failed: Connection failure: Connection refused
Jan 21 15:54:19 freenas notifier: Stopping nut_upslog.
Jan 21 15:54:19 freenas notifier: Waiting for PIDS: 8884.
Jan 21 15:54:19 freenas notifier: Stopping nut_upsmon.
Jan 21 15:54:43 freenas upsmon[8862]: upsmon parent: read
Jan 21 15:54:43 freenas notifier: Waiting for PIDS: 8871, 8871, 8871, 8871, 8871, 8871, 8871, 8871, 8871, 8871, 8871, 8871, 8871, 8871, 8871, 8871, 8871, 8871, 8871, 8871, 8871, 8871, 8871, 8871, 8871.
Jan 21 15:54:43 freenas notifier: nut not running? (check /var/db/nut/upsd.pid).
Jan 21 16:00:05 freenas autosnap.py: [tools.autosnap:71] Popen()ing: /sbin/zfs snapshot -r "Pool@auto-20160121.1600-2w"
Jan 21 16:00:05 freenas autosnap.py: [tools.autosnap:71] Popen()ing: /sbin/zfs snapshot -r "FNPool@auto-20160121.1600-2w"
Jan 21 16:08:09 freenas notifier: nut not running? (check /var/db/nut/upsd.pid).
Jan 21 16:08:09 freenas notifier: nut_upsmon not running? (check /var/db/nut/upsmon.pid).
Jan 21 16:08:09 freenas notifier: nut_upslog not running? (check /var/db/nut/upslog.pid).
Jan 21 16:08:09 freenas notifier: Will not 'restart' nut because nut_enable is NO.
Jan 21 16:08:09 freenas notifier: Will not 'restart' nut_upsmon because nut_upsmon_enable is NO.
Jan 21 16:08:09 freenas notifier: Will not 'restart' nut_upslog because nut_upslog_enable is NO.
Jan 21 16:08:28 freenas notifier: tcgetattr(/dev/ugen0.3): Inappropriate ioctl for device
Jan 21 16:08:28 freenas notifier: Network UPS Tools - APC Smart protocol driver 3.1 (2.7.3)
Jan 21 16:08:28 freenas notifier: APC command table version 3.1
Jan 21 16:08:28 freenas notifier: Driver failed to start (exit status=1)
Jan 21 16:08:28 freenas notifier: Network UPS Tools - UPS driver controller 2.7.3
Jan 21 16:08:28 freenas root: /usr/local/etc/rc.d/nut: WARNING: failed precmd routine for nut
Jan 21 16:08:28 freenas notifier: /usr/local/etc/rc.d/nut: WARNING: failed precmd routine for nut
Jan 21 16:08:28 freenas notifier: Starting nut_upsmon.
Jan 21 16:08:28 freenas notifier: kill: No such process
Jan 21 16:08:28 freenas notifier: UPS: ups (master) (power value 1)
Jan 21 16:08:28 freenas notifier: Using power down flag file /etc/nokillpower
Jan 21 16:08:28 freenas upsmon[13205]: UPS [ups]: connect failed: Connection failure: Connection refused
Jan 21 16:08:28 freenas upsmon[13205]: Communications with UPS ups lost
Jan 21 16:08:28 freenas notifier: Starting nut_upslog.
Jan 21 16:08:28 freenas notifier: Warning: initial connect failed: Connection failure: Connection refused
Jan 21 16:08:33 freenas upsmon[13205]: UPS [ups]: connect failed: Connection failure: Connection refused
Jan 21 16:08:33 freenas upsmon[13205]: UPS ups is unavailable
Jan 21 16:08:35 freenas notifier: Stopping nut_upslog.
Jan 21 16:08:35 freenas notifier: Waiting for PIDS: 13227.
Jan 21 16:08:35 freenas notifier: Stopping nut_upsmon.
Jan 21 16:08:53 freenas upsmon[13204]: upsmon parent: read
Jan 21 16:08:54 freenas notifier: Waiting for PIDS: 13205, 13205, 13205, 13205, 13205, 13205, 13205, 13205, 13205, 13205, 13205, 13205, 13205, 13205, 13205, 13205, 13205, 13205, 13205, 13205.
Jan 21 16:08:54 freenas notifier: nut not running? (check /var/db/nut/upsd.pid).
Jan 21 16:11:08 freenas notifier: nut not running? (check /var/db/nut/upsd.pid).
Jan 21 16:11:08 freenas notifier: nut_upsmon not running? (check /var/db/nut/upsmon.pid).
Jan 21 16:11:08 freenas notifier: nut_upslog not running? (check /var/db/nut/upslog.pid).
Jan 21 16:11:08 freenas notifier: Will not 'restart' nut because nut_enable is NO.
Jan 21 16:11:08 freenas notifier: Will not 'restart' nut_upsmon because nut_upsmon_enable is NO.
Jan 21 16:11:08 freenas notifier: Will not 'restart' nut_upslog because nut_upslog_enable is NO.

 

[BigDave]

Try using a different driver, there's about 5 or 6 different ones for APC

upshid-ups is the genic driver that seems to work for alot of people.

 

[DrKK]

Stupid question: did you set the correct USB port? This is exactly the message you'll get if you've tied the service to the wrong USB port number.

Also, as BigDave says, usbhid-ups has a 92% of being the correct driver for this model with this setup. As long as you choose any make/model that uses usbhid, that is more than likely correct.

 

[RichTJ99]

I just tried to start the service without doing anything else :(

How do i find the port for the usb/ups?

 

[RichTJ99]

I dont see it listed:

Code:

[root@freenas] ~# usbconfig
ugen0.1: <EHCI root HUB Intel> at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=S                                                                             AVE (0mA)
ugen1.1: <EHCI root HUB Intel> at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=S                                                                             AVE (0mA)
ugen0.2: <product 0x8008 vendor 0x8087> at usbus0, cfg=0 md=HOST spd=HIGH (480Mb                                                                             ps) pwr=SAVE (0mA)
ugen1.2: <product 0x8000 vendor 0x8087> at usbus1, cfg=0 md=HOST spd=HIGH (480Mb                                                                             ps) pwr=SAVE (0mA)
ugen0.3: <product 0x7000 vendor 0x0557> at usbus0, cfg=0 md=HOST spd=HIGH (480Mb                                                                             ps) pwr=SAVE (100mA)
ugen0.4: <product 0x2419 vendor 0x0557> at usbus0, cfg=0 md=HOST spd=LOW (1.5Mbp                                                                             s) pwr=ON (160mA)
ugen1.3: <Cruzer Fit SanDisk> at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON                                                                              (200mA)
ugen1.4: <Cruzer Fit SanDisk> at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON                                                                              (200mA)
ugen1.5: <Dell USB Keyboard Dell> at usbus1, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr                                                                             =ON (70mA)

 

[DrKK]

interesting.

Well, the "right" way to find out what port it's in: be on the console menu, and then plug in the USB to the UPS and then unplug it, etc. Immediately, you should see devd throw a notice up on the console that a device has been plugged in, together with this port identifier (e.g., ugen0.4 or whatever). If no notice is thrown up, then, I would say, you have a bum USB cable.

 

[RichTJ99]

Hi,

Ok it turns out (I have two identical APC 1500's) that the unit that was 'refurbished' by APC has a bad data port. I tried the same cable in my other APC 1500 & it works.

I set the page for /dev/ugen1.6 & used various drivers. Now my shell console on the bottom of the page is frozen since 9am.

Is the method to hook up the UPS to just try until it works?

Thanks,
Rich

Code:

Jan 22 08:45:33 freenas ugen1.6: <American Power Conversion> at usbus1
Jan 22 08:48:16 freenas notifier: nut not running? (check /var/db/nut/upsd.pid).
Jan 22 08:48:16 freenas notifier: nut_upsmon not running? (check /var/db/nut/upsmon.pid).
Jan 22 08:48:16 freenas notifier: nut_upslog not running? (check /var/db/nut/upslog.pid).
Jan 22 08:48:16 freenas notifier: Will not 'restart' nut because nut_enable is NO.
Jan 22 08:48:16 freenas notifier: Will not 'restart' nut_upsmon because nut_upsmon_enable is NO.
Jan 22 08:48:16 freenas notifier: Will not 'restart' nut_upslog because nut_upslog_enable is NO.
Jan 22 08:48:53 freenas notifier: nut not running? (check /var/db/nut/upsd.pid).
Jan 22 08:48:53 freenas notifier: nut_upsmon not running? (check /var/db/nut/upsmon.pid).
Jan 22 08:48:53 freenas notifier: nut_upslog not running? (check /var/db/nut/upslog.pid).
Jan 22 08:48:53 freenas notifier: Will not 'restart' nut because nut_enable is NO.
Jan 22 08:48:53 freenas notifier: Will not 'restart' nut_upsmon because nut_upsmon_enable is NO.
Jan 22 08:48:53 freenas notifier: Will not 'restart' nut_upslog because nut_upslog_enable is NO.
Jan 22 08:49:48 freenas notifier: nut not running? (check /var/db/nut/upsd.pid).
Jan 22 08:49:48 freenas notifier: nut_upsmon not running? (check /var/db/nut/upsmon.pid).
Jan 22 08:49:48 freenas notifier: nut_upslog not running? (check /var/db/nut/upslog.pid).
Jan 22 08:49:48 freenas notifier: Will not 'restart' nut because nut_enable is NO.
Jan 22 08:49:48 freenas notifier: Will not 'restart' nut_upsmon because nut_upsmon_enable is NO.
Jan 22 08:49:48 freenas notifier: Will not 'restart' nut_upslog because nut_upslog_enable is NO.

 

[DrKK]

The messages about nut_upslog_enable being "NO" means that the services->UPS is not clicked to "ON".

When it's working, you should have a ups.log in /var/log/, and it should look something like this:

Code:

20160122 133237 100 124.0 9 [OL] NA NA
20160122 133737 100 124.0 9 [OL] NA NA
20160122 134237 100 124.0 9 [OL] NA NA
20160122 134737 100 123.0 9 [OL] NA NA
20160122 135237 100 123.0 9 [OL] NA NA
20160122 135737 100 123.0 9 [OL] NA NA
20160122 140237 100 123.0 9 [OL] NA NA
20160122 140737 100 123.0 9 [OL] NA NA
20160122 141237 100 124.0 9 [OL] NA NA
20160122 141737 100 124.0 9 [OL] NA NA
20160122 142237 100 123.0 9 [OL] NA NA
20160122 142737 100 123.0 9 [OL] NA NA

Where you will have more or less "NA"'s depending on whether or not your model does, or does not, support various features/reporting.