Re: [Nut-upsuser] new NUT release please!
I'll take this hit: Dutchman01, why should there be a new version released? Is there a significant problem with the current version, or major functionality that is missing? Releasing a new version for the sake of an updated version number isn't a reason for releasing an update. On 11/9/17 1:56 am, Dutchman01 wrote: 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 ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
[Nut-upsuser] CyberPower ol2000ertxl2u
Hi all, I'm picking up a CyberPower OL2000ERTXL2U tomorrow (needs new batteries), should that be supported via the powerpanel driver? Thanks, Greg ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Call to funding NUT infrastructure
Hi Arnaud, You are an officer and a gentleman, very helpful on the email lists when time permits, and I am very happy to support the NUT infrastructure! I hope that my donation makes the hosting easier to run for a while! Cheers, Greg On 3/07/2015 2:49 am, Arnaud Quette wrote: Dear NUT Community, It's not something you've been used to from me, but... I've been funding the NUT infrastructure on my own for many years now. I'm currently in a situation that is a bit hard, financially speaking. I've recently renewed the networkupstools.org http://networkupstools.org domain name. But now comes the server in itself (BaseInstance Cloud slice on Gandi). It's not that many bucks a year, but already too much currently. Life push all of us to some priority. I could be asking Eaton obviously, but would prefer for now that we keep the community approach only. I would also like to expand a bit the resources to relaunch a demo.networkupstools.org http://demo.networkupstools.org for example, which means a bit more money (btw, any idea beside demo.n.o is welcome...). So, I would welcome any and all donation through my paypal account (arnaud.que...@gmail.com mailto:arnaud.que...@gmail.com). Thanks and cheers, Arno -- NUT (Network UPS Tools) Project Leader - http://www.networkupstools.org Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.fr ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
[Nut-upsuser] Belkin UPS, master netbook, slave MythTV server
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 protection: Netbook (details below) * I would like the UPS to turn off at 20% battery capacity Netbook with Debian 7.7.0, * Attached via USB to Belkin UPS * Battery in netbook lasts three hours, it will outlast the UPS by a fair way, so does not need UPS battery supply * 'master' where upsd runs * runs upsc, upsd, upsmon, upsc, nut-cgi, apache, nagios MythTV server with Ubuntu 14.04 * plugged into Belkin UPS * to be turned off within 5 minutes of loss of supply * to be turned back on after 15 minutes of return of supply (WOL?) * 2xSSD drives, 1x4Tb 3.5, 1x250Gb 2.5 * 'slave' system I'm digging through the nut documentation now, I'm sure that I can configure nut to do all of this... right? Thanks, Greg ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] usbhid-ups must use '-u root'
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 backports is not working! (New package won't install when running 'aptitude -t wheezy-backports install nut-server', even though aptitude got the updated package list correctly...) Thanks, Greg On 14/11/2014 9:57 pm, Greg Vickers wrote: 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@monitor:/lib/nut# cat /etc/nut/ups.conf [greything] driver = usbhid-ups port = auto root@monitor:/lib/nut# ./usbhid-ups -a greything Network UPS Tools - Generic HID driver 0.37 (2.6.4) USB communication driver 0.32 Can't claim USB device [050d:0912]: could not detach kernel driver from interface 0: Operation not permitted root@monitor:/lib/nut# ./usbhid-ups -a greything -u root Network UPS Tools - Generic HID driver 0.37 (2.6.4) USB communication driver 0.32 Using subdriver: Belkin HID 0.15 root@monitor:/lib/nut# ps aux | grep usbhid root 4857 0.1 0.0 16888 712 ?Ss 21:54 0:00 ./usbhid-ups -a greything -u root root 4859 0.0 0.0 7836 880 pts/0S+ 21:54 0:00 grep usbhid Is this expected behavior? Seems like it should not be required, a quick google found this: https://bugzilla.redhat.com/show_bug.cgi?id=488368 (not the same situation, but the short-term fix detailed works, i.e. use '-u root') Thanks, Greg ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Formalizing the end of the relationship with Eaton
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 [1]. Quoting these main changes: Eaton, has been the main NUT supporter in the past, between 2007 and 2011, continuing MGE UPS SYSTEMS efforts. ... The situation has evolved, and since 2011 Eaton does not support NUT anymore. This may still evolve in the future. But for now, please do not consider anymore that buying Eaton products will provide you with official support from Eaton, or a better level of device support in NUT. Considering that I'm still an Eaton employee, this blurry situation was one of the main factors that kept me away from NUT for the past couple of years. Not the only one, but I'm working on these points one after another. You can expect to see me slowly starting to bother you all again in a soon future ;) Aw, you never bothered :) Thanks for the clarification, I've been unaware of that particular situation. You must be relieved that this situation is becoming a bit clearer, and hopefully gives you the ability to pursue what you want to do! Cheers, Greg Cheers, Arnaud -- [1] http://www.networkupstools.org/acknowledgements.html#Eaton ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Eaton Powerware 5110 - some stats not reported
On 16/02/14 10:03, Charles Lepple wrote: 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 think the meter map is the source of the numeric variables: 0.566550Index Offset Format NUT 0.566617002751 output.frequency 0.5666800028000451 input.frequency 0.5667430033000851 battery.voltage 0.56680500410012f0 battery.voltage.low 0.56686600430016f0 battery.charge.low 0.56692800470020f0 ups.load 0.56698900560024f0 input.voltage 0.5670510065002851 output.current 0.5671130068003251 output.current.nominal 0.56717500780036f0 output.voltage 0.56723700910040f0 input.quality Maybe Alf has some additional insights? Ah, I see - I've noticed that when I browse to upsset.cgi, that there are no Settings reported when I select Settings and click the View button. If I select the Commands function and click View, there are only four available: - Turn off the load and return when power is back - Turn off the load and remain off - Start a battery test - Description unavailable I think Settings are what you would see from upsrw ups, and Commands are listed by upscmd -l ups. You're going to make me actually install the CGI programs, aren't you? Everything else I have been able to just look up in the source :-) And correspondingly with what you say here, the same detail is returned by these commands: $ sudo upsrw Powerware5110 $ (wow, nothing returned!) $ sudo upscmd -l Powerware5110 Instant commands supported on UPS [Powerware5110]: shutdown.return - Turn off the load and return when power is back shutdown.stayoff - Turn off the load and remain off test.battery.start - Start a battery test test.system.start - Description unavailable Bugger, huh. Guess I'll have to use the Windows software to set the beeper[1] to OFF. You don't have to install the cgi scripts, I'll be the guinea pig for the driver[0]! I have a Belkin UPS which I was running on this system up to a few days ago when I figured out that the battery was totally cactus, and I put the Eaton back in until I get replacement batteries for the Belkin. (The Belkin is two 12v batteries, the Eaton is one.) Anyway, the driver for the Belkin actually has Settings reported, and I can't remember, but about 10+ different Commands. Is the lack of Settings or Commands indicative of any problem, or is it the case that these just haven't been implemented on this driver? Right, or that the protocol doesn't expose the settings or commands. p.s. The only difference I can see from the web page any my upsc output is that my UPS is a 700, and the driver was developed on a 500? The part that confuses me is why they would have the same firmware revision for what seem to be different sets of capabilities. Usually, the only internal difference between a 500 VA UPS and a 700 VA UPS is the size of the battery string and maybe the power electronics module. [0] Hurmm, well, I'm happy to do any testing of code with this 700i model! [1] Once I get replacement batteries for the 1200VA Belkin, the Powerware 5110 will be moved to hold up my weather station and wfrog laptop, so I can keep recording weather events if we lose power! Cheers, Greg ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Eaton Powerware 5110 - some stats not reported
On 13/02/14 12:16, Charles Lepple wrote: On Feb 12, 2014, at 7:50 PM, Tim Dawson wrote: Run the driver with -D 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 - it throws out tons of never ending information, what am I looking for? :) Tim, is this the issue you mentioned on 2014-02-02 with blocks 0x9 and 0x13? I'll reply to that email. On 02/12/2014 06:46 PM, Greg Vickers wrote: Hi all, I've hooked up an Eaton Powerware 5110 to Ubuntu 13.10 server, and configured nut appropriately. The cgi scripts are working fine, but on upsstats.cgi, the Batter, UPS Temp and Battery Runtime fields are all blank - and there are no entries for these values in the 'All data' tree. Greg, From http://packages.ubuntu.com/saucy/nut-server it looks like you have 2.6.4. There was a big rewrite of the bcmxcp driver core which became part of 2.7.1. It might be possible to drop in the bcmxcp driver binary from Ubuntu trusty - I wouldn't force-install the whole package, just in case they changed things regarding init scripts and other libraries, but the drivers should be pretty self-contained. Or you could build just that driver from source, making sure to use the same paths as Ubuntu uses to build their binaries. Let me know if you're interested in trying one of those routes (admittedly, it makes for a bit of a Frankenstein system) and I can explain in more detail. Charles, thanks very much for the information :) I've parachuted in the bcmxcp_usb binary from Ubuntu Trusty from nut-server (http://mirrors.kernel.org/ubuntu/pool/main/n/nut/nut-server_2.7.1-1ubuntu1_i386.deb) by using dpkg-deb to pull it out of the .deb file: $ ls -l /lib/nut/bcmxcp* -rwxr-xr-x 1 root root 75880 May 20 2013 /lib/nut/bcmxcp -rwxr-xr-x 1 root root 80544 Feb 15 09:03 /lib/nut/bcmxcp_usb -rwxr-xr-x 1 root root 71816 Feb 15 09:03 /lib/nut/bcmxcp_usb.2.6.4 -rwxr-xr-x 1 root root 80544 Feb 15 09:02 /lib/nut/bcmxcp_usb.2.7.1 And stopped both nut-client and nut-server, then started them both up. There is no change to what is displayed in the cgi, the same fields are still missing :( On 13/02/14 15:55, Alf Høgemark wrote: Hi On http://nutwiki.kanonbra.com/wiki/Category:Eaton_Powerware_5110 you can see what is reported. The unreleased part refers to v2.7.1, which is now released. OK, from that table, should the nut cgi be showing the Battery, UPS Temp and Battery Runtime values? Sorry, I don't know how these values are translated into what is shown in the cgi displays. I've got nut running, and can use upsc to get the values directly: $ ps aux | grep nut nut 18306 1.3 0.0 2640 636 ?Ss 15:14 0:00 /lib/nut/bcmxcp_usb -a Powerware5110 nut 18308 0.0 0.0 2620 708 ?Ss 15:14 0:00 /sbin/upsd nut 18326 0.0 0.0 2592 764 ?S15:14 0:00 /sbin/upsmon $ sudo upsc Powerware5110 battery.charge.low: 11 battery.voltage: 13.5 battery.voltage.low: 10 device.mfr: Eaton device.model: POWERWARE UPS700i device.part: 103004267-5591 device.serial: device.type: ups driver.name: bcmxcp_usb driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.version: 2.7.1 driver.version.internal: 0.28 input.frequency: 49.9 input.frequency.high: 55 input.frequency.low: 45 input.frequency.nominal: 50 input.quality: 2 input.transfer.boost.high: 216 input.transfer.high: 280 input.transfer.low: 186 input.transfer.trim.low: 260 input.voltage: 240 input.voltage.nominal: 240 output.current: 0.4 output.current.nominal: 1.8 output.frequency: 49.9 output.frequency.nominal: 50 output.phases: 1 output.voltage: 240 output.voltage.nominal: 240 ups.beeper.status: enabled ups.description: Line-Interactive UPS, Single Phase ups.firmware: Cont:00.50 Inve:01.50 ups.load: 24 ups.mfr: Eaton ups.model: POWERWARE UPS700i ups.power.nominal: 700 ups.serial: ups.status: OL ups.test.result: Done and passed Happy to do more checks, I see the firmware on my 5110 700VA has the same values as the 5110 500VA on the wiki, but there are a few fields different, I guess there is a difference between the wiki page and the driver in Ubuntu Trusty. Thanks, Greg ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
[Nut-upsuser] error: Unknown UPS
Hi all, I've got nut going with a Belkin F6C120auUNV. I'm able to communicate with the UPS, upsc gives data: $ sudo upsc BelkinUPS battery.charge: 37 battery.charge.low: 30 battery.charge.warning: 30 battery.runtime: 120 battery.type: PbAc battery.voltage: 23.7 ... I've enabled the CGI, and when I go to upsstats.cgi, I see a line entry like this: System: BelkinUPS Model: [error: Unknown UPS] (light blue background) Status: [error: Unknown UPS] (yellow background) Battery, Input, Output, Load, UPS Temp, Battery are all blank with a green background. hosts.conf: MONTIOR admin@localhost BelkinUPS ups.conf: [BelkinUPS] driver = usbhid-ups port = auto upsmon.conf: MONITOR BelkinUPS@localhost 1 admin ** master upsd.users: [admin] password = ** upsmon master upsset.conf: I_HAVE_SECURED_MY_CGI_DIRECTORY So I'm not sure why the cgi scripts aren't working, does anyone have a suggestion? Thanks, Greg ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] bcmxcp_usb can not communicate with Eaton Powerware 5110
Hi Arnaud, On 13/08/12 18:09, Arnaud Quette wrote: Hey Massimo and Greg, 2012/8/12 Massimo Gais massimo.g...@iki.fi mailto:massimo.g...@iki.fi On Sun, Aug 12, 2012 at 5:11 AM, Greg Vickers daehe...@iinet.net.au mailto:daehe...@iinet.net.au wrote: I have not yet gotten rid of it, so thank you very much! It's a case of download, extract, apply patch, and compile on my RPi, correct? Hello Greg, yes you can compile it directly on the RPI. See anyway that if you have the old deb package installed and you want to replace only the recompiled driver, you may have some mismatch with the pidpath/statepath directories (/var/state/ups vs /var/run/nut). I tried to make a debian package on the RPi, but it was requiring to install all the documentation tools, and I did not have enough SD disk space for that. I have finally gotten around to compiling nut with the patch! It was on my list of things to do :) use the following configuration line to get back inline with deb directives: ./configure --prefix= --includedir=/usr/include --mandir=/usr/share/man --sysconfdir=/etc/nut --localstatedir=/var --without-ssl --with-cgi --with-dev --enable-static --with-statepath=/var/run/nut --with-altpidpath=/var/run/nut --with-drvpath=/lib/nut --with-cgipath=/usr/lib/cgi-bin/nut --with-htmlpath=/usr/share/nut/www --with-pidpath=/var/run/nut --datadir=/usr/share/nut --with-pkgconfig-dir=/usr/lib/pkgconfig --with-user=nut --with-group=nut --with-udev-dir=/lib/udev --without-doc I saw that 'compile usb drivers = no' was set, and added --with-usb to get bcmxcp_usb to compile. you may also want to disable a few more things, like CGI, by using --without-cgi for example... this will lower the dependencies barrier. The only packages I had to add were 'libgd2-xmp-dev' and 'libusb-dev'. I've just tested it and it work great! Thanks very much :) The only thing plugged into this UPS is the power supply for the RaspberryPi - nut reports the load as 0.0% :) I'm going to also plug in the 5-port switch and ADSL modem/router, I expect to be online for some time when there is a local power failure :D Cheers, Greg ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] bcmxcp_usb can not communicate with Eaton Powerware 5110
On 08/08/12 20:19, Massimo Gais wrote: I have the same issue with Raspberry Pi (running 'raspbian') and Powerware 5110, and I'd like to help to solve it, as I don't have the priviledge to replace UPS :-). I'm moving my nut server from an old NSLU2 with debian squeeze (where it was working properly) to RPi as I need a miniserver with more memory to run also other tasks. So, is there any debug information that I can provide to help ? # uname -a Linux raspi0 3.1.9+ #272 PREEMPT Tue Aug 7 22:51:44 BST 2012 armv6l GNU/Linux # ldd bcmxcp_usb /usr/lib/arm-linux-gnueabihf/libcofi_rpi.so (0x40148000) libusb-0.1.so.4 = /lib/arm-linux-gnueabihf/libusb-0.1.so.4 (0x40151000) libpthread.so.0 = /lib/arm-linux-gnueabihf/libpthread.so.0 (0x40024000) libc.so.6 = /lib/arm-linux-gnueabihf/libc.so.6 (0x4016) /lib/arm-linux-gnueabihf/ld-linux.so.3 = /lib/ld-linux-armhf.so.3 (0x4005) # dpkg --list | grep -E 'nut-server|libc6|raspi-copies-and-fills' ii libc6:armhf 2.13-33 Embedded GNU C Library: Shared libraries ii libc6-dev:armhf 2.13-33 Embedded GNU C Library: Development Libraries and Header Files ii nut-server2.6.4-1 network UPS tools - core system ii raspi-copies-and-fills0.1 Optimised memcpy/memset implementation for ARM11 used in Raspberry Pi Fantastic Massimo, thank you! I have yet to replace my 5110, so if there is anything I can contribute, I will do. It looks like the only difference between our systems is the kernel version (I've put the latest rasbian image on, which has kernel 3.2.0-3-rpi). Cheers, Greg ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] bcmxcp_usb can not communicate with Eaton Powerware 5110
Hi Arnaud, On 31/07/12 01:02, Arnaud Quette wrote: Hi Greg, 2012/7/29 Greg Vickers daehe...@iinet.net.au mailto:daehe...@iinet.net.au On 22/07/12 20:14, Greg Vickers wrote: Hi Arnaud, On 18/07/12 20:59, Arnaud Quette wrote: I've just made a quick test on an Opengear ACM 50004-2 (ARM supervision appliance). For the record: - uname -a: Linux acm5004-2 2.6.30.2-uc0 #1 Tue Feb 15 09:30:54 EST 2011 armv4tl unknown - nut version: 2.4.3 (so bcmxcp_usb 0.23) - tried with a PW5110 (ups.firmware: Cont:00.50 Inve:01.50) and everything worked like a charm. That said, Charles and Kjell comments are fully valid. That is, try with the latest version (2.6.4). It has at least more debug traces to help getting visibility. I've tested with nut 2.6.4, with the same result, i.e. this driver can't communicate with the UPS. What switches should I use with the driver to provide you the debug information? More -D switches? Could you perhaps test the 5110 on your Ubuntu system, with a recent NUT? OK, tested on the Ubuntu system and it works just fine! My PW5110 has the same firmware versions as yours, and the Ubuntu system I tested on has kernel 3.2.0 on it and nut 2.6.3. I'll see if I can get kernel 3.2.0 on the RaspberryPi and report back. I've got kernel 3.2.0 on the RaspberryPi and nut 2.6.4 and the bcmxcp_usb driver reports the same problem :( damn, this would lead me to also think about a kernel or libusb issue. just to be sure, is bcmxcp_usb linked against libusb *0.1* and not 1.0-compat? $ ldd bcmxcp_usb /usr/lib/arm-linux-gnueabihf/libcofi_rpi.so (0x401b4000) libusb-0.1.so.4 = /lib/arm-linux-gnueabihf/libusb-0.1.so.4 (0x4014f000) libpthread.so.0 = /lib/arm-linux-gnueabihf/libpthread.so.0 (0x40068000) libc.so.6 = /lib/arm-linux-gnueabihf/libc.so.6 (0x401bd000) /lib/arm-linux-gnueabihf/ld-linux.so.3 = /lib/ld-linux-armhf.so.3 (0x40037000) So yes, looks like it's linked to libusb 0.1. I'm going to go with the last option I have, and will replace this UPS with one that works with this combination of architecture and OS! :) yup, still an option ;) Thanks for your help! Cheers, Greg ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] bcmxcp_usb can not communicate with Eaton Powerware 5110
On 22/07/12 20:14, Greg Vickers wrote: Hi Arnaud, On 18/07/12 20:59, Arnaud Quette wrote: I've just made a quick test on an Opengear ACM 50004-2 (ARM supervision appliance). For the record: - uname -a: Linux acm5004-2 2.6.30.2-uc0 #1 Tue Feb 15 09:30:54 EST 2011 armv4tl unknown - nut version: 2.4.3 (so bcmxcp_usb 0.23) - tried with a PW5110 (ups.firmware: Cont:00.50 Inve:01.50) and everything worked like a charm. That said, Charles and Kjell comments are fully valid. That is, try with the latest version (2.6.4). It has at least more debug traces to help getting visibility. I've tested with nut 2.6.4, with the same result, i.e. this driver can't communicate with the UPS. What switches should I use with the driver to provide you the debug information? More -D switches? Could you perhaps test the 5110 on your Ubuntu system, with a recent NUT? OK, tested on the Ubuntu system and it works just fine! My PW5110 has the same firmware versions as yours, and the Ubuntu system I tested on has kernel 3.2.0 on it and nut 2.6.3. I'll see if I can get kernel 3.2.0 on the RaspberryPi and report back. I've got kernel 3.2.0 on the RaspberryPi and nut 2.6.4 and the bcmxcp_usb driver reports the same problem :( I'm going to go with the last option I have, and will replace this UPS with one that works with this combination of architecture and OS! :) As a side note, I still hope to rewrite this driver, part of 2.8.0. It will however depend on my available time, and the progress on the main 2.8.0 items... Thanks, Greg ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] bcmxcp_usb can not communicate with Eaton Powerware 5110
Hi Arnaud, On 18/07/12 20:59, Arnaud Quette wrote: I've just made a quick test on an Opengear ACM 50004-2 (ARM supervision appliance). For the record: - uname -a: Linux acm5004-2 2.6.30.2-uc0 #1 Tue Feb 15 09:30:54 EST 2011 armv4tl unknown - nut version: 2.4.3 (so bcmxcp_usb 0.23) - tried with a PW5110 (ups.firmware: Cont:00.50 Inve:01.50) and everything worked like a charm. That said, Charles and Kjell comments are fully valid. That is, try with the latest version (2.6.4). It has at least more debug traces to help getting visibility. I've tested with nut 2.6.4, with the same result, i.e. this driver can't communicate with the UPS. What switches should I use with the driver to provide you the debug information? More -D switches? Could you perhaps test the 5110 on your Ubuntu system, with a recent NUT? OK, tested on the Ubuntu system and it works just fine! My PW5110 has the same firmware versions as yours, and the Ubuntu system I tested on has kernel 3.2.0 on it and nut 2.6.3. I'll see if I can get kernel 3.2.0 on the RaspberryPi and report back. As a side note, I still hope to rewrite this driver, part of 2.8.0. It will however depend on my available time, and the progress on the main 2.8.0 items... Thanks, Greg ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] NUT monitor
Hi Gene, On 16/07/12 07:48, Gene Ulmer wrote: I installed NUT version 2.6.3-1ubuntu1.1 w/the client and server and the nut monitor. When I open the monitor, I get an error: error connecting to 'local host' ([Errno] connection refused). What can I do to get NUT to work? I can not tell if the NUT program is working or not. I'm running Ubuntu 12.04 32 bit Installed NUT from the Synaptic Package Manager. My computer is a Systemax w/MSI motherboard K9N6GM series, 64bit. The UPS is a Tripplite AVR-550u connected to computer w/USB cable. Have you configured nut to talk to your UPS? You'll need to follow the configuration information in the nut user pages here: http://www.networkupstools.org/documentation.html I would also do a google search for 'nut tripplite avr-550u' and see what kind of information you find, I would also search ubuntuforums.org for your UPS model. At a minimum, you need to configure hosts.conf, ups.conf and upsmon.conf - you should also understand what all the options do, as this will have a critical effect on how the UPS behaves when it loses mains power. Cheers, Greg ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] bcmxcp_usb can not communicate with Eaton Powerware 5110
On 13/07/12 22:24, Charles Lepple wrote: On Jul 13, 2012, at 12:41 AM, Greg Vickers wrote: 0.238682get_answer: (128 bytes) = ab 01 79 01 02 50 00 50 01 00 0e 00 01 00 10 50 0.239445 4f 57 45 52 57 41 52 45 20 55 50 53 20 20 20 5c 00 00 00 00 00 00 00 00 00 0.240107 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 51 51 00 00 00 00 51 0.240351 00 00 00 00 00 00 00 f0 00 f0 00 00 00 f0 00 00 00 00 00 00 00 00 f0 00 00 0.240558 00 00 00 00 00 00 51 00 00 51 00 00 00 00 00 00 00 00 00 f0 00 00 00 00 00 0.241334 00 00 00 00 00 00 00 f0 18 3b ab 01 0.241969get_answer: block_number = 1 0.242121get_answer: sequence number (1) is ok 0.242254get_answer: checksum is ok 0.242891get_answer: block_number = 1 0.243072Communications with UPS lost: get_answer: not the right sequence received 0!!! Well, that's odd. I'm not an expert on this driver, but a quick read of that portion of the code implies that this shouldn't happen. The last line says the received sequence number is 0. I think the sequence number is the 4th byte (my_buf[3]), which is 1 in the hex dump you posted: http://trac.networkupstools.org/projects/nut/browser/trunk/drivers/bcmxcp_usb.c#L236 I was going to take a look at the source package to see if any extra patches were included, but it looks like there's a newer version of Debian for the Raspberry Pi (based on wheezy instead of squeeze), and it includes a newer build of NUT. It doesn't look like much has changed in the NUT source tree between 2.4.3 and 2.6.4, but there's a significant chance that Debian wheezy was built with a newer compiler. Can you give that a try? If not, I'd recommend rebuilding NUT from source, so that we can patch in a few more debug statements. Ah, thanks! I've installed nut from wheezy: $ dpkg -l nut* +++-=-=-== ii nut 2.6.4-1 network UPS tools - metapackage ii nut-cgi 2.4.3-1.1squeeze1 network UPS tools - web interface ii nut-client2.6.4-1 network UPS tools - clients ii nut-server2.6.4-1 network UPS tools - core system But when calling the driver to communicate with the UPS, the result is the same. What is the next step for debugging this driver? Thanks, Greg ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
[Nut-upsuser] bcmxcp_usb can not communicate with Eaton Powerware 5110
Hi, I have set up a RaspberryPi computer to do monitoring of two UPSs. One is an MGE evolution 800, one is an Eaton Powerware 5110. The MGE was being monitored by another Linux (Ubuntu 12.04) computer, and I just copied and pasted in the relevant nut config and it works just fine with nut. I've tried to set up the Powerware 5110 with nut, and the bcmxcp_usb driver can't communicate with the 5110. Here are the details of the RaspberryPi (I'm running the pre-built Debian distribution): $ uname -a Linux monitor 3.1.9+ #90 Wed Apr 18 18:23:05 BST 2012 armv6l GNU/Linux Here is details of the nut package: $ dpkg -l nut ||/ Name VersionDescription +++-==-==- ii nut2.4.3-1.1squeeze1 network UPS tools - core system Here is the ups.conf file: $ sudo cat /etc/nut/ups.conf [pw5110] driver = bcmxcp_usb port = auto Here's what happens when I try to get the driver to talk to the UPS: $ sudo /lib/nut/bcmxcp_usb -DD -a pw5110 Network UPS Tools - BCMXCP UPS driver 0.23 (2.4.3) USB communication subdriver 0.18 0.00debug level is '2' 0.008810device 004 opened successfully 0.011517entering get_answer(31) 0.013401get_answer: (8 bytes) = ab 01 79 01 02 50 00 50 0.014623get_answer: block_number = 1 0.015972get_answer: need to read 118 more data 0.017549get_answer: (16 bytes) = ab 01 79 01 02 50 00 50 01 00 0e 00 01 00 10 50 0.018769get_answer: block_number = 1 0.019927get_answer: need to read 110 more data 0.030671get_answer: (24 bytes) = ab 01 79 01 02 50 00 50 01 00 0e 00 01 00 10 50 0.031399 4f 57 45 52 57 41 52 45 0.031564get_answer: block_number = 1 0.032179get_answer: need to read 102 more data 0.046680get_answer: (32 bytes) = ab 01 79 01 02 50 00 50 01 00 0e 00 01 00 10 50 0.047836 4f 57 45 52 57 41 52 45 20 55 50 53 20 20 20 5c 0.048017get_answer: block_number = 1 0.048165get_answer: need to read 94 more data 0.062676get_answer: (40 bytes) = ab 01 79 01 02 50 00 50 01 00 0e 00 01 00 10 50 0.063836 4f 57 45 52 57 41 52 45 20 55 50 53 20 20 20 5c 00 00 00 00 00 00 00 00 0.064508get_answer: block_number = 1 0.064703get_answer: need to read 86 more data 0.078676get_answer: (48 bytes) = ab 01 79 01 02 50 00 50 01 00 0e 00 01 00 10 50 0.079436 4f 57 45 52 57 41 52 45 20 55 50 53 20 20 20 5c 00 00 00 00 00 00 00 00 00 0.080076 00 00 00 00 00 00 00 0.080230get_answer: block_number = 1 0.080842get_answer: need to read 78 more data 0.094677get_answer: (56 bytes) = ab 01 79 01 02 50 00 50 01 00 0e 00 01 00 10 50 0.095441 4f 57 45 52 57 41 52 45 20 55 50 53 20 20 20 5c 00 00 00 00 00 00 00 00 00 0.096094 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0.096245get_answer: block_number = 1 0.097018get_answer: need to read 70 more data 0.110676get_answer: (64 bytes) = ab 01 79 01 02 50 00 50 01 00 0e 00 01 00 10 50 0.111436 4f 57 45 52 57 41 52 45 20 55 50 53 20 20 20 5c 00 00 00 00 00 00 00 00 00 0.111642 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 51 51 00 00 00 0.112272get_answer: block_number = 1 0.112436get_answer: need to read 62 more data 0.126675get_answer: (72 bytes) = ab 01 79 01 02 50 00 50 01 00 0e 00 01 00 10 50 0.127825 4f 57 45 52 57 41 52 45 20 55 50 53 20 20 20 5c 00 00 00 00 00 00 00 00 00 0.128075 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 51 51 00 00 00 00 51 0.128694 00 00 00 00 00 00 0.128843get_answer: block_number = 1 0.128980get_answer: need to read 54 more data 0.142678get_answer: (80 bytes) = ab 01 79 01 02 50 00 50 01 00 0e 00 01 00 10 50 0.143436 4f 57 45 52 57 41 52 45 20 55 50 53 20 20 20 5c 00 00 00 00 00 00 00 00 00 0.144122 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 51 51 00 00 00 00 51 0.144361 00 00 00 00 00 00 00 f0 00 f0 00 00 00 f0 0.145140get_answer: block_number = 1 0.145314get_answer: need to read 46 more data 0.158684get_answer: (88 bytes) = ab 01 79 01 02 50 00 50 01 00 0e 00 01 00 10 50 0.159443 4f 57 45 52 57 41 52 45 20 55 50 53 20 20 20 5c 00 00 00 00 00 00 00 00 00 0.160119 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 51 51 00 00 00 00 51 0.160332 00 00 00 00 00 00 00 f0 00 f0 00 00 00 f0 00 00 00 00 00 00 00 00 0.160956get_answer: block_number = 1 0.161109get_answer: need to read 38 more data 0.174685get_answer: (96 bytes) = ab 01 79 01 02 50 00 50 01 00 0e 00 01 00 10 50 0.175448 4f 57 45 52 57 41 52 45 20 55 50 53 20 20 20 5c 00 00 00 00 00 00 00 00 00 0.176120 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 51 51 00 00 00 00 51 0.176798 00 00 00 00 00 00 00 f0
Re: [Nut-upsuser] Powerware 5110 UPS with nut in Ubuntu
Hi Arnaud, Arnaud Quette aquette@gmail.com wrote: Hi Greg first, a thank to Kjell too... 2009/7/12 Greg Vickers daehe...@optusnet.com.au Hi Kjell, Kjell Claesson wrote: Hi all, Hi Greg, I've got a Powerware 5110 UPS that I'm trying to set up with nut in Ubuntu. I've installed nut and configured the first two files: $ cat /etc/nut/nut.conf MODE=standalone $ cat /etc/nut/ups.conf [pw5110] driver = bcmxcp_usb port = auto # port = /dev/bus/usb/002/002 Yes the port should be auto. And if you use the latest libusb you should have a device at /dev/bus/usb/002/002 that you have found. When I try to test this configuration with the following command: $ sudo upsdrvctl start pw5110 Network UPS Tools - UPS driver controller 2.4.1 Network UPS Tools - BCMXCP UPS driver 0.21 (2.4.1) USB communication subdriver 0.17 Can't set POWERWARE USB configuration Unable to find POWERWARE UPS device on USB bus To make a real test that it read the usb you can do the following. Set libusb debug to 3. sudo export LIBUSB_DEBUG=3 Then run the driver in debug (not by upsdrvctl). sudo /path/to/bcmxcp_usb -DD -u -a pw5110 Now it should spit out some info. You end it by ctrl-c. Report back and we can have a look. We may have a bug here, but it is not confirmed as our tests does not reveal it. After leaving my Ubuntu host overnight, I've turned it on and the nut daemon was running when I tried the above check. I stopped that daemon and the above test worked just fine! I didn't change anything and now it's working just fine. Thank you for the information about the debug test! All OK now! :) well, ok now, but there is still something under the hood! my guess is that the udev update change introduced by Scott James doesn't fully refresh the udev rights. I've not taken the time to validate it though, so mea culpa. the result is basically that if you don't unplug/replug your device or reboot your system after nut installation, the udev rule is not applied. I did try unplugging and replugging the USB cable the UPS was attached by, and still couldn't contact the UPS correctly. I have also had trouble on this system with the IR receiver on my TV tuner card not reappearing on a reboot, I have to do a shutdown and turn the host back on to get the IR receiver device to reappear. I didn't diagnose this IR receiver problem until after that night, so I suspect that this may have impacted the UPS communication as well. However, now when I do a reboot, the UPS is detected just fine - go figure. At one point I was suspicious that the udev rule wasn't being run, and tried copying it into /etc/udev/rules.d, and un/re-plugging the UPS, but to no avail. I'll try to check that tomorrow, and make some more progress on 2.4.1-4, which will be a major Debian update. Thanks, Greg ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Powerware 5110 UPS with nut in Ubuntu
Hi Kjell, Kjell Claesson wrote: Hi all, Hi Greg, I've got a Powerware 5110 UPS that I'm trying to set up with nut in Ubuntu. I've installed nut and configured the first two files: $ cat /etc/nut/nut.conf MODE=standalone $ cat /etc/nut/ups.conf [pw5110] driver = bcmxcp_usb port = auto # port = /dev/bus/usb/002/002 Yes the port should be auto. And if you use the latest libusb you should have a device at /dev/bus/usb/002/002 that you have found. When I try to test this configuration with the following command: $ sudo upsdrvctl start pw5110 Network UPS Tools - UPS driver controller 2.4.1 Network UPS Tools - BCMXCP UPS driver 0.21 (2.4.1) USB communication subdriver 0.17 Can't set POWERWARE USB configuration Unable to find POWERWARE UPS device on USB bus To make a real test that it read the usb you can do the following. Set libusb debug to 3. sudo export LIBUSB_DEBUG=3 Then run the driver in debug (not by upsdrvctl). sudo /path/to/bcmxcp_usb -DD -u -a pw5110 Now it should spit out some info. You end it by ctrl-c. Report back and we can have a look. We may have a bug here, but it is not confirmed as our tests does not reveal it. After leaving my Ubuntu host overnight, I've turned it on and the nut daemon was running when I tried the above check. I stopped that daemon and the above test worked just fine! I didn't change anything and now it's working just fine. Thank you for the information about the debug test! All OK now! :) Cheers, Greg ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
[Nut-upsuser] Powerware 5110 UPS with nut in Ubuntu
Hi all, I've got a Powerware 5110 UPS that I'm trying to set up with nut in Ubuntu. I've installed nut and configured the first two files: $ cat /etc/nut/nut.conf MODE=standalone $ cat /etc/nut/ups.conf [pw5110] driver = bcmxcp_usb port = auto # port = /dev/bus/usb/002/002 When I try to test this configuration with the following command: $ sudo upsdrvctl start pw5110 Network UPS Tools - UPS driver controller 2.4.1 Network UPS Tools - BCMXCP UPS driver 0.21 (2.4.1) USB communication subdriver 0.17 Can't set POWERWARE USB configuration Unable to find POWERWARE UPS device on USB bus Things to try: - Connect UPS device to USB bus - Run this driver as another user (upsdrvctl -u or 'user=...' in ups.conf). See upsdrvctl(8) and ups.conf(5). Fatal error: unusable configuration Driver failed to start (exit status=1) I found which device was being created by the udev rules and the device /dev/bus/usb/002/002 does exist and the group is set to 'nut'. (You can see that I have tried specifying the port as this device, to no avail.) I'm obviously missing something, does anyone have any suggestions? Thanks, Greg ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
