How to configure the UPS port?

[jfr2006]

Hi:

I've an APC Back-UPS ES700 model connected by USB to my freenas. However, i'm unable to start the service, since i get this error:

Jul 8 22:27:29 freenas freenas[1805]: Executing: /usr/sbin/service nut restart
Jul 8 22:27:29 freenas freenas: nut not running? (check /var/db/nut/upsd.pid).
Jul 8 22:27:29 freenas freenas: Error: you must specify a port name in ups.conf. Try -h for help.
Jul 8 22:27:29 freenas freenas: Network UPS Tools - APC Smart protocol driver 2.00 (2.4.1)

How can i know which port to use?

Regards.

 

[James]

Does it work if you set it in Services -> UPS? http://doc.freenas.org/index.php/UPS

 

[jfr2006]

The problem is i don't know what to put on the port field. I tried /dev/ugen0.2, but then i get this:

Jul 9 22:10:53 freenas freenas: Fatal error: unusable configuration
Jul 9 22:10:53 freenas freenas: Network UPS Tools - APC Smart protocol driver 2.00 (2.4.1)
Jul 9 22:10:53 freenas freenas: APC command table version 2.0
Jul 9 22:10:53 freenas freenas:
Jul 9 22:10:53 freenas freenas: Unable to open /dev/ugen0.2: Permission denied
Jul 9 22:10:53 freenas freenas:
Jul 9 22:10:53 freenas freenas: Current user id: uucp (66)
Jul 9 22:10:53 freenas freenas: Serial port owner: root (0)
Jul 9 22:10:53 freenas freenas: Serial port group: operator (5)
Jul 9 22:10:53 freenas freenas: Mode of port: 0600
Jul 9 22:10:53 freenas freenas:
Jul 9 22:10:53 freenas freenas: Things to try:
Jul 9 22:10:53 freenas freenas:
Jul 9 22:10:53 freenas freenas: - Use another port (with the right permissions)
Jul 9 22:10:53 freenas freenas:
Jul 9 22:10:53 freenas freenas: - Fix the port owner/group or permissions on this port
Jul 9 22:10:53 freenas freenas:
Jul 9 22:10:53 freenas freenas: - Run this driver as another user (upsdrvctl -u or 'user=...' in ups.conf).
Jul 9 22:10:53 freenas freenas: See upsdrvctl(8) and ups.conf(5).
Jul 9 22:10:53 freenas freenas:
Jul 9 22:10:53 freenas freenas: Driver failed to start (exit status=1)
Jul 9 22:10:53 freenas freenas: Network UPS Tools - UPS driver controller 2.4.1
Jul 9 22:10:53 freenas root: /usr/local/etc/rc.d/nut: WARNING: failed precmd routine for nut
Jul 9 22:10:53 freenas freenas: /usr/local/etc/rc.d/nut: WARNING: failed precmd routine for nut
Jul 9 22:10:53 freenas freenas[1805]: Executing: /bin/pgrep -F /var/db/nut/upsd.pid upsd

 

[James]

It's my understanding that a USB port should be a /dev/uhid# where # is 0 for first USB port, 1 for second, etc. Let us know if that works because if it does not the doc needs to be updated.

 

[jfr2006]

I don't think so, because there are no such files on the /dev directory. Here is a list:

