UPS monitor not starting up

[Tony Self]

I have a Cleanline model D-1000HD UPS connected to my HP Microserver Gen8. FreeNAS is recognising the port I am plugging the USB cable into and I have configured the UPS service appropriately, but when I try to start the service I get the following error.

I am not sure where to go from here. Is there a log that will give more information?


Sent from my iPad using Tapatalk

 

[dlavigne]

Which build version of FreeNAS (from System -> Information)? Anything related in /var/log/messages?

 

[Mr_N]

need to try other drivers until you find one that works :)

 

[Tony Self]

Which build version of FreeNAS (from System -> Information)? Anything related in /var/log/messages?

Sorry, forgot to include that. I am on FreeNAS-9.10.2-U2.

 

[Tony Self]

I have started making progress, but still have problems.

i discovered that the "blazer_usb" appeared to work and after starting the UPS service everything seemed fine for a while. I got messages saying the ups was online and if i unplugged the ups i got a message saying on battery. Plug the power back in and i get the online message. I even managed to test a power down successfully.

The trouble is after about 5 minutes i get the following messages

"freenas upsmon[15941]: Poll UPS [cleanline] failed - Driver not connected"

these are repeating every 5 secs.

I followed another thread on this topic, which suggested the usb cable might be faulty. I have now tried three separate cables. When I reconnected a cable i got this error

"Can't connect to UPS [cleanline] (blazer_usb-cleanline): No such file or directory"

cleanline is the make of UPS and the name I assigned to the ups service.

This looks like it could be a permission problem, but I don't know what file or directory it is talking about. I have set the user in the ups service to be root, to try and avoid permission problems.

I am not quite sure what to try next. I am prepared to go and buy a another UPS if necessary (APC this time), but I don't want to spend more money and find I still have similar problem.

I need to get this fixed in the next week as I will be leaving the server running on its own for over a month and I want to make sure it will power down gracefully when there are power cuts.

Any suggestions will be gratefully received

 

[Tony Self]

Well, I just tried another restart of the UPS Service and it stayed up and running for 20 mins now with no errors. It must have been a permission problem. I was sure I had restarted the service since I updated the user to root, but perhaps not.

Anyway, so far so good

 

[Tony Self]

But it only lasted for another 5 minutes before it lost the connection and the "Poll UPS" started appearing again.

So, again I am asking for help please.

 

[Tony Self]

Here is a section of the log showing from where I restarted the UPS up to the time that it lost communication again. As you can see it lasted less than 5 minutes this time.

Apr 7 16:26:49 freenas notifier: Starting nut_upsmon.
Apr 7 16:26:49 freenas notifier: kill: No such process
Apr 7 16:26:49 freenas notifier: UPS: cleanline (master) (power value 1)
Apr 7 16:26:49 freenas notifier: Using power down flag file /etc/nokillpower
Apr 7 16:26:49 freenas notifier: Starting nut_upslog.
Apr 7 16:31:21 freenas blazer_usb[26723]: Permissions problem: Input/output error
Apr 7 16:31:21 freenas upsd[26725]: Can't connect to UPS [cleanline] (blazer_usb-cleanline): No such file or directory
Apr 7 16:31:25 freenas upsmon[26740]: Poll UPS [cleanline] failed - Driver not connected
Apr 7 16:31:25 freenas upsmon[26740]: Communications with UPS cleanline lost
Apr 7 16:31:30 freenas upsmon[26740]: Poll UPS [cleanline] failed - Driver not connected

 

[Mr_N]

the login for the my ups service is as follows...

user:upsmon
password:master

this may vary but it def wont be root , if you can issue the command:

upsc cleanline

from the shell and get the output from UPS then you know the user/pass is working...

 

[Tony Self]

the login for the my ups service is as follows...

user:upsmon
password:master

this may vary but it def wont be root , if you can issue the command:

upsc cleanline

from the shell and get the output from UPS then you know the user/pass is working...

Thanks Mr_N
I have tried that from the shell after restarting the service and I got the following: -

[root@freenas] ~# upsc cleanline
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/ugen0.5
driver.parameter.synchronous: no
driver.version: 2.7.3
driver.version.internal: 0.11
input.current.nominal: 2.0
input.frequency: 50.1
input.frequency.nominal: 50
input.voltage: 224.4
input.voltage.fault: 224.4
input.voltage.nominal: 220
output.voltage: 224.4
ups.beeper.status: enabled
ups.delay.shutdown: 30
ups.delay.start: 180
ups.load: 24
ups.productid: 5161
ups.status: OL
ups.type: offline / line interactive
ups.vendorid: 0665


But again after a short while the driver has disconnected again and I now only get : -


Error: Driver not connected


For some reason the driver is not holding connection to the UPS hardware. There also does not appear to be any consistency over the time it takes to lose its connection. This time it was less than a minute. But yesterday it did manage to stay connected for 25 minutes one time.

Is there anything in the initial information listed that will give some idea why it is dropping the connection?

 

[Tony Self]

Well I couldn't resolve the connection issue with the Cleanline UPS, so today I purchased an APC BX950U Backup UPS. As soon as I connected this new UPS it has been behaving perfectly. No connection problems and I have already performed a test shutdown.

So for the time being I will close this thread. I will perhaps try and get the Cleanline working later in the year when I plan to setup Corral on my old HP Microserver.