Re: [Nut-upsuser] Update on gnome-power-manager
Hi Philip, 2011/1/8 Phillip Susi ps...@cfl.rr.com The FAQ mentions how to configure nut to pass the power information to HAL so that gnome-power-manager can display it, but HAL has been depreciated and removed from Ubuntu since 2007. Has nut been updated to worth with UPower instead? no, not yet. I've been hesitating for long, on either removing this or updating it to feed UPower. my stance is now that NUT will allows to feed UPower, for any kind of driver (including serial). but this will need some more investigation and work, that I'm willing to put during the 2.8 development cycle (ie once 2.6.0 is out... this week). In the meantime, I'm interested in feedback. So if you have any remark, I'd happy to hear these... cheers, Arnaud -- Linux / Unix Expert RD - Eaton - http://powerquality.eaton.com Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.free.fr/ ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Can't get iDowell to work
Hi Mick 2011/1/9 Mick michaelkintz...@gmail.com (Apologies for the long message, but there's a lot to report here.) After a lot of help from Kjell (thank you!) I am now testing the 2.6.0-pre1 version with a usbhid-ups that recognises my UPS: # /etc/init.d/upsdrv start * Starting UPS drivers ... Network UPS Tools - UPS driver controller 2.6.0-pre1 Network UPS Tools - Generic HID driver 0.35 (2.6.0-pre1) USB communication driver 0.31 Using subdriver: iDowell HID 0.1 libusb_get_report: No error libusb_get_report: No error libusb_get_report: No error libusb_get_report: No error libusb_get_report: No error libusb_get_report: No error libusb_get_report: No error libusb_get_report: No error libusb_get_report: No error libusb_get_report: No error libusb_get_report: No error libusb_get_report: No error libusb_get_report: No error libusb_get_report: No error libusb_get_report: No error libusb_get_report: No error [ ok ] # /etc/init.d/upsd start * Starting upsd ... Network UPS Tools upsd 2.6.0-pre1 listening on 127.0.0.1 port 3493 Connected to UPS [iDowell]: usbhid-ups-iDowell allowfrom in upsd.users is no longer used [ ok ] # upsc iDowell battery.capacity: 0.03 battery.charge: 100 battery.charge.low: 15 battery.runtime: 342 --this seems to fluctuate this is calculated and reported by the device . nothing we can do about in NUT... device.mfr: iDowell device.model: iBox device.serial: 0001 device.type: ups driver.flag.pollonly: enabled driver.name: usbhid-ups driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.version: 2.6.0-pre1 driver.version.data: iDowell HID 0.1 driver.version.internal: 0.35 ups.delay.shutdown: 20 ups.delay.start: 30 ups.mfr: iDowell ups.model: iBox ups.productid: 0300 ups.serial: 0001 ups.status: OL CHRG ups.vendorid: 075d There does seem to be one problem with my system which generates reports like this before I start upsdrv: === Jan 9 19:23:20 compaq kernel: usb 3-2: USB disconnect, address 4 Jan 9 19:23:21 compaq kernel: usb 3-2: new low speed USB device using uhci_hcd and address 5 Jan 9 19:23:21 compaq kernel: usb 3-2: new low speed USB device using uhci_hcd and address 5 Jan 9 19:23:21 compaq kernel: usb 3-2: New USB device found, idVendor=075d, idProduct=0300 Jan 9 19:23:21 compaq kernel: usb 3-2: New USB device found, idVendor=075d, idProduct=0300 Jan 9 19:23:21 compaq kernel: usb 3-2: New USB device strings: Mfr=3, Product=1, SerialNumber=2 Jan 9 19:23:21 compaq kernel: usb 3-2: New USB device strings: Mfr=3, Product=1, SerialNumber=2 Jan 9 19:23:21 compaq kernel: usb 3-2: Product: iBox Jan 9 19:23:21 compaq kernel: usb 3-2: Product: iBox Jan 9 19:23:21 compaq kernel: usb 3-2: Manufacturer: iDowell Jan 9 19:23:21 compaq kernel: usb 3-2: Manufacturer: iDowell Jan 9 19:23:21 compaq kernel: usb 3-2: SerialNumber: 0001 Jan 9 19:23:21 compaq kernel: usb 3-2: SerialNumber: 0001 Jan 9 19:23:21 compaq kernel: generic-usb 0003:075D:0300.0005: hidraw1: USB HID v1.10 Device [iDowell iBox] on usb-:00:1d.1-2/input0 Jan 9 19:23:21 compaq kernel: generic-usb 0003:075D:0300.0005: hidraw1: USB HID v1.10 Device [iDowell iBox] on usb-:00:1d.1-2/input0 Jan 9 19:23:36 compaq kernel: usb 3-2: USB disconnect, address 5 Jan 9 19:23:36 compaq kernel: usb 3-2: USB disconnect, address 5 ... === (it'll keep disconnecting and reconnecting) and like this after I connect to it with upsdrv: === Jan 9 19:24:45 compaq usbhid-ups[5228]: Startup successful Jan 9 19:24:45 compaq usbhid-ups[5228]: Startup successful Jan 9 19:24:45 compaq usbhid-ups[5228]: libusb_get_report: No error Jan 9 19:24:46 compaq upsd[4933]: Connected to UPS [iDowell]: usbhid-ups-iDowell Jan 9 19:24:46 compaq upsd[4933]: Connected to UPS [iDowell]: usbhid-ups-iDowell Jan 9 19:24:47 compaq usbhid-ups[5228]: libusb_get_report: could not claim interface 0: Device or resource busy Jan 9 19:24:47 compaq usbhid-ups[5228]: Got disconnected by another driver: Device or resource busy Jan 9 19:24:49 compaq usbhid-ups[5228]: libusb_get_report: could not claim interface 0: Device or resource busy Jan 9 19:24:49 compaq usbhid-ups[5228]: Got disconnected by another driver: Device or resource busy Jan 9 19:24:51 compaq usbhid-ups[5228]: libusb_get_report: could not claim interface 0: Device or resource busy Jan 9 19:24:51 compaq usbhid-ups[5228]: Got disconnected by another driver: Device or resource busy Jan 9 19:24:53 compaq usbhid-ups[5228]: libusb_get_report: could not claim interface 0: Device or resource busy === ... and so on. At the
Re: [Nut-upsuser] Success and USB IDs for TrippLite SmartOnline SU1000RTXL2ua
Hi Michael, 2011/1/7 Michael Hatzakis Jr MD m...@hatzakis.net Michael Michael Hatzakis, Jr MD Physical Medicine and Rehabilitation you have probably missed a piece of your mail ;-) cheers, Arnaud -- Linux / Unix Expert RD - Eaton - http://powerquality.eaton.com Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.free.fr/ ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] upsd crashes with a broken pipe error
2011/1/5 Zach La Celle lace...@roboticresearch.com
On 01/04/2011 08:20 AM, Arnaud Quette wrote:
2011/1/4 Charles Lepple clep...@gmail.com
On Mon, Jan 3, 2011 at 8:29 AM, Zach La Celle
lace...@roboticresearch.com wrote:
On 12/29/2010 10:00 AM, Zach La Celle wrote:
On 12/29/2010 08:34 AM, Charles Lepple wrote:
On Dec 27, 2010, at 9:36 AM, Zach La Celle wrote:
I ran this in debug mode and captures the backtrace.
r...@*:/etc/nut# upsd -D
Network UPS Tools upsd 2.4.3
0.00 listening on 0.0.0.0 port 3493
0.000354 Connected to UPS [rack1ups]: apcsmart-rack1ups
2.550554 User ups...@127.0.0.1 logged into UPS [rack1ups]
*** glibc detected *** upsd: free(): invalid next size (fast):
0x012c9870 ***
Can you give us some background information about this system? What
OS
and version, who built the package, etc.
Just to be sure, are you running the Ubuntu-provided package, or
something from another package repository? Which version of Ubuntu?
Running valgrind might produce similarly opaque results without debug
symbols (which you can enable if you build from source).
debug syms are available as separate debs.
As an example, for Ubuntu, look here:
https://wiki.kubuntu.org/DebuggingProgramCrash
then look for installing {nut,libupsclient}-dbgsym and others if needed
otherwise...
That is a bit
more involved, though (especially if you want to keep the installed
files in the same place) so I'd try that after Arjen's suggestion with
-DDD.
seconded for a first run.
cheers,
Arnaud
--
Linux / Unix Expert RD - Eaton - http://powerquality.eaton.com
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.free.fr/
The only extra package I could find is the dev package. I'm not sure
if
that contains debugging symbols.
I'm running with the -DDD option now. It hasn't crashed over the
weekend, so we'll see how long it takes to crash now. I'm getting
source to
try and rebuild it so that I can walk through in GDB if necessary.
have you looked at the pointer I've sent, *and* applied the various
mentioned actions (adding key and repository, refresh apt cache, ...)?
otherwise, you won't see these packages!
I still fail to see what is your exact system (Ubuntu? which version?)
apart
from the arch which is x86_64...
cheers,
Arnaud
--
Linux / Unix Expert RD - Eaton - http://powerquality.eaton.com
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.free.fr/
I'm sorry, I'll be more specific. I'm running Ubuntu Server, 10.04.
The problem has reoccurred with a little more information. It seems like
a particular query fails, which causes the crash.
I'm sorry to paste the entire printout, but I think it might help. I'm
not sure what mailing list etiquette is for attaching files.
264490.001405 write: [destfd=6] [len=34] [VAR rack1ups ups.status TRIM
OL]
264490.001440 mainloop: polling 3 filedescriptors
264490.338233 mainloop: polling 3 filedescriptors
264492.340332 mainloop: no data available
264492.340379 mainloop: polling 3 filedescriptors
264494.342463 mainloop: no data available
264494.342503 mainloop: polling 3 filedescriptors
264495.001776 write: [destfd=6] [len=34] [VAR rack1ups ups.status TRIM
OL]
264495.001817 mainloop: polling 3 filedescriptors
264497.003930 mainloop: no data available
264497.003984 mainloop: polling 3 filedescriptors
264497.148206 mainloop: polling 3 filedescriptors
264499.150306 mainloop: no data available
264499.150356 mainloop: polling 3 filedescriptors
264500.002191 write: [destfd=6] [len=34] [VAR rack1ups ups.status TRIM
OL]
264500.002228 mainloop: polling 3 filedescriptors
264502.004317 mainloop: no data available
264502.004371 mainloop: polling 3 filedescriptors
264502.348230 mainloop: polling 3 filedescriptors
264502.407564 Connect from **.**.**.**
264502.407607 mainloop: polling 4 filedescriptors
264502.407654 write: [destfd=7] [len=21] [ERR INVALID-ARGUMENT]
264502.407675 write: [destfd=7] [len=20] [ERR UNKNOWN-COMMAND]
264502.407690 mainloop: polling 4 filedescriptors
264503.118172 mainloop: polling 4 filedescriptors
264504.409126 Disconnect **.**.**.** (no data available)
264504.409170 Disconnect from **.**.**.**
264504.409209 mainloop: polling 3 filedescriptors
264505.002641 write: [destfd=6] [len=34] [VAR rack1ups ups.status TRIM
OL]
264505.002672 mainloop: polling 3 filedescriptors
264505.168211 mainloop: polling 3 filedescriptors
264506.218088 mainloop: polling 3 filedescriptors
264508.208199 mainloop: polling 3 filedescriptors
264509.148184 mainloop: polling 3 filedescriptors
264510.003107 write: [destfd=6] [len=34] [VAR rack1ups ups.status TRIM
OL]
264510.003153 mainloop: polling
Re: [Nut-upsuser] Update on gnome-power-manager
On 1/10/2011 7:03 AM, Arnaud Quette wrote: no, not yet. I've been hesitating for long, on either removing this or updating it to feed UPower. my stance is now that NUT will allows to feed UPower, for any kind of driver (including serial). but this will need some more investigation and work, that I'm willing to put during the 2.8 development cycle (ie once 2.6.0 is out... this week). In the meantime, I'm interested in feedback. So if you have any remark, I'd happy to hear these... When you come up with some patches I'll be happy to test. I have an old CyperPower 1000AVR with a serial interface. I've never even tried to get it running under Linux because I figured they used a proprietary protocol, but recently I found nut and noticed it supports it. It would be nice to be able to see the stats in gnome-power-manager. I just replaced the batteries again a few weeks ago and it would be nice to be able to monitor the battery voltage and do a load test periodically and tell when the batteries are getting weak before they just fail outright during a black/brown out. ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] upsd crashes with a broken pipe error
On 01/06/2011 08:06 AM, Arnaud Quette wrote:
2011/1/5 Zach La Celle lace...@roboticresearch.com
mailto:lace...@roboticresearch.com
On 01/04/2011 08:20 AM, Arnaud Quette wrote:
2011/1/4 Charles Lepple clep...@gmail.com
mailto:clep...@gmail.com
On Mon, Jan 3, 2011 at 8:29 AM, Zach La Celle
lace...@roboticresearch.com
mailto:lace...@roboticresearch.com wrote:
On 12/29/2010 10:00 AM, Zach La Celle wrote:
On 12/29/2010 08:34 AM, Charles Lepple wrote:
On Dec 27, 2010, at 9:36 AM, Zach La Celle wrote:
I ran this in debug mode and captures the backtrace.
r...@*:/etc/nut# upsd -D
Network UPS Tools upsd 2.4.3
0.00 listening on 0.0.0.0 port 3493
0.000354 Connected to UPS [rack1ups]: apcsmart-rack1ups
2.550554 User ups...@127.0.0.1
mailto:ups...@127.0.0.1 logged into UPS [rack1ups]
*** glibc detected *** upsd: free(): invalid next size
(fast):
0x012c9870 ***
Can you give us some background information about this
system? What OS
and version, who built the package, etc.
Just to be sure, are you running the Ubuntu-provided package, or
something from another package repository? Which version of
Ubuntu?
Running valgrind might produce similarly opaque results
without debug
symbols (which you can enable if you build from source).
debug syms are available as separate debs.
As an example, for Ubuntu, look here:
https://wiki.kubuntu.org/DebuggingProgramCrash
then look for installing {nut,libupsclient}-dbgsym and others if
needed otherwise...
That is a bit
more involved, though (especially if you want to keep the
installed
files in the same place) so I'd try that after Arjen's
suggestion with
-DDD.
seconded for a first run.
cheers,
Arnaud
--
Linux / Unix Expert RD - Eaton - http://powerquality.eaton.com
Network UPS Tools (NUT) Project Leader -
http://www.networkupstools.org/
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.free.fr/
The only extra package I could find is the dev package. I'm not
sure if that contains debugging symbols.
I'm running with the -DDD option now. It hasn't crashed over
the weekend, so we'll see how long it takes to crash now. I'm
getting source to try and rebuild it so that I can walk through in
GDB if necessary.
have you looked at the pointer I've sent, *and* applied the various
mentioned actions (adding key and repository, refresh apt cache, ...)?
otherwise, you won't see these packages!
I still fail to see what is your exact system (Ubuntu? which version?)
apart from the arch which is x86_64...
cheers,
Arnaud
--
Linux / Unix Expert RD - Eaton - http://powerquality.eaton.com
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.free.fr/
I'm having trouble finding the upsd source code, or maybe I just don't
understand how to run it properly. The source I have for ubuntu/lucid
seems to either be for a different UPSD project, or to run very
differently than the version off of the Ubuntu repositories. Can you
point me to the correct source for upsd?
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Can't get iDowell to work
On 10 January 2011 20:28, Mick michaelkintz...@gmail.com wrote: On Monday 10 January 2011 12:19:34 you wrote: Hi Mick 2011/1/9 Mick michaelkintz...@gmail.com -rwxr-xr-x 1 root root 17840 Jul 25 11:45 /usr/libexec/hald-addon-hid-ups [snip ...] Could any of the above be causing the clash? indeed, /usr/libexec/hald-addon-hid-ups which is part of UPower (integrated power management), which is automatically launched when a new USB/HID UPS is plugged. since UPower is running as root, it will prevent usbhid-ups from claiming back your UPS after software disconnection. you may try to run nut as root to check if you still see the claim interface failure. I'll have to check UPower, since iirc, it wasn't previously running as root (or I'm maybe confusing with HAL...) So assuming that the new driver can now deal with my UPS, is this something that I'll have wait for to settle, as hal is deprecated and on a path to be replaced with upower? Some more testing tonight and after a reboot I get this. :-) # upsc iDowell battery.capacity: 0.03 battery.charge: 100 battery.charge.low: 15 battery.runtime: 650 device.mfr: iDowell device.model: iBox device.serial: 0001 device.type: ups driver.name: usbhid-ups driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.parameter.productid: 0300 driver.parameter.vendorid: 075d driver.version: 2.6.0-pre1 driver.version.data: iDowell HID 0.1 driver.version.internal: 0.35 ups.delay.shutdown: 20 ups.delay.start: 30 ups.mfr: iDowell ups.model: iBox ups.productid: 0300 ups.serial: 0001 ups.status: OL CHRG ups.timer.start: 0 ups.vendorid: 075d While nut is running, my logs fill up with: Jan 10 22:50:06 compaq usbhid-ups[5083]: libusb_get_report: No error Jan 10 22:50:08 compaq usbhid-ups[5083]: libusb_get_report: No error Jan 10 22:50:10 compaq usbhid-ups[5083]: libusb_get_report: No error Jan 10 22:50:12 compaq usbhid-ups[5083]: libusb_get_report: No error regularly at 2 second intervals. Is there a way to tell it to not log such messages (or log them only once?) If I add pollonly in ups.conf I get these messages: Jan 10 23:15:57 compaq upsd[5995]: listening on 127.0.0.1 port 3493 Jan 10 23:15:57 compaq upsd[5995]: Connected to UPS [iDowell]: usbhid-ups-iDowell Jan 10 23:15:57 compaq upsd[5995]: allowfrom in upsd.users is no longer used Jan 10 23:15:57 compaq upsd[5996]: Startup successful Jan 10 23:15:57 compaq usbhid-ups[5945]: libusb_get_report: could not claim interface 0: Device or resource busy Jan 10 23:15:57 compaq usbhid-ups[5945]: Got disconnected by another driver: Device or resource busy Jan 10 23:15:59 compaq usbhid-ups[5945]: libusb_get_report: could not claim interface 0: Device or resource busy Jan 10 23:15:59 compaq usbhid-ups[5945]: Got disconnected by another driver: Device or resource busy ... and so on. Not sure if this is how it should be - but within a few minutes I get: # upsc iDowell Error: Data stale PS. What is the meaning of: battery.capacity: 0.03 ? -- Regards, Mick ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Can't get iDowell to work
Citeren Mick michaelkintz...@gmail.com:
While nut is running, my logs fill up with:
Jan 10 22:50:06 compaq usbhid-ups[5083]: libusb_get_report: No error
Jan 10 22:50:08 compaq usbhid-ups[5083]: libusb_get_report: No error
Jan 10 22:50:10 compaq usbhid-ups[5083]: libusb_get_report: No error
Jan 10 22:50:12 compaq usbhid-ups[5083]: libusb_get_report: No error
regularly at 2 second intervals. Is there a way to tell it to not log
such messages (or log them only once?)
Yes. Make your system not log messages at LOG_DEBUG. Usually you can
configure this in '/etc/syslog.conf'. On a production system, you
should not log messages with LOG_DEBUG since this is reserved for
debugging messages and can be very verbose (risking flooding the logs).
If I add pollonly in ups.conf I get these messages:
Jan 10 23:15:57 compaq upsd[5995]: listening on 127.0.0.1 port 3493
Jan 10 23:15:57 compaq upsd[5995]: Connected to UPS [iDowell]:
usbhid-ups-iDowell
Jan 10 23:15:57 compaq upsd[5995]: allowfrom in upsd.users is no longer used
Jan 10 23:15:57 compaq upsd[5996]: Startup successful
Jan 10 23:15:57 compaq usbhid-ups[5945]: libusb_get_report: could not
claim interface 0: Device or resource busy
Jan 10 23:15:57 compaq usbhid-ups[5945]: Got disconnected by another
driver: Device or resource busy
Jan 10 23:15:59 compaq usbhid-ups[5945]: libusb_get_report: could not
claim interface 0: Device or resource busy
Jan 10 23:15:59 compaq usbhid-ups[5945]: Got disconnected by another
driver: Device or resource busy
... and so on.
Not sure if this is how it should be - but within a few minutes I get:
# upsc iDowell
Error: Data stale
You *must* stop the usbhid-ups driver for a UPS before starting a new
one. The message Got disconnected by another driver: Device or
resource busy is a tell tale sign that you didn't. Before running
'upsdrvctl start', always run 'upsdrvctl stop' first. A crude method
would be to reboot the system, if you can't find the running
usbhid-ups processes. I usually use 'top -u upsd' ('upsd' is the name
of the NUT user on my system) to find any drivers running.
PS. What is the meaning of: battery.capacity: 0.03 ?
This is a mapping problem. The UPS is reporting 100% battery capacity
is available and I mistakenly mapped this to the battery capacity (Ah)
value. I will remove this later on.
Best regards, Arjen
--
Please keep list traffic on the list (off-list replies will be rejected)
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