freenas# ls -all
total 4
dr-xr-xr-x 8 root wheel 512 Jul 8 12:04 .
drwxr-xr-x 20 root wheel 512 Jul 2 22:50 ..
crw-r--r-- 1 root wheel 0, 31 Jul 8 12:04 acpi
crw-r----- 1 root operator 0, 94 Jul 8 12:04 ada0
crw-r----- 1 root operator 0, 104 Jul 8 12:04 ada0p1
crw-r----- 1 root operator 0, 105 Jul 8 12:04 ada0p2
crw-r----- 1 root operator 0, 95 Jul 8 12:04 ada1
crw-r----- 1 root operator 0, 106 Jul 8 12:04 ada1p1
crw-r----- 1 root operator 0, 107 Jul 8 12:04 ada1p2
crw-r----- 1 root operator 0, 96 Jul 8 12:04 ada2
crw-r----- 1 root operator 0, 108 Jul 8 12:04 ada2p1
crw-r----- 1 root operator 0, 109 Jul 8 12:04 ada2p2
crw-r----- 1 root operator 0, 97 Jul 8 12:04 ada3
crw-r----- 1 root operator 0, 110 Jul 8 12:04 ada3p1
crw-r----- 1 root operator 0, 111 Jul 8 12:04 ada3p2
crw-r----- 1 root operator 0, 98 Jul 8 12:04 ada4
crw-r----- 1 root operator 0, 112 Jul 8 12:04 ada4p1
crw-r----- 1 root operator 0, 113 Jul 8 12:04 ada4p2
crw------- 1 root wheel 0, 49 Jul 8 12:04 atkbd0
crw------- 1 root kmem 0, 17 Jul 8 12:04 audit
crw------- 1 root wheel 0, 28 Jul 8 12:04 bpf
lrwxr-xr-x 1 root wheel 3 Jul 8 12:04 bpf0 -> bpf
crw------- 1 root wheel 0, 5 Jul 10 03:47 console
crw------- 1 root wheel 0, 48 Jul 8 12:04 consolectl
crw-rw-rw- 1 root wheel 0, 27 Jul 8 12:04 ctty
crw-r----- 1 root operator 0, 83 Jul 8 12:04 da0
crw-r----- 1 root operator 0, 90 Jul 8 12:04 da0s1
crw-r----- 1 root operator 0, 99 Jul 8 12:04 da0s1a
crw-r----- 1 root operator 0, 91 Jul 8 12:04 da0s2
crw-r----- 1 root operator 0, 92 Jul 8 12:04 da0s3
crw-r----- 1 root operator 0, 93 Jul 8 12:04 da0s4
crw------- 1 root wheel 0, 4 Jul 8 12:04 devctl
cr-------- 1 root wheel 0, 82 Jul 8 12:04 devstat
dr-xr-xr-x 2 root wheel 512 Jul 8 12:04 fd
crw------- 1 root wheel 0, 30 Jul 8 12:04 fido
crw-r----- 1 root operator 0, 3 Jul 8 12:04 geom.ctl
dr-xr-xr-x 2 root wheel 512 Jul 8 12:04 gptid
crw------- 1 root wheel 0, 25 Jul 8 12:04 io
lrwxr-xr-x 1 root wheel 6 Jul 8 12:04 kbd0 -> atkbd0
lrwxr-xr-x 1 root wheel 7 Jul 8 12:04 kbd1 -> kbdmux0
crw------- 1 root wheel 0, 6 Jul 8 12:04 kbdmux0
crw------- 1 root wheel 0, 23 Jul 8 12:04 klog
crw-r----- 1 root kmem 0, 9 Jul 8 12:04 kmem
lrwxr-xr-x 1 root wheel 12 Jul 8 12:05 log -> /var/run/log
crw-r----- 1 root operator 0, 131 Jul 8 12:04 md0
crw-r----- 1 root operator 0, 132 Jul 8 12:05 md1
crw-r----- 1 root operator 0, 133 Jul 8 12:05 md2
crw------- 1 root wheel 0, 53 Jul 8 12:04 mdctl
crw-r----- 1 root kmem 0, 8 Jul 8 12:04 mem
crw------- 1 root kmem 0, 16 Jul 8 12:04 nfslock
crw-rw-rw- 1 root wheel 0, 18 Jul 10 22:47 null
crw------- 1 root operator 0, 84 Jul 8 12:04 pass0
crw------- 1 root operator 0, 85 Jul 8 12:04 pass1
crw------- 1 root operator 0, 86 Jul 8 12:04 pass2
crw------- 1 root operator 0, 87 Jul 8 12:04 pass3
crw------- 1 root operator 0, 88 Jul 8 12:04 pass4
crw------- 1 root operator 0, 89 Jul 8 12:04 pass5
crw-r--r-- 1 root wheel 0, 20 Jul 8 12:04 pci
crw-rw-rw- 1 root wheel 0, 26 Jul 8 12:04 ptmx
dr-xr-xr-x 2 root wheel 512 Jul 8 22:30 pts
crw-rw-rw- 1 root wheel 0, 21 Jul 8 12:05 random
lrwxr-xr-x 1 root wheel 4 Jul 8 12:04 stderr -> fd/2
lrwxr-xr-x 1 root wheel 4 Jul 8 12:04 stdin -> fd/0
lrwxr-xr-x 1 root wheel 4 Jul 8 12:04 stdout -> fd/1
crw------- 1 root wheel 0, 24 Jul 8 12:04 sysmouse
crw------- 1 root wheel 0, 32 Jul 8 12:06 ttyv0
crw------- 1 root wheel 0, 33 Jul 8 12:06 ttyv1
crw------- 1 root wheel 0, 34 Jul 8 12:06 ttyv2
crw------- 1 root wheel 0, 35 Jul 8 12:06 ttyv3
crw------- 1 root wheel 0, 36 Jul 8 12:06 ttyv4
crw------- 1 root wheel 0, 37 Jul 8 12:06 ttyv5
crw------- 1 root wheel 0, 38 Jul 8 12:06 ttyv6
crw------- 1 root wheel 0, 39 Jul 8 12:06 ttyv7
crw------- 1 root wheel 0, 40 Jul 8 12:04 ttyv8
crw------- 1 root wheel 0, 41 Jul 8 12:04 ttyv9
crw------- 1 root wheel 0, 42 Jul 8 12:04 ttyva
crw------- 1 root wheel 0, 43 Jul 8 12:04 ttyvb
crw------- 1 root wheel 0, 44 Jul 8 12:04 ttyvc
crw------- 1 root wheel 0, 45 Jul 8 12:04 ttyvd
crw------- 1 root wheel 0, 46 Jul 8 12:04 ttyve
crw------- 1 root wheel 0, 47 Jul 8 12:04 ttyvf
dr-xr-xr-x 2 root wheel 512 Jul 8 12:04 ufs
dr-xr-xr-x 2 root wheel 512 Jul 8 12:04 ufsid
lrwxr-xr-x 1 root wheel 9 Jul 8 12:04 ugen0.1 -> usb/0.1.0
lrwxr-xr-x 1 root wheel 9 Jul 8 22:28 ugen0.2 -> usb/0.2.0
lrwxr-xr-x 1 root wheel 9 Jul 8 12:04 ugen1.1 -> usb/1.1.0
lrwxr-xr-x 1 root wheel 9 Jul 8 12:04 ugen2.1 -> usb/2.1.0
lrwxr-xr-x 1 root wheel 9 Jul 8 12:04 ugen3.1 -> usb/3.1.0
lrwxr-xr-x 1 root wheel 9 Jul 8 12:04 ugen3.2 -> usb/3.2.0
lrwxr-xr-x 1 root wheel 9 Jul 8 12:04 ugen4.1 -> usb/4.1.0
lrwxr-xr-x 1 root wheel 9 Jul 8 12:04 ugen5.1 -> usb/5.1.0
lrwxr-xr-x 1 root wheel 9 Jul 8 12:04 ugen6.1 -> usb/6.1.0
lrwxr-xr-x 1 root wheel 6 Jul 8 12:04 urandom -> random
dr-xr-xr-x 2 root wheel 512 Jul 8 12:04 usb
crw-r--r-- 1 root operator 0, 51 Jul 8 12:04 usbctl
crw------- 1 root operator 0, 52 Jul 8 12:04 xpt0
crw-rw-rw- 1 root wheel 0, 19 Jul 9 22:01 zero
crw-rw-rw- 1 root operator 0, 134 Jul 8 12:05 zfs
freenas#

 

