similar to: error: Unknown UPS

On Feb 11, 2014, at 6:52 AM, Greg Vickers wrote: > hosts.conf: > MONTIOR admin at localhost "BelkinUPS" The second field is upsname at hostname (rather than username at hostname). Along these lines, the third field is descriptive only, and doesn't need to match anything (e.g. "Belkin UPS at the bottom of the rack") -- Charles Lepple clepple at gmail

Hi all, I've finally gotten around to setting up the netbook that controls my UPS and I would like to make sure that I've got the metacode correct before configuring nut :) Here's what I've got: Belkin UPS F6C120auUNV * Batteries recently replaced * On battery: 24 port switch, PoE AP, antenna power booster, ADSL modem, MythTV server, 19" monitor * On surge

Hi, These are the instructions I have about accessing nut online. By using the cgi use flag you have the files to use on the webserver. > > If you look in /usr/html after emerge you find the html files. > Copy this files to /var/www/localhost/htdocs/nut > (if you want it as www.my.org/nut ) > > > In /usr/share/nut you find the cgi files. Copy this files to >

Hi all, (Keeping this in a separate email from my first one so as to not make it horribly complex) I've connected my Belkin F6C120auUNV UPS to my Debian 7.7.0 host via USB, and found that the usbhid-ups driver will not start unless I use the option '-u root', even when starting this driver as root: root at monitor:/lib/nut# cat /etc/nut/ups.conf [greything] driver =

Hi, Self-reply ftw, is it something to do with the permissions of the device that is created when the UPS is plugged in? I remember that Debian does have a pretty strict permissions structure, so do I have to fiddle the permissions of something in /dev? I'll try updating nut-server to version 2.6.4-2.3+deb7u1 in wheezy backports and report back - initial attempt to install from wheezy

Hello all, I have succefully configure a trust 1200v ups with nut-2.2.2 on an ubuntu 6.06 LTS by follow this instructions : http://www.networkupstools.org/doc/2.2.0/INSTALL.html I have the nut-cgi 2.0.3-4 from the ubuntu repos installed Now, I have problems to configure the nut-cgi in my web browser and I have this when i tried to http://localhost/cgi-bin/nut/upsstats.cgi. Error: can't

On Feb 15, 2014, at 6:46 PM, Greg Vickers wrote: > Thanks! I've attached the file to this email (bcmxcp_usb.output2014160926.gz), it ran for 12 seconds, and looks like it's looping by that time. I'm not sure what to look for, does grepping for 'Yes' show the variables that the driver can pull off this UPS? The boolean variables seem to be indicated by "Yes". I

On 16/02/14 00:38, Charles Lepple wrote: > On Feb 15, 2014, at 2:57 AM, Tim Dawson wrote: >> The driver will poll the UPS for what variables it supports when it starts, and then go into a polling loop. Look for a section defining the meter map, and you should see the result, as well as the raw data. > Tim: spot on. > > Greg, > > If you want, you can capture the -DDDD output

Arjen, all, Just dropping a note on two points. First, Voltages are perfect in 2.4.1 for the Cyberpower ups's. Glad to see I'm not pushing 20+ any more: http://www.3111skyline.com/nut/ Second, even though the changes to where the monitor lines go in the configs and changes from ACCEPT, etc.. to LISTEN are fairly old now, the documentation for setting up monitoring for multiple UPSs

Arjen, All, I need help unwrapping my head from around the problem of getting nut running on the same machine it runs fine with on another drive!! Sound easy -- not here :) I have network-ups-tools 2.4.1-2 on two servers. On one server I had a raid drive fail (which I'm still booting from and running nut on just fine). I bought a second pair of drives to establish a new array in the

The driver will poll the UPS for what variables it supports when it starts, and then go into a polling loop. Look for a section defining the meter map, and you should see the result, as well as the raw data. You can get the comm spec for XCP from the nut site if you want to delve deeper. I'd give more specifics, but am out of town and only working from memory at the moment . . . - Tim On

On Feb 12, 2014, at 7:50 PM, Tim Dawson wrote: > Run the driver with -DDDDD and see what variables it picks up. I have noted that with the Prestige 9 in bcmxcp, some variables are not consistent within models, and had to do some gentle remapping to get things to work correctly. Tim, is this the issue you mentioned on 2014-02-02 with blocks 0x9 and 0x13? I'll reply to that email. > On

I'll test it. I'm a bit confused with cgi-bin. I have made a lot of hosts.conf copies and didn't understand where does upsstats trying to find hosts.conf # ps -aux | grep ups _ups 13934 0.0 0.0 484 920 ?? Ss 5:41PM 0:01.53 /usr/local/bin/riello_ser -a senpro _ups 9171 0.0 0.1 532 1168 ?? Ss 5:41PM 0:00.13 /usr/local/sbin/upsd _ups 16906 0.0 0.1

Whenever I try to set a value like battery.charge.low using the Network UPS Tools upsset 2.4.3 cgi script, I get an error: Unexpected response: ERR ACCESS-DENIED I can not start a quick UPS test either. Which credentials are used to logon to the upsset.cgi page? I've tried... the username that I configured in upsd.users the root credentials adding a POSIX account & password to match

Bill S wrote, On 4/15/2014 11:18 AM: > The problem is that when I run upsset.cgi I first get a prompt for > user name and password. I then enter the same username and password > as I established in upsd.users and it seems to accept it. upsset.cgi doesn't check that user/password is valid, it just tries it when doing a command. I just tested it, it is working for me on a remote and

On 13/02/14 12:16, Charles Lepple wrote: > On Feb 12, 2014, at 7:50 PM, Tim Dawson wrote: > >> Run the driver with -DDDDD and see what variables it picks up. I have noted that with the Prestige 9 in bcmxcp, some variables are not consistent within models, and had to do some gentle remapping to get things to work correctly. I ran the new driver (see below) and with -DDDD it throws out

On 15/02/14 19:56, Arnaud Quette wrote: > Dear NUT users, > > The relationship with Eaton was in need of clarification for a long > time, which happened over the past weeks.This is now officially noted > on the NUT side, through moving Eaton from the "Main supporter" to > "Supporting UPS manufacturer", rewording the content and putting a big > warning

Since there is apparently no immediate solution to upsstats.cgi not reading the output voltage correctly, I have moved on to trying to use upsset.cgi. To recap the UPS is a CyberPower CyberPower CP1500PFCLCD UPS running on a headless server running Slackware 14.1 with the 3.10.7 kernel. The version of NUT is 2.71 and I am using usbhid-ups for communication with the UPS The problem is that when

Hello all, I request a new NUT release as current dates back to March 9, 2016: NUT 2.7.4 The fact stays that not all distro's use latest snapshots/commits from github dev tree. So please do release a new up to date version please. Thank you Dutchman -------------- next part -------------- An HTML attachment was scrubbed... URL:

I'm access nut online via localhost. But I have the following problems. When I click on Statistics I get cannot open /etc/hosts.conf. When I click on settings I get: Error: Can't open upsset.conf to verify security settings. Refusing to start until this is fixed. I have .htaccess in cgi-bin with the following: <Files upsset.cgi> deny from all allow from 127.0.0.1 </Files>