UPS setup problems

[satyr]

I have an APC BR1000G that I've been trying to connect to my Freenas 9.3 server. Everything seemed to be okay as far as generating upsd reports (the system would yield correct outputs and I wasn't receiving email errors). However, one reboot of the server led to a string of problems that causes constant COMMBAD email reports and an inability for the server to recognize the UPS.

With regard to drivers and USB ports, I believe that is all setup correctly. I've tried two different drivers that many users have stated worked fine with this UPS (and since it worked at first, this all seems to be correct).

Here is a few outputs from commands that I know, and I included the current UPS config setup. Note that the driver that is attached to the usb port is not for the correct unit. I've tried resetting the USB driver and stopping/reloading the UPS driver--which did not help. I was hoping for a way to reset the UPS drivers to a new state, but am unsure if that's the correct procedure or how I would go about that. Any help would be appreciated.

 

[satyr]

The frequency of COMMBAD emails has increased drastically. 50+ each day. Not so much of a concern if the UPS will actually work if power fails...more of a concern if it won't work. Any tips?

 

[DrKK]

Something is wrong.

Have you done something in the command-line interface that you should have been doing in the GUI?

Turn the UPS service off in the GUI and turn it on again. What messages occur in the footer?

 

[anodos]

Have you tried swapping cables?

 

[satyr]

Something is wrong.

Have you done something in the command-line interface that you should have been doing in the GUI?

Turn the UPS service off in the GUI and turn it on again. What messages occur in the footer?

I haven't done anything in CLI aside from running usbconfig and upsd, only to identify if the driver is picking up the UPS or not.

When I turn off the UPS service: "upsmon[26321]: upsmon parent: read" "upsd[26305]: mainloop: interrupted system call"

When I turn on UPS service: nothing comes up at all. The service turns on but nothing displays in CLI to suggest it's turning on. UPSD returns "fatal error: a previous upsd instance is already running!"

 

[DrKK]

I haven't done anything in CLI aside from running usbconfig and upsd, only to identify if the driver is picking up the UPS or not.

When I turn off the UPS service: "upsmon[26321]: upsmon parent: read" "upsd[26305]: mainloop: interrupted system call"

When I turn on UPS service: nothing comes up at all. The service turns on but nothing displays in CLI to suggest it's turning on. UPSD returns "fatal error: a previous upsd instance is already running!"

sounds to me like the service is on.

What does /var/log/ups.log say about the situation? Does it appear to be recording some/most of its fields validly? Or no.

 

[satyr]

It's got 2300+ lines of:

20150803 201938 100 114.0 16 [OL] NA NA
20150803 202438 100 114.0 16 [OL] NA NA
20150803 202938 100 114.0 16 [OL] NA NA

 

[DrKK]

Actually, that's very good. That means your UPS is working and communicating, and your upsd service has been daemonized and is running correctly.

Those numbers are, respectively, date, time, batt %, VAC input, load %, and then most lower-end UPS's don't use the remaining two fields and they show as NA.

There is no evidence of COMMBAD's here or anything. This looks good.

What's the problem?

 

[satyr]

I'm still getting the COMMBAD - UPS emails sent to me every few hours. Also, upsd commands all return, "fatal error: a previous upsd instance is already running!"
Any ideas for resolving those issues? When I first installed the driver, upsd commands would return all the pertinent info for the unit--which was nice (and gave me some insight as to what level of communication was being made).

Lastly, are there any tests to run to see if the UPS is working and configured correctly, short of disconnecting the supply or cutting power to the house? I'd like to run some sort of mock test, if possible.

 

[satyr]

Any other ideas?

 

[SweetAndLow]

Sounds like you started a service by hand and freenas is trying to start the save service. Just kill the service and let freenas deal with it or just reboot.

 

[SweetAndLow]

Sounds like you started a service by hand and freenas is trying to start the save service. Just kill the service and let freenas deal with it or just reboot.

 

[DrKK]

Sounds like you started a service by hand and freenas is trying to start the save service. Just kill the service and let freenas deal with it or just reboot.

Yeah that's what I thought too, but then, I figured I was getting confused somehow.

You should not be running "upsd" at the command line. Why are you doing that?

 

[satyr]

I had the mistaken idea that I could reset the driver through CLI, since I couldn't find any option for doing that in the GUI. I had initially switched USB ports on the box, and that seemed to be when the errors originated. After resolving that issue, this new one began. Clearly, my thoughts about using the UPSD commands were erroneous. My question now is, what can be done to rectify the situation? Any commands to reset the UPSD?

I tried killing the service to see if there was still a version running from when I tried starting it through CLI, but the log returns:
20150807 185249 NA NA NA [NA] NA NA

 

[satyr]

Also, I am happy to report that the UPSC commands return all the UPS info from the unit (battery charge info, serial number, driver config, etc).
So I believe the backup is working.

That being said, is there a way to actually test the setup, short of cutting power to the unit?

 

[DrKK]

Can you...not...go in to the "SERVICES" screen and simply click "off" on the UPS service, then "ON" again?

 

[DifferentStrokes]

Also, I am happy to report that the UPSC commands return all the UPS info from the unit (battery charge info, serial number, driver config, etc).
So I believe the backup is working.

That being said, is there a way to actually test the setup, short of cutting power to the unit?

I find unplugging the UPS from the wall is the best way for me to check things. About once a month I pull the plug and wait for my email telling me the server has gone on battery. I let it run on battery for a few minutes to test things. Then I plug it back in and wait for the online email.

 

[satyr]

Can you...not...go in to the "SERVICES" screen and simply click "off" on the UPS service, then "ON" again?

Yes, and that works fine. However, it hasn't solved the problem of me getting 20+ COMMBAD emails each day. I must have accidentally turned on another service through CLI (though, not sure how I would have managed that) that isn't communicating, despite the UPS service through the GUI working okay--at least, it seems to be working okay.

 

[satyr]

I find unplugging the UPS from the wall is the best way for me to check things. About once a month I pull the plug and wait for my email telling me the server has gone on battery. I let it run on battery for a few minutes to test things. Then I plug it back in and wait for the online email.

That's what I figured. Will have to give it a shot tonight. Didn't know if there was an internal failsafe in the UPS that disables it if it's been unplugged or something. Thanks.

 

[satyr]

So, unplugging kept power to the unit but did not generate an email report. Still getting 50+ COMMBAD emails each day. I'd like to get that resolved if anyone has any ideas, short of rebuilding the entire config.