[Milhouse]

For a USB UPS, try "auto" as the port.

 

[jfr2006]

For a USB UPS, try "auto" as the port.

Still no luck:

Jul 11 10:07:56 freenas freenas[1805]: Executing: /usr/sbin/service ix-ups quietstart
Jul 11 10:07:57 freenas freenas[1805]: Executing: /usr/sbin/service nut restart
Jul 11 10:07:57 freenas freenas: Will not 'restart' nut because nut_enable is NO.
Jul 11 10:07:57 freenas freenas[1805]: Executing: /bin/pgrep -F /var/db/nut/upsd.pid upsd
Jul 11 10:08:02 freenas freenas[1805]: Executing: /usr/sbin/service ix-ups quietstart
Jul 11 10:08:02 freenas freenas[1805]: Executing: /usr/sbin/service nut restart
Jul 11 10:08:02 freenas freenas: nut not running? (check /var/db/nut/upsd.pid).
Jul 11 10:08:02 freenas freenas: Fatal error: unusable configuration
Jul 11 10:08:02 freenas freenas: Network UPS Tools - APC Smart protocol driver 2.00 (2.4.1)
Jul 11 10:08:02 freenas freenas: APC command table version 2.0
Jul 11 10:08:02 freenas freenas:
Jul 11 10:08:02 freenas freenas: Unable to open auto: No such file or directory
Jul 11 10:08:02 freenas freenas:
Jul 11 10:08:02 freenas freenas: Things to try:
Jul 11 10:08:02 freenas freenas:
Jul 11 10:08:02 freenas freenas: - Check 'port=' in ups.conf
Jul 11 10:08:02 freenas freenas:
Jul 11 10:08:02 freenas freenas: - Check owner/permissions of all parts of path
Jul 11 10:08:02 freenas freenas:
Jul 11 10:08:02 freenas freenas: Driver failed to start (exit status=1)
Jul 11 10:08:02 freenas freenas: Network UPS Tools - UPS driver controller 2.4.1
Jul 11 10:08:02 freenas root: /usr/local/etc/rc.d/nut: WARNING: failed precmd routine for nut
Jul 11 10:08:02 freenas freenas: /usr/local/etc/rc.d/nut: WARNING: failed precmd routine for nut
Jul 11 10:08:02 freenas freenas[1805]: Executing: /bin/pgrep -F /var/db/nut/upsd.pid upsd

 

