[Bug 226405] Re: Missing support for upsmon only configuration (slave)
A MIR for a nut-client package (and some others) is underway: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/816414 better late than never... cheers, Arnaud ** Changed in: nut (Ubuntu) Status: Triaged = Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/226405 Title: Missing support for upsmon only configuration (slave) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/226405/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Blueprint server-o-infra-power] Infrastructure power management
Blueprint changed by Arnaud Quette: Whiteboard changed: Work items: [fredericbohe] Implement device discovery tools / libs / binding in NUT: INPROGRESS [aquette] Implement configuration library and tool for NUT: TODO [aquette] Create Augeas lenses for configuration for NUT: DONE - [aquette] Distribute NUT Augeas lenses: INPROGRESS - [aquette] Distribute the new NUT documentation: INPROGRESS - [aquette] Create a NUT client only (upsmon) package: INPROGRESS + [bigon] Distribute NUT Augeas lenses: INPROGRESS + [bigon] Distribute the new NUT documentation: INPROGRESS + [bigon] Create a NUT client only (upsmon) package: INPROGRESS [aquette] Convert initscripts to upstart: TODO [aquette] Create Avahi publication script for : DONE [aquette] Implement a native NUT PSU (power supply unit) / IPMI driver, using FreeIPMI: INPROGRESS [aquette] MIR for libfreeipmi and libipmimonitoring for nut-ipmi: TODO [aquette] Implement PowerChain in NUT: INPROGRESS [zulcss] Investigate and implement NUT Puppet integration: TODO [zulcss] Investigate and implement NUT cobbler integration: TODO [zulcss] Investigate and implement NUT Orchestra integration: TODO [zulcss] Investigate and implement NUT Ensemble integration: TODO Investigate and implement NUT Ensemble integration: TODO [aquette] Implement improved PDU and power devices support in fence-agents: DONE [andreserl] provide fence-agents package (part of server-o-cluster-stack): DONE [andreserl] Investigate PowerNap using NUT as a data broker: INPROGRESS [aquette] Investigate PowerNap using NUT as a data broker: INPROGRESS [andreserl] Implement NUT client support in PowerWake: TODO [aquette] Implement NUT client support in PowerWake: TODO [bencer] Implement NUT support in Zentyal: TODO [aquette] Implement NUT support in Zentyal: TODO [cr3] Implement support for UPS testing in Checkbox using NUT: TODO [aquette] Implement support for UPS testing in Checkbox using NUT: TODO Remaining questions: - is Augeas support sufficient for configuration, or does it need a more advanced wrapper? - related to the above, is a configuration library / tool needed? - @zulcss: does Nagios nut plug-in offer sufficient features for your purpose? - MIR for FreeIPMI? == Items to consider == 1. Implement power support in Cloud schedulers using NUT: TODO (lack an assignee) 2. Create power consumption reports (not ready for billing, only informative) 3. Asset management support for power devices. Ie, Provide device information like manufacturer name and model, serial number, location, contact, service dates, ... -- Infrastructure power management https://blueprints.launchpad.net/ubuntu/+spec/server-o-infra-power -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 816414] [NEW] [MIR] nut (nut-doc, nut-client, nut-server)
moreover, it's part of the ServerOneiricInfraPower blueprint: https://blueprints.launchpad.net/ubuntu/+spec/server-o-infra-power 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/ -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in Ubuntu. https://bugs.launchpad.net/bugs/816414 Title: [MIR] nut (nut-doc, nut-client, nut-server) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/816414/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 816414] [NEW] [MIR] nut (nut-doc, nut-client, nut-server)
moreover, it's part of the ServerOneiricInfraPower blueprint: https://blueprints.launchpad.net/ubuntu/+spec/server-o-infra-power 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/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/816414 Title: [MIR] nut (nut-doc, nut-client, nut-server) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/816414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 815760] Re: 2.6.1-2ubuntu1 FTBFS on i386
Hi James, thanks for your report. 2011/7/25 James Page 815...@bugs.launchpad.net Reproduced locally in sbuild environment; a bit more information on the failure: xsltproc --stringparam callout.graphics 0 --stringparam navig.graphics 0 --stringparam admon.textlabel 1 --stringparam admon.graphics 0 --stringparam base.dir user-manual.chunked/ /etc/asciidoc/docbook-xsl/chunked.xsl /build/jamespage-nut_2.6.1-2ubuntu1-i386-VnuJ0Q/nut-2.6.1/docs/user-manual.xml warning: failed to load external entity http://docbook.sourceforge.net/release/xsl/current/xhtml/docbook.xsl; compilation error: file http://docbook.sourceforge.net/release/xsl/current/xhtml/chunk.xsl line 25 element import xsl:import : unable to load http://docbook.sourceforge.net/release/xsl/current/xhtml/docbook.xsl strange. Can you please try with the verbose version: $ ASCIIDOC_VERBOSE=-v make we should get more info, since the above is probably not the actual issue... 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/ -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in Ubuntu. https://bugs.launchpad.net/bugs/815760 Title: 2.6.1-2ubuntu1 FTBFS on i386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/815760/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 815760] Re: 2.6.1-2ubuntu1 FTBFS on i386
Hi James, thanks for your report. 2011/7/25 James Page 815...@bugs.launchpad.net Reproduced locally in sbuild environment; a bit more information on the failure: xsltproc --stringparam callout.graphics 0 --stringparam navig.graphics 0 --stringparam admon.textlabel 1 --stringparam admon.graphics 0 --stringparam base.dir user-manual.chunked/ /etc/asciidoc/docbook-xsl/chunked.xsl /build/jamespage-nut_2.6.1-2ubuntu1-i386-VnuJ0Q/nut-2.6.1/docs/user-manual.xml warning: failed to load external entity http://docbook.sourceforge.net/release/xsl/current/xhtml/docbook.xsl; compilation error: file http://docbook.sourceforge.net/release/xsl/current/xhtml/chunk.xsl line 25 element import xsl:import : unable to load http://docbook.sourceforge.net/release/xsl/current/xhtml/docbook.xsl strange. Can you please try with the verbose version: $ ASCIIDOC_VERBOSE=-v make we should get more info, since the above is probably not the actual issue... 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/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/815760 Title: 2.6.1-2ubuntu1 FTBFS on i386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/815760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 578200] Re: (megatec_usb) error: Driver not connected
guys, this seems related to a udev issue. things to try: - stop nut (sudo service nut stop ; killall -9 megatec_usb) - start the driver and server as root (sudo /lib/nut/megatec_usb -u root -a belkin-ups sudo upsd -u root) - then check using upsc you should also try the blazer_usb driver, as it has since replaced megatec_usb. finally, using packages from natty or maverick may be an option -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in Ubuntu. https://bugs.launchpad.net/bugs/578200 Title: (megatec_usb) error: Driver not connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/578200/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 578200] Re: (megatec_usb) error: Driver not connected
guys, this seems related to a udev issue. things to try: - stop nut (sudo service nut stop ; killall -9 megatec_usb) - start the driver and server as root (sudo /lib/nut/megatec_usb -u root -a belkin-ups sudo upsd -u root) - then check using upsc you should also try the blazer_usb driver, as it has since replaced megatec_usb. finally, using packages from natty or maverick may be an option -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/578200 Title: (megatec_usb) error: Driver not connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/578200/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 608182] Re: problems with ups (mge pulsar es 8+)
2011/7/18 Dave Walker davewal...@ubuntu.com @Arnaud, I'm confused as to the current status of this bug. Is there anything that needs to be done? @Dave: I'm not completely sure. the user has found a workaround. IMHO, we are probably facing some race condition between upstart native script Vs sysV, and udev serial port privileges. @Wolfgang: any update on your issue? how have you configured privileges on your serial port? (refer to /usr/share/doc/nut/README.Debian.gz, (II) - (3) - (b)) have you tried moving up the NUT (sysV) script' priority? Ie $ sudo update-rc.d nut start 90 2 3 4 5 . stop 90 0 1 6 . and reboot the system... 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/ -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in Ubuntu. https://bugs.launchpad.net/bugs/608182 Title: problems with ups (mge pulsar es 8+) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/608182/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 608182] Re: problems with ups (mge pulsar es 8+)
2011/7/18 Dave Walker davewal...@ubuntu.com @Arnaud, I'm confused as to the current status of this bug. Is there anything that needs to be done? @Dave: I'm not completely sure. the user has found a workaround. IMHO, we are probably facing some race condition between upstart native script Vs sysV, and udev serial port privileges. @Wolfgang: any update on your issue? how have you configured privileges on your serial port? (refer to /usr/share/doc/nut/README.Debian.gz, (II) - (3) - (b)) have you tried moving up the NUT (sysV) script' priority? Ie $ sudo update-rc.d nut start 90 2 3 4 5 . stop 90 0 1 6 . and reboot the system... 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/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/608182 Title: problems with ups (mge pulsar es 8+) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/608182/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 811976] [NEW] Update nut to 2.6.1-2
Public bug reported: Debian (Laurent Bigonville) has released a package update: Changes: nut (2.6.1-2) unstable; urgency=low . * debian/nut.README.Debian: Adjust udev rules naming for permissions override (Closes: #529664) * Re-add and refresh debian/patches/0001-fix_spelling_and_typo.patch: Some typos and spelling errors remain. * Split nut package into nut-client and nut-server, keep nut package as metapackage * Generate PDF and html doc and install it in nut-doc package * debian/rules: - List non-installed files - Includes python-module.mk - Add flags to build documentation and install it * debian/control: - Add python-nut package and add python build-dependency - Set nut-powerman-pdu priority to extras - Add nut-monitor package - Add nut-doc package and add required C/R/P - Add libups-nut-perl package * debian/nut-server.prerm: Remove /var/run/nut during removal ** Affects: nut (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in Ubuntu. https://bugs.launchpad.net/bugs/811976 Title: Update nut to 2.6.1-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/811976/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 811976] [NEW] Update nut to 2.6.1-2
Public bug reported: Debian (Laurent Bigonville) has released a package update: Changes: nut (2.6.1-2) unstable; urgency=low . * debian/nut.README.Debian: Adjust udev rules naming for permissions override (Closes: #529664) * Re-add and refresh debian/patches/0001-fix_spelling_and_typo.patch: Some typos and spelling errors remain. * Split nut package into nut-client and nut-server, keep nut package as metapackage * Generate PDF and html doc and install it in nut-doc package * debian/rules: - List non-installed files - Includes python-module.mk - Add flags to build documentation and install it * debian/control: - Add python-nut package and add python build-dependency - Set nut-powerman-pdu priority to extras - Add nut-monitor package - Add nut-doc package and add required C/R/P - Add libups-nut-perl package * debian/nut-server.prerm: Remove /var/run/nut during removal ** Affects: nut (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/811976 Title: Update nut to 2.6.1-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/811976/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Blueprint server-o-infra-power] Infrastructure power management
Blueprint changed by Arnaud Quette: Whiteboard changed: Work items: [fredericbohe] Implement device discovery tools / libs / binding in NUT: INPROGRESS [aquette] Implement configuration library and tool for NUT: TODO [aquette] Create Augeas lenses for configuration for NUT: DONE [aquette] Distribute NUT Augeas lenses: INPROGRESS [aquette] Distribute the new NUT documentation: INPROGRESS [aquette] Create a NUT client only (upsmon) package: INPROGRESS [aquette] Convert initscripts to upstart: TODO [aquette] Create Avahi publication script for : DONE [aquette] Implement a native NUT PSU (power supply unit) / IPMI driver, using FreeIPMI: INPROGRESS + [aquette] MIR for libfreeipmi and libipmimonitoring for nut-ipmi: TODO [aquette] Implement PowerChain in NUT: INPROGRESS [zulcss] Investigate and implement NUT Puppet integration: TODO [zulcss] Investigate and implement NUT cobbler integration: TODO [zulcss] Investigate and implement NUT Orchestra integration: TODO [zulcss] Investigate and implement NUT Ensemble integration: TODO Investigate and implement NUT Ensemble integration: TODO [aquette] Implement improved PDU and power devices support in fence-agents: DONE [andreserl] provide fence-agents package (part of server-o-cluster-stack): DONE [andreserl] Investigate PowerNap using NUT as a data broker: INPROGRESS [aquette] Investigate PowerNap using NUT as a data broker: INPROGRESS [andreserl] Implement NUT client support in PowerWake: TODO [aquette] Implement NUT client support in PowerWake: TODO [bencer] Implement NUT support in Zentyal: TODO [aquette] Implement NUT support in Zentyal: TODO [cr3] Implement support for UPS testing in Checkbox using NUT: TODO [aquette] Implement support for UPS testing in Checkbox using NUT: TODO Remaining questions: - is Augeas support sufficient for configuration, or does it need a more advanced wrapper? - related to the above, is a configuration library / tool needed? - @zulcss: does Nagios nut plug-in offer sufficient features for your purpose? - MIR for FreeIPMI? == Items to consider == 1. Implement power support in Cloud schedulers using NUT: TODO (lack an assignee) 2. Create power consumption reports (not ready for billing, only informative) 3. Asset management support for power devices. Ie, Provide device information like manufacturer name and model, serial number, location, contact, service dates, ... -- Infrastructure power management https://blueprints.launchpad.net/ubuntu/+spec/server-o-infra-power -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 779512] Re: nut-2.6.0-1ubuntu3 behavior regression
Hi Martin, 2011/6/27 Martin Ewing martin.s.ew...@gmail.com I have a very similar situation with my Belkin UPS on Natty (worked on previous release). See $ lsb_release -rd Description:Ubuntu 11.04 Release:11.04 martin@gimli:~$ aptitude show nut Package: nut State: installed Automatically installed: no Version: 2.6.0-1ubuntu3 ... sudo /lib/nut/usbhid-ups - -a mybelkin Network UPS Tools - Generic HID driver 0.35 (2.6.0) USB communication driver 0.31 0.00 debug level is '4' 0.000583 upsdrv_initups... 0.266176 Checking device (1D6B/0001) (008/001) 0.266219 - VendorID: 1d6b 0.266226 - ProductID: 0001 0.266232 - Manufacturer: unknown 0.266237 - Product: unknown 0.266242 - Serial Number: unknown 0.266247 - Bus: 008 0.266252 Trying to match device 0.266275 Device does not match - skipping 0.266285 Checking device (1D6B/0001) (007/001) 0.266303 - VendorID: 1d6b 0.266309 - ProductID: 0001 0.266315 - Manufacturer: unknown 0.266320 - Product: unknown 0.266325 - Serial Number: unknown 0.266330 - Bus: 007 0.266335 Trying to match device 0.266341 Device does not match - skipping 0.266349 Checking device (050D/1100) (006/002) 0.291945 - VendorID: 050d 0.291959 - ProductID: 1100 0.291966 - Manufacturer: Belkin 0.291972 - Product: Belkin UPS 0.291977 - Serial Number: unknown 0.291982 - Bus: 006 0.291987 Trying to match device 0.291995 Device matches (...) 0.383981 Entering libusb_get_report 0.388933 libusb_get_report: error sending control message: Operation not permitted ... Is this the same bug? I don't think so. the issue reported here was related to a code change, that resulted in a regression. yours seem to be with privileges. to validate this, try launching the driver with root privs (note the -u root): $ sudo /lib/nut/usbhid-ups -u root - -a mybelkin Is there a fix it's related to udev, and since there seems to be quite some similar issues, I'm wondering if there is a race condition between udev (started through upstart native scripts) and nut (started through upstart sysV compat script). 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/ -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in Ubuntu. https://bugs.launchpad.net/bugs/779512 Title: nut-2.6.0-1ubuntu3 behavior regression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/779512/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 779512] Re: nut-2.6.0-1ubuntu3 behavior regression
2011/7/13 Martin Ewing martin.s.ew...@gmail.com Arnaud, Thanks for the reply! I imagine you are correct. I ran the command you suggested (below). Apparently nut knows the device it should connect to, but that device is busy. And running as root doesn't overcome the problem... (And I don't know why I should have to make /var/run/nut, either.) this specific issue with claim is generally bound to another instance of the driver still running. I am not well versed in Ubuntu bug reporting. Do you think I need to submit this separately? Or should I just wait until the next release? (The lazy way out.) for now, we'll focus on hunting your issue here. if it goes beyond another 2 mails, then we'll check for creating a dedicated bug report, to be able to close it through 2.6.1 upload, while not forgiving you ;) 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/ -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in Ubuntu. https://bugs.launchpad.net/bugs/779512 Title: nut-2.6.0-1ubuntu3 behavior regression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/779512/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 779512] Re: nut-2.6.0-1ubuntu3 behavior regression
Hi Martin, 2011/6/27 Martin Ewing martin.s.ew...@gmail.com I have a very similar situation with my Belkin UPS on Natty (worked on previous release). See $ lsb_release -rd Description:Ubuntu 11.04 Release:11.04 martin@gimli:~$ aptitude show nut Package: nut State: installed Automatically installed: no Version: 2.6.0-1ubuntu3 ... sudo /lib/nut/usbhid-ups - -a mybelkin Network UPS Tools - Generic HID driver 0.35 (2.6.0) USB communication driver 0.31 0.00 debug level is '4' 0.000583 upsdrv_initups... 0.266176 Checking device (1D6B/0001) (008/001) 0.266219 - VendorID: 1d6b 0.266226 - ProductID: 0001 0.266232 - Manufacturer: unknown 0.266237 - Product: unknown 0.266242 - Serial Number: unknown 0.266247 - Bus: 008 0.266252 Trying to match device 0.266275 Device does not match - skipping 0.266285 Checking device (1D6B/0001) (007/001) 0.266303 - VendorID: 1d6b 0.266309 - ProductID: 0001 0.266315 - Manufacturer: unknown 0.266320 - Product: unknown 0.266325 - Serial Number: unknown 0.266330 - Bus: 007 0.266335 Trying to match device 0.266341 Device does not match - skipping 0.266349 Checking device (050D/1100) (006/002) 0.291945 - VendorID: 050d 0.291959 - ProductID: 1100 0.291966 - Manufacturer: Belkin 0.291972 - Product: Belkin UPS 0.291977 - Serial Number: unknown 0.291982 - Bus: 006 0.291987 Trying to match device 0.291995 Device matches (...) 0.383981 Entering libusb_get_report 0.388933 libusb_get_report: error sending control message: Operation not permitted ... Is this the same bug? I don't think so. the issue reported here was related to a code change, that resulted in a regression. yours seem to be with privileges. to validate this, try launching the driver with root privs (note the -u root): $ sudo /lib/nut/usbhid-ups -u root - -a mybelkin Is there a fix it's related to udev, and since there seems to be quite some similar issues, I'm wondering if there is a race condition between udev (started through upstart native scripts) and nut (started through upstart sysV compat script). 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/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/779512 Title: nut-2.6.0-1ubuntu3 behavior regression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/779512/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 779512] Re: nut-2.6.0-1ubuntu3 behavior regression
2011/7/13 Martin Ewing martin.s.ew...@gmail.com Arnaud, Thanks for the reply! I imagine you are correct. I ran the command you suggested (below). Apparently nut knows the device it should connect to, but that device is busy. And running as root doesn't overcome the problem... (And I don't know why I should have to make /var/run/nut, either.) this specific issue with claim is generally bound to another instance of the driver still running. I am not well versed in Ubuntu bug reporting. Do you think I need to submit this separately? Or should I just wait until the next release? (The lazy way out.) for now, we'll focus on hunting your issue here. if it goes beyond another 2 mails, then we'll check for creating a dedicated bug report, to be able to close it through 2.6.1 upload, while not forgiving you ;) 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/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/779512 Title: nut-2.6.0-1ubuntu3 behavior regression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/779512/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 809166] [NEW] Update fence-agents to 3.1.5
Public bug reported: fence-agents 3.1.5 has been released on 08-Jul-2011: https://fedorahosted.org/releases/f/e/fence-agents/ Please consider an update Andres ;-) cheers, Arnaud ** Affects: fence-agents (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/809166 Title: Update fence-agents to 3.1.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/809166/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Blueprint server-o-infra-power] Infrastructure power management
Blueprint changed by Arnaud Quette: Whiteboard changed: Work items: [fredericbohe] Implement device discovery tools / libs / binding in NUT: INPROGRESS [aquette] Implement configuration library and tool for NUT: TODO [aquette] Create Augeas lenses for configuration for NUT: DONE - [aquette] Distribute NUT Augeas lenses: TODO - [aquette] Distribute the new NUT documentation: TODO - [aquette] Create a NUT client only (upsmon) package: TODO + [aquette] Distribute NUT Augeas lenses: INPROGRESS + [aquette] Distribute the new NUT documentation: INPROGRESS + [aquette] Create a NUT client only (upsmon) package: INPROGRESS [aquette] Convert initscripts to upstart: TODO [aquette] Create Avahi publication script for : INPROGRESS - [aquette] Implement a native NUT PSU (power supply unit) / IPMI driver, using OpenIPMI: TODO - [aquette] Implement PowerChain in NUT: TODO + [aquette] Implement a native NUT PSU (power supply unit) / IPMI driver, using OpenIPMI: INPROGRESS + [aquette] Implement PowerChain in NUT: INPROGRESS [zulcss] Investigate and implement NUT Puppet integration: TODO [zulcss] Investigate and implement NUT cobbler integration: TODO [zulcss] Investigate and implement NUT Orchestra integration: TODO [zulcss] Investigate and implement NUT Ensemble integration: TODO [kim0] Investigate and implement NUT Ensemble integration: TODO [aquette] Implement improved PDU and power devices support in fence-agents: DONE [andreserl] provide fence-agents package (part of server-o-cluster-stack): DONE [andreserl] Investigate PowerNap using NUT as a data broker: INPROGRESS [aquette] Investigate PowerNap using NUT as a data broker: INPROGRESS [andreserl] Implement NUT client support in PowerWake: TODO [aquette] Implement NUT client support in PowerWake: TODO [bencer] Implement NUT support in Zentyal: TODO [aquette] Implement NUT support in Zentyal: TODO [cr3] Implement support for UPS testing in Checkbox using NUT: TODO [aquette] Implement support for UPS testing in Checkbox using NUT: TODO Remaining questions: - is Augeas support sufficient for configuration, or does it need a more advanced wrapper? - related to the above, is a configuration library / tool needed? - @zulcss: does Nagios nut plug-in offer sufficient features for your purpose? == Items to consider == 1. Implement power support in Cloud schedulers using NUT: TODO (lack an assignee) 2. Create power consumption reports (not ready for billing, only informative) 3. Asset management support for power devices. Ie, Provide device information like manufacturer name and model, serial number, location, contact, service dates, ... -- Infrastructure power management https://blueprints.launchpad.net/ubuntu/+spec/server-o-infra-power -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint server-o-infra-power] Infrastructure power management
Blueprint changed by Arnaud Quette: Whiteboard changed: Work items: [aquette] Implement device discovery tools / libs / binding in NUT: INPROGRESS [aquette] Implement configuration library and tool for NUT: TODO [aquette] Create Augeas lenses for configuration for NUT: DONE [aquette] Distribute NUT Augeas lenses: TODO [aquette] Distribute the new NUT documentation: TODO [aquette] Create a NUT client only (upsmon) package: TODO - [?] Convert initscripts to upstart: TODO + [server-o-cluster-stack] Convert initscripts to upstart: TODO [aquette] Create Avahi publication script for : INPROGRESS [aquette] Implement a native NUT PSU (power supply unit) driver, using libsmbios: TODO [aquette] Implement a native NUT IPMI driver (remove the need for PowerMan) using OpenIPMI: TODO - [aquette] Implement the PowerPath (or PowerChain) notion in NUT, to be able to link for example PSU1 - PDU outlet2 - UPS1: TODO + [aquette] Implement PowerChain in NUT: TODO [zulcss] Investigate and implement NUT Puppet integration: TODO [zulcss] Investigate and implement NUT cobbler integration: TODO [zulcss] Investigate and implement NUT Orchestra integration: TODO [zulcss] Investigate and implement NUT Ensemble integration: TODO [kim0] Investigate and implement NUT Ensemble integration: TODO [aquette] Implement improved PDU and power devices support in fence-agents: TODO - [?] provide fence-agents package (separated from cman): TODO + [andreserl] provide fence-agents package (part of server-o-cluster-stack): TODO [andreserl] Investigate PowerNap using NUT as a data broker: INPROGRESS [aquette] Investigate PowerNap using NUT as a data broker: INPROGRESS [andreserl] Implement NUT client support in PowerWake: TODO [aquette] Implement NUT client support in PowerWake: TODO [bencer] Implement NUT support in Zentyal: TODO [aquette] Implement NUT support in Zentyal: TODO - [?] Implement power support in Cloud schedulers using NUT: TODO [cr3] Implement support for UPS testing in Checkbox using NUT: TODO [aquette] Implement support for UPS testing in Checkbox using NUT: TODO Remaining questions: - is Augeas support sufficient for configuration, or does it need a more advanced wrapper? - related to the above, is a configuration library / tool needed? - @zulcss: does Nagios nut plug-in offer sufficient features for your purpose? == Items to consider == - 1. Create power consumption reports (not ready for billing, only informative) - 2. Asset management support for power devices. Ie, Provide device information like manufacturer name and model, serial number, location, contact, service dates, ... + 1. Implement power support in Cloud schedulers using NUT: TODO (lack an assignee) + 2. Create power consumption reports (not ready for billing, only informative) + 3. Asset management support for power devices. Ie, Provide device information like manufacturer name and model, serial number, location, contact, service dates, ... -- Infrastructure power management https://blueprints.launchpad.net/ubuntu/+spec/server-o-infra-power -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint server-o-infra-power] Infrastructure power management
Blueprint changed by Arnaud Quette: Whiteboard changed: Work items: [aquette] Implement device discovery tools / libs / binding in NUT: INPROGRESS [aquette] Implement configuration library and tool for NUT: TODO [aquette] Create Augeas lenses for configuration for NUT: DONE [aquette] Distribute NUT Augeas lenses: TODO [aquette] Distribute the new NUT documentation: TODO [aquette] Create a NUT client only (upsmon) package: TODO - [server-o-cluster-stack] Convert initscripts to upstart: TODO + [aquette] Convert initscripts to upstart: TODO [aquette] Create Avahi publication script for : INPROGRESS - [aquette] Implement a native NUT PSU (power supply unit) driver, using libsmbios: TODO - [aquette] Implement a native NUT IPMI driver (remove the need for PowerMan) using OpenIPMI: TODO + [aquette] Implement a native NUT PSU (power supply unit) / IPMI driver, using OpenIPMI: TODO [aquette] Implement PowerChain in NUT: TODO [zulcss] Investigate and implement NUT Puppet integration: TODO [zulcss] Investigate and implement NUT cobbler integration: TODO [zulcss] Investigate and implement NUT Orchestra integration: TODO [zulcss] Investigate and implement NUT Ensemble integration: TODO [kim0] Investigate and implement NUT Ensemble integration: TODO [aquette] Implement improved PDU and power devices support in fence-agents: TODO [andreserl] provide fence-agents package (part of server-o-cluster-stack): TODO [andreserl] Investigate PowerNap using NUT as a data broker: INPROGRESS [aquette] Investigate PowerNap using NUT as a data broker: INPROGRESS [andreserl] Implement NUT client support in PowerWake: TODO [aquette] Implement NUT client support in PowerWake: TODO [bencer] Implement NUT support in Zentyal: TODO [aquette] Implement NUT support in Zentyal: TODO [cr3] Implement support for UPS testing in Checkbox using NUT: TODO [aquette] Implement support for UPS testing in Checkbox using NUT: TODO Remaining questions: - is Augeas support sufficient for configuration, or does it need a more advanced wrapper? - related to the above, is a configuration library / tool needed? - @zulcss: does Nagios nut plug-in offer sufficient features for your purpose? == Items to consider == 1. Implement power support in Cloud schedulers using NUT: TODO (lack an assignee) 2. Create power consumption reports (not ready for billing, only informative) 3. Asset management support for power devices. Ie, Provide device information like manufacturer name and model, serial number, location, contact, service dates, ... -- Infrastructure power management https://blueprints.launchpad.net/ubuntu/+spec/server-o-infra-power -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint server-o-infra-power] Infrastructure power management
Blueprint changed by Arnaud Quette: Whiteboard changed: Work items: - [aquette] Implement device discovery tools / libs / binding in NUT: INPROGRESS + [fredericbohe] Implement device discovery tools / libs / binding in NUT: INPROGRESS [aquette] Implement configuration library and tool for NUT: TODO [aquette] Create Augeas lenses for configuration for NUT: DONE [aquette] Distribute NUT Augeas lenses: TODO [aquette] Distribute the new NUT documentation: TODO [aquette] Create a NUT client only (upsmon) package: TODO [aquette] Convert initscripts to upstart: TODO [aquette] Create Avahi publication script for : INPROGRESS [aquette] Implement a native NUT PSU (power supply unit) / IPMI driver, using OpenIPMI: TODO [aquette] Implement PowerChain in NUT: TODO [zulcss] Investigate and implement NUT Puppet integration: TODO [zulcss] Investigate and implement NUT cobbler integration: TODO [zulcss] Investigate and implement NUT Orchestra integration: TODO [zulcss] Investigate and implement NUT Ensemble integration: TODO [kim0] Investigate and implement NUT Ensemble integration: TODO [aquette] Implement improved PDU and power devices support in fence-agents: TODO [andreserl] provide fence-agents package (part of server-o-cluster-stack): TODO [andreserl] Investigate PowerNap using NUT as a data broker: INPROGRESS [aquette] Investigate PowerNap using NUT as a data broker: INPROGRESS [andreserl] Implement NUT client support in PowerWake: TODO [aquette] Implement NUT client support in PowerWake: TODO [bencer] Implement NUT support in Zentyal: TODO [aquette] Implement NUT support in Zentyal: TODO [cr3] Implement support for UPS testing in Checkbox using NUT: TODO [aquette] Implement support for UPS testing in Checkbox using NUT: TODO Remaining questions: - is Augeas support sufficient for configuration, or does it need a more advanced wrapper? - related to the above, is a configuration library / tool needed? - @zulcss: does Nagios nut plug-in offer sufficient features for your purpose? == Items to consider == 1. Implement power support in Cloud schedulers using NUT: TODO (lack an assignee) 2. Create power consumption reports (not ready for billing, only informative) 3. Asset management support for power devices. Ie, Provide device information like manufacturer name and model, serial number, location, contact, service dates, ... -- Infrastructure power management https://blueprints.launchpad.net/ubuntu/+spec/server-o-infra-power -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 779512] Re: nut-2.6.0-1ubuntu3 behavior regression
2011/5/14 Mr. Muskrat 779...@bugs.launchpad.net Yes, I can confirm that this fixed the issue I reported. thanks for the confirmation Arnaud, thank you so much! my pleasure Matt :) 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/ -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in Ubuntu. https://bugs.launchpad.net/bugs/779512 Title: nut-2.6.0-1ubuntu3 behavior regression -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 779512] Re: nut-2.6.0-1ubuntu3 behavior regression
2011/5/14 Mr. Muskrat 779...@bugs.launchpad.net Yes, I can confirm that this fixed the issue I reported. thanks for the confirmation Arnaud, thank you so much! my pleasure Matt :) 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/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/779512 Title: nut-2.6.0-1ubuntu3 behavior regression -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 779512] Re: nut-2.6.0-1ubuntu3 behavior regression
Hey Matt, 2011/5/13 Mr. Muskrat 779...@bugs.launchpad.net I thought I'd be able to just copy/paste the instructions one at a time but I hit a few snags. I installed the missing prereqs and continued on. (...) hem, sorry. I should have given you more info on build-deps and more generally well, the point is that you found your way (congrats) and that everything seems fixed on your side. can you please confirm? I'll do some more checking on my side, but 2.6.1 (soon to go out) will fix your issue. as a temporary solution, you may backup /lib/nut/usbhid-ups and replace it with drivers/usbhid-ups, while waiting for an updated package. 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/ -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in Ubuntu. https://bugs.launchpad.net/bugs/779512 Title: nut-2.6.0-1ubuntu3 behavior regression -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 779512] Re: nut-2.6.0-1ubuntu3 behavior regression
Hey Matt, 2011/5/13 Mr. Muskrat 779...@bugs.launchpad.net I thought I'd be able to just copy/paste the instructions one at a time but I hit a few snags. I installed the missing prereqs and continued on. (...) hem, sorry. I should have given you more info on build-deps and more generally well, the point is that you found your way (congrats) and that everything seems fixed on your side. can you please confirm? I'll do some more checking on my side, but 2.6.1 (soon to go out) will fix your issue. as a temporary solution, you may backup /lib/nut/usbhid-ups and replace it with drivers/usbhid-ups, while waiting for an updated package. 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/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/779512 Title: nut-2.6.0-1ubuntu3 behavior regression -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 779512] Re: nut-2.6.0-1ubuntu3 behavior regression
2011/5/11 Mr. Muskrat 779...@bugs.launchpad.net Certainly! excellent, here we go: $ svn co svn://svn.debian.org/nut/trunk $ ./autogen.sh $ ./configure --prefix=/usr \ --exec-prefix=/ \ --sysconfdir=/etc/nut \ --mandir=/usr/share/man \ --libdir=/lib \ --includedir=/usr/include \$ sudo --without-all \ --with-usb \ --enable-static \ --with-statepath=/var/run/nut \ --with-altpidpath=/var/run/nut \ --with-drvpath=/lib/nut \ --with-pidpath=/var/run/nut \ --datadir=/usr/share/nut \ --with-user=nut --with-group=nut $ sudo ./drivers/usbhid-ups -u root - -a cyberpower @Fred: can you please do the same with Troy, and send (only to) me the output. We should have sufficient validation with that. Note that a 2 mn run is sufficient... 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/ -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in Ubuntu. https://bugs.launchpad.net/bugs/779512 Title: nut-2.6.0-1ubuntu3 behavior regression -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 779512] Re: nut-2.6.0-1ubuntu3 behavior regression
2011/5/11 Mr. Muskrat 779...@bugs.launchpad.net Certainly! excellent, here we go: $ svn co svn://svn.debian.org/nut/trunk $ ./autogen.sh $ ./configure --prefix=/usr \ --exec-prefix=/ \ --sysconfdir=/etc/nut \ --mandir=/usr/share/man \ --libdir=/lib \ --includedir=/usr/include \$ sudo --without-all \ --with-usb \ --enable-static \ --with-statepath=/var/run/nut \ --with-altpidpath=/var/run/nut \ --with-drvpath=/lib/nut \ --with-pidpath=/var/run/nut \ --datadir=/usr/share/nut \ --with-user=nut --with-group=nut $ sudo ./drivers/usbhid-ups -u root - -a cyberpower @Fred: can you please do the same with Troy, and send (only to) me the output. We should have sufficient validation with that. Note that a 2 mn run is sufficient... 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/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/779512 Title: nut-2.6.0-1ubuntu3 behavior regression -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 779512] Re: nut-2.6.0-1ubuntu3 behavior regression
2011/5/11 Mr. Muskrat 779...@bugs.launchpad.net Arnaud, I hope that I captured enough of the information for you. thanks Matt. I'm still trying to find a solution that would satisfy everybody. not that easy! would you be able to test an svn version (just a checkout and minimum compilation to run the driver in debug mode)? cheers, Arno -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in Ubuntu. https://bugs.launchpad.net/bugs/779512 Title: nut-2.6.0-1ubuntu3 behavior regression -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 779512] Re: nut-2.6.0-1ubuntu3 behavior regression
2011/5/11 Mr. Muskrat 779...@bugs.launchpad.net Arnaud, I hope that I captured enough of the information for you. thanks Matt. I'm still trying to find a solution that would satisfy everybody. not that easy! would you be able to test an svn version (just a checkout and minimum compilation to run the driver in debug mode)? cheers, Arno -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/779512 Title: nut-2.6.0-1ubuntu3 behavior regression -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 779512] Re: nut-2.6.0-1ubuntu3 behavior regression
Hi Matt, 2011/5/10 Mr. Muskrat 779...@bugs.launchpad.net Arnaud, Here is what you have asked for. Matt •[x4linux:~] mmusgrove $ sudo service nut stop [sudo] password for mmusgrove: * Stopping Network UPS Tools [ OK ] •[x4linux:~] mmusgrove $ export USB_DEBUG=3 •[x4linux:~] mmusgrove $ sudo /lib/nut/usbhid-ups - -a cyberpower can you please try again with: $ sudo /lib/nut/usbhid-ups -u root - -a cyberpower I was thinking about the report size issue, but you're there hitting a permissions one... 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/ -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in Ubuntu. https://bugs.launchpad.net/bugs/779512 Title: nut-2.6.0-1ubuntu3 behavior regression -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 779512] Re: nut-2.6.0-1ubuntu3 behavior regression
Hi Matt, 2011/5/10 Mr. Muskrat 779...@bugs.launchpad.net Arnaud, Here is what you have asked for. Matt •[x4linux:~] mmusgrove $ sudo service nut stop [sudo] password for mmusgrove: * Stopping Network UPS Tools [ OK ] •[x4linux:~] mmusgrove $ export USB_DEBUG=3 •[x4linux:~] mmusgrove $ sudo /lib/nut/usbhid-ups - -a cyberpower can you please try again with: $ sudo /lib/nut/usbhid-ups -u root - -a cyberpower I was thinking about the report size issue, but you're there hitting a permissions one... 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/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/779512 Title: nut-2.6.0-1ubuntu3 behavior regression -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 779512] [NEW] nut-2.6.0-1ubuntu3 behavior regression
2011/5/8 Mr. Muskrat 779...@bugs.launchpad.net Public bug reported: Binary package hint: nut Prior to upgrading to Natty, I had the nut-2.4.3-1ubuntu5 package and it was working correctly. right, but the fix made for the kind of devices you have (ie not fully complying to USB standards) broke other devices / features. the right fix would have to be in libusb, but since we're still on 0.1 (which is not maintained anymore), the solution may come from the port to libusb 1.0. After upgrading to Natty, I have the nut-2.6.0-1ubuntu3 package and it is not working correctly. Here's my release info: •[x4linux:~] mmusgrove $ lsb_release -rd Description:Ubuntu 11.04 Release:11.04 The symptom is that it can't initialize data from HID UPS and so the driver fails to start. •[x4linux:~] mmusgrove $ sudo upsdrvctl start Network UPS Tools - UPS driver controller 2.6.0 Network UPS Tools - Generic HID driver 0.35 (2.6.0) USB communication driver 0.31 Using subdriver: CyberPower HID 0.3 libusb_get_report: No error Can't initialize data from HID UPS Driver failed to start (exit status=1) (...) could you please do the following test and send back the output: - first, stop nut - then export USB_DEBUG=3 - start the driver using sudo /lib/nut/usbhid-ups - -a upsname where upsname is the one from ups.conf. - the output of dpkg -l '*libusb*' would also be useful. 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/ -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in Ubuntu. https://bugs.launchpad.net/bugs/779512 Title: nut-2.6.0-1ubuntu3 behavior regression -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 779512] [NEW] nut-2.6.0-1ubuntu3 behavior regression
2011/5/8 Mr. Muskrat 779...@bugs.launchpad.net Public bug reported: Binary package hint: nut Prior to upgrading to Natty, I had the nut-2.4.3-1ubuntu5 package and it was working correctly. right, but the fix made for the kind of devices you have (ie not fully complying to USB standards) broke other devices / features. the right fix would have to be in libusb, but since we're still on 0.1 (which is not maintained anymore), the solution may come from the port to libusb 1.0. After upgrading to Natty, I have the nut-2.6.0-1ubuntu3 package and it is not working correctly. Here's my release info: •[x4linux:~] mmusgrove $ lsb_release -rd Description:Ubuntu 11.04 Release:11.04 The symptom is that it can't initialize data from HID UPS and so the driver fails to start. •[x4linux:~] mmusgrove $ sudo upsdrvctl start Network UPS Tools - UPS driver controller 2.6.0 Network UPS Tools - Generic HID driver 0.35 (2.6.0) USB communication driver 0.31 Using subdriver: CyberPower HID 0.3 libusb_get_report: No error Can't initialize data from HID UPS Driver failed to start (exit status=1) (...) could you please do the following test and send back the output: - first, stop nut - then export USB_DEBUG=3 - start the driver using sudo /lib/nut/usbhid-ups - -a upsname where upsname is the one from ups.conf. - the output of dpkg -l '*libusb*' would also be useful. 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/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/779512 Title: nut-2.6.0-1ubuntu3 behavior regression -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 535583] Excessive logging by apcsmart program
2011/4/21 Michal Soltys sol...@ziu.info On 11-04-21 10:34, Arnaud Quette wrote: Hi Lupe, since we now have an apcsmart maintainer, I'm forwarding this issue to him. @Michal: could you please have a look at this issue [1], and give us your feeling? cheers, Arnaud -- [1] https://bugs.launchpad.net/bugs/535583 2011/2/15 Lupe Christoph l...@lupe-christoph.de mailto:l...@lupe-christoph.de The suggestions are pretty fine. - flushing stale input (though at driver level) Certainly. I even added some flushes earlier, but haven't touched the updateinfo and/or the functions it calls yet. I'll add it along with forthcoming patches (icanon mode and the rest). Looking at the strace, flushing post-failure might be good idea in certain cases as well. - reopening serial port If the upper layers of nut don't disallow this kind of behaviour for some reason - it's good idea as well. Should be helpful in weird cases, and at the very least wouldn't hurt at all. If it would help in this particular case, hard to say. none special. we already have to somehow do so with USB devices. - smartmode() TBH, I'm not sure why it diligently tries to enter SM 5 times. Pre-emptive flush + 'Y' + reasonable delay (icanon or not) should be all that is necessary. If we don't succeed, next attempt shouldn't miraculously (in theory) make much of a difference 1 second later ... Thanks for pointing out those issues. thanks for taking care of it ;-) 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/ -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in Ubuntu. https://bugs.launchpad.net/bugs/535583 Title: Excessive logging by apcsmart program -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 535583] Excessive logging by apcsmart program
2011/4/21 Michal Soltys sol...@ziu.info On 11-04-21 10:34, Arnaud Quette wrote: Hi Lupe, since we now have an apcsmart maintainer, I'm forwarding this issue to him. @Michal: could you please have a look at this issue [1], and give us your feeling? cheers, Arnaud -- [1] https://bugs.launchpad.net/bugs/535583 2011/2/15 Lupe Christoph l...@lupe-christoph.de mailto:l...@lupe-christoph.de The suggestions are pretty fine. - flushing stale input (though at driver level) Certainly. I even added some flushes earlier, but haven't touched the updateinfo and/or the functions it calls yet. I'll add it along with forthcoming patches (icanon mode and the rest). Looking at the strace, flushing post-failure might be good idea in certain cases as well. - reopening serial port If the upper layers of nut don't disallow this kind of behaviour for some reason - it's good idea as well. Should be helpful in weird cases, and at the very least wouldn't hurt at all. If it would help in this particular case, hard to say. none special. we already have to somehow do so with USB devices. - smartmode() TBH, I'm not sure why it diligently tries to enter SM 5 times. Pre-emptive flush + 'Y' + reasonable delay (icanon or not) should be all that is necessary. If we don't succeed, next attempt shouldn't miraculously (in theory) make much of a difference 1 second later ... Thanks for pointing out those issues. thanks for taking care of it ;-) 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/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/535583 Title: Excessive logging by apcsmart program -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 535583] Excessive logging by apcsmart program
Hi Lupe,
since we now have an apcsmart maintainer, I'm forwarding this issue to
him.
@Michal: could you please have a look at this issue [1], and give us your
feeling?
cheers,
Arnaud
--
[1] https://bugs.launchpad.net/bugs/535583
2011/2/15 Lupe Christoph l...@lupe-christoph.de
On Tuesday, 2011-02-15 at 13:16:58 -, Arnaud Quette wrote:
this is not the problem. This code is in the smartmode() function of
apcsmart.c:
http://svn.debian.org/wsvn/nut/trunk/drivers/apcsmart.c
we see the 5 attempts to go to smart mode ('Y' command), but my aim is to
understand why it is failing, and how to cleanly solve this without
impacting support for other units.
I found no code that does five attempts. But this code in main.c,
starting on Line 618:
while (!exit_flag) {
struct timeval timeout;
gettimeofday(timeout, NULL);
timeout.tv_sec += poll_interval;
upsdrv_updateinfo();
while (!dstate_poll_fds(timeout, extrafd) !exit_flag) {
/* repeat until time is up or extrafd has data */
upsdrv_updateinfo() calls smartmode().
dstate_poll_fds() checks if there is any file descriptor that is
available. In our case:
select(7, [4 5 6], NULL, NULL, {1, 999837}) = 1 (in [4], left {1, 999835})
FD 4 is the serial line, which is passed to dstate_poll_fds() as
extrafd.
When there is data that can be read from the UPS no code in
dstate_poll_fds() reads from extrafd, there is only code that reads
from the other input FDs. The outer loop above also ignores extrafd.
exit_flag is never set, so it continues. And because there is an active
file descriptor, the select returns immediately (actually it takes two
microseconds).
The solution is to add code that reads all data from extrafd and discards
it because nobody asked for it. I would also close and reopen the serial
line in smartmode(). I would prepare a patch if I knew more about the
I/O abstractions used in the nut driver code. Sorry.
HTH,
Lupe Christoph
--
| It is a well-known fact in any organisation that, if you want a job|
| done, you should give it to someone who is already very busy. |
| Terry Pratchett, Unseen Academicals |
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in Ubuntu.
https://bugs.launchpad.net/bugs/535583
Title:
Excessive logging by apcsmart program
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 535583] Excessive logging by apcsmart program
Hi Lupe,
since we now have an apcsmart maintainer, I'm forwarding this issue to
him.
@Michal: could you please have a look at this issue [1], and give us your
feeling?
cheers,
Arnaud
--
[1] https://bugs.launchpad.net/bugs/535583
2011/2/15 Lupe Christoph l...@lupe-christoph.de
On Tuesday, 2011-02-15 at 13:16:58 -, Arnaud Quette wrote:
this is not the problem. This code is in the smartmode() function of
apcsmart.c:
http://svn.debian.org/wsvn/nut/trunk/drivers/apcsmart.c
we see the 5 attempts to go to smart mode ('Y' command), but my aim is to
understand why it is failing, and how to cleanly solve this without
impacting support for other units.
I found no code that does five attempts. But this code in main.c,
starting on Line 618:
while (!exit_flag) {
struct timeval timeout;
gettimeofday(timeout, NULL);
timeout.tv_sec += poll_interval;
upsdrv_updateinfo();
while (!dstate_poll_fds(timeout, extrafd) !exit_flag) {
/* repeat until time is up or extrafd has data */
upsdrv_updateinfo() calls smartmode().
dstate_poll_fds() checks if there is any file descriptor that is
available. In our case:
select(7, [4 5 6], NULL, NULL, {1, 999837}) = 1 (in [4], left {1, 999835})
FD 4 is the serial line, which is passed to dstate_poll_fds() as
extrafd.
When there is data that can be read from the UPS no code in
dstate_poll_fds() reads from extrafd, there is only code that reads
from the other input FDs. The outer loop above also ignores extrafd.
exit_flag is never set, so it continues. And because there is an active
file descriptor, the select returns immediately (actually it takes two
microseconds).
The solution is to add code that reads all data from extrafd and discards
it because nobody asked for it. I would also close and reopen the serial
line in smartmode(). I would prepare a patch if I knew more about the
I/O abstractions used in the nut driver code. Sorry.
HTH,
Lupe Christoph
--
| It is a well-known fact in any organisation that, if you want a job|
| done, you should give it to someone who is already very busy. |
| Terry Pratchett, Unseen Academicals |
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/535583
Title:
Excessive logging by apcsmart program
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 753661] Re: upsd write() failed for 127.0.0.1: Broken pipe
so what if you issue again an upsc powercom? does it still broke the pipe? is your issue 100 % reproducible? my guess, is ATM, that the faulty end-of-line marker in battery.type is causing parseconf to close prematurely the connexion, while upsd is still sending data. which explains why unit requests works, while getting the whole tree fails... the only way to ensure this is the root cause is to fix the function that retrieve strings from the device's indexed table, to trim EOL, and check if it solves your issue. would you be ready to test a fix using subversion? cheers, Arno -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in Ubuntu. https://bugs.launchpad.net/bugs/753661 Title: upsd write() failed for 127.0.0.1: Broken pipe -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 753661] Re: upsd write() failed for 127.0.0.1: Broken pipe
2011/4/18 Virus 753...@bugs.launchpad.net yes, it 100 % reproducible. I also managed to reproduce it using dummy-ups (the simulation driver) and injecting the error on the same variable: adding a newline (ie \n) results in a broken pipe on upsc side. i am ready to test svn version. ok, here we go: 1) checkout an svn copy using: $ svn co svn://svn.debian.org/nut/trunk 2) configure it using (Debian arguments, limited for the current test scope ; should be sufficient): --prefix=/usr \ --exec-prefix=/ \ --sysconfdir=/etc/nut \ --mandir=/usr/share/man \ --libdir=/lib \ --includedir=/usr/include \ --without-all \ --with-usb \ --enable-static \ --with-statepath=/var/run/nut \ --with-altpidpath=/var/run/nut \ --with-drvpath=/lib/nut \ --with-pidpath=/var/run/nut \ --datadir=/usr/share/nut \ --with-pkgconfig-dir=/usr/lib/pkgconfig \ --with-user=nut --with-group=nut 3) apply the attached patch $ patch -p0 /path/to/virus.patch 4) make as usual, ie $ make 5) stop all previous NUT instances, then launch the new driver and upsd $ sudo drivers/usbhid-ups -a powercom $ sudo server/upsd -DDD 6) now issue your upsc of death $ upsc powercom everything should behave fine. Remember that it's a blind patch: I've not validated the above configure line, nor the patch itself! 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/ ** Attachment added: virus.patch https://bugs.launchpad.net/bugs/753661/+attachment/2059655/+files/virus.patch -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in Ubuntu. https://bugs.launchpad.net/bugs/753661 Title: upsd write() failed for 127.0.0.1: Broken pipe -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 753661] Re: upsd write() failed for 127.0.0.1: Broken pipe
2011/4/18 Virus 753...@bugs.launchpad.net It`s working great! Many thanks! excellent, thanks for the feedback. I've just committed it upstream (r2972) the changeset will be available on the NUT Trac mirror (just give it some minutes to sync): http://trac.networkupstools.org/projects/nut/changeset/2972 I'll leave up to our Ubuntu friends to generate an updated package. I have to note that importance is low since this should not affect the protection (ie upsmon is still working fine). @Virus: can you please confirm this point? 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/ -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in Ubuntu. https://bugs.launchpad.net/bugs/753661 Title: upsd write() failed for 127.0.0.1: Broken pipe -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 753661] Re: upsd write() failed for 127.0.0.1: Broken pipe
so what if you issue again an upsc powercom? does it still broke the pipe? is your issue 100 % reproducible? my guess, is ATM, that the faulty end-of-line marker in battery.type is causing parseconf to close prematurely the connexion, while upsd is still sending data. which explains why unit requests works, while getting the whole tree fails... the only way to ensure this is the root cause is to fix the function that retrieve strings from the device's indexed table, to trim EOL, and check if it solves your issue. would you be ready to test a fix using subversion? cheers, Arno -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/753661 Title: upsd write() failed for 127.0.0.1: Broken pipe -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 753661] Re: upsd write() failed for 127.0.0.1: Broken pipe
2011/4/18 Virus 753...@bugs.launchpad.net yes, it 100 % reproducible. I also managed to reproduce it using dummy-ups (the simulation driver) and injecting the error on the same variable: adding a newline (ie \n) results in a broken pipe on upsc side. i am ready to test svn version. ok, here we go: 1) checkout an svn copy using: $ svn co svn://svn.debian.org/nut/trunk 2) configure it using (Debian arguments, limited for the current test scope ; should be sufficient): --prefix=/usr \ --exec-prefix=/ \ --sysconfdir=/etc/nut \ --mandir=/usr/share/man \ --libdir=/lib \ --includedir=/usr/include \ --without-all \ --with-usb \ --enable-static \ --with-statepath=/var/run/nut \ --with-altpidpath=/var/run/nut \ --with-drvpath=/lib/nut \ --with-pidpath=/var/run/nut \ --datadir=/usr/share/nut \ --with-pkgconfig-dir=/usr/lib/pkgconfig \ --with-user=nut --with-group=nut 3) apply the attached patch $ patch -p0 /path/to/virus.patch 4) make as usual, ie $ make 5) stop all previous NUT instances, then launch the new driver and upsd $ sudo drivers/usbhid-ups -a powercom $ sudo server/upsd -DDD 6) now issue your upsc of death $ upsc powercom everything should behave fine. Remember that it's a blind patch: I've not validated the above configure line, nor the patch itself! 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/ ** Attachment added: virus.patch https://bugs.launchpad.net/bugs/753661/+attachment/2059655/+files/virus.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/753661 Title: upsd write() failed for 127.0.0.1: Broken pipe -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 753661] Re: upsd write() failed for 127.0.0.1: Broken pipe
2011/4/18 Virus 753...@bugs.launchpad.net It`s working great! Many thanks! excellent, thanks for the feedback. I've just committed it upstream (r2972) the changeset will be available on the NUT Trac mirror (just give it some minutes to sync): http://trac.networkupstools.org/projects/nut/changeset/2972 I'll leave up to our Ubuntu friends to generate an updated package. I have to note that importance is low since this should not affect the protection (ie upsmon is still working fine). @Virus: can you please confirm this point? 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/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/753661 Title: upsd write() failed for 127.0.0.1: Broken pipe -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 753661] Re: upsd write() failed for 127.0.0.1: Broken pipe
2011/4/16 Virus 753...@bugs.launchpad.net $ upsc battery.type Error: Unknown UPS $ upsc ups.status Error: Unknown UPS damn, I missed a bit (ie the device name): $ upsc powercom battery.type Error: Unknown UPS $ upsc powercom ups.status Error: Unknown UPS don't forget to run upsd in debug mode, as in the previous test. I need to see how it react. cheers Arno -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in Ubuntu. https://bugs.launchpad.net/bugs/753661 Title: upsd write() failed for 127.0.0.1: Broken pipe -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 753661] Re: upsd write() failed for 127.0.0.1: Broken pipe
2011/4/16 Virus 753...@bugs.launchpad.net $ upsc battery.type Error: Unknown UPS $ upsc ups.status Error: Unknown UPS damn, I missed a bit (ie the device name): $ upsc powercom battery.type Error: Unknown UPS $ upsc powercom ups.status Error: Unknown UPS don't forget to run upsd in debug mode, as in the previous test. I need to see how it react. cheers Arno -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/753661 Title: upsd write() failed for 127.0.0.1: Broken pipe -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 753661] [NEW] upsd write() failed for 127.0.0.1: Broken pipe
2011/4/7 Virus 753...@bugs.launchpad.net Public bug reported: Binary package hint: nut I have Powercom UPS and trying configure it with NUT. lsusb: Bus 006 Device 002: ID 0d9f:0004 Powercom Co., Ltd ups.conf: [powercom] driver = usbhid-ups port = /dev/usb/hiddev0 putting auto is sufficient here productid = 0004 this productid should be added to the driver. before that, I need the output f an lsusb -v -d 0x0d9f:0004 desc = My UPS but when i trying run `upsc powercom` got this output: -- battery.charge: 99 battery.charge.low: 10 battery.charge.warning: 30 battery.date: 2009/12/23 battery.runtime: 24576 battery.type: PbAc -- and `upsd[24062]: write() failed for 127.0.0.1: Broken pipe` in /var/log/daemon.log how i can fix this? good question! is the driver still running? what is your start method (ie using invoke-rc.d or alike, or directly starting components manually)? what is the content of your upsd.conf? after having stopped previous instance (invoke-rc.d nut stop), what is the output of: $ sudo upsd -v then, stop upsd (sudo upsd -c stop) and start in 3 separate consoles: $ sudo upsd -DDD $ sudo /lib/nut/usbhid-ups -D -a powercom $ upsc powercom and send back the various output. 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/ -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in Ubuntu. https://bugs.launchpad.net/bugs/753661 Title: upsd write() failed for 127.0.0.1: Broken pipe -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 753661] Re: upsd write() failed for 127.0.0.1: Broken pipe
2011/4/16 Virus 753...@bugs.launchpad.net Seems driver respond correctly, but upsd return Broken pipe after: 25.768861 write: [destfd=6] [len=35] [VAR powercom battery.type PbAc ] Two lines? yup, but upsd sends everything. and upsc brokes the pipe. the driver is still there, so the issue is really between upsc and upsd. 2 more tests, still with upsd running in debug mode: $ upsc battery.type $ upsc ups.status cheers, Arno -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in Ubuntu. https://bugs.launchpad.net/bugs/753661 Title: upsd write() failed for 127.0.0.1: Broken pipe -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 753661] [NEW] upsd write() failed for 127.0.0.1: Broken pipe
2011/4/7 Virus 753...@bugs.launchpad.net Public bug reported: Binary package hint: nut I have Powercom UPS and trying configure it with NUT. lsusb: Bus 006 Device 002: ID 0d9f:0004 Powercom Co., Ltd ups.conf: [powercom] driver = usbhid-ups port = /dev/usb/hiddev0 putting auto is sufficient here productid = 0004 this productid should be added to the driver. before that, I need the output f an lsusb -v -d 0x0d9f:0004 desc = My UPS but when i trying run `upsc powercom` got this output: -- battery.charge: 99 battery.charge.low: 10 battery.charge.warning: 30 battery.date: 2009/12/23 battery.runtime: 24576 battery.type: PbAc -- and `upsd[24062]: write() failed for 127.0.0.1: Broken pipe` in /var/log/daemon.log how i can fix this? good question! is the driver still running? what is your start method (ie using invoke-rc.d or alike, or directly starting components manually)? what is the content of your upsd.conf? after having stopped previous instance (invoke-rc.d nut stop), what is the output of: $ sudo upsd -v then, stop upsd (sudo upsd -c stop) and start in 3 separate consoles: $ sudo upsd -DDD $ sudo /lib/nut/usbhid-ups -D -a powercom $ upsc powercom and send back the various output. 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/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/753661 Title: upsd write() failed for 127.0.0.1: Broken pipe -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 753661] Re: upsd write() failed for 127.0.0.1: Broken pipe
2011/4/16 Virus 753...@bugs.launchpad.net Seems driver respond correctly, but upsd return Broken pipe after: 25.768861 write: [destfd=6] [len=35] [VAR powercom battery.type PbAc ] Two lines? yup, but upsd sends everything. and upsc brokes the pipe. the driver is still there, so the issue is really between upsc and upsd. 2 more tests, still with upsd running in debug mode: $ upsc battery.type $ upsc ups.status cheers, Arno -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/753661 Title: upsd write() failed for 127.0.0.1: Broken pipe -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 743484] [NEW] libupsclient.pc contains unresolved symbols
Salut Fabrice
2011/3/27 Fabrice Coutadeur coutade...@gmail.com
Public bug reported:
Binary package hint: nut
Hi,
While I was investigating a FTBFS in collectd:
...
configure:22249: checking for upscli_connect in -lupsclient
configure:22274: i686-linux-gnu-gcc -o conftest -Wall -g -O2
-I/build/fabrice-collectd_4.10.1-2.1build1-i386-7yH3eE/collectd-4.10.1/debian/include
-DLT_LAZY_OR_NOW='RTLD_LAZY|RTLD_GLOBAL' -UCONFIGFILE
-DCONFIGFILE='/etc/collectd/collectd.conf' -Wl,-Bsymbolic-functions
@LIBSSL_LDFLAGS@ -L/lib -lupsclient conftest.c -lupsclient -ldl 5
i686-linux-gnu-gcc: @LIBSSL_LDFLAGS@: No such file or directory
I discovered that this reference to LIBSSL_LDFLAGS comes from
libupsclient.pc.
As you can see in actual .pc file, this reference has not been resolved at
compile time (content of more /usr/lib/pkgconfig/libupsclient.pc in a natty
schroot):
prefix=/usr
exec_prefix=/
libdir=/lib
includedir=/usr/include
sysconfdir=/etc/nut
statepath=/var/run/nut
nutuser=nut
Name: libupsclient
Description: UPS monitoring with Network UPS Tools
Version: 2.6.0
Libs: -L${libdir} -lupsclient @LIBSSL_LDFLAGS@
Cflags: -I${includedir}
This is because configure script and all makefile.in has been updated to
use and substitute LIBSSL_LIBS instead of LIBSSL_LDFLAGS, but
libupsclient.pc.in has not been updated.
By replacing LIBSSL_LDFLAGS with LIBSSL_LIBS in .in files, the generated
.pc file is correct.
fully right, thanks for investigation and patch.
For the sake of completion, lib/libupsclient-config.in (a replacement when
pkg-config is not present) also need to be fixed.
I've just applied it upstream (in NUT, commit r2960) while waiting for a new
Debian upload (I may lag a bit more, considering my current workload...):
http://trac.networkupstools.org/projects/nut/changeset/2960
Note that the above link may not yet be active by the reception of this
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/
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in Ubuntu.
https://bugs.launchpad.net/bugs/743484
Title:
libupsclient.pc contains unresolved symbols
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 743484] [NEW] libupsclient.pc contains unresolved symbols
Salut Fabrice
2011/3/27 Fabrice Coutadeur coutade...@gmail.com
Public bug reported:
Binary package hint: nut
Hi,
While I was investigating a FTBFS in collectd:
...
configure:22249: checking for upscli_connect in -lupsclient
configure:22274: i686-linux-gnu-gcc -o conftest -Wall -g -O2
-I/build/fabrice-collectd_4.10.1-2.1build1-i386-7yH3eE/collectd-4.10.1/debian/include
-DLT_LAZY_OR_NOW='RTLD_LAZY|RTLD_GLOBAL' -UCONFIGFILE
-DCONFIGFILE='/etc/collectd/collectd.conf' -Wl,-Bsymbolic-functions
@LIBSSL_LDFLAGS@ -L/lib -lupsclient conftest.c -lupsclient -ldl 5
i686-linux-gnu-gcc: @LIBSSL_LDFLAGS@: No such file or directory
I discovered that this reference to LIBSSL_LDFLAGS comes from
libupsclient.pc.
As you can see in actual .pc file, this reference has not been resolved at
compile time (content of more /usr/lib/pkgconfig/libupsclient.pc in a natty
schroot):
prefix=/usr
exec_prefix=/
libdir=/lib
includedir=/usr/include
sysconfdir=/etc/nut
statepath=/var/run/nut
nutuser=nut
Name: libupsclient
Description: UPS monitoring with Network UPS Tools
Version: 2.6.0
Libs: -L${libdir} -lupsclient @LIBSSL_LDFLAGS@
Cflags: -I${includedir}
This is because configure script and all makefile.in has been updated to
use and substitute LIBSSL_LIBS instead of LIBSSL_LDFLAGS, but
libupsclient.pc.in has not been updated.
By replacing LIBSSL_LDFLAGS with LIBSSL_LIBS in .in files, the generated
.pc file is correct.
fully right, thanks for investigation and patch.
For the sake of completion, lib/libupsclient-config.in (a replacement when
pkg-config is not present) also need to be fixed.
I've just applied it upstream (in NUT, commit r2960) while waiting for a new
Debian upload (I may lag a bit more, considering my current workload...):
http://trac.networkupstools.org/projects/nut/changeset/2960
Note that the above link may not yet be active by the reception of this
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/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/743484
Title:
libupsclient.pc contains unresolved symbols
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 535583] Excessive logging by apcsmart program
2011/2/15 Lupe Christoph
On Monday, 2011-02-14 at 21:54:20 -, Arnaud Quette wrote:
I definitely need more info!
please reply to ALL:
- what is the exact model and date of manufacturing?
SmartUPS 300I NET. I have the serial number (GS9809283199) but no date.
it seems to be a recent model.
- are you sure this unit is ok?
You can't prove the absence of faults.
this was related to the following question...
- have you really checked the cabling or made the whole (cable + UPS)
work
somehow (using APC's software or apcupsd)?
Well, as I said this is working OK for days or weeks. Then something
happens that triggers a bug in apcsmart.
quickly reading back the thread, I can't find these info...
- what is the meantime between occurrences of these issues?
I don;t have enough data. It's in the range of weeks or months.
as per your previous posts, this seemed more to be a matter of minutes /
hours.
- is the device reachable (using upsc for example) between issues?
Sure, everything works fine.
A driver debug output is really needed!
I'm running it again, but no promises. Reboots are much more frequent
than this misbehaviour.
Note that I'm not the developer of this driver, nor have any acquaintance
with APC.
Same here. Though I will probably try to locate this bug if we don;t
make progress with the debugging output, either because it does not tell
us enough or because I don't manage to capture it.
I would have thought finding the place in the code where it is trying to
reset the UPS connection wouldn't be this hard.
this is not the problem. This code is in the smartmode() function of
apcsmart.c:
http://svn.debian.org/wsvn/nut/trunk/drivers/apcsmart.c
we see the 5 attempts to go to smart mode ('Y' command), but my aim is to
understand why it is failing, and how to cleanly solve this without
impacting support for other units.
Some more questions:
- how are you handling the device's permissions?
Refer to § II, section 3:
http://git.debian.org/?p=collab-maint/nut.git;a=blob_plain;f=debian/nut.README.Debian;hb=HEAD
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/
--
Conseiller Municipal - Saint Bernard du Touvet
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in ubuntu.
https://bugs.launchpad.net/bugs/535583
Title:
Excessive logging by apcsmart program
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 535583] Excessive logging by apcsmart program
2011/2/15 Lupe Christoph
On Monday, 2011-02-14 at 21:54:20 -, Arnaud Quette wrote:
I definitely need more info!
please reply to ALL:
- what is the exact model and date of manufacturing?
SmartUPS 300I NET. I have the serial number (GS9809283199) but no date.
it seems to be a recent model.
- are you sure this unit is ok?
You can't prove the absence of faults.
this was related to the following question...
- have you really checked the cabling or made the whole (cable + UPS)
work
somehow (using APC's software or apcupsd)?
Well, as I said this is working OK for days or weeks. Then something
happens that triggers a bug in apcsmart.
quickly reading back the thread, I can't find these info...
- what is the meantime between occurrences of these issues?
I don;t have enough data. It's in the range of weeks or months.
as per your previous posts, this seemed more to be a matter of minutes /
hours.
- is the device reachable (using upsc for example) between issues?
Sure, everything works fine.
A driver debug output is really needed!
I'm running it again, but no promises. Reboots are much more frequent
than this misbehaviour.
Note that I'm not the developer of this driver, nor have any acquaintance
with APC.
Same here. Though I will probably try to locate this bug if we don;t
make progress with the debugging output, either because it does not tell
us enough or because I don't manage to capture it.
I would have thought finding the place in the code where it is trying to
reset the UPS connection wouldn't be this hard.
this is not the problem. This code is in the smartmode() function of
apcsmart.c:
http://svn.debian.org/wsvn/nut/trunk/drivers/apcsmart.c
we see the 5 attempts to go to smart mode ('Y' command), but my aim is to
understand why it is failing, and how to cleanly solve this without
impacting support for other units.
Some more questions:
- how are you handling the device's permissions?
Refer to § II, section 3:
http://git.debian.org/?p=collab-maint/nut.git;a=blob_plain;f=debian/nut.README.Debian;hb=HEAD
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/
--
Conseiller Municipal - Saint Bernard du Touvet
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/535583
Title:
Excessive logging by apcsmart program
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 535583] Re: Excessive logging by apcsmart program
I definitely need more info! please reply to ALL: - what is the exact model and date of manufacturing? - are you sure this unit is ok? - have you really checked the cabling or made the whole (cable + UPS) work somehow (using APC's software or apcupsd)? - what is the meantime between occurrences of these issues? - is the device reachable (using upsc for example) between issues? A driver debug output is really needed! Note that I'm not the developer of this driver, nor have any acquaintance with APC. cheers Arnaud -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in ubuntu. https://bugs.launchpad.net/bugs/535583 Title: Excessive logging by apcsmart program -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 535583] Re: Excessive logging by apcsmart program
I definitely need more info! please reply to ALL: - what is the exact model and date of manufacturing? - are you sure this unit is ok? - have you really checked the cabling or made the whole (cable + UPS) work somehow (using APC's software or apcupsd)? - what is the meantime between occurrences of these issues? - is the device reachable (using upsc for example) between issues? A driver debug output is really needed! Note that I'm not the developer of this driver, nor have any acquaintance with APC. cheers Arnaud -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/535583 Title: Excessive logging by apcsmart program -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 535583] Re: Excessive logging by apcsmart program
Hi Christoph, 2011/2/10 Lupe Christoph Since the supposed fix, I have had several ne incidents of this bug. I'm now running Maverick Meerkat, and the log shows this: Feb 10 14:10:14 alanya apcsmart[3238]: Communications with UPS lost: Communications with UPS lost - check cabling Feb 10 14:10:14 alanya apcsmart[3238]: smartmode: ser_send_char failed: Input/output error Feb 10 14:10:14 alanya apcsmart[3238]: last message repeated 9 times ... and nauseam, or until the /var/log partition fills up. The nut package is up to data (2.4.3-1ubuntu5). Please reopen this bug. could you please send us a driver debug output for investigation purpose. Ie, after having stopped the running NUT instance, launch: $ sudo /lib/nut/apcsmart -D -a device-id-from-ups.conf let it run for a few seconds / minutes (at least, have a couple of issue reproduction), then break using Ctrl+C. Don't forget to relaunch NUT then... 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/ -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in ubuntu. https://bugs.launchpad.net/bugs/535583 Title: Excessive logging by apcsmart program -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 535583] Re: Excessive logging by apcsmart program
Hi Christoph, 2011/2/10 Lupe Christoph Since the supposed fix, I have had several ne incidents of this bug. I'm now running Maverick Meerkat, and the log shows this: Feb 10 14:10:14 alanya apcsmart[3238]: Communications with UPS lost: Communications with UPS lost - check cabling Feb 10 14:10:14 alanya apcsmart[3238]: smartmode: ser_send_char failed: Input/output error Feb 10 14:10:14 alanya apcsmart[3238]: last message repeated 9 times ... and nauseam, or until the /var/log partition fills up. The nut package is up to data (2.4.3-1ubuntu5). Please reopen this bug. could you please send us a driver debug output for investigation purpose. Ie, after having stopped the running NUT instance, launch: $ sudo /lib/nut/apcsmart -D -a device-id-from-ups.conf let it run for a few seconds / minutes (at least, have a couple of issue reproduction), then break using Ctrl+C. Don't forget to relaunch NUT then... 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/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/535583 Title: Excessive logging by apcsmart program -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 705552] Re: 10.04 nut package is missing 52_nut-usbups.rules
2011/1/24 Hugh Saunders Apologies, I had forgotten about /lib/udev/rules.d. I have removed 52-nut-usbups.rules from /etc/udev/rules.d and it still works (see log below). There must have been some other configuration problem initially. I have marked this bug as invalid. (...) quite probably the udevadm trigger line that isn't sufficient to refresh privileges for already plugged devices. This won't be noticed if the device's USB cord is plugged after NUT installation, or if there is a reboot somewhere in the process... 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/ -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in ubuntu. https://bugs.launchpad.net/bugs/705552 Title: 10.04 nut package is missing 52_nut-usbups.rules -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 705552] Re: 10.04 nut package is missing 52_nut-usbups.rules
2011/1/24 Hugh Saunders Apologies, I had forgotten about /lib/udev/rules.d. I have removed 52-nut-usbups.rules from /etc/udev/rules.d and it still works (see log below). There must have been some other configuration problem initially. I have marked this bug as invalid. (...) quite probably the udevadm trigger line that isn't sufficient to refresh privileges for already plugged devices. This won't be noticed if the device's USB cord is plugged after NUT installation, or if there is a reboot somewhere in the process... 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/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/705552 Title: 10.04 nut package is missing 52_nut-usbups.rules -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 687985] Re: [FTBFS] package 'nut' (2.4.3-1ubuntu5) failed to build on natty
2011/1/10 Laurent Bigonville bi...@bigon.be I've found the issue. Actually the nut_check_*.m4 are setting *_LDFLAGS instead of *_LIBS, and due to a toolchain change this become visible (gcc -o testusb testusb.c -lusb is working but gcc -o testusb -lusb testusb.c is not working anymore) Any reason nut is not using PKG_CHECK_MODULE macro? the most basic ones: lack of time / manpower and low priority task. until now, the wide availability of the macro was also another, though it should be good now. I know that we can ship our own version, but that can lead to other issues. thanks for your patch Laurent, I've just applied it (r2821). so it will be available in 2.6.0 (a little bit more retained due to late bug reports like this one). 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/ -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in ubuntu. https://bugs.launchpad.net/bugs/687985 Title: [FTBFS] package 'nut' (2.4.3-1ubuntu5) failed to build on natty -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 687985] Re: [FTBFS] package 'nut' (2.4.3-1ubuntu5) failed to build on natty
2011/1/10 Laurent Bigonville bi...@bigon.be I've found the issue. Actually the nut_check_*.m4 are setting *_LDFLAGS instead of *_LIBS, and due to a toolchain change this become visible (gcc -o testusb testusb.c -lusb is working but gcc -o testusb -lusb testusb.c is not working anymore) Any reason nut is not using PKG_CHECK_MODULE macro? the most basic ones: lack of time / manpower and low priority task. until now, the wide availability of the macro was also another, though it should be good now. I know that we can ship our own version, but that can lead to other issues. thanks for your patch Laurent, I've just applied it (r2821). so it will be available in 2.6.0 (a little bit more retained due to late bug reports like this one). 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/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/687985 Title: [FTBFS] package 'nut' (2.4.3-1ubuntu5) failed to build on natty -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 692171] [NEW] using BUS= in udev rules causes system boot error/warning
2010/12/19 Alf Aedan 692...@bugs.launchpad.net Public bug reported: Binary package hint: nut Whenever I boot my system (running Ubuntu 10.10), I get these errors in my boot.log and on the screen if I'm on the console: udevd[458]: BUS= will be removed in a future udev version, please use SUBSYSTEM= to match the event device, or SUBSYSTEMS= to match a parent device, in /lib/udev/rules.d/52-nut-usbups.rules:6 this has been fixed upstream (r2456) and will be available in ~ a week in 2.6.0 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/ -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in ubuntu. https://bugs.launchpad.net/bugs/692171 Title: using BUS= in udev rules causes system boot error/warning -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 692171] [NEW] using BUS= in udev rules causes system boot error/warning
2010/12/19 Alf Aedan 692...@bugs.launchpad.net Public bug reported: Binary package hint: nut Whenever I boot my system (running Ubuntu 10.10), I get these errors in my boot.log and on the screen if I'm on the console: udevd[458]: BUS= will be removed in a future udev version, please use SUBSYSTEM= to match the event device, or SUBSYSTEMS= to match a parent device, in /lib/udev/rules.d/52-nut-usbups.rules:6 this has been fixed upstream (r2456) and will be available in ~ a week in 2.6.0 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/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/692171 Title: using BUS= in udev rules causes system boot error/warning -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 687985] Re: [FTBFS] package 'nut' (2.4.3-1ubuntu5) failed to build on natty
Hi Dave, thanks for your report and logs. this is strange, since there is only a minor libusb update, which seems not to break compatibility. but the fact is that AC_CHECK_FUNCS doesn't find usb_init() anymore, so there is actually something wrong. I'm currently busy preparing 2.6.0, so don't have much time to investigate. can you please also send a config.log for analysis? I'll do some pbuilder testing on my side, and will propose a patch to fix that. 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/ -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in ubuntu. https://bugs.launchpad.net/bugs/687985 Title: [FTBFS] package 'nut' (2.4.3-1ubuntu5) failed to build on natty -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 687985] Re: [FTBFS] package 'nut' (2.4.3-1ubuntu5) failed to build on natty
Hi Dave, thanks for your report and logs. this is strange, since there is only a minor libusb update, which seems not to break compatibility. but the fact is that AC_CHECK_FUNCS doesn't find usb_init() anymore, so there is actually something wrong. I'm currently busy preparing 2.6.0, so don't have much time to investigate. can you please also send a config.log for analysis? I'll do some pbuilder testing on my side, and will propose a patch to fix that. 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/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/687985 Title: [FTBFS] package 'nut' (2.4.3-1ubuntu5) failed to build on natty -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 662435] Re: megatec_usb driver stopped working after upgrade from 8.04 to 10.04
Hi Michael, thanks for your feedback! I'm cc'ing the NUT users list for info. I've also added an entry for your device (Powerwalker Line Interactive VI 1400, using blazer_usb). Can you please send back an upsc output, and at least check for the shutdown behavior, if not already done: http://new.networkupstools.org/user-manual.html#Testing_shutdowns 2010/10/19 MichaelE 662...@bugs.launchpad.net It works now! I reinstalled 2.4.3 and checked the blazer_usb driver again. First I thought it did not work but then discovered a configuration error: When changing from megatec to blazer, the value for offdelay needs to be changed. In megatec it is minutes and in blazer it is seconds. As it does not allow a value smaller than 6, the blazer_usb refused to work (it was 1 in megatec). Thanks a lot to Arnaud for the quick reply! thanks goes to Arjen de Korte, a NUT senior lieutenant, who worte the blazer drivers. Here is my new ups.conf now: [ups01] driver= blazer_usb port = auto vendorid = 0665 productid = 5161 # after shutdown, wait 5 minutes after return of power ondelay = 5 # wait 1 minute after power-off command before cutting power offdelay = 60 ** Changed in: nut (Ubuntu) Status: Incomplete = Fix Released -- megatec_usb driver stopped working after upgrade from 8.04 to 10.04 https://bugs.launchpad.net/bugs/662435 You received this bug notification because you are subscribed to nut in ubuntu. 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/ -- megatec_usb driver stopped working after upgrade from 8.04 to 10.04 https://bugs.launchpad.net/bugs/662435 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Fwd: [Bug 662435] Re: megatec_usb driver stopped working after upgrade from 8.04 to 10.04
FYI @Arjen: anything else required? cheers, Arnaud -- Forwarded message -- From: MichaelE 662...@bugs.launchpad.net Date: 2010/10/20 Subject: [Bug 662435] Re: megatec_usb driver stopped working after upgrade from 8.04 to 10.04 To: aquette@gmail.com I tested the shutdown behaviour and it works as expected. The UPS disconnected the load and then came back on again after power returned (waiting the defined delay). I also attached the blazer_usb output in case this is needed. If there are other testes required to improve the driver I am happy to do this (maybe read out the remaining battery capacity?). This is the output of upsc: r...@xen-base:~# upsc ups01 battery.voltage: 25.70 battery.voltage.nominal: 24.0 beeper.status: enabled device.type: ups driver.name: blazer_usb driver.parameter.offdelay: 60 driver.parameter.ondelay: 5 driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.parameter.productid: 5161 driver.parameter.vendorid: 0665 driver.version: 2.4.3 driver.version.internal: 0.03 input.current.nominal: 2.0 input.frequency: 50.1 input.frequency.nominal: 50 input.voltage: 224.3 input.voltage.fault: 224.3 input.voltage.nominal: 230 output.voltage: 219.5 ups.delay.shutdown: 60 ups.delay.start: 300 ups.load: 11 ups.productid: 5161 ups.status: OL ups.temperature: 25.0 ups.type: offline / line interactive ups.vendorid: 0665 -- megatec_usb driver stopped working after upgrade from 8.04 to 10.04 https://bugs.launchpad.net/bugs/662435 You received this bug notification because you are subscribed to nut in ubuntu. -- megatec_usb driver stopped working after upgrade from 8.04 to 10.04 https://bugs.launchpad.net/bugs/662435 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 662435] Re: megatec_usb driver stopped working after upgrade from 8.04 to 10.04
Hi Michael, thanks for your feedback! I'm cc'ing the NUT users list for info. I've also added an entry for your device (Powerwalker Line Interactive VI 1400, using blazer_usb). Can you please send back an upsc output, and at least check for the shutdown behavior, if not already done: http://new.networkupstools.org/user-manual.html#Testing_shutdowns 2010/10/19 MichaelE 662...@bugs.launchpad.net It works now! I reinstalled 2.4.3 and checked the blazer_usb driver again. First I thought it did not work but then discovered a configuration error: When changing from megatec to blazer, the value for offdelay needs to be changed. In megatec it is minutes and in blazer it is seconds. As it does not allow a value smaller than 6, the blazer_usb refused to work (it was 1 in megatec). Thanks a lot to Arnaud for the quick reply! thanks goes to Arjen de Korte, a NUT senior lieutenant, who worte the blazer drivers. Here is my new ups.conf now: [ups01] driver= blazer_usb port = auto vendorid = 0665 productid = 5161 # after shutdown, wait 5 minutes after return of power ondelay = 5 # wait 1 minute after power-off command before cutting power offdelay = 60 ** Changed in: nut (Ubuntu) Status: Incomplete = Fix Released -- megatec_usb driver stopped working after upgrade from 8.04 to 10.04 https://bugs.launchpad.net/bugs/662435 You received this bug notification because you are subscribed to nut in ubuntu. 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/ -- megatec_usb driver stopped working after upgrade from 8.04 to 10.04 https://bugs.launchpad.net/bugs/662435 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Fwd: [Bug 662435] Re: megatec_usb driver stopped working after upgrade from 8.04 to 10.04
FYI @Arjen: anything else required? cheers, Arnaud -- Forwarded message -- From: MichaelE 662...@bugs.launchpad.net Date: 2010/10/20 Subject: [Bug 662435] Re: megatec_usb driver stopped working after upgrade from 8.04 to 10.04 To: aquette@gmail.com I tested the shutdown behaviour and it works as expected. The UPS disconnected the load and then came back on again after power returned (waiting the defined delay). I also attached the blazer_usb output in case this is needed. If there are other testes required to improve the driver I am happy to do this (maybe read out the remaining battery capacity?). This is the output of upsc: r...@xen-base:~# upsc ups01 battery.voltage: 25.70 battery.voltage.nominal: 24.0 beeper.status: enabled device.type: ups driver.name: blazer_usb driver.parameter.offdelay: 60 driver.parameter.ondelay: 5 driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.parameter.productid: 5161 driver.parameter.vendorid: 0665 driver.version: 2.4.3 driver.version.internal: 0.03 input.current.nominal: 2.0 input.frequency: 50.1 input.frequency.nominal: 50 input.voltage: 224.3 input.voltage.fault: 224.3 input.voltage.nominal: 230 output.voltage: 219.5 ups.delay.shutdown: 60 ups.delay.start: 300 ups.load: 11 ups.productid: 5161 ups.status: OL ups.temperature: 25.0 ups.type: offline / line interactive ups.vendorid: 0665 -- megatec_usb driver stopped working after upgrade from 8.04 to 10.04 https://bugs.launchpad.net/bugs/662435 You received this bug notification because you are subscribed to nut in ubuntu. -- megatec_usb driver stopped working after upgrade from 8.04 to 10.04 https://bugs.launchpad.net/bugs/662435 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 662435] [NEW] megatec_usb driver stopped working after upgrade from 8.04 to 10.04
2010/10/18 MichaelE 662...@bugs.launchpad.net Public bug reported: Binary package hint: nut I was using nut with the megatec_usb driver for years without problems. Now I upgraded my server to 10.04 and the driver stopped to work with nut_2.4.3-1ubuntu3.1. Here is the ups.conf I am using [ups01] driver= megatec_usb port = auto vendorid = 0665 productid = 5161 mfr = Powerwalker model = Line Interactive VI 1400 serial = 73712C8 Also tested the subdrivers without success. I now downgraded the nut package to nut_2.2.2-6ubuntu1_amd64.deb and the driver works again. PLEASE MIND, THAT THE BUG IS WITH VERSION 2.4.3 not 2.2.2. can you please check the blazer_usb driver, since it is set to replace megatec* by NUT 2.6.0? cheers, Arnaud -- Linux / Unix Expert RD - Eaton - http://www.eaton.com/mgeops Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.free.fr/ -- megatec_usb driver stopped working after upgrade from 8.04 to 10.04 https://bugs.launchpad.net/bugs/662435 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 662435] [NEW] megatec_usb driver stopped working after upgrade from 8.04 to 10.04
2010/10/18 MichaelE 662...@bugs.launchpad.net Public bug reported: Binary package hint: nut I was using nut with the megatec_usb driver for years without problems. Now I upgraded my server to 10.04 and the driver stopped to work with nut_2.4.3-1ubuntu3.1. Here is the ups.conf I am using [ups01] driver= megatec_usb port = auto vendorid = 0665 productid = 5161 mfr = Powerwalker model = Line Interactive VI 1400 serial = 73712C8 Also tested the subdrivers without success. I now downgraded the nut package to nut_2.2.2-6ubuntu1_amd64.deb and the driver works again. PLEASE MIND, THAT THE BUG IS WITH VERSION 2.4.3 not 2.2.2. can you please check the blazer_usb driver, since it is set to replace megatec* by NUT 2.6.0? cheers, Arnaud -- Linux / Unix Expert RD - Eaton - http://www.eaton.com/mgeops Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.free.fr/ -- megatec_usb driver stopped working after upgrade from 8.04 to 10.04 https://bugs.launchpad.net/bugs/662435 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 608182] Re: problems with ups (mge pulsar es 8+)
** Attachment added: replacement /etc/init.d/nut for debug / investigation purpose http://launchpadlibrarian.net/52657944/nut -- problems with ups (mge pulsar es 8+) https://bugs.launchpad.net/bugs/608182 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 608182] Re: problems with ups (mge pulsar es 8+)
2010/7/28 Wolfgang Lubowski there are no results for mge-utalk in /var/log/messages any (driver(s) failed) message during the boot? if I don't start nut manually with /etc/init.d/nut start, I always get the following message: Broadcast Message from n...@l4 (somewhere) at 10:40 ... UPS mge...@localhost is unavailable so, I think, nut starts not completly, or nut starts and the driver doesn't start, or something like this the above is indeed upsd notifying that the driver is not there! try the following (as root): - backup your /etc/init.d/nut - overwrite it with the attachment - reboot your computer and send us back /tmp/mge-utalk.log for investigation - restore everything and reboot cheers, Arnaud -- problems with ups (mge pulsar es 8+) https://bugs.launchpad.net/bugs/608182 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 608182] Re: problems with ups (mge pulsar es 8+)
** Attachment added: replacement /etc/init.d/nut for debug / investigation purpose http://launchpadlibrarian.net/52657944/nut -- problems with ups (mge pulsar es 8+) https://bugs.launchpad.net/bugs/608182 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 608182] Re: problems with ups (mge pulsar es 8+)
2010/7/28 Wolfgang Lubowski there are no results for mge-utalk in /var/log/messages any (driver(s) failed) message during the boot? if I don't start nut manually with /etc/init.d/nut start, I always get the following message: Broadcast Message from n...@l4 (somewhere) at 10:40 ... UPS mge...@localhost is unavailable so, I think, nut starts not completly, or nut starts and the driver doesn't start, or something like this the above is indeed upsd notifying that the driver is not there! try the following (as root): - backup your /etc/init.d/nut - overwrite it with the attachment - reboot your computer and send us back /tmp/mge-utalk.log for investigation - restore everything and reboot cheers, Arnaud -- problems with ups (mge pulsar es 8+) https://bugs.launchpad.net/bugs/608182 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 608182] Re: problems with ups (mge pulsar es 8+)
2010/7/26 Wolfgang Lubowski w@gmx.at I still get the same outputs with NUT-Monitor. my nut.conf looks now the following: MODE=standalone ps -efl | grep mge-utalk: 0 S root 2066 2002 0 80 0 - 1907 pipe_w 08:37 pts/000:00:00 grep --color=auto mge-utalk upsc mgeups: Error: Driver not connected ls -la /var/run/nut: insgesamt 8 drwxrwx--- 2 root nut 80 2010-07-26 08:32 . drwxr-xr-x 22 root root 760 2010-07-26 08:32 .. -rw-r--r-- 1 nut nut5 2010-07-26 08:32 upsd.pid -rw-r--r-- 1 root root 5 2010-07-26 08:32 upsmon.pid all this confirms that the driver failed to start. can you try grep'ing your /var/log/messages for mge-utalk the NUT-Monitor problem are related to that. If you have any other info (or a screenshot) to give more details on the it starts not correctly. Ie does it crash, is there a trace, ...? Arnaud -- problems with ups (mge pulsar es 8+) https://bugs.launchpad.net/bugs/608182 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 608182] Re: problems with ups (mge pulsar es 8+)
2010/7/26 Wolfgang Lubowski w@gmx.at I still get the same outputs with NUT-Monitor. my nut.conf looks now the following: MODE=standalone ps -efl | grep mge-utalk: 0 S root 2066 2002 0 80 0 - 1907 pipe_w 08:37 pts/000:00:00 grep --color=auto mge-utalk upsc mgeups: Error: Driver not connected ls -la /var/run/nut: insgesamt 8 drwxrwx--- 2 root nut 80 2010-07-26 08:32 . drwxr-xr-x 22 root root 760 2010-07-26 08:32 .. -rw-r--r-- 1 nut nut5 2010-07-26 08:32 upsd.pid -rw-r--r-- 1 root root 5 2010-07-26 08:32 upsmon.pid all this confirms that the driver failed to start. can you try grep'ing your /var/log/messages for mge-utalk the NUT-Monitor problem are related to that. If you have any other info (or a screenshot) to give more details on the it starts not correctly. Ie does it crash, is there a trace, ...? Arnaud -- problems with ups (mge pulsar es 8+) https://bugs.launchpad.net/bugs/608182 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 608182] Re: problems with ups (mge pulsar es 8+)
2010/7/23 Wolfgang Lubowski w@gmx.at this is the output for upsc mgeups: device.mfr: MGE UPS SYSTEMS device.model: Pulsar ES8+ device.type: ups driver.name: mge-utalk driver.parameter.pollinterval: 2 driver.parameter.port: /dev/ttyS0 driver.version: 2.4.3 driver.version.internal: 0.89 ups.firmware: 0 ups.id: Pulsar ES8+ 0 ups.mfr: MGE UPS SYSTEMS ups.model: Pulsar ES8+ ups.status: OL CHRG upsrw mgeups doesn't give any output I think there is a bug or something like this in PyNUT-rw-except.diff, because when I run cd /usr/lib/pymodules/python2.6 sudo patch --dry-run -p0 /home/lub/Downloads/PyNUT-rw-except.diff I get the following output: patching file PyNUT.py patch unexpectedly ends in middle of line Hunk #1 succeeded at 193 (offset 3 lines). well, 2 things: - the patch, once processed by launchpad, seems to alter something. not much harms though. - I've wrongly left the --dry-run part of the patch command. Just remove this option, and relaunch the full line, ie: cd /usr/lib/pymodules/python2.6 sudo patch -p0 /home/lub/Downloads/PyNUT-rw-except.diff and concerning the autostart-problem: I had already added nut to group dialout, but this hadn't changed anything you have still not answered my question on the content of /etc/nut/nut.conf! I'd also need the result of the following commands, issued just after a reboot, without restarting the driver: ps -efl | grep mge-utalk upsc mgeups ls -la /var/run/nut cheers, Arnaud -- problems with ups (mge pulsar es 8+) https://bugs.launchpad.net/bugs/608182 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 608182] Re: problems with ups (mge pulsar es 8+)
2010/7/23 Wolfgang Lubowski w@gmx.at this is the output for upsc mgeups: device.mfr: MGE UPS SYSTEMS device.model: Pulsar ES8+ device.type: ups driver.name: mge-utalk driver.parameter.pollinterval: 2 driver.parameter.port: /dev/ttyS0 driver.version: 2.4.3 driver.version.internal: 0.89 ups.firmware: 0 ups.id: Pulsar ES8+ 0 ups.mfr: MGE UPS SYSTEMS ups.model: Pulsar ES8+ ups.status: OL CHRG upsrw mgeups doesn't give any output I think there is a bug or something like this in PyNUT-rw-except.diff, because when I run cd /usr/lib/pymodules/python2.6 sudo patch --dry-run -p0 /home/lub/Downloads/PyNUT-rw-except.diff I get the following output: patching file PyNUT.py patch unexpectedly ends in middle of line Hunk #1 succeeded at 193 (offset 3 lines). well, 2 things: - the patch, once processed by launchpad, seems to alter something. not much harms though. - I've wrongly left the --dry-run part of the patch command. Just remove this option, and relaunch the full line, ie: cd /usr/lib/pymodules/python2.6 sudo patch -p0 /home/lub/Downloads/PyNUT-rw-except.diff and concerning the autostart-problem: I had already added nut to group dialout, but this hadn't changed anything you have still not answered my question on the content of /etc/nut/nut.conf! I'd also need the result of the following commands, issued just after a reboot, without restarting the driver: ps -efl | grep mge-utalk upsc mgeups ls -la /var/run/nut cheers, Arnaud -- problems with ups (mge pulsar es 8+) https://bugs.launchpad.net/bugs/608182 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 608182] Re: problems with ups (mge pulsar es 8+)
Hi Wolfgang, I'm cc'ing NUT-Monitor author, for info 2010/7/22 Wolfgang Lubowski sorry for bothering you again autoshutdown works fine, thank you :) but a graphical tool would be nice too, and nut-monitor doesn't work up to now: if I start it from terminal, I get the following: Traceback (most recent call last): File /usr/bin/NUT-Monitor, line 883, in module gui = interface() File /usr/bin/NUT-Monitor, line 208, in __init__ self.connect_to_ups() File /usr/bin/NUT-Monitor, line 690, in connect_to_ups self.__ups_rw_vars = self.__ups_handler.GetRWVars( self.__current_ups ) File /usr/lib/pymodules/python2.6/PyNUT.py, line 208, in GetRWVars data = current[ offset: ].split( '' )[1] IndexError: list index out of range What must I change? (I've looked it up in the internet, but didn't find much) can you please send back the following outputs: - upsc mgeups - upsrw mgeups as for the exception, apply the attached (untested) patch should fix the issue. apply it using: cd /usr/lib/pymodules/python2.6 sudo patch --dry-run -p0 /path/to/PyNUT-rw-except.diff cheers, Arnaud ** Patch added: PyNUT-rw-except.diff http://launchpadlibrarian.net/52326897/PyNUT-rw-except.diff -- problems with ups (mge pulsar es 8+) https://bugs.launchpad.net/bugs/608182 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 608182] Re: problems with ups (mge pulsar es 8+)
2010/7/22 Wolfgang Lubowski 608...@bugs.launchpad.net and there is another thing I don't really understand: these ups-things aren't started completely, after reboot I get UPS mge...@localhost is unavailable, so I have to run /etc/init.d/nut start and then it works. there can be several reasons. but the first that comes to mind is some serial port privileges issue at startup: check /usr/share/doc/nut/README.Debian.gz, section (II) Installation - device port permissions. mge-utalk may fail to switch to the nut user if the permissions are set *after* nut startup. This is my /etc/default/nut: # start upsd START_UPSD=yes # start upsmon START_UPSMON=yes once more, this file is now replaced by /etc/nut/nut.conf. this one must contain the line: MODE=standalone please confirm that you have done this. Arnaud -- problems with ups (mge pulsar es 8+) https://bugs.launchpad.net/bugs/608182 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 608182] Re: problems with ups (mge pulsar es 8+)
Hi Wolfgang, I'm cc'ing NUT-Monitor author, for info 2010/7/22 Wolfgang Lubowski sorry for bothering you again autoshutdown works fine, thank you :) but a graphical tool would be nice too, and nut-monitor doesn't work up to now: if I start it from terminal, I get the following: Traceback (most recent call last): File /usr/bin/NUT-Monitor, line 883, in module gui = interface() File /usr/bin/NUT-Monitor, line 208, in __init__ self.connect_to_ups() File /usr/bin/NUT-Monitor, line 690, in connect_to_ups self.__ups_rw_vars = self.__ups_handler.GetRWVars( self.__current_ups ) File /usr/lib/pymodules/python2.6/PyNUT.py, line 208, in GetRWVars data = current[ offset: ].split( '' )[1] IndexError: list index out of range What must I change? (I've looked it up in the internet, but didn't find much) can you please send back the following outputs: - upsc mgeups - upsrw mgeups as for the exception, apply the attached (untested) patch should fix the issue. apply it using: cd /usr/lib/pymodules/python2.6 sudo patch --dry-run -p0 /path/to/PyNUT-rw-except.diff cheers, Arnaud ** Patch added: PyNUT-rw-except.diff http://launchpadlibrarian.net/52326897/PyNUT-rw-except.diff -- problems with ups (mge pulsar es 8+) https://bugs.launchpad.net/bugs/608182 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 608182] Re: problems with ups (mge pulsar es 8+)
2010/7/22 Wolfgang Lubowski 608...@bugs.launchpad.net and there is another thing I don't really understand: these ups-things aren't started completely, after reboot I get UPS mge...@localhost is unavailable, so I have to run /etc/init.d/nut start and then it works. there can be several reasons. but the first that comes to mind is some serial port privileges issue at startup: check /usr/share/doc/nut/README.Debian.gz, section (II) Installation - device port permissions. mge-utalk may fail to switch to the nut user if the permissions are set *after* nut startup. This is my /etc/default/nut: # start upsd START_UPSD=yes # start upsmon START_UPSMON=yes once more, this file is now replaced by /etc/nut/nut.conf. this one must contain the line: MODE=standalone please confirm that you have done this. Arnaud -- problems with ups (mge pulsar es 8+) https://bugs.launchpad.net/bugs/608182 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 608182] Re: problems with ups (mge pulsar es 8+)
Hi Wolfgang, a first and quick comment: this is not a NUT bug, but rather a PSP one! 2010/7/21 Wolfgang Lubowski oops, doesn't work like I expected :) nut.conf: MODE=none apart from some binary issues with PSP, this one is still sitting on NUT 2.2 compatibility. On Debian, I've recently added with the 2.4 releases the above nut.conf. This one is not supported by PSP for generating NUT configuration files. Thus, PSP still generates /etc/default/nut. so, first, modify the above none for standalone, and call a sudo invoke-rc.d nut start then check that it is working with upsc mgeups. Also note that the PSP is abandoned. I've not worked on it for a long time, and will not work on it anymore. Prefer NUT-Monitor (http://www.lestat.st/informatique/projets/nut-monitor-en) which will be distributed with NUT packages (and is already part of the source .tar.gz). cheers, Arnaud -- Linux / Unix Expert RD - Eaton - http://www.eaton.com/mgeops Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.free.fr/ -- problems with ups (mge pulsar es 8+) https://bugs.launchpad.net/bugs/608182 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 608182] Re: problems with ups (mge pulsar es 8+)
Hi Wolfgang, a first and quick comment: this is not a NUT bug, but rather a PSP one! 2010/7/21 Wolfgang Lubowski oops, doesn't work like I expected :) nut.conf: MODE=none apart from some binary issues with PSP, this one is still sitting on NUT 2.2 compatibility. On Debian, I've recently added with the 2.4 releases the above nut.conf. This one is not supported by PSP for generating NUT configuration files. Thus, PSP still generates /etc/default/nut. so, first, modify the above none for standalone, and call a sudo invoke-rc.d nut start then check that it is working with upsc mgeups. Also note that the PSP is abandoned. I've not worked on it for a long time, and will not work on it anymore. Prefer NUT-Monitor (http://www.lestat.st/informatique/projets/nut-monitor-en) which will be distributed with NUT packages (and is already part of the source .tar.gz). cheers, Arnaud -- Linux / Unix Expert RD - Eaton - http://www.eaton.com/mgeops Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.free.fr/ -- problems with ups (mge pulsar es 8+) https://bugs.launchpad.net/bugs/608182 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 578200] Re: (megatec_usb) error: Driver not connected
guys, I'd be interested in a driver debug output, ie: $ export USB_DEBUG=3 $ /lib/nut/megatec_usb -D -a upsname let it run for a couple of minutes, then break it (using Ctrl+C) and send back the trace. cheers, Arnaud -- Linux / Unix Expert RD - Eaton - http://www.eaton.com/mgeops Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.free.fr/ -- (megatec_usb) error: Driver not connected https://bugs.launchpad.net/bugs/578200 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 578200] Re: (megatec_usb) error: Driver not connected
guys, I'd be interested in a driver debug output, ie: $ export USB_DEBUG=3 $ /lib/nut/megatec_usb -D -a upsname let it run for a couple of minutes, then break it (using Ctrl+C) and send back the trace. cheers, Arnaud -- Linux / Unix Expert RD - Eaton - http://www.eaton.com/mgeops Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.free.fr/ -- (megatec_usb) error: Driver not connected https://bugs.launchpad.net/bugs/578200 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 598028] Re: Only pwrkap-gui should depend on python-matplotlib
2010/7/5 Thierry Carrez @Arnaud: python-matplotlib is still a depends from pwrkap in 7.30-4: ooch, I did it. -5 uploaded, and actually fixing it (double² checked) Arno -- Only pwrkap-gui should depend on python-matplotlib https://bugs.launchpad.net/bugs/598028 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 598028] Re: Only pwrkap-gui should depend on python-matplotlib
2010/6/25 Thierry Carrez Thanks Arnaud, will do ! you're welcome. -4 is now in unstable, so ready for the sync: http://packages.qa.debian.org/p/pwrkap/news/20100624T190215Z.html cheers, Arno -- Only pwrkap-gui should depend on python-matplotlib https://bugs.launchpad.net/bugs/598028 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 598028] [NEW] Only pwrkap-gui should depend on python-matplotlib
Hi Thierry, 2010/6/24 Thierry Carrez thierry.car...@ubuntu.com Public bug reported: Binary package hint: pwrkap pwrkap depends on python-matplotlib, which depends on graphical libraries. This pulls unnecessary slack on servers where pwrkap would be installed. It looks like only pwrkap-gui would need to depend on python-matplotlib ? indeed, and that's what I intended to do (back during UDS Jaunty). thanks for pointing that bug ;-) since there was no upstream update, no bugs in Debian nor Ubuntu and no lintian issue, this is the only bug. You can raise the severity since it forces to pull hosts of GUI deps in headless mode. Which can be considered major by the server team. Note that I'm preparing to upload 7.30-4 in Sid. Count a few hour, and ask for a sync. cheers, Arnaud -- Only pwrkap-gui should depend on python-matplotlib https://bugs.launchpad.net/bugs/598028 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 572262] Re: [SRU] libusb_get_report: error sending control message: Operation not permitted
2010/5/3 Chuck Short chuck.sh...@canonical.com Statement of Impact: nut in lucid was shipped with a bug that prevented some UPSes from connecting to the nut daemon. Checking google fedora was also affected by the same problem and has the same patch that we used. Explanation: This bug has been fixed by the attached debdiff that fixes this issue. This patch needs to be sent upstream if its not already fixed. FYI, this has already reached upstream (through RH/Fedora maintainer who is part of the team) and was applied in NUT trunk r2407 ( http://boxster.ghz.cc/projects/nut/changeset/2407) cheers, Arnaud -- Linux / Unix Expert RD - Eaton - http://www.eaton.com/mgeops Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.free.fr/ -- [SRU] libusb_get_report: error sending control message: Operation not permitted https://bugs.launchpad.net/bugs/572262 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 572262] Re: [SRU] libusb_get_report: error sending control message: Operation not permitted
2010/5/3 Chuck Short chuck.sh...@canonical.com Statement of Impact: nut in lucid was shipped with a bug that prevented some UPSes from connecting to the nut daemon. Checking google fedora was also affected by the same problem and has the same patch that we used. Explanation: This bug has been fixed by the attached debdiff that fixes this issue. This patch needs to be sent upstream if its not already fixed. FYI, this has already reached upstream (through RH/Fedora maintainer who is part of the team) and was applied in NUT trunk r2407 ( http://boxster.ghz.cc/projects/nut/changeset/2407) cheers, Arnaud -- Linux / Unix Expert RD - Eaton - http://www.eaton.com/mgeops Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.free.fr/ -- [SRU] libusb_get_report: error sending control message: Operation not permitted https://bugs.launchpad.net/bugs/572262 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 572262] [NEW] libusb_get_report: error sending control message: Operation not permitted
please try to unplug and plug back your UPS's USB cord, and then relaunch nut. cheers, Arnaud -- Linux / Unix Expert RD - Eaton - http://www.eaton.com/mgeops Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.free.fr/ -- libusb_get_report: error sending control message: Operation not permitted https://bugs.launchpad.net/bugs/572262 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 572262] [NEW] libusb_get_report: error sending control message: Operation not permitted
please try to unplug and plug back your UPS's USB cord, and then relaunch nut. cheers, Arnaud -- Linux / Unix Expert RD - Eaton - http://www.eaton.com/mgeops Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.free.fr/ -- libusb_get_report: error sending control message: Operation not permitted https://bugs.launchpad.net/bugs/572262 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 535152] Re: FFE for nut 2.4.3
guys, 2010/3/9 Chuck Short: Unfortunately it hasnt been tested by me. I rather get Arnaud's thoughts on this. I've not been able to do much testing on DK-p and none UPower. what I can say for the DK-p side (which theoretically should be applicable to UPower) is: - if a USB UPS is plugged, DK-p will take the hand on it. - if NUT is then started, it will kick off DK-p (by detaching the hiddev kernel driver, and so cutting the link used by DK-p), and will take the hand on the device. - if NUT is then stopped, you will have to unplug / replug your UPS' USB cord to generate a new udev event so that DK-p probes the new devices and restore the link to it. So, I'm confident that this upload won't break DK-p or UPower, and will fixe many things. as a side note, I have a 2.4.3-2 underway which solves the bull**it introduced by Scott James for refreshing the USB bus on postinst... The result is that any USB user has to unplug / plug back his UPS' USB cord to get udev apply the right rules. ie, in nut.postint: udevadm trigger --action=change should be replaced by udevadm trigger --subsystem-match=usb though I've not finished investigation / work on this, and won't commit on an upload date. this is limited to new installation where the UPS is already plugged in. I hope this helps... Arnaud -- Linux / Unix Expert RD - Eaton - http://www.eaton.com/mgeops Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.free.fr/ -- FFE for nut 2.4.3 https://bugs.launchpad.net/bugs/535152 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 535152] Re: FFE for nut 2.4.3
guys, 2010/3/9 Chuck Short: Unfortunately it hasnt been tested by me. I rather get Arnaud's thoughts on this. I've not been able to do much testing on DK-p and none UPower. what I can say for the DK-p side (which theoretically should be applicable to UPower) is: - if a USB UPS is plugged, DK-p will take the hand on it. - if NUT is then started, it will kick off DK-p (by detaching the hiddev kernel driver, and so cutting the link used by DK-p), and will take the hand on the device. - if NUT is then stopped, you will have to unplug / replug your UPS' USB cord to generate a new udev event so that DK-p probes the new devices and restore the link to it. So, I'm confident that this upload won't break DK-p or UPower, and will fixe many things. as a side note, I have a 2.4.3-2 underway which solves the bull**it introduced by Scott James for refreshing the USB bus on postinst... The result is that any USB user has to unplug / plug back his UPS' USB cord to get udev apply the right rules. ie, in nut.postint: udevadm trigger --action=change should be replaced by udevadm trigger --subsystem-match=usb though I've not finished investigation / work on this, and won't commit on an upload date. this is limited to new installation where the UPS is already plugged in. I hope this helps... Arnaud -- Linux / Unix Expert RD - Eaton - http://www.eaton.com/mgeops Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.free.fr/ -- FFE for nut 2.4.3 https://bugs.launchpad.net/bugs/535152 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 447586] Re: megatec_usb does not work anymore with a Trust PW-4130M UPS
Hey Björn, 2009/10/26 Björn Torkelsson: I extracted the megatec_usb and blazer_usb from the 2.4.1-3ubuntu2 and tried them using the method in comment 5. No sucess though. ** Attachment added: Test with the Blazer driver from karmic (2.4.1-3ubuntu2) http://launchpadlibrarian.net/34425912/blazer-karmic.txt -- megatec_usb does not work anymore with a Trust PW-4130M UPS https://bugs.launchpad.net/bugs/447586 thanks for these tests and feedback. reading back the thread, blazer_usb in the trunk is working. the fact is that there were changes here, but no version bump (still 0.03) which led to confusion here. the attached patch should fix this issue. cheers, Arnaud -- Linux / Unix Expert RD - Eaton - http://www.eaton.com/mgeops Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.free.fr/ ** Attachment added: trust-pw4130m.diff http://launchpadlibrarian.net/34549731/trust-pw4130m.diff -- megatec_usb does not work anymore with a Trust PW-4130M UPS https://bugs.launchpad.net/bugs/447586 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 447586] Re: megatec_usb does not work anymore with a Trust PW-4130M UPS
Hey Björn, 2009/10/26 Björn Torkelsson: I extracted the megatec_usb and blazer_usb from the 2.4.1-3ubuntu2 and tried them using the method in comment 5. No sucess though. ** Attachment added: Test with the Blazer driver from karmic (2.4.1-3ubuntu2) http://launchpadlibrarian.net/34425912/blazer-karmic.txt -- megatec_usb does not work anymore with a Trust PW-4130M UPS https://bugs.launchpad.net/bugs/447586 thanks for these tests and feedback. reading back the thread, blazer_usb in the trunk is working. the fact is that there were changes here, but no version bump (still 0.03) which led to confusion here. the attached patch should fix this issue. cheers, Arnaud -- Linux / Unix Expert RD - Eaton - http://www.eaton.com/mgeops Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.free.fr/ ** Attachment added: trust-pw4130m.diff http://launchpadlibrarian.net/34549731/trust-pw4130m.diff -- megatec_usb does not work anymore with a Trust PW-4130M UPS https://bugs.launchpad.net/bugs/447586 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 447586] [NEW] megatec_usb does not work anymore with a Trust PW-4130M UPS
Hi Björn, 2009/10/9 Björn Torkelsson Public bug reported: Binary package hint: nut I have recently upgraded from hardy to intrepid to jaunty. After upgrading to Intrepid the megatec_usb stopped recognizing my Trust PW- 4130M ups, it still does not work on Jaunty. It worked without any problems in hardy. I tried the megatec_usb driver from hardy and it detects the ups. ProblemType: Bug Architecture: amd64 DistroRelease: Ubuntu 9.04 Package: nut 2.4.1-2ubuntu4 [modified: usr/share/nut/driver.list lib/nut/megatec_usb] SourcePackage: nut Uname: Linux 2.6.28-15-server x86_64 ** Affects: nut (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug -- megatec_usb does not work anymore with a Trust PW-4130M UPS https://bugs.launchpad.net/bugs/447586 You received this bug notification because you are subscribed to nut in ubuntu. (leaving the full bug report for the NUT team) I vaguely remember something with this driver and the default subdriver used. Alex may have more info. can you check the latest development version (subversion trunk). For more info on getting and compiling the development release: http://buildbot.ghz.cc/~buildbot/docs/r2003-144/website/download.html Note that you don't need to install nut ; simply running from the build directory is sufficient, using: $ sudo ./drivers/megatec_usb -D -a upsname you might also give a try to blazer_usb, which will replace megatec* $ sudo /lib/nut/blazer_usb -D -a upsname and/or $ sudo ./drivers/blazer_usb -D -a upsname cheers, Arnaud -- Linux / Unix Expert RD - Eaton - http://www.eaton.com/mgeops Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.free.fr/ -- megatec_usb does not work anymore with a Trust PW-4130M UPS https://bugs.launchpad.net/bugs/447586 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
