Fortron UPS connection failure

[nidur]

Hi there,

Two questions about UPS I have not been able to find an answer to.

After buying my new Freenas setup setting up a UPS with it seemed logical, though we never seem to have shortages in Iceland it's better to be safe than sorry, so its for those 1 in a year or less occations.

I bought the Line Interactive 650 from FSP after checking on the UPS Drivers Freenas supports.
And I'm using the "FSP ups 2 EP650 USB (blazer_usb)"

1. Question
Is it normal that the NUT is not able to run upsd.pid is there something I need to setup.

Code:

Feb  8 22:50:50 freenas notifier: nut not running? (check /var/db/nut/upsd.pid).
Feb  8 22:50:50 freenas notifier: nut_upsmon not running? (check /var/db/nut/upsmon.pid).
Feb  8 22:50:50 freenas notifier: nut_upslog not running? (check /var/db/nut/upslog.pid).
Feb  8 22:50:50 freenas notifier: nut not running? (check /var/db/nut/upsd.pid).
Feb  8 22:50:50 freenas notifier: Supported UPS detected with mustek protocol
Feb  8 22:50:52 freenas notifier: Vendor information unavailable
Feb  8 22:50:52 freenas notifier: No values provided for battery high/low voltages in ups.conf
Feb  8 22:50:52 freenas notifier:
Feb  8 22:50:52 freenas notifier: Using 'guestimation' (low: 10.400000, high: 13.000000)!
Feb  8 22:50:52 freenas notifier: Battery runtime will not be calculated (runtimecal not set)
Feb  8 22:50:52 freenas notifier: Network UPS Tools - UPS driver controller 2.7.2
Feb  8 22:50:52 freenas notifier: Starting nut.
Feb  8 22:50:52 freenas notifier: fopen /var/db/nut/upsd.pid: No such file or directory
Feb  8 22:50:52 freenas notifier: listening on 127.0.0.1 port 3493
Feb  8 22:50:52 freenas notifier: Connected to UPS [FortronUSP]: blazer_usb-FortronUSP
Feb  8 22:50:52 freenas notifier: nut_upsmon not running? (check /var/db/nut/upsmon.pid).
Feb  8 22:50:52 freenas notifier: Starting nut_upsmon.
Feb  8 22:50:52 freenas notifier: kill: No such process
Feb  8 22:50:52 freenas notifier: UPS: FortronUSP (master) (power value 1)
Feb  8 22:50:52 freenas notifier: nut_upslog not running? (check /var/db/nut/upslog.pid).
Feb  8 22:50:52 freenas notifier: Starting nut_upslog.

2. Question
Driver looses connection randomly and needs to be reset.
I have tried 3 different cables, 2 of them shielded, same issue on all of them. Is this a driver issue, could I use a generic one for this UPS. Is this connected to the NUT not running correctly.

Code:

Feb  8 22:40:46 freenas blazer_usb[7738]: Permissions problem: Input/output error
Feb  8 22:40:46 freenas upsd[7740]: Can't connect to UPS [FortronUSP] (blazer_usb-FortronUSP): No such
file or directory
Feb  8 22:40:48 freenas upsmon[7765]: Poll UPS [FortronUSP] failed - Driver not connected
Feb  8 22:40:48 freenas upsmon[7765]: Communications with UPS FortronUSP lost
Feb  8 22:40:53 freenas upsmon[7765]: Poll UPS [FortronUSP] failed - Driver not connected
Feb  8 22:40:58 freenas upsmon[7765]: Poll UPS [FortronUSP] failed - Driver not connected
Feb  8 22:41:03 freenas upsmon[7765]: Poll UPS [FortronUSP] failed - Driver not connected
Feb  8 22:41:08 freenas upsmon[7765]: Poll UPS [FortronUSP] failed - Driver not connected
Feb  8 22:41:13 freenas upsmon[7765]: Poll UPS [FortronUSP] failed - Driver not connected
Feb  8 22:41:18 freenas upsmon[7765]: Poll UPS [FortronUSP] failed - Driver not connected

When I run upsc FortronUPS@localhost the reporting is working.

Code:

battery.charge: 100
battery.voltage: 13.70
battery.voltage.high: 13.00
battery.voltage.low: 10.40
battery.voltage.nominal: 12.0
device.type: ups
driver.name: blazer_usb
driver.parameter.pollinterval: 2
driver.parameter.port: /dev/ugen1.4
driver.version: 2.7.2
driver.version.internal: 0.11
input.current.nominal: 2.0
input.frequency: 50.1
input.frequency.nominal: 50
input.voltage: 232.8
input.voltage.fault: 232.8
input.voltage.nominal: 230
output.voltage: 232.8
ups.beeper.status: enabled
ups.delay.shutdown: 30
ups.delay.start: 180
ups.load: 8
ups.productid: 5161
ups.status: OL
ups.type: offline / line interactive
ups.vendorid: 0665

The port works as /dev/ugen1.4 and as auto but both lose connection.

I just started looking into UPS for Freenas so any suggestions are appreciated.

*I should add that the shutdown works correctly when the driver is connected

 

[dlavigne]

Which version of FreeNAS?

 

[nidur]

Freenas 9.3

 

[SweetAndLow]

looks like you are using the correct drive and for the port make sure you are using the one that your device is plugged into. I know with the usbhid-ups driver the port doesn't matter but with the blazer driver it might matter. You can always try starting NUT in debug mode manually but you are going to have to dig through nut doc's online to learn how. I would also think about filing a bug for this one since it looks like you are doing things correctly. You can try plugging things into a linux machine to make sure the ups is working properly.

 

[pschatz100]

Perhaps you have a hardware issue. You haven't provided any details, so it's impossible to offer much in the way of a suggestion.

Have you tried different USB ports?

 

[nidur]

My hardware is as follows:

Supermicro X10SL7-F
Intel Core i3 4150 3.5GHz
Crucial CT2KIT102472BD160B 16GB (2x 8GB)
USP Line Interactive 650 from FSP

Thank you for the suggestions I will look into other usb ports, and the NUT debug mode

 

[Squinchy]

Same issue here with the FSP 650 on a power edge 840 running 9.3

Have also tested on another freenas box i have with the same issue.

Must be a driver issue and not hardware

 

[Squinchy]

For some reason it seems to work when i add to the Auxiliary parameters box: pollinterval=10

 

[Squinchy]

Never mind, that stopped working

 

[DrKK]

Yeah, I have seen this issue for years on various UPS's. I am 99.1184% certain it is an issue with the nut daemon itself on FreeBSD, and that you're doing everything right.