[jenksdrummer]

I ran into this, I have a Cyberpower 685 AVR UPS connected to my freenas box, and from what I can tell, it was refusing to load the driver assigned to it according to the list. I swapped over to the other CyberPower drivers, and the UPS service will start, but it does give some error that alludes to it not being right.

I'll see if I can post the error (running disk benchmark / stress test). Also, FWIW, I'm running 8.0.1-BETA3 build 6929

 

[cbray]

USB ports for UPS

Hi youins,

I'm having the same problem with ALL my various models of APC UPS.

I found out which port my UPS was on by plugging in an old USB mouse.
After boot I could see the port the mouse was on.
In my case it was USB port #1 Address #2.
I moved it around and rebooted verifying which ports were numbered which.
I have my USB stick inside my machine connected to a header on the MoBo.
So I knew that only my external USB ports were showing after boot.
USB port naming conventions (within fN8) seem to be:
2 Physical USB connectors = 2 logical addresses per 1 logical port.
So your ugen3.1 = USB PORT#3, ADDR#1 and ugen3.2 = USB PORT#3 Adress #2.
Or on One USB Logical Port #3 you have Two Physical Connectors = addr1 and addr2.

Now You show 7 logical ports, numbered 0 thru 6.
With 2 Addresses or Physical USB connectors per port; your motherboard probably has the ability of up to 14 USB devices. In order to do that you would (most likely) need additional USB/Header connectors. These are cables that connect internally on to your motherboard and then to the front of your case or to slot plates containing 2 REAL Physical USB ports on the back.

Assuming (yeah Joe, I know...:p) that you have a pretty normal MoBo layout and Case configuration... you probably have either 4 or 6 or 8 PHYSICAL USB ports on the back of the machine and 2 more on the front. Then you would have pins on the MoBo inside where you would attach the front case USB ports and more if you needed.

Let us know more about your layout and installation ?
What are all of the USB devices that are actually plugged in ?
USB MEM Stick for boot?
USB Keyboard ?
USB Mouse ?
USB Printer ?


Since I don't know your motherboard layout I can't give you much better info other than that.

The bad news is that I know what port my APC is plugged into and that it is a supported Model under the NUT daemon.
Now my problem is one of what syntax do I use to say that USB port 1 Addr2 is where my UPS is. I have tried all sorts of combinations and even moved the UPS to a different port and tried them all again.


I also don't know why:

Jul 11 10:07:57 freenas freenas: Will not 'restart' nut because nut_enable is NO.

I left off at my attempts while awaiting 8B4 that I prayed would arrive today.
My prayers were answered and I am gonna try the UPS daemon in BETA4 now.

More later.... more prayers now...

Peace,
CB

 

[James]

If you turn on "show console messages" in System -> Settings -> Advanced and watch the messages as you plug in the UPS, it should show the FreeBSD device name. Please post what it is as I don't have a USB UPS to test to update doc.freenas.org.

Regarding the nut_enable=NO message, a smilar message will happen with any service that has not been enabled in Services -> Control Services.

 

[jfr2006]

Hi:

cbray, here is a picture of the board and a arrow showing at which port it is connected:


admin:

yes i tried that and got a message that identified something like ugen0.2..anyway, here is quote from the boot process:

Jul 14 12:03:29 freenas kernel: ugen0.2: <APC> at usbus0

 

[cbray]

UPS port SYNTAX for GUI ?

When I saw the picture, I immediately said to self: self that should be port #0 addr #2.

