Weird UPS problem

[DVitoD]

G'day :D

I'm testing FreeNAS the latest and greatest in order to find out if I want to migrate to it. I am currently running into a weird problem which uncle Google doesn't tell me how to solve.

Problem:

upsc ups@localhost error: connection failure: connection refused

However: something clearly IS working

The setup:

1. Synology NAS set up as UPS master.
2. FreeNAS setup as slave on the default port (which is what Synology also uses), with the UID/pwd that works for my other servers too.
3. Run the above command - and get the above error.
4. Unplug the USB cable from the Synology and put it in the FreeNAS testbox:

   Communications with UPS ups@192.168.17.21:3493 lost

   + emailalert:

   COMMBAD ups@192.168.17.21:3493

5. Plug the USB cable back into the Synology UPS server:

   Communications with UPS ups@192.168.2.21:3493 established

   + emailalert:

   COMMOK ups@192.168.17.21:3493

So clearly something is working: FreeNAS is communicating with the Synology UPS server, despite the above error message.

I'd love to monitor my stuff (would love a widget in the GUI too with important system information :p), so would anybody happen to have any clue how to fix this problem?

Thank you in advance very much :D

Bye,

 

[Ericloewe]

That's odd, but I think I had a similar experience the other day, when trying to move my UPS to the pfSense router. Reverted quickly and never bothered to get it working, since I then got it to work on pfSense.

The fact that it mentions ups@localhost leaves the impression that it's looking in the wrong place.

 

[DVitoD]

That's odd, but I think I had a similar experience the other day, when trying to move my UPS to the pfSense router. Reverted quickly and never bothered to get it working, since I then got it to work on pfSense.

The fact that it mentions ups@localhost leaves the impression that it's looking in the wrong place.

Thanks for your reply :)

I tried to use ups@freenas as well, which is the name of this test box. And I tried ups@freenas.WORKGROUP; doesn't make a difference. I will try to put the test box in server mode, to see if I can isolate so more.


(Anybody who runs pfSense is a friend by design, btw:D

So, as a side note: pfSense is the UPS server on LAN now? Could I ask what your consideration for that is? To not to do it my consideration was: it so happens I need to reboot/upgrade/etc that box from time to time. That means the UPS server goes down, and that means all servers on the UPS go down. That's why I kept the UPS server outside pfSense, and on a NAS, the core reason for buying my UPS in the first place. What are your considerations for putting the UPS server on pfSense?)

 

[Ericloewe]

The UPS should be up@$_remote_ups_server - at leas that's what I'd expect, intuitively.

Regarding my UPS set up:

The original idea was to have the UPS on the router, which should be the last device to power down (it's hard for networking to work if DHCP goes down). The server would shut down after a certain time, with the router following it another while later.
Haven't had the time to properly configure pfSense, but at least the FreeNAS server shuts down as it should.

 

[DVitoD]

The UPS should be up@$_remote_ups_server - at leas that's what I'd expect, intuitively.

Cough, cough, cough (starts to clean up spilled out coffee)

When I do that I get:

Code:

battery.charge: 100
battery.charge.low: 10
battery.charge.warning: 50
battery.runtime: 1860
battery.runtime.low: 120
battery.type: PbAc
battery.voltage: 27.4
battery.voltage.nominal: 24.0
device.mfr: American Power Conversion
device.model: Smart-UPS 1000
device.type: ups
driver.name: usbhid-ups
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 5
driver.parameter.port: auto
driver.version: SDS4-3-2013Q3branch-3795-131004
driver.version.data: APC HID 0.95
driver.version.internal: 0.37
ups.beeper.status: enabled
ups.delay.shutdown: 20
ups.firmware: UPS 06.5 / ID=18
ups.mfr: American Power Conversion
ups.mfr.date: 2012/02/17
ups.model: Smart-UPS 1000
ups.productid: 0003
ups.status: OL
ups.timer.reboot: -1
ups.timer.shutdown: -1
ups.vendorid: 051d

:D

Thank you for waking me up :p

:D

 

[Ericloewe]

I'm glad that was sorted out :D