FreeNAS upsmon: Poll UPS

[Redcoat]

Understood, but I wouldn't quit without trying it and without trying the other usb drivers besides blazer-usb...

Also, look here for a situation eerily similar to yours https://forums.freenas.org/index.php?threads/ups-headaches.38241/

I can't "help" more, I'm afraid.

 

[BerryPlay]

I restarted my Server and ran:

Code:

upsc PowerWalkerUPS@localhost

I get the following output:

Code:

battery.charge: 100
battery.voltage: 13.50
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/ugen0.5
driver.parameter.synchronous: no
driver.version: 2.7.4
driver.version.internal: 0.12
input.current.nominal: 2.0
input.frequency: 50.1
input.frequency.nominal: 50
input.voltage: 230.8
input.voltage.fault: 230.8
input.voltage.nominal: 230
output.voltage: 230.8
ups.beeper.status: enabled
ups.delay.shutdown: 30
ups.delay.start: 180
ups.load: 17
ups.productid: 5161
ups.status: OL
ups.type: offline / line interactive
ups.vendorid: 0665

And again, after a few minutes, i only get (running the same command):

Code:

Error: Driver not connected

Edit:
Ok, i tried to set the device to /dev/ugen0.1 and now I also get the output:

Code:

battery.charge: 100
battery.voltage: 13.50
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/ugen0.1
driver.parameter.synchronous: no
driver.version: 2.7.4
driver.version.internal: 0.12
input.current.nominal: 2.0
input.frequency: 50.1
input.frequency.nominal: 50
input.voltage: 230.8
input.voltage.fault: 230.8
input.voltage.nominal: 230
output.voltage: 230.8
ups.beeper.status: enabled
ups.delay.shutdown: 30
ups.delay.start: 180
ups.load: 17
ups.productid: 5161
ups.status: OL
ups.type: offline / line interactive
ups.vendorid: 0665

And after a while...the same trouble.

 

[Redcoat]

My last suggestion: Did you study the information at http://networkupstools.org/docs/man/ups.conf.html in conjunction with the above list? Maybe you'll see something else to try.
Good luck!

 

[BerryPlay]

My last suggestion: Did you study the information at http://networkupstools.org/docs/man/ups.conf.html in conjunction with the above list? Maybe you'll see something else to try.
Good luck!

I read the page but doesn't really get any useful informations from it.

I activated the console messages on the FreeNAS Dashboard (funnily enough they are more detailed than the output on the FreeNAS console directly) and got the following messages:

It says, that it failed to start nut_upsmon.

 

[BerryPlay]

Ok, there is a new cognizance. I tried the UPS on a different Server and...it works. So it's neither an error with the UPS nor with the driver. Has anyone a clue, what the problem could be? A USB incompatibility?

 

[unseen]

I have a PowerWalker (under a different name) UPS on my FreeNAS.

It uses the blazer_usb driver and like yours, would regularly experience this problem. After considerable digging, I found that this was due to a weakness in the blazer_usb driver.

What I did to fix it was to install the source code for the driver and make a small change in blazer_usb.c

Code:

	   case -EPERM:			/* Operation not permitted */
			   // fatal_with_errno(EXIT_FAILURE, "Permissions problem");
			   upsdebugx(1, "Permission problem. Retry");
			   break;

By commenting out the "fatal_with_errno" call, the driver just ignores the false error and happily continues. I have saved a copy of my updated driver so that I can replace it after installing any updates as they will overwrite the driver with the standard version.