Then as I read down, it said ugen 0.2

So that is confirmation you are on USB port0 addr2.

Now... you are where I am. We both need the correct syntax to enter into the gui.

Admin: ah ok. I read early yesterday what the nut daemon was... UPS tools. But when I went to double check it during my post I got a different link and believed it was a general usb port daemon. Sorry for my confusion.

So when I click start service and it tries, then fails (I do watch and reread the console msgs in my browser), it actually is the UPS daemon (NUT) starting and stopping.

So here we are:
We know what port and address we have our UPS plugged into.
We know that our UPS is listed as a compatible or supported unit in FreeBSD NUT daemon.
We are comfortable in saying that "auto" does not work as port in gui.
So we might only need someone to tell us the syntax for describing the correct port
in the FeeNAS gui.

Does anyone have their UPS daemon working in services ?
What port did you use and what did you call it ?

My APC is on ugen1.2 making it the 4th usb port.
So /dev/uhid4 should work but doesn't.

I spent too much time on email and posts last night to install BETA-4 so I am going to do that right now.

More data later.

Peace,
CB


OK BETA-4 freshly installed. NO issues during install. 7 minutes from boot of CD to Reboot from USB.


Here's what I 've located:

Jul 14 13:56:04 freenas kernel: ugen1.2: <APC> at usbus1

That puts me on the 4th port counting ugen0.1, ugen0.2, ugen1.1 and then ugen1.2

That will give me these results when I use this in the GUI for port '/dev/uhid4' and I try to start the UPS service:

Jul 14 13:59:45 freenas freenas[1536]: Executing: /usr/sbin/service ix-ups quietstart
Jul 14 13:59:45 freenas freenas[1536]: Executing: /usr/sbin/service nut restart
Jul 14 13:59:45 freenas freenas: nut not running? (check /var/db/nut/upsd.pid).
Jul 14 13:59:45 freenas freenas: Network UPS Tools - Generic HID driver 0.34 (2.4.1)
Jul 14 13:59:45 freenas freenas: USB communication driver 0.31
Jul 14 13:59:45 freenas freenas: No matching HID UPS found
Jul 14 13:59:45 freenas freenas: Driver failed to start (exit status=1)
Jul 14 13:59:45 freenas freenas: Network UPS Tools - UPS driver controller 2.4.1
Jul 14 13:59:45 freenas root: /usr/local/etc/rc.d/nut: WARNING: failed precmd routine for nut
Jul 14 13:59:45 freenas freenas: /usr/local/etc/rc.d/nut: WARNING: failed precmd routine for nut
Jul 14 13:59:46 freenas freenas[1536]: Executing: /bin/pgrep -F /var/db/nut/upsd.pid upsd

I tried a few of my different models of APC UPS which are listed in the pulldown.
I'm ready for professional help (of more than one kind) :D

So I'm gonna set this issue aside while I play more with 8.B4

CB

 

[William Grzybowski]

Hello,

This is probably a bug in the implementation of UPS, which is 100% untested...
I would like help to track down what's wrong to fix it...

For USB, can you try using /dev/ugenX.X as the device name, and chmod it so ups daemon can have read access?
Like chmod 777 /dev/ugenX.X , and just then start the UPS service?

I know it is not safe but it is just for debugging purposes...

Thank you

 

[jfr2006]

It worked ;). I had already though doing that, but it should not be necessary :(

Jul 15 15:22:47 freenas freenas[1859]: Executing: /usr/sbin/service ix-ups quietstart
Jul 15 15:22:48 freenas freenas[1859]: Executing: /usr/sbin/service nut restart
Jul 15 15:22:48 freenas freenas: Will not 'restart' nut because nut_enable is NO.
Jul 15 15:22:48 freenas freenas[1859]: Executing: /bin/pgrep -F /var/db/nut/upsd.pid upsd
Jul 15 15:22:51 freenas freenas[1859]: Executing: /usr/sbin/service ix-ups quietstart
Jul 15 15:22:51 freenas freenas[1859]: Executing: /usr/sbin/service nut restart
Jul 15 15:22:51 freenas freenas: nut not running? (check /var/db/nut/upsd.pid).
Jul 15 15:22:52 freenas root: Unknown USB device: vendor 0x051d product 0x0002 bus uhub0
Jul 15 15:22:52 freenas freenas: Using subdriver: APC HID 0.93
Jul 15 15:22:52 freenas freenas: Network UPS Tools - Generic HID driver 0.34 (2.4.1)
Jul 15 15:22:52 freenas freenas: USB communication driver 0.31
Jul 15 15:22:52 freenas freenas: Network UPS Tools - UPS driver controller 2.4.1
Jul 15 15:22:52 freenas freenas: Starting nut.
Jul 15 15:22:53 freenas freenas: listening on 0.0.0.0 port 3493
Jul 15 15:22:53 freenas freenas: Connected to UPS [ups]: usbhid-ups-ups
Jul 15 15:22:53 freenas freenas[1859]: Executing: /bin/pgrep -F /var/db/nut/upsd.pid upsd

Now, it would be nice to have statistics of the UPS on the reporting tab ;)

 

[William Grzybowski]

What happens if you run "upsc UPS@localhost"

Also, can you try "go on battery" and set freenas to shutdown on battery to check if it works? Or if it doesnt trying to figure out why?

Really appreciate, thanks

 

[cbray]

UPS port syntax ?!

Well this worked to get the service to start:

For USB, can you try using /dev/ugenX.X as the device name, and chmod it so ups daemon can have read access?
Like chmod 777 /dev/ugenX.X , and just then start the UPS service?

I used: chmod 777 /dev/ugen1.2

Then the UPS service did start.
But after that you can put anything into the port field in the gui, and the UPS will still start. Just as long as it is not blank.
Also, I got nothing in email from the service.
Go figure.

Thanks WG for the assistance.

Peace,
CB

 

[Milhouse]

What happens if you run "upsc UPS@localhost"

Also, can you try "go on battery" and set freenas to shutdown on battery to check if it works? Or if it doesnt trying to figure out why?

Really appreciate, thanks

Just to say the best/safest way to test a UPS is as follows:

• Connect FreeNAS server to mains power
• Connect UPS to FreeNAS using USB/serial etc. (maybe one day, network :))
• Connect a table lamp (60W, 100W bulb etc.) to UPS battery outlet (it may flicker due to the more square than sine wave power provided by some cheap UPS)
• Disconnect UPS from mains - FreeNAS should think it's on battery power, load from table lamp will start to discharge UPS battery
• When battery power level becomes low (~10% remaining) FreeNAS should power down, and the table lamp will remain on until the battery is completely flat. If UPS functionality is not working correctly, the FreeNAS box will remain ON when the table lamp goes OFF.

You should be able to monitor UPS status (including remaining battery level etc.) by running "upsc UPS@localhost" at the CLI.

 

[jfr2006]

What happens if you run "upsc UPS@localhost"

Also, can you try "go on battery" and set freenas to shutdown on battery to check if it works? Or if it doesnt trying to figure out why?

Really appreciate, thanks

Got this:

freenas# upsc UPS@localhost
battery.charge: 100
battery.charge.low: 10
battery.charge.warning: 50
battery.date: not set
battery.mfr.date: 2009/10/14
battery.runtime: 3015
battery.runtime.low: 120
battery.type: PbAc
battery.voltage: 13.6
battery.voltage.nominal: 12.0
driver.name: usbhid-ups
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 2
driver.parameter.port: /dev/ugen0.2
driver.version: 2.4.1
driver.version.data: APC HID 0.93
driver.version.internal: 0.34
input.transfer.high: 266
input.transfer.low: 180
input.voltage: 234.0
input.voltage.nominal: 230
ups.beeper.status: enabled
ups.delay.shutdown: 20
ups.firmware: 829.D3 .I
ups.firmware.aux: D3
ups.load: 0
ups.mfr: APC
ups.mfr.date: 2009/10/14
ups.model: Back-UPS ES 700
ups.productid: 0002
ups.serial: 5B0942T73100
ups.status: OL
ups.timer.reboot: 0
ups.timer.shutdown: -1
ups.vendorid: 051d

Ok..set the option to turn off on battery. Disconnected the ups from the mains...freenas had no reaction at all...Something is still wrong... :(

Regards.

 

[cbray]

UPS problems.

WG asked:

What happens if you run "upsc UPS@localhost"

I too get a report similar to jfrs. It IDs my UPS and UPS configurations correctly.

Does the system need a user entry for UPS similar to other daemons ?

Thanks,
CB

 

[KitDavis]

I too get the same report as well. When I remove the power source to the UPS, FreeNAS looses the connection with the UPS. Once I plug the UPS back in, I can re-establish a connection.