Re: [Bug 1814314] Re: add nut-scanner to build
Hi fellows, It's always true that I'm more focused on upstream these years, than on Debian an Ubuntu. I'll try to make a summary to explain the what and how on this nut-scanner feature, on the Debian ticket cheers Arno -- Eaton Data Center Automation Solutions - Opensource Leader - http://42ity.org NUT (Network UPS Tools) Project Leader - http://www.networkupstools.org Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.fr -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814314 Title: add nut-scanner to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1814314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1647088] Re: NUT not work with apc backups with usb through usbhid-ups
Hi guys, this is very possibly a duplicate of #1483615 the error is probably due to an issue retrieving a string, and not handled in the driver code. To confirm, please start the driver in debug mode using (as root): /lib/nut/usbhid-ups -u nut -DDD -a myups then /lib/nut/usbhid-ups -u root -DDD -a myups if confirmed, this was fixed upstream: https://github.com/networkupstools/nut/commit/f679a2820e49cbdec4138295de5e8947ee953a8a However, as mentioned in the other ticket, the above fix has some negative impact. this may in the end be due to another ticket (tied to udev and privileges application) logged by Charles Lepple. This privileges issues could lead to the string retrieval issue, causing these bugs. All in all, adding the patch has more benefits than drawbacks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1647088 Title: NUT not work with apc backups with usb through usbhid-ups To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1647088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1099947] Re: driver unable to connect to CyberPower UPS using usbhid-ups driver
** Bug watch added: Debian Bug tracker #721600 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=721600 ** Also affects: nut (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=721600 Importance: Unknown Status: Unknown -- 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/1099947 Title: driver unable to connect to CyberPower UPS using usbhid-ups driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1099947/+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 1099947] Re: driver unable to connect to CyberPower UPS using usbhid-ups driver
Logged upstream, fixed and due with the next 2.7.3 release: https://github.com/networkupstools/nut/issues/140 -- 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/1099947 Title: driver unable to connect to CyberPower UPS using usbhid-ups driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1099947/+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 1099947] Re: driver unable to connect to CyberPower UPS using usbhid-ups driver
** Bug watch added: Debian Bug tracker #721600 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=721600 ** Also affects: nut (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=721600 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1099947 Title: driver unable to connect to CyberPower UPS using usbhid-ups driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1099947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1099947] Re: driver unable to connect to CyberPower UPS using usbhid-ups driver
Logged upstream, fixed and due with the next 2.7.3 release: https://github.com/networkupstools/nut/issues/140 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1099947 Title: driver unable to connect to CyberPower UPS using usbhid-ups driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1099947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1197878] Re: SNMPv3 not working with APC
The user has found a solution: https://github.com/networkupstools/nut/commit/7ab6c65872f663eefa9c6cd0fc73942c3540b5b8 Simply add privProtocol=AES to your UPS entry in /etc/nut/ups.conf, i.e.: [myups] driver = snmp-ups privProtocol=AES ** Changed in: nut (Ubuntu) Status: Confirmed = Fix Released ** Changed in: nut (Ubuntu) Assignee: (unassigned) = Arnaud Quette (aquette) -- 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/1197878 Title: SNMPv3 not working with APC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1197878/+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 1197878] Re: SNMPv3 not working with APC
I forgot: could you please confirm back, so that I can update NUT HCL. -- 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/1197878 Title: SNMPv3 not working with APC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1197878/+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 1197878] Re: SNMPv3 not working with APC
I forgot: could you please confirm back, so that I can update NUT HCL. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1197878 Title: SNMPv3 not working with APC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1197878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1197878] Re: SNMPv3 not working with APC
The user has found a solution: https://github.com/networkupstools/nut/commit/7ab6c65872f663eefa9c6cd0fc73942c3540b5b8 Simply add privProtocol=AES to your UPS entry in /etc/nut/ups.conf, i.e.: [myups] driver = snmp-ups privProtocol=AES ** Changed in: nut (Ubuntu) Status: Confirmed = Fix Released ** Changed in: nut (Ubuntu) Assignee: (unassigned) = Arnaud Quette (aquette) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1197878 Title: SNMPv3 not working with APC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1197878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1197878] [NEW] SNMPv3 not working with APC
Have you tried without mentioning mibs=apcc in ups.conf? Arno -- (sent from my eeePad... please excuse my brevity) -- 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/1197878 Title: SNMPv3 not working with APC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1197878/+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 1197878] [NEW] SNMPv3 not working with APC
Have you tried without mentioning mibs=apcc in ups.conf? Arno -- (sent from my eeePad... please excuse my brevity) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1197878 Title: SNMPv3 not working with APC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1197878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 915985] Re: usbhid-ups regression (APC BE525-RS)
Dmitry, 2012/9/11 Frederic Bohe 915...@bugs.launchpad.net Please see http://lists.alioth.debian.org/pipermail/nut- upsuser/2012-September/007909.html please check the above reference pointed by Fred. This is the solution you were waiting for. To Ubuntu packagers fellows: the patch to be applied are http://trac.networkupstools.org/projects/nut/changeset/3721 http://trac.networkupstools.org/projects/nut/changeset/3723 These patches also applies to 2.6.1 (the version of the present report), though there are a few hunks on the first one. Since these only impacts source files, there is nothing else required than patching before the build. cheers, Arnaud -- Linux / Unix / Opensource Engineering Expert - Eaton - http://opensource.eaton.com Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.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/915985 Title: usbhid-ups regression (APC BE525-RS) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/915985/+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 915985] Re: usbhid-ups regression (APC BE525-RS)
Dmitry, 2012/9/11 Frederic Bohe 915...@bugs.launchpad.net Please see http://lists.alioth.debian.org/pipermail/nut- upsuser/2012-September/007909.html please check the above reference pointed by Fred. This is the solution you were waiting for. To Ubuntu packagers fellows: the patch to be applied are http://trac.networkupstools.org/projects/nut/changeset/3721 http://trac.networkupstools.org/projects/nut/changeset/3723 These patches also applies to 2.6.1 (the version of the present report), though there are a few hunks on the first one. Since these only impacts source files, there is nothing else required than patching before the build. cheers, Arnaud -- Linux / Unix / Opensource Engineering Expert - Eaton - http://opensource.eaton.com Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.fr -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/915985 Title: usbhid-ups regression (APC BE525-RS) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/915985/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1014347] Re: NUT License prevents distribution of SSL-enabled builds
We (NUT upstream) are working on fixing this long term issue. The option we've chosen is to propose a 2nd implementation, beside of OpenSSL, using Mozilla NSS. There is a branch available, that is currently under heavy testing: https://github.com/aquette/nut/tree/ssl-nss-port-CFL This will be available in NUT 2.8.0 (exact release date to be defined) ** Changed in: nut (Ubuntu) Status: New = In Progress ** Changed in: nut (Ubuntu) Assignee: (unassigned) = Arnaud Quette (aquette) ** Bug watch added: Red Hat Bugzilla #347771 https://bugzilla.redhat.com/show_bug.cgi?id=347771 ** Also affects: nut (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=347771 Importance: Unknown Status: Unknown -- 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/1014347 Title: NUT License prevents distribution of SSL-enabled builds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1014347/+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 920844] Re: nut-client is missing /etc/init.d/ups-monitor for MODE=netclient (is in nut-server)
This will be fixed with the next sync with Debian (nut-2.6.3-2 or better, nut 2.6.4-1) -- 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/920844 Title: nut-client is missing /etc/init.d/ups-monitor for MODE=netclient (is in nut-server) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/920844/+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 1014347] Re: NUT License prevents distribution of SSL-enabled builds
We (NUT upstream) are working on fixing this long term issue. The option we've chosen is to propose a 2nd implementation, beside of OpenSSL, using Mozilla NSS. There is a branch available, that is currently under heavy testing: https://github.com/aquette/nut/tree/ssl-nss-port-CFL This will be available in NUT 2.8.0 (exact release date to be defined) ** Changed in: nut (Ubuntu) Status: New = In Progress ** Changed in: nut (Ubuntu) Assignee: (unassigned) = Arnaud Quette (aquette) ** Bug watch added: Red Hat Bugzilla #347771 https://bugzilla.redhat.com/show_bug.cgi?id=347771 ** Also affects: nut (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=347771 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1014347 Title: NUT License prevents distribution of SSL-enabled builds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1014347/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 920844] Re: nut-client is missing /etc/init.d/ups-monitor for MODE=netclient (is in nut-server)
This will be fixed with the next sync with Debian (nut-2.6.3-2 or better, nut 2.6.4-1) -- Arnaud -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/920844 Title: nut-client is missing /etc/init.d/ups-monitor for MODE=netclient (is in nut-server) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/920844/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 915985] Re: usbhid-ups regression (APC BE525-RS)
2012/6/9 Dmitry Andreychuk 915...@bugs.launchpad.net I'll test it next week, as soon as i get to the hardware. great, thanks. 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/915985 Title: usbhid-ups regression (APC BE525-RS) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/915985/+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 915985] Re: usbhid-ups regression (APC BE525-RS)
2012/6/9 Dmitry Andreychuk 915...@bugs.launchpad.net I'll test it next week, as soon as i get to the hardware. great, thanks. 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/915985 Title: usbhid-ups regression (APC BE525-RS) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/915985/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 915985] Re: usbhid-ups regression (APC BE525-RS)
Dimitry, can you please test the last patch I sent (apc-hid-overflow-2.diff) and report the output? cheers, --- Arnaud ** Changed in: nut (Ubuntu) Assignee: (unassigned) = Arnaud Quette (aquette) ** Changed in: nut (Ubuntu) Status: Confirmed = In Progress -- 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/915985 Title: usbhid-ups regression (APC BE525-RS) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/915985/+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 915985] Re: usbhid-ups regression (APC BE525-RS)
Dimitry, can you please test the last patch I sent (apc-hid-overflow-2.diff) and report the output? cheers, --- Arnaud ** Changed in: nut (Ubuntu) Assignee: (unassigned) = Arnaud Quette (aquette) ** Changed in: nut (Ubuntu) Status: Confirmed = In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/915985 Title: usbhid-ups regression (APC BE525-RS) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/915985/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 575573] Re: libusb_get_interrupt: Connection timed out
we (NUT upstream) had a lot of success report with this specific type of units (USB 0x0665:0x5161) since this bug report, using blazer_usb instead of megatec_usb. Considering the bug age, the lack of activity (feedback) and the existence of a solution, I'm thus closing this bug. If you feel this issue still affects you, please reopen the present bug. cheers --- Arnaud ** Changed in: nut (Ubuntu) Status: Fix Committed = Fix Released -- 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/575573 Title: libusb_get_interrupt: Connection timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/575573/+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 839509] Re: nut can not log to syslog when shutdown
Considering that NUT can't log the poweroff) actions, since this action is called from halt, there is no RW filesystem at this stage. So the log_* LSB functions are really called for console output. upsmon already logged that it was bringing down the system, so there is no need to add more... in the syslog at least. I'm thus closing this bug. cheers -- Arnaud ** Changed in: nut (Ubuntu) Status: New = Invalid -- 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/839509 Title: nut can not log to syslog when shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/839509/+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 608182] Re: problems with ups (mge pulsar es 8+)
Wolfgang, I'm closing the bug since you have a fix. If you feel you are still facing an issue, don't hesitate to reopen this bug, or open a new one. cheers, --- Arnaud ** Changed in: nut (Ubuntu) Status: Triaged = Fix Released -- 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
[Bug 575573] Re: libusb_get_interrupt: Connection timed out
we (NUT upstream) had a lot of success report with this specific type of units (USB 0x0665:0x5161) since this bug report, using blazer_usb instead of megatec_usb. Considering the bug age, the lack of activity (feedback) and the existence of a solution, I'm thus closing this bug. If you feel this issue still affects you, please reopen the present bug. cheers --- Arnaud ** Changed in: nut (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/575573 Title: libusb_get_interrupt: Connection timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/575573/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 839509] Re: nut can not log to syslog when shutdown
Considering that NUT can't log the poweroff) actions, since this action is called from halt, there is no RW filesystem at this stage. So the log_* LSB functions are really called for console output. upsmon already logged that it was bringing down the system, so there is no need to add more... in the syslog at least. I'm thus closing this bug. cheers -- Arnaud ** Changed in: nut (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/839509 Title: nut can not log to syslog when shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/839509/+subscriptions -- 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+)
Wolfgang, I'm closing the bug since you have a fix. If you feel you are still facing an issue, don't hesitate to reopen this bug, or open a new one. cheers, --- Arnaud ** Changed in: nut (Ubuntu) Status: Triaged = Fix Released -- 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 915985] Re: [Nut-upsuser] libusb_get_report: Unknown error
2012/4/11 Robert Ayrapetyan robert.ayrapet...@gmail.com Seems I've missed confirmation mail somewhere, now registered. have you patched your 2.6.1 or used trunk + the patch? I've used trunk + the patch. I'd be interested in a trace without the patch, to see if we're still on the overflow side. trunk (rev.3529) with no patch log attached. Btw I've checked all logs I've sent so far - all of them contain: 1.199490 libusb_get_report: Unknown error 1.199512 Can't retrieve Report 0c: Input/output error Seems you are talking about Dmitry's case (overflow). you're right: your issues are the same, but BSD doesn't report EOVERFLOW has it should. while Dmitry is running on Linux, the patch should work there. @Robert: could you please run the test again (with wathever version), using debug level 5 (-D) and doing export USB_DEBUG=3 before launching the driver? if there is no way to catch overflow on BSD, I fear I'll have to create a driver option to bypass this... cheers, Arno On 04/11/12 16:35, Arnaud Quette wrote: 2012/4/11 Robert Ayrapetyan robert.ayrapet...@gmail.com mailto:robert.ayrapetyan@**gmail.com robert.ayrapet...@gmail.com Hi. Hi Robert, please check your subscription. I'm still told that you're not subscribed! Mine output after patch looks same (attached). in fact, it's different. It's no more an overflow error, but an I/O error! have you patched your 2.6.1 or used trunk + the patch? in the latter case, I'd be interested in a trace without the patch, to see if we're still on the overflow side. On Wed, Apr 11, 2012 at 12:55 AM, Arnaud Quette aquette@gmail.com mailto:aquette@gmail.com** wrote: Hi Robert and Dmitry, I'm crossing LP with the nut mailing list, since this is the same EOVERFLOW issue. @Dmitry: it comes out that my previous patch was missing the libusb.c part :-/ to both, the attached patch should fix your issue. please send compressed debug output to confirm the fix. I'll have to do some more testing tomorrow since it's blind coded (Ie, just compiled, not tested with HW) cheers, Arnaud cheers, Arnaud -- Linux / Unix Expert RD - Eaton - http://powerquality.eaton.com Network UPS Tools (NUT) Project Leader - http://www.networkupstools.** org/ 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/915985 Title: usbhid-ups regression (APC BE525-RS) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/915985/+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 915985] Re: [Nut-upsuser] libusb_get_report: Unknown error
2012/4/11 Robert Ayrapetyan robert.ayrapet...@gmail.com Seems I've missed confirmation mail somewhere, now registered. have you patched your 2.6.1 or used trunk + the patch? I've used trunk + the patch. I'd be interested in a trace without the patch, to see if we're still on the overflow side. trunk (rev.3529) with no patch log attached. Btw I've checked all logs I've sent so far - all of them contain: 1.199490 libusb_get_report: Unknown error 1.199512 Can't retrieve Report 0c: Input/output error Seems you are talking about Dmitry's case (overflow). you're right: your issues are the same, but BSD doesn't report EOVERFLOW has it should. while Dmitry is running on Linux, the patch should work there. @Robert: could you please run the test again (with wathever version), using debug level 5 (-D) and doing export USB_DEBUG=3 before launching the driver? if there is no way to catch overflow on BSD, I fear I'll have to create a driver option to bypass this... cheers, Arno On 04/11/12 16:35, Arnaud Quette wrote: 2012/4/11 Robert Ayrapetyan robert.ayrapet...@gmail.com mailto:robert.ayrapetyan@**gmail.com robert.ayrapet...@gmail.com Hi. Hi Robert, please check your subscription. I'm still told that you're not subscribed! Mine output after patch looks same (attached). in fact, it's different. It's no more an overflow error, but an I/O error! have you patched your 2.6.1 or used trunk + the patch? in the latter case, I'd be interested in a trace without the patch, to see if we're still on the overflow side. On Wed, Apr 11, 2012 at 12:55 AM, Arnaud Quette aquette@gmail.com mailto:aquette@gmail.com** wrote: Hi Robert and Dmitry, I'm crossing LP with the nut mailing list, since this is the same EOVERFLOW issue. @Dmitry: it comes out that my previous patch was missing the libusb.c part :-/ to both, the attached patch should fix your issue. please send compressed debug output to confirm the fix. I'll have to do some more testing tomorrow since it's blind coded (Ie, just compiled, not tested with HW) cheers, Arnaud cheers, Arnaud -- Linux / Unix Expert RD - Eaton - http://powerquality.eaton.com Network UPS Tools (NUT) Project Leader - http://www.networkupstools.** org/ 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/915985 Title: usbhid-ups regression (APC BE525-RS) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/915985/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 915985] Re: [Nut-upsuser] libusb_get_report: Unknown error
2012/4/11 Robert Ayrapetyan robert.ayrapet...@gmail.com Hi. Hi Robert, please check your subscription. I'm still told that you're not subscribed! Mine output after patch looks same (attached). in fact, it's different. It's no more an overflow error, but an I/O error! have you patched your 2.6.1 or used trunk + the patch? in the latter case, I'd be interested in a trace without the patch, to see if we're still on the overflow side. On Wed, Apr 11, 2012 at 12:55 AM, Arnaud Quette aquette@gmail.com wrote: Hi Robert and Dmitry, I'm crossing LP with the nut mailing list, since this is the same EOVERFLOW issue. @Dmitry: it comes out that my previous patch was missing the libusb.c part :-/ to both, the attached patch should fix your issue. please send compressed debug output to confirm the fix. I'll have to do some more testing tomorrow since it's blind coded (Ie, just compiled, not tested with HW) cheers, Arnaud 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/915985 Title: usbhid-ups regression (APC BE525-RS) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/915985/+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 915985] Re: [Nut-upsuser] libusb_get_report: Unknown error
2012/4/11 Robert Ayrapetyan robert.ayrapet...@gmail.com Hi. Hi Robert, please check your subscription. I'm still told that you're not subscribed! Mine output after patch looks same (attached). in fact, it's different. It's no more an overflow error, but an I/O error! have you patched your 2.6.1 or used trunk + the patch? in the latter case, I'd be interested in a trace without the patch, to see if we're still on the overflow side. On Wed, Apr 11, 2012 at 12:55 AM, Arnaud Quette aquette@gmail.com wrote: Hi Robert and Dmitry, I'm crossing LP with the nut mailing list, since this is the same EOVERFLOW issue. @Dmitry: it comes out that my previous patch was missing the libusb.c part :-/ to both, the attached patch should fix your issue. please send compressed debug output to confirm the fix. I'll have to do some more testing tomorrow since it's blind coded (Ie, just compiled, not tested with HW) cheers, Arnaud 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/915985 Title: usbhid-ups regression (APC BE525-RS) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/915985/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 915985] Re: [Nut-upsuser] libusb_get_report: Unknown error
Hi Robert and Dmitry, I'm crossing LP with the nut mailing list, since this is the same EOVERFLOW issue. @Dmitry: it comes out that my previous patch was missing the libusb.c part :-/ to both, the attached patch should fix your issue. please send compressed debug output to confirm the fix. I'll have to do some more testing tomorrow since it's blind coded (Ie, just compiled, not tested with HW) cheers, Arnaud ** Attachment added: apc-hid-overflow-2.diff https://bugs.launchpad.net/bugs/915985/+attachment/3043072/+files/apc-hid-overflow-2.diff -- 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/915985 Title: usbhid-ups regression (APC BE525-RS) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/915985/+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 915985] Re: [Nut-upsuser] libusb_get_report: Unknown error
Hi Robert and Dmitry, I'm crossing LP with the nut mailing list, since this is the same EOVERFLOW issue. @Dmitry: it comes out that my previous patch was missing the libusb.c part :-/ to both, the attached patch should fix your issue. please send compressed debug output to confirm the fix. I'll have to do some more testing tomorrow since it's blind coded (Ie, just compiled, not tested with HW) cheers, Arnaud ** Attachment added: apc-hid-overflow-2.diff https://bugs.launchpad.net/bugs/915985/+attachment/3043072/+files/apc-hid-overflow-2.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/915985 Title: usbhid-ups regression (APC BE525-RS) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/915985/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 779512] Re: nut-2.6.0-1ubuntu3 behavior regression
Hi Martin, thanks for your confirmation. I'm now closing this bug. Arnaud ** Changed in: nut (Ubuntu) Assignee: (unassigned) = Arnaud Quette (aquette) ** Changed in: nut (Ubuntu) Status: Fix Committed = Fix Released -- 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
[Bug 575573] Re: libusb_get_interrupt: Connection timed out
Dear all, could you all please try blazer_usb, which has replaced megatec_usb for some time. blazer_usb has improved a lot the situation, and many issues, like yours, have been fixed with it. cheers, Arnaud ** Changed in: nut (Ubuntu) Status: Confirmed = Fix Committed ** Changed in: nut (Ubuntu) Assignee: (unassigned) = Arnaud Quette (aquette) -- 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/575573 Title: libusb_get_interrupt: Connection timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/575573/+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 920844] Re: nut-client is missing /etc/init.d/ups-monitor for MODE=netclient (is in nut-server)
** Changed in: nut (Ubuntu) Assignee: (unassigned) = Arnaud Quette (aquette) ** Changed in: nut (Ubuntu) Status: New = In Progress -- 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/920844 Title: nut-client is missing /etc/init.d/ups-monitor for MODE=netclient (is in nut-server) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/920844/+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 779512] Re: nut-2.6.0-1ubuntu3 behavior regression
Hi Martin, thanks for your confirmation. I'm now closing this bug. Arnaud ** Changed in: nut (Ubuntu) Assignee: (unassigned) = Arnaud Quette (aquette) ** Changed in: nut (Ubuntu) Status: Fix Committed = Fix Released -- 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 575573] Re: libusb_get_interrupt: Connection timed out
Dear all, could you all please try blazer_usb, which has replaced megatec_usb for some time. blazer_usb has improved a lot the situation, and many issues, like yours, have been fixed with it. cheers, Arnaud ** Changed in: nut (Ubuntu) Status: Confirmed = Fix Committed ** Changed in: nut (Ubuntu) Assignee: (unassigned) = Arnaud Quette (aquette) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/575573 Title: libusb_get_interrupt: Connection timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/575573/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 920844] Re: nut-client is missing /etc/init.d/ups-monitor for MODE=netclient (is in nut-server)
** Changed in: nut (Ubuntu) Assignee: (unassigned) = Arnaud Quette (aquette) ** Changed in: nut (Ubuntu) Status: New = In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/920844 Title: nut-client is missing /etc/init.d/ups-monitor for MODE=netclient (is in nut-server) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/920844/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 920844] Re: nut-client is missing /etc/init.d/ups-monitor for MODE=netclient (is in nut-server)
** Bug watch added: Debian Bug tracker #634858 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=634858 ** Also affects: nut (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=634858 Importance: Unknown Status: Unknown -- 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/920844 Title: nut-client is missing /etc/init.d/ups-monitor for MODE=netclient (is in nut-server) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/920844/+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 328057] Re: virtualbox's udev rule overwrite nut rule about group owner
This has been fixed where it should, Ie in VirtualBox. The fix seems to be available since VirtualBox 4.0: https://www.virtualbox.org/ticket/7759 Arnaud ** Bug watch added: Virtualbox Trac #7759 http://www.virtualbox.org/ticket/7759 ** Changed in: nut (Ubuntu) Status: Confirmed = Fix Released -- 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/328057 Title: virtualbox's udev rule overwrite nut rule about group owner To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/328057/+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
NUT release 2.6.2 has fixed the regression in udev rules file creation. In case you're stuck with an older version, I've attached a udev rules file. Just overwrite the one on your system, using: 1) first, identify the current location of the udev file: $ ls /???/udev/rules.d/*nut* This should point either '/etc/udev/rules.d/52-nut-usbups.rules' (older release) or '/lib/udev/rules.d/52-nut-usbups.rules' 2) now, overwrite this file using the one provided here: $ cp -f /path/to/new/52-nut-usbups.rules /???/udev/rules.d/52-nut-usbups.rules Remember to replace '???' by either 'etc' or 'lib', according to the result of (1). 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/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
--- Ubuntu Bug Squad volunteer triager http://wiki.ubuntu.com/BugSquad ** Attachment added: Fixed udev rules file for NUT https://bugs.launchpad.net/ubuntu/+source/nut/+bug/578200/+attachment/2690918/+files/52-nut-usbups.rules ** Changed in: nut (Ubuntu) Status: New = Fix Released -- 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 779512] Re: nut-2.6.0-1ubuntu3 behavior regression
Martin, could you please check this bug report, and apply the udev related procedure I've documented at the end of the thread: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/578200 Once applied, stop nut, unplug/replug your UPS USB cord, and restart nut (at least the driver), and report back the status. Arnaud ** Changed in: nut (Ubuntu) Status: Triaged = Fix Committed -- 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
[Bug 920844] Re: nut-client is missing /etc/init.d/ups-monitor for MODE=netclient (is in nut-server)
** Bug watch added: Debian Bug tracker #634858 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=634858 ** Also affects: nut (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=634858 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/920844 Title: nut-client is missing /etc/init.d/ups-monitor for MODE=netclient (is in nut-server) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/920844/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 328057] Re: virtualbox's udev rule overwrite nut rule about group owner
This has been fixed where it should, Ie in VirtualBox. The fix seems to be available since VirtualBox 4.0: https://www.virtualbox.org/ticket/7759 Arnaud ** Bug watch added: Virtualbox Trac #7759 http://www.virtualbox.org/ticket/7759 ** Changed in: nut (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/328057 Title: virtualbox's udev rule overwrite nut rule about group owner To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/328057/+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
NUT release 2.6.2 has fixed the regression in udev rules file creation. In case you're stuck with an older version, I've attached a udev rules file. Just overwrite the one on your system, using: 1) first, identify the current location of the udev file: $ ls /???/udev/rules.d/*nut* This should point either '/etc/udev/rules.d/52-nut-usbups.rules' (older release) or '/lib/udev/rules.d/52-nut-usbups.rules' 2) now, overwrite this file using the one provided here: $ cp -f /path/to/new/52-nut-usbups.rules /???/udev/rules.d/52-nut-usbups.rules Remember to replace '???' by either 'etc' or 'lib', according to the result of (1). Arnaud -- 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
[Bug 578200] Re: (megatec_usb) error: Driver not connected
--- Ubuntu Bug Squad volunteer triager http://wiki.ubuntu.com/BugSquad ** Attachment added: Fixed udev rules file for NUT https://bugs.launchpad.net/ubuntu/+source/nut/+bug/578200/+attachment/2690918/+files/52-nut-usbups.rules ** Changed in: nut (Ubuntu) Status: New = Fix Released -- 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
[Bug 779512] Re: nut-2.6.0-1ubuntu3 behavior regression
Martin, could you please check this bug report, and apply the udev related procedure I've documented at the end of the thread: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/578200 Once applied, stop nut, unplug/replug your UPS USB cord, and restart nut (at least the driver), and report back the status. 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/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 915985] Re: usbhid-ups regression (APC BE525-RS)
2012/1/19 Dmitry Andreychuk 915...@bugs.launchpad.net: Attaching logs with power failure for versions 2.6.1-2ubuntu2 and 2.6.3. Power failures and power returns are marked with NOTE in the logs. I noticed that UPS.PowerSummary.RemainingCapacity came with input report only once. The device didn't send it upon changes for some reason. buggy firmware again... Attached is a patch against the latest development version (Subversion trunk). It also applies on 2.6.2 and 2.6.3 using (from within the top source dir): $ patch -p0 /path/to/apc-hid-overflow.diff Could you please test it (same procedure as before) and report back (including a driver debug output) to see if things are going better? 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/ ** Patch added: apc-hid-overflow.diff https://bugs.launchpad.net/bugs/915985/+attachment/2689102/+files/apc-hid-overflow.diff -- 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/915985 Title: usbhid-ups regression (APC BE525-RS) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/915985/+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 915985] Re: usbhid-ups regression (APC BE525-RS)
2012/1/19 Dmitry Andreychuk 915...@bugs.launchpad.net: Attaching logs with power failure for versions 2.6.1-2ubuntu2 and 2.6.3. Power failures and power returns are marked with NOTE in the logs. I noticed that UPS.PowerSummary.RemainingCapacity came with input report only once. The device didn't send it upon changes for some reason. buggy firmware again... Attached is a patch against the latest development version (Subversion trunk). It also applies on 2.6.2 and 2.6.3 using (from within the top source dir): $ patch -p0 /path/to/apc-hid-overflow.diff Could you please test it (same procedure as before) and report back (including a driver debug output) to see if things are going better? 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/ ** Patch added: apc-hid-overflow.diff https://bugs.launchpad.net/bugs/915985/+attachment/2689102/+files/apc-hid-overflow.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/915985 Title: usbhid-ups regression (APC BE525-RS) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/915985/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 915985] Re: usbhid-ups regression (APC BE525-RS)
Hi Sergey, cc'ing NUT users list, since others may be interested in the topic (for those, follow the bug link below). 2012/1/16 Dmitry Andreychuk 915...@bugs.launchpad.net: Hi Arnaud, Thanks for your reply! Attaching output for 2.6.0-1ubuntu3. ** Attachment added: usbhid-ups_2.6.0-1ubuntu3.log https://bugs.launchpad.net/ubuntu/+source/nut/+bug/915985/+attachment/2676822/+files/usbhid-ups_2.6.0-1ubuntu3.log -- You received this bug notification because you are subscribed to nut in Ubuntu. https://bugs.launchpad.net/bugs/915985 Title: usbhid-ups regression (APC BE525-RS) ok, I got it! first, both of your issues are related. we reverted in 2.6.1 a change on how we get data from the UPS. we were previously requesting a very large size, while we now only ask for the data actual size. your device is reporting extra garbage data (buggy firmware) when requesting (Feature report) battery.charge (UPS.PowerSummary.RemainingCapacity), while the notified version (Input report, sent by the device upon changes, like SNMP traps) is good. this cause, at libusb level, an EOVERFLOW with 2.6.1+, which is logged every 30 sec. (polling freq), and cause this data to not be processed. now, Input report data should take over, and feed battery.charge! I'd be interested in seeing a debug output of a faulty version (2.6.1+), that includes a power failure. the bad news: ATM, I've no solution that can be applied upstream and distributed. the good news: well, you already know: keep running 2.6.0 for the time being. 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/915985 Title: usbhid-ups regression (APC BE525-RS) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/915985/+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 915985] Re: usbhid-ups regression (APC BE525-RS)
Hi Sergey, cc'ing NUT users list, since others may be interested in the topic (for those, follow the bug link below). 2012/1/16 Dmitry Andreychuk 915...@bugs.launchpad.net: Hi Arnaud, Thanks for your reply! Attaching output for 2.6.0-1ubuntu3. ** Attachment added: usbhid-ups_2.6.0-1ubuntu3.log https://bugs.launchpad.net/ubuntu/+source/nut/+bug/915985/+attachment/2676822/+files/usbhid-ups_2.6.0-1ubuntu3.log -- You received this bug notification because you are subscribed to nut in Ubuntu. https://bugs.launchpad.net/bugs/915985 Title: usbhid-ups regression (APC BE525-RS) ok, I got it! first, both of your issues are related. we reverted in 2.6.1 a change on how we get data from the UPS. we were previously requesting a very large size, while we now only ask for the data actual size. your device is reporting extra garbage data (buggy firmware) when requesting (Feature report) battery.charge (UPS.PowerSummary.RemainingCapacity), while the notified version (Input report, sent by the device upon changes, like SNMP traps) is good. this cause, at libusb level, an EOVERFLOW with 2.6.1+, which is logged every 30 sec. (polling freq), and cause this data to not be processed. now, Input report data should take over, and feed battery.charge! I'd be interested in seeing a debug output of a faulty version (2.6.1+), that includes a power failure. the bad news: ATM, I've no solution that can be applied upstream and distributed. the good news: well, you already know: keep running 2.6.0 for the time being. 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/915985 Title: usbhid-ups regression (APC BE525-RS) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/915985/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 915985] [NEW] usbhid-ups regression (APC BE525-RS)
Hi Dmitry, 2012/1/13 Dmitry Andreychuk Public bug reported: Ubuntu 11.10 nut 2.6.1-2ubuntu2 UPS model: APC Back-UPS ES 525 (BE525-RS) driver: usbhid-ups I get the following error approximately every 30 seconds: usb 4-2: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 161 rq 1 len 2 ret -75 The simalar error is described in the driver's known issues but increasing pollinterval doesn't help - the interval between error messages just increases accordingly. I also noticed that battery.charge returned by upsc doesn't change when the UPS is actually discharging. I called upsc, unplugged UPS and called upsc again after a while: ups.status, battery.runtime and input.voltage reasonably changed but battery.charge stayed at 100%. So maybe the retreiving of this variable is working incorrectly. as per your provided log, both issues are related: errno -75 is EOVERFLOW (Value too large for defined data type). We can see 1 successful retrieval of battery. charge (HID path: UPS.PowerSummary.RemainingCapacity, ReportID: 0x0c), obtained through the interrupt pipe (ie, not requested explicitly, but sent by the device itself, upon change) All other request are failing, with EOVERFLOW, which should mean a fault from the device (sending more data than it should I've tested a few other versions and got this: 2.4.3-1ubuntu3.1 - ok 2.6.0-1ubuntu3 - ok 2.6.1-2ubuntu2 - error 2.6.2-1ubuntu1 - error 2.6.3 (upstream) - error. Actually I didn't manage to run daemon that I built from source, so I ran just the driver and it reported the same error. could you please send an output from a working version (preferably 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/915985 Title: usbhid-ups regression (APC BE525-RS) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/915985/+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 915985] [NEW] usbhid-ups regression (APC BE525-RS)
Hi Dmitry, 2012/1/13 Dmitry Andreychuk Public bug reported: Ubuntu 11.10 nut 2.6.1-2ubuntu2 UPS model: APC Back-UPS ES 525 (BE525-RS) driver: usbhid-ups I get the following error approximately every 30 seconds: usb 4-2: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 161 rq 1 len 2 ret -75 The simalar error is described in the driver's known issues but increasing pollinterval doesn't help - the interval between error messages just increases accordingly. I also noticed that battery.charge returned by upsc doesn't change when the UPS is actually discharging. I called upsc, unplugged UPS and called upsc again after a while: ups.status, battery.runtime and input.voltage reasonably changed but battery.charge stayed at 100%. So maybe the retreiving of this variable is working incorrectly. as per your provided log, both issues are related: errno -75 is EOVERFLOW (Value too large for defined data type). We can see 1 successful retrieval of battery. charge (HID path: UPS.PowerSummary.RemainingCapacity, ReportID: 0x0c), obtained through the interrupt pipe (ie, not requested explicitly, but sent by the device itself, upon change) All other request are failing, with EOVERFLOW, which should mean a fault from the device (sending more data than it should I've tested a few other versions and got this: 2.4.3-1ubuntu3.1 - ok 2.6.0-1ubuntu3 - ok 2.6.1-2ubuntu2 - error 2.6.2-1ubuntu1 - error 2.6.3 (upstream) - error. Actually I didn't manage to run daemon that I built from source, so I ran just the driver and it reported the same error. could you please send an output from a working version (preferably 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/915985 Title: usbhid-ups regression (APC BE525-RS) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/915985/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Blueprint servercloud-p-cloud-power-management] Cloud power management
Blueprint changed by Arnaud Quette: Whiteboard changed: Work Items: [aquette] support for power devices in OCS and Fusion inventory: INPROGRESS - NUT integration in Cobbler (replace fence-agents): TODO + NUT integration in Cobbler (replace or complement fence-agents): TODO [aquette] Write juju charm for NUT: TODO [andreserl] Write juju charm for NUT: TODO [aquette] Design OpenStack (Nova, Power Scheduler) integration with PowerWake/PowerNap/NUT: TODO [andreserl] Design OpenStack (Nova, Power Scheduler) integration with PowerWake/PowerNap/NUT: TODO [andreserl] Implement NUT client support in PowerWake: TODO [aquette] Implement NUT client support in PowerWake: TODO [aquette] Implement PowerChain (power distribution tracking) in NUT: INPROGRESS [aquette] Implement configuration library and tool for NUT: TODO [aquette] Implement network support in nut-ipmipsu: TODO - [aquette] Implement fence mode (full args on cmd line, no daemonization) in NUT (probably not needed): POSTPONED + [aquette] Implement fence_nut in fence-agents: TODO + [aquette] Create fence_nut Cobbler template: INPROGRESS [aquette] Check if all supported fence devices are present in NUT too: INPROGRESS - [aquette] Implement IPMI detection in nut-scanner: TODO + [aquette] Implement IPMI detection in nut-scanner: DONE [aquette] Implement Python wrapper for nut-scanner: TODO [aquette] Implement Perl wrapper for nut-scanner (for inventories): TODO [aquette] Update NUT script in Ubuntu QA Regression Testing: DONE - [emilienkia] AppArmor integration: TODO + [emilienkia] AppArmor integration: INPROGRESS Convert NUT initscript to upstart: TODO - Convert NUT initscript to systemd: TODO + [aquette] Convert NUT initscript to systemd: DONE [aquette] Help / NMU FreeIPMI packages: TODO [aquette] MIR for libfreeipmi and libipmimonitoring for nut-ipmi: TODO - [aquette] Package Avahi publication script for NUT: INPROGRESS [aquette] Package Avahi publication script for NUT: INPROGRESS [aquette] Package nut-ipmi (need freeipmi packages update): BLOCKED [aquette] Package java-nut: TODO [aquette] Package nut-scanner: TODO [aquette] NUT debconf support: TODO Remaining bits from UDS-O = Implement NUT support in checkbox: TODO [aquette] Implement support for power management testing in servercloud-p-complex-deployment-testing using NUT: TODO [andreserl] Investigate PowerNap using NUT as a data broker: TODO [aquette] Investigate PowerNap using NUT as a data broker: TODO -- Cloud power management https://blueprints.launchpad.net/ubuntu/+spec/servercloud-p-cloud-power-management -- 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 226405] Re: Missing support for upsmon only configuration (slave)
this has been fixed in nut-2.6.2 packages, though there is still a bug (missing client init script). Final fix scheduled for the next Debian upload / Ubuntu sync. ** Changed in: nut (Ubuntu) Status: Fix Committed = Fix Released -- 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/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-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 226405] Re: Missing support for upsmon only configuration (slave)
this has been fixed in nut-2.6.2 packages, though there is still a bug (missing client init script). Final fix scheduled for the next Debian upload / Ubuntu sync. ** Changed in: nut (Ubuntu) Status: Fix Committed = Fix Released -- 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
Re: [Bug 779512] Re: nut-2.6.0-1ubuntu3 behavior regression
I don't see any message related to usbhid-ups.
Is it started?
we can see hiddev0 (the device linked to the kernel module hiddev) loaded,
but nothing more.
So, try launching again nut, and check back /var/log/syslog for usb and nut
('ups') messages.
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
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
I don't see any message related to usbhid-ups.
Is it started?
we can see hiddev0 (the device linked to the kernel module hiddev) loaded,
but nothing more.
So, try launching again nut, and check back /var/log/syslog for usb and nut
('ups') messages.
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
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 575573] Re: libusb_get_interrupt: Connection timed out
Can you please test with the blazer_usb driver and report back? This one has replaced megatec_usb officially since 2.4.3, but was already available in 2.4.1 (though not as mature). 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/575573 Title: libusb_get_interrupt: Connection timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/575573/+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 545319] Re: nut configuration should be config files, not conffiles
There is an effort underway to provide the needed foundations for adding a decent debconf for generating a suitable configuration. I will leave this bug open as a reminder. thanks for your report, 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/545319 Title: nut configuration should be config files, not conffiles To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/545319/+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 779512] Re: nut-2.6.0-1ubuntu3 behavior regression
Note for Ubuntu packagers: - the original report was an issue with udev, and will be fixed with 2.6.3 upload, - the 2nd one (Martin Ewing) was probably invalid, due to an already running driver instance. I've asked the user for some more feedback. 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/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, I'm adding the nut users list, since other may be interested in. 2011/12/16 Martin Ewing martin.s.ew...@gmail.com I do still have an issue with NUT on Ubuntu Natty (64 bit). I attach my latest info. Will appreciate any further suggestions about how to tame this problem - whether my configuration or otherwise. Thanks! Martin ** Attachment added: ups_problem.txt https://bugs.launchpad.net/ubuntu/+source/nut/+bug/779512/+attachment/2636234/+files/ups_problem.txt What is strange, as per your next mail, is that ls /dev/usb shows hiddev1! Can you please forward us an excerpt of your system log, using the usb pattern. 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/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
[Bug 575573] Re: libusb_get_interrupt: Connection timed out
Can you please test with the blazer_usb driver and report back? This one has replaced megatec_usb officially since 2.4.3, but was already available in 2.4.1 (though not as mature). 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/575573 Title: libusb_get_interrupt: Connection timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/575573/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 779512] Re: nut-2.6.0-1ubuntu3 behavior regression
Note for Ubuntu packagers: - the original report was an issue with udev, and will be fixed with 2.6.3 upload, - the 2nd one (Martin Ewing) was probably invalid, due to an already running driver instance. I've asked the user for some more feedback. 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/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 545319] Re: nut configuration should be config files, not conffiles
There is an effort underway to provide the needed foundations for adding a decent debconf for generating a suitable configuration. I will leave this bug open as a reminder. thanks for your report, Arnaud -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/545319 Title: nut configuration should be config files, not conffiles To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/545319/+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
Hi Martin, I'm adding the nut users list, since other may be interested in. 2011/12/16 Martin Ewing martin.s.ew...@gmail.com I do still have an issue with NUT on Ubuntu Natty (64 bit). I attach my latest info. Will appreciate any further suggestions about how to tame this problem - whether my configuration or otherwise. Thanks! Martin ** Attachment added: ups_problem.txt https://bugs.launchpad.net/ubuntu/+source/nut/+bug/779512/+attachment/2636234/+files/ups_problem.txt What is strange, as per your next mail, is that ls /dev/usb shows hiddev1! Can you please forward us an excerpt of your system log, using the usb pattern. 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/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
[Blueprint servercloud-p-cloud-power-management] Cloud power management
Blueprint changed by Arnaud Quette: Whiteboard changed: Work Items: [aquette] support for power devices in OCS and Fusion inventory: INPROGRESS NUT integration in Cobbler (replace fence-agents): TODO [aquette] Write juju charm for NUT: TODO [andreserl] Write juju charm for NUT: TODO [aquette] Design OpenStack (Nova, Power Scheduler) integration with PowerWake/PowerNap/NUT: TODO [andreserl] Design OpenStack (Nova, Power Scheduler) integration with PowerWake/PowerNap/NUT: TODO [andreserl] Implement NUT client support in PowerWake: TODO [aquette] Implement NUT client support in PowerWake: TODO [aquette] Implement PowerChain (power distribution tracking) in NUT: INPROGRESS [aquette] Implement configuration library and tool for NUT: TODO [aquette] Implement network support in nut-ipmipsu: TODO - [aquette] Implement fence mode (full args on cmd line, no daemonization) in NUT: TODO + [aquette] Implement fence mode (full args on cmd line, no daemonization) in NUT (probably not needed): POSTPONED [aquette] Check if all supported fence devices are present in NUT too: INPROGRESS [aquette] Implement IPMI detection in nut-scanner: TODO [aquette] Implement Python wrapper for nut-scanner: TODO [aquette] Implement Perl wrapper for nut-scanner (for inventories): TODO [aquette] Update NUT script in Ubuntu QA Regression Testing: DONE [emilienkia] AppArmor integration: TODO Convert NUT initscript to upstart: TODO Convert NUT initscript to systemd: TODO [aquette] Help / NMU FreeIPMI packages: TODO [aquette] MIR for libfreeipmi and libipmimonitoring for nut-ipmi: TODO - [aquette] Package Avahi publication script for NUT: TODO + [aquette] Package Avahi publication script for NUT: INPROGRESS + [aquette] Package Avahi publication script for NUT: INPROGRESS [aquette] Package nut-ipmi (need freeipmi packages update): BLOCKED [aquette] Package java-nut: TODO [aquette] Package nut-scanner: TODO [aquette] NUT debconf support: TODO Remaining bits from UDS-O = Implement NUT support in checkbox: TODO [aquette] Implement support for power management testing in servercloud-p-complex-deployment-testing using NUT: TODO [andreserl] Investigate PowerNap using NUT as a data broker: TODO [aquette] Investigate PowerNap using NUT as a data broker: TODO -- Cloud power management https://blueprints.launchpad.net/ubuntu/+spec/servercloud-p-cloud-power-management -- 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 809166] Re: [Cluster-devel] Fix fence-agents manpages
2011/12/6 Fabio M. Di Nitto fabbi...@fabbione.net On 12/6/2011 4:05 PM, Arnaud Quette wrote: Hi Fabio, 2011/12/6 Fabio M. Di Nitto fabbi...@fabbione.net: On 12/6/2011 2:27 PM, Arnaud Quette wrote: Hi Cluster-devel list, You will find attached a patch originating from Ubuntu (Andres Rodriguez), that fixes a few issues in manpages (namely fence_drac and fence_scsi). I wonder why the ubuntu/canonical maintainers can´t post patches directly for upstream inclusion. they obviously can Fabio. But I proposed to do this on my side, since I still have some things to do around fence_eaton... That way, they can focus on other things. After all, it's just posting an email. The actual and important work is to catch bugs and fix this ;-) Please consider applying it. As a side note, you may want to consider Asciidoc [1] to handle generation of manpages, in groff and html format. This already takes care of the groff formating, and would avoid the above kind of issues. That said, iirc you're also doing some POD style extraction, so it may not be fully relevant. goal is to have all manpages generated at build time via fence_agent -o metadata output. Most of patches already exists for those few agents that don´t it. ok, that confirms the POD style approach. I wasn't sure if you were standardizing on this, or going away from. The patch will be obsoleted in the fence-agents release or max two. thanks for these info. I take it as this patch is discarded, and the proper fix will come very soon. 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/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
[Bug 809166] Fix fence-agents manpages
Hi Cluster-devel list, You will find attached a patch originating from Ubuntu (Andres Rodriguez), that fixes a few issues in manpages (namely fence_drac and fence_scsi). Please consider applying it. As a side note, you may want to consider Asciidoc [1] to handle generation of manpages, in groff and html format. This already takes care of the groff formating, and would avoid the above kind of issues. That said, iirc you're also doing some POD style extraction, so it may not be fully relevant. 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/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
[Bug 809166] Re: Update fence-agents to 3.1.5
** Attachment added: fence-agents-manpages.diff https://bugs.launchpad.net/bugs/809166/+attachment/2621786/+files/fence-agents-manpages.diff -- 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
[Bug 809166] Re: [Cluster-devel] Fix fence-agents manpages
Hi Fabio, 2011/12/6 Fabio M. Di Nitto fabbi...@fabbione.net: On 12/6/2011 2:27 PM, Arnaud Quette wrote: Hi Cluster-devel list, You will find attached a patch originating from Ubuntu (Andres Rodriguez), that fixes a few issues in manpages (namely fence_drac and fence_scsi). I wonder why the ubuntu/canonical maintainers can´t post patches directly for upstream inclusion. they obviously can Fabio. But I proposed to do this on my side, since I still have some things to do around fence_eaton... That way, they can focus on other things. After all, it's just posting an email. The actual and important work is to catch bugs and fix this ;-) Please consider applying it. As a side note, you may want to consider Asciidoc [1] to handle generation of manpages, in groff and html format. This already takes care of the groff formating, and would avoid the above kind of issues. That said, iirc you're also doing some POD style extraction, so it may not be fully relevant. goal is to have all manpages generated at build time via fence_agent -o metadata output. Most of patches already exists for those few agents that don´t it. ok, that confirms the POD style approach. I wasn't sure if you were standardizing on this, or going away from. 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/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 servercloud-p-cloud-power-management] Cloud power management
Blueprint changed by Arnaud Quette: Whiteboard changed: Work Items: [aquette] support for power devices in OCS and Fusion inventory: INPROGRESS NUT integration in Cobbler (replace fence-agents): TODO [aquette] Write juju charm for NUT: TODO [andreserl] Write juju charm for NUT: TODO - [aquette] Design OpenStack (Nova, Power Scheduler) integration with PowerWake/PowerNap: TODO - [andreserl] Design OpenStack (Nova, Power Scheduler) integration with PowerWake/PowerNap: TODO + [aquette] Design OpenStack (Nova, Power Scheduler) integration with PowerWake/PowerNap/NUT: TODO + [andreserl] Design OpenStack (Nova, Power Scheduler) integration with PowerWake/PowerNap/NUT: TODO [andreserl] Implement NUT client support in PowerWake: TODO [aquette] Implement NUT client support in PowerWake: TODO [aquette] Implement PowerChain (power distribution tracking) in NUT: INPROGRESS [aquette] Implement configuration library and tool for NUT: INPROGRESS [aquette] Implement network support in nut-ipmipsu: TODO [aquette] Implement fence mode (full args on cmd line, no daemonization) in NUT: TODO [aquette] Check if all supported fence devices are present in NUT too: INPROGRESS [aquette] Implement IPMI detection in nut-scanner: TODO [aquette] Implement Python wrapper for nut-scanner: TODO [aquette] Implement Perl wrapper for nut-scanner (for inventories): TODO [aquette] Update NUT script in Ubuntu QA Regression Testing: DONE [aquette] AppArmor integration: TODO Convert NUT initscript to upstart: TODO Convert NUT initscript to systemd: TODO [aquette] Help / NMU FreeIPMI packages: TODO [aquette] MIR for libfreeipmi and libipmimonitoring for nut-ipmi: TODO [aquette] Package Avahi publication script for NUT: TODO [aquette] Package nut-ipmi (need freeipmi packages update): BLOCKED [aquette] Package java-nut: TODO [aquette] Package nut-scanner: TODO [aquette] NUT debconf support: TODO Remaining bits from UDS-O = Implement NUT support in checkbox: TODO [aquette] Implement support for power management testing in servercloud-p-complex-deployment-testing using NUT: TODO [andreserl] Investigate PowerNap using NUT as a data broker: TODO [aquette] Investigate PowerNap using NUT as a data broker: TODO -- Cloud power management https://blueprints.launchpad.net/ubuntu/+spec/servercloud-p-cloud-power-management -- 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 servercloud-p-cloud-power-management] Cloud power management
Blueprint changed by Arnaud Quette: Whiteboard changed: Work Items: [aquette] support for power devices in OCS and Fusion inventory: INPROGRESS NUT integration in Cobbler (replace fence-agents): TODO [aquette] Write juju charm for NUT: TODO [andreserl] Write juju charm for NUT: TODO [aquette] Design OpenStack (Nova, Power Scheduler) integration with PowerWake/PowerNap/NUT: TODO [andreserl] Design OpenStack (Nova, Power Scheduler) integration with PowerWake/PowerNap/NUT: TODO [andreserl] Implement NUT client support in PowerWake: TODO [aquette] Implement NUT client support in PowerWake: TODO [aquette] Implement PowerChain (power distribution tracking) in NUT: INPROGRESS - [aquette] Implement configuration library and tool for NUT: INPROGRESS + [aquette] Implement configuration library and tool for NUT: TODO [aquette] Implement network support in nut-ipmipsu: TODO [aquette] Implement fence mode (full args on cmd line, no daemonization) in NUT: TODO [aquette] Check if all supported fence devices are present in NUT too: INPROGRESS [aquette] Implement IPMI detection in nut-scanner: TODO [aquette] Implement Python wrapper for nut-scanner: TODO [aquette] Implement Perl wrapper for nut-scanner (for inventories): TODO [aquette] Update NUT script in Ubuntu QA Regression Testing: DONE - [aquette] AppArmor integration: TODO + [emilienkia] AppArmor integration: TODO Convert NUT initscript to upstart: TODO Convert NUT initscript to systemd: TODO [aquette] Help / NMU FreeIPMI packages: TODO [aquette] MIR for libfreeipmi and libipmimonitoring for nut-ipmi: TODO [aquette] Package Avahi publication script for NUT: TODO [aquette] Package nut-ipmi (need freeipmi packages update): BLOCKED [aquette] Package java-nut: TODO [aquette] Package nut-scanner: TODO [aquette] NUT debconf support: TODO Remaining bits from UDS-O = Implement NUT support in checkbox: TODO [aquette] Implement support for power management testing in servercloud-p-complex-deployment-testing using NUT: TODO [andreserl] Investigate PowerNap using NUT as a data broker: TODO [aquette] Investigate PowerNap using NUT as a data broker: TODO -- Cloud power management https://blueprints.launchpad.net/ubuntu/+spec/servercloud-p-cloud-power-management -- 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 809166] Re: Update fence-agents to 3.1.5
Hi Andres, I'm sorry if my comment sound angry but I wasn't :). ok, just wanted to be sure that there wasn't some pending problems ;-) And the Debian maintainer has taken my changes now so I'll be updating it. Thank you! perfect! Though I've not seen a patch on cluster-devel to fix this upstream (still better in the long run)! -- 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 servercloud-p-cloud-power-management] Cloud power management
Blueprint changed by Arnaud Quette: Whiteboard changed: Work Items: [aquette] support for power devices in OCS and Fusion inventory: INPROGRESS NUT integration in Cobbler (replace fence-agents): TODO [aquette] Write juju charm for NUT: TODO [andreserl] Write juju charm for NUT: TODO [aquette] Design OpenStack (Nova, Power Scheduler) integration with PowerWake/PowerNap: TODO [andreserl] Design OpenStack (Nova, Power Scheduler) integration with PowerWake/PowerNap: TODO [aquette] Implement PowerChain (power distribution tracking) in NUT: INPROGRESS - Implement configuration library and tool for NUT: INPROGRESS + [aquette] Implement configuration library and tool for NUT: INPROGRESS [aquette] Implement network support in nut-ipmipsu: TODO - Implement fence mode (full args on cmd line, no daemonization) in NUT: TODO - Check if all supported fence devices are present in NUT too: INPROGRESS + [aquette] Implement fence mode (full args on cmd line, no daemonization) in NUT: TODO + [aquette] Check if all supported fence devices are present in NUT too: INPROGRESS [aquette] Implement IPMI detection in nut-scanner: TODO - Implement Python wrapper for nut-scanner: TODO - Implement Perl wrapper for nut-scanner (for inventories): TODO + [aquette] Implement Python wrapper for nut-scanner: TODO + [aquette] Implement Perl wrapper for nut-scanner (for inventories): TODO [aquette] Update NUT script in Ubuntu QA Regression Testing: DONE [aquette] AppArmor integration: TODO Convert NUT initscript to upstart: TODO Convert NUT initscript to systemd: TODO [aquette] Help / NMU FreeIPMI packages: TODO [aquette] MIR for libfreeipmi and libipmimonitoring for nut-ipmi: TODO [aquette] Package Avahi publication script for NUT: TODO - [aquette] Package nut-ipmi: TODO + [aquette] Package nut-ipmi (need freeipmi packages update): BLOCKED [aquette] Package java-nut: TODO [aquette] Package nut-scanner: TODO - NUT debconf support: TODO + [aquette] NUT debconf support: TODO Remaining bits from UDS-O = Implement NUT support in checkbox: TODO [aquette] Implement support for power management testing in servercloud-p-complex-deployment-testing using NUT: TODO [andreserl] Investigate PowerNap using NUT as a data broker: TODO [aquette] Investigate PowerNap using NUT as a data broker: TODO [andreserl] Implement NUT client support in PowerWake: TODO [aquette] Implement NUT client support in PowerWake: TODO -- Cloud power management https://blueprints.launchpad.net/ubuntu/+spec/servercloud-p-cloud-power-management -- 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 servercloud-p-cloud-power-management] Cloud power management
Blueprint changed by Arnaud Quette: Whiteboard changed: Work Items: [aquette] support for power devices in OCS and Fusion inventory: INPROGRESS NUT integration in Cobbler (replace fence-agents): TODO [aquette] Write juju charm for NUT: TODO [andreserl] Write juju charm for NUT: TODO [aquette] Design OpenStack (Nova, Power Scheduler) integration with PowerWake/PowerNap: TODO [andreserl] Design OpenStack (Nova, Power Scheduler) integration with PowerWake/PowerNap: TODO + [andreserl] Implement NUT client support in PowerWake: TODO + [aquette] Implement NUT client support in PowerWake: TODO [aquette] Implement PowerChain (power distribution tracking) in NUT: INPROGRESS [aquette] Implement configuration library and tool for NUT: INPROGRESS [aquette] Implement network support in nut-ipmipsu: TODO [aquette] Implement fence mode (full args on cmd line, no daemonization) in NUT: TODO [aquette] Check if all supported fence devices are present in NUT too: INPROGRESS [aquette] Implement IPMI detection in nut-scanner: TODO [aquette] Implement Python wrapper for nut-scanner: TODO [aquette] Implement Perl wrapper for nut-scanner (for inventories): TODO [aquette] Update NUT script in Ubuntu QA Regression Testing: DONE [aquette] AppArmor integration: TODO Convert NUT initscript to upstart: TODO Convert NUT initscript to systemd: TODO [aquette] Help / NMU FreeIPMI packages: TODO [aquette] MIR for libfreeipmi and libipmimonitoring for nut-ipmi: TODO [aquette] Package Avahi publication script for NUT: TODO [aquette] Package nut-ipmi (need freeipmi packages update): BLOCKED [aquette] Package java-nut: TODO [aquette] Package nut-scanner: TODO [aquette] NUT debconf support: TODO Remaining bits from UDS-O = Implement NUT support in checkbox: TODO [aquette] Implement support for power management testing in servercloud-p-complex-deployment-testing using NUT: TODO [andreserl] Investigate PowerNap using NUT as a data broker: TODO [aquette] Investigate PowerNap using NUT as a data broker: TODO - [andreserl] Implement NUT client support in PowerWake: TODO - [aquette] Implement NUT client support in PowerWake: TODO -- Cloud power management https://blueprints.launchpad.net/ubuntu/+spec/servercloud-p-cloud-power-management -- 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 servercloud-p-cloud-power-management] Cloud power management
Blueprint changed by Arnaud Quette: Whiteboard changed: + Work Items: support for power devices in OCS and Fusion inventory: INPROGRESS [server-team] NUT integration in Cobbler (replace fence-agents): TODO Write juju charm for NUT: TODO [andreserl] Write juju charm for NUT: TODO Design OpenStack (Nova, Power Scheduler) integration with PowerWake/PowerNap: TODO [andreserl] Design OpenStack (Nova, Power Scheduler) integration with PowerWake/PowerNap: TODO Implement PowerChain (power distribution tracking) in NUT: INPROGRESS - Implement configuration library and tool for NUT: TODO + Implement configuration library and tool for NUT: INPROGRESS Implement network support in nut-ipmipsu: TODO - Implement fence mode (no daemonization) in NUT: TODO - Check if all supported fence devices are present in NUT too: TODO + Implement fence mode (full args on cmd line, no daemonization) in NUT: TODO + Check if all supported fence devices are present in NUT too: INPROGRESS + Implement IPMI detection in nut-scanner: TODO + Implement Python wrapper for nut-scanner: TODO + Implement Perl wrapper for nut-scanner (for inventories): TODO - [aquette] Update NUT script in Ubuntu QA Regression Testing: INPROGRESS + [aquette] Update NUT script in Ubuntu QA Regression Testing: DONE [aquette] AppArmor integration: TODO Convert NUT initscript to upstart: TODO Convert NUT initscript to systemd: TODO [aquette] Help / NMU FreeIPMI packages: TODO [aquette] MIR for libfreeipmi and libipmimonitoring for nut-ipmi: TODO [aquette] Package Avahi publication script for NUT: TODO [aquette] Package nut-ipmi: TODO [aquette] Package java-nut: TODO [aquette] Package nut-scanner: TODO NUT debconf support: TODO Remaining bits from UDS-O = Implement NUT support in checkbox: TODO [aquette] Implement support for power management testing in servercloud-p-complex-deployment-testing using NUT: TODO [andreserl] Investigate PowerNap using NUT as a data broker: TODO [aquette] Investigate PowerNap using NUT as a data broker: TODO [andreserl] Implement NUT client support in PowerWake: TODO [aquette] Implement NUT client support in PowerWake: TODO - - Work Items: - - Work Items: -- Cloud power management https://blueprints.launchpad.net/ubuntu/+spec/servercloud-p-cloud-power-management -- 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 servercloud-p-cloud-power-management] Cloud power management
Blueprint changed by Arnaud Quette: Whiteboard changed: Work Items: support for power devices in OCS and Fusion inventory: INPROGRESS [server-team] NUT integration in Cobbler (replace fence-agents): TODO Write juju charm for NUT: TODO [andreserl] Write juju charm for NUT: TODO Design OpenStack (Nova, Power Scheduler) integration with PowerWake/PowerNap: TODO [andreserl] Design OpenStack (Nova, Power Scheduler) integration with PowerWake/PowerNap: TODO - Implement PowerChain (power distribution tracking) in NUT: INPROGRESS Implement configuration library and tool for NUT: INPROGRESS Implement network support in nut-ipmipsu: TODO Implement fence mode (full args on cmd line, no daemonization) in NUT: TODO Check if all supported fence devices are present in NUT too: INPROGRESS Implement IPMI detection in nut-scanner: TODO Implement Python wrapper for nut-scanner: TODO Implement Perl wrapper for nut-scanner (for inventories): TODO - [aquette] Update NUT script in Ubuntu QA Regression Testing: DONE [aquette] AppArmor integration: TODO - Convert NUT initscript to upstart: TODO Convert NUT initscript to systemd: TODO [aquette] Help / NMU FreeIPMI packages: TODO [aquette] MIR for libfreeipmi and libipmimonitoring for nut-ipmi: TODO [aquette] Package Avahi publication script for NUT: TODO [aquette] Package nut-ipmi: TODO [aquette] Package java-nut: TODO [aquette] Package nut-scanner: TODO NUT debconf support: TODO Remaining bits from UDS-O = Implement NUT support in checkbox: TODO [aquette] Implement support for power management testing in servercloud-p-complex-deployment-testing using NUT: TODO [andreserl] Investigate PowerNap using NUT as a data broker: TODO [aquette] Investigate PowerNap using NUT as a data broker: TODO [andreserl] Implement NUT client support in PowerWake: TODO [aquette] Implement NUT client support in PowerWake: TODO -- Cloud power management https://blueprints.launchpad.net/ubuntu/+spec/servercloud-p-cloud-power-management -- 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 servercloud-p-cloud-power-management] Cloud power management
Blueprint changed by Arnaud Quette: Whiteboard changed: Work Items: - support for power devices in OCS and Fusion inventory: INPROGRESS + [aquette] support for power devices in OCS and Fusion inventory: INPROGRESS [server-team] NUT integration in Cobbler (replace fence-agents): TODO - Write juju charm for NUT: TODO + [aquette] Write juju charm for NUT: TODO [andreserl] Write juju charm for NUT: TODO - Design OpenStack (Nova, Power Scheduler) integration with PowerWake/PowerNap: TODO + [aquette] Design OpenStack (Nova, Power Scheduler) integration with PowerWake/PowerNap: TODO [andreserl] Design OpenStack (Nova, Power Scheduler) integration with PowerWake/PowerNap: TODO - Implement PowerChain (power distribution tracking) in NUT: INPROGRESS + [aquette] Implement PowerChain (power distribution tracking) in NUT: INPROGRESS Implement configuration library and tool for NUT: INPROGRESS - Implement network support in nut-ipmipsu: TODO + [aquette] Implement network support in nut-ipmipsu: TODO Implement fence mode (full args on cmd line, no daemonization) in NUT: TODO Check if all supported fence devices are present in NUT too: INPROGRESS - Implement IPMI detection in nut-scanner: TODO + [aquette] Implement IPMI detection in nut-scanner: TODO Implement Python wrapper for nut-scanner: TODO Implement Perl wrapper for nut-scanner (for inventories): TODO [aquette] Update NUT script in Ubuntu QA Regression Testing: DONE [aquette] AppArmor integration: TODO Convert NUT initscript to upstart: TODO Convert NUT initscript to systemd: TODO [aquette] Help / NMU FreeIPMI packages: TODO [aquette] MIR for libfreeipmi and libipmimonitoring for nut-ipmi: TODO [aquette] Package Avahi publication script for NUT: TODO [aquette] Package nut-ipmi: TODO [aquette] Package java-nut: TODO [aquette] Package nut-scanner: TODO NUT debconf support: TODO Remaining bits from UDS-O = Implement NUT support in checkbox: TODO [aquette] Implement support for power management testing in servercloud-p-complex-deployment-testing using NUT: TODO [andreserl] Investigate PowerNap using NUT as a data broker: TODO [aquette] Investigate PowerNap using NUT as a data broker: TODO [andreserl] Implement NUT client support in PowerWake: TODO [aquette] Implement NUT client support in PowerWake: TODO -- Cloud power management https://blueprints.launchpad.net/ubuntu/+spec/servercloud-p-cloud-power-management -- 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 809166] Re: Update fence-agents to 3.1.5
Hey Andres and all, 2011/11/23 Andres Rodriguez andres...@ubuntu-pe.org: All, I'll update fence-agents once the debian maintainer takes the Ubuntu packaging changes into the debian packages. take it easy Andres, you seem to be a little angry on this ;) from an upstream and DD point of view: - FA Debian maintainer may have missed your package and patches. Looking at the PTS, Ubuntu patch does not appear, due to the version differences and patch reporting mechanism (3.1.4 in Ubuntu and 3.1.5 in Debian): http://packages.qa.debian.org/f/fence-agents.html Moreover, there is no bug report that could highlight this. - the manpages fixes have not been contributed upstream, which is best in the long run, since this ensure the best possible solution for everybody. AFAICT, there seem to be some POD fixes missing (only the existing manpages have been fixed, not the generated ones!) I can take care of thi s point if you want/need. Just let me know... 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/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 servercloud-p-cloud-power-management] Cloud power management
Blueprint changed by Arnaud Quette: Whiteboard changed: - support for power devices in OCS and Fusion inventory: TODO + support for power devices in OCS and Fusion inventory: INPROGRESS [server-team] NUT integration in Cobbler (replace fence-agents): TODO Write juju charm for NUT: TODO [andreserl] Write juju charm for NUT: TODO Design OpenStack (Nova, Power Scheduler) integration with PowerWake/PowerNap: TODO [andreserl] Design OpenStack (Nova, Power Scheduler) integration with PowerWake/PowerNap: TODO Implement PowerChain (power distribution tracking) in NUT: INPROGRESS Implement configuration library and tool for NUT: TODO Implement network support in nut-ipmipsu: TODO Implement fence mode (no daemonization) in NUT: TODO Check if all supported fence devices are present in NUT too: TODO [aquette] Update NUT script in Ubuntu QA Regression Testing: INPROGRESS [aquette] AppArmor integration: TODO Convert NUT initscript to upstart: TODO Convert NUT initscript to systemd: TODO [aquette] Help / NMU FreeIPMI packages: TODO [aquette] MIR for libfreeipmi and libipmimonitoring for nut-ipmi: TODO [aquette] Package Avahi publication script for NUT: TODO [aquette] Package nut-ipmi: TODO [aquette] Package java-nut: TODO [aquette] Package nut-scanner: TODO NUT debconf support: TODO Remaining bits from UDS-O = Implement NUT support in checkbox: TODO [aquette] Implement support for power management testing in servercloud-p-complex-deployment-testing using NUT: TODO [andreserl] Investigate PowerNap using NUT as a data broker: TODO [aquette] Investigate PowerNap using NUT as a data broker: TODO [andreserl] Implement NUT client support in PowerWake: TODO [aquette] Implement NUT client support in PowerWake: TODO Work Items: Work Items: -- Cloud power management https://blueprints.launchpad.net/ubuntu/+spec/servercloud-p-cloud-power-management -- 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 servercloud-p-cloud-power-management] Cloud power management
Blueprint changed by Arnaud Quette: Whiteboard changed: support for power devices in OCS inventory: TODO [server-team] NUT integration in Cobbler (replace fence-agents): TODO Write juju charm for NUT: TODO [andreserl] Write juju charm for NUT: TODO Design OpenStack (Nova, Power Scheduler) integration with PowerWake/PowerNap: TODO [andreserl] Design OpenStack (Nova, Power Scheduler) integration with PowerWake/PowerNap: TODO Implement PowerChain (power distribution tracking) in NUT: INPROGRESS Implement configuration library and tool for NUT: TODO Implement network support in nut-ipmipsu: TODO Implement fence mode (no daemonization) in NUT: TODO - Check if all supported fence devices are present in NUT too: TODO + Check if all supported fence devices are present in NUT too: TODO - [aquette] Update NUT script in Ubuntu QA Regression Testing/TODO + [aquette] Update NUT script in Ubuntu QA Regression Testing: INPROGRESS + [aquette] AppArmor integration: TODO Convert NUT initscript to upstart: TODO Convert NUT initscript to systemd: TODO [aquette] Help / NMU FreeIPMI packages: TODO [aquette] MIR for libfreeipmi and libipmimonitoring for nut-ipmi: TODO [aquette] Package Avahi publication script for NUT: TODO [aquette] Package nut-ipmi: TODO [aquette] Package java-nut: TODO [aquette] Package nut-scanner: TODO NUT debconf support: TODO - Remaining bits from UDS-O = Implement NUT support in checkbox: TODO [aquette] Implement support for power management testing in servercloud-p-complex-deployment-testing using NUT: TODO [andreserl] Investigate PowerNap using NUT as a data broker: TODO [aquette] Investigate PowerNap using NUT as a data broker: TODO [andreserl] Implement NUT client support in PowerWake: TODO [aquette] Implement NUT client support in PowerWake: TODO + + Work Items: + + Work Items: -- Cloud power management https://blueprints.launchpad.net/ubuntu/+spec/servercloud-p-cloud-power-management -- 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 servercloud-p-cloud-power-management] Cloud power management
Blueprint changed by Arnaud Quette: Whiteboard changed: - Bits from UDS-O - === + support for power devices in OCS inventory: TODO + [server-team] NUT integration in Cobbler (replace fence-agents): TODO + Write juju charm for NUT: TODO + [andreserl] Write juju charm for NUT: TODO + Design OpenStack (Nova, Power Scheduler) integration with PowerWake/PowerNap: TODO + [andreserl] Design OpenStack (Nova, Power Scheduler) integration with PowerWake/PowerNap: TODO - Remaining work items from UDS-O: - [aquette] Implement PowerChain (power distribution tracking) in NUT: INPROGRESS - [zulcss] Investigate and implement NUT Puppet, cobbler, Orchestra, Juju integration: TODO - [aquette] Investigate and implement NUT Puppet, cobbler, Orchestra, Juju integration: TODO - [aquette] Implement configuration library and tool for NUT: TODO + Implement PowerChain (power distribution tracking) in NUT: INPROGRESS + Implement configuration library and tool for NUT: TODO + Implement network support in nut-ipmipsu: TODO + Implement fence mode (no daemonization) in NUT: TODO + Check if all supported fence devices are present in NUT too: TODO + + [aquette] Update NUT script in Ubuntu QA Regression Testing/TODO + + Convert NUT initscript to upstart: TODO + Convert NUT initscript to systemd: TODO + [aquette] Help / NMU FreeIPMI packages: TODO [aquette] MIR for libfreeipmi and libipmimonitoring for nut-ipmi: TODO + [aquette] Package Avahi publication script for NUT: TODO + [aquette] Package nut-ipmi: TODO + [aquette] Package java-nut: TODO + [aquette] Package nut-scanner: TODO + NUT debconf support: TODO + + + Remaining bits from UDS-O + = + + Implement NUT support in checkbox: TODO + [aquette] Implement support for power management testing in servercloud-p-complex-deployment-testing using NUT: TODO [andreserl] Investigate PowerNap using NUT as a data broker: TODO [aquette] Investigate PowerNap using NUT as a data broker: TODO [andreserl] Implement NUT client support in PowerWake: TODO [aquette] Implement NUT client support in PowerWake: TODO - - Other needed items derived from UDS-O or for UDS-P: - [aquette] Implement support for power management testing in servercloud-p-complex-deployment-testing using NUT: TODO - [aquette] Help / NMU FreeIPMI packages: TODO - [aquette] Package Avahi publication script for NUT: TODO - [aquette] Package nut-ipmi, java-nut, nut-scanner: TODO - - Work items DONE since UDS-O: - [fredericbohe] Implement device discovery tools / libs / binding in NUT: DONE - [aquette] Create Augeas lenses for configuration for NUT: DONE - [bigon] Distribute NUT Augeas lenses: DONE - [bigon] Distribute the new NUT documentation: DONE - [bigon] Create a NUT client only (upsmon) package: DONE - [aquette] Create Avahi publication script for NUT: DONE - [aquette] Implement a native NUT PSU (power supply unit) / IPMI driver, using FreeIPMI: DONE - [aquette] Implement improved PDU and power devices support in fence-agents: DONE - [andreserl] provide fence-agents package (part of server-o-cluster-stack): DONE - - Remaining questions: - - is Augeas support sufficient for configuration, or does it need a more advanced and simple wrapper? - - @zulcss: does Nagios nut plug-in offer sufficient features for your purpose? - - Implement support for UPS testing in Checkbox using NUT? - - Convert NUT initscripts to upstart? - - == 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, ... - [aquette] This is related to servercloud-p-orchestra-itsm (Inventory Management system) -- Cloud power management https://blueprints.launchpad.net/ubuntu/+spec/servercloud-p-cloud-power-management -- 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 servercloud-p-complex-deployment-testing] Automated Complex Server Deployment Testing
Blueprint changed by Arnaud Quette: Whiteboard changed: Scope: Deployment and Testing of Ubuntu Server to support complex requirements i.e. OpenStack + others Coverage: - OpenStack - Wiki + Database + Memcache + Load Balancer - Networking File Systems - Samba + LDAP or Kerberos Backend - Backup solutions - bacula? - Ruby on Rails stack UDS-O - Complex Deployment Scenarios: Method: orchestra+juju AND cloud+juju james-page proposed a method for testing juju charms on juju@l.u.c - see https://lists.ubuntu.com/archives/juju/2011-October/000837.html This involves a new charm when can test other charms - results are then collated and can be reported on. This is then executed by a framework (TBN) which set's up the juju environment and services, executes the charm testing and then can execute tests on the deployed environment. I think this is the right way todo this testing - it can be used with any juju provider so can be applied in both physical and cloud environments. Frequency: - Daily Test with current development release - Triggered when key packages change in released versions of Ubuntu in -proposed? Questions/Proposals: [james-page] We need to verify the list of deployments and get volunteers to develop charms for them where gaps exist. Work Items: Develop juju charm testing framework to support all requirements: TODO Writing testing hooks for all charms which we want to test this way: TODO Setup OpenStack test lab: TODO Identify OpenStack testing requirements on the deployed service: TODO Stuff left from UDS-O not covered in other specs b) Package Removal Testing: - install services - start services - check services - stop services - uninstall services - re-install same services - start re-check services d) Automated Boot Testing: Minimal install - startup and shutdown OK Full install - startup and shutdown OK Complete upgrade and then re-test. f) Recovery Testing: Recovery Mode Testing: + + + aquette propose a method to automate testing of power infrastructure (UPS, power distribution units and servers power supplies): + http://bazaar.launchpad.net/~ubuntu-bugcontrol/qa-regression-testing/master/view/257//scripts/test-nut.py -- Automated Complex Server Deployment Testing https://blueprints.launchpad.net/ubuntu/+spec/servercloud-p-complex-deployment-testing -- 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 servercloud-p-cloud-power-management] Cloud power management
Blueprint changed by Arnaud Quette: Whiteboard changed: - I've pushed this out to P, as it clearly won't complete in this cycle [robbie.w] - I've released NUT 2.6.2 today... [aquette] + Bits from UDS-O + === - Work items: + Remaining work items from UDS-O: + [aquette] Implement PowerChain (power distribution tracking) in NUT: INPROGRESS + [zulcss] Investigate and implement NUT Puppet, cobbler, Orchestra, Juju integration: TODO + [aquette] Investigate and implement NUT Puppet, cobbler, Orchestra, Juju integration: TODO + [aquette] Implement configuration library and tool for NUT: TODO + [aquette] MIR for libfreeipmi and libipmimonitoring for nut-ipmi: TODO + [andreserl] Investigate PowerNap using NUT as a data broker: TODO + [aquette] Investigate PowerNap using NUT as a data broker: TODO + [andreserl] Implement NUT client support in PowerWake: TODO + [aquette] Implement NUT client support in PowerWake: TODO + + Other needed items derived from UDS-O or for UDS-P: + [aquette] Implement support for power management testing in servercloud-p-complex-deployment-testing using NUT: TODO + [aquette] Help / NMU FreeIPMI packages: TODO + [aquette] Package Avahi publication script for NUT: TODO + [aquette] Package nut-ipmi, java-nut, nut-scanner: TODO + + Work items DONE since UDS-O: [fredericbohe] Implement device discovery tools / libs / binding in NUT: DONE - [aquette] Implement configuration library and tool for NUT: POSTPONED [aquette] Create Augeas lenses for configuration for NUT: DONE [bigon] Distribute NUT Augeas lenses: DONE [bigon] Distribute the new NUT documentation: DONE [bigon] Create a NUT client only (upsmon) package: DONE - [aquette] Convert initscripts to upstart: POSTPONED - [aquette] Create Avahi publication script for : DONE + [aquette] Create Avahi publication script for NUT: DONE [aquette] Implement a native NUT PSU (power supply unit) / IPMI driver, using FreeIPMI: DONE - [aquette] MIR for libfreeipmi and libipmimonitoring for nut-ipmi: POSTPONED - [aquette] Implement PowerChain in NUT: POSTPONED - [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: POSTPONED - [aquette] Investigate PowerNap using NUT as a data broker: POSTPONED - [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? + - is Augeas support sufficient for configuration, or does it need a more advanced and simple wrapper? - @zulcss: does Nagios nut plug-in offer sufficient features for your purpose? - - MIR for FreeIPMI? + - Implement support for UPS testing in Checkbox using NUT? + - Convert NUT initscripts to upstart? == 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, ... + [aquette] This is related to servercloud-p-orchestra-itsm (Inventory Management system) -- Cloud power management https://blueprints.launchpad.net/ubuntu/+spec/servercloud-p-cloud-power-management -- 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 753661] Re: [Nut-upsuser] PowerCOM BNT-800AP (0d9f:0004)
Hi Pavel, 2011/10/4 Павел Гуменюк pavel.gumen...@gmail.com: Hello. I've been trying to got it work but haven't luck. I'm using NUT 2.6.0-1 under Windows XP with libusb driver installed (USB\VID_0D9FPID_0004REV_0001). I had tryed all options with such config: PWCOM] driver = usbhid-ups port = auto vendorid = 0d9f desc = Powercom BNT-800AP type=BNT as per a previous report on Ubuntu, we know that this UPS is supported: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/753661 that being said, it seems I've not completed my actions and committed a patch for this new device ID. Fixed in the development version (trunk), r3265. Also note that the type option is supported by the powercom driver, not the usbhid-ups 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/753661 Title: upsd write() failed for 127.0.0.1: Broken pipe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/753661/+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 753661] Re: [Nut-upsuser] PowerCOM BNT-800AP (0d9f:0004)
Hi Pavel, 2011/10/4 Павел Гуменюк pavel.gumen...@gmail.com: Hello. I've been trying to got it work but haven't luck. I'm using NUT 2.6.0-1 under Windows XP with libusb driver installed (USB\VID_0D9FPID_0004REV_0001). I had tryed all options with such config: PWCOM] driver = usbhid-ups port = auto vendorid = 0d9f desc = Powercom BNT-800AP type=BNT as per a previous report on Ubuntu, we know that this UPS is supported: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/753661 that being said, it seems I've not completed my actions and committed a patch for this new device ID. Fixed in the development version (trunk), r3265. Also note that the type option is supported by the powercom driver, not the usbhid-ups 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/753661 Title: upsd write() failed for 127.0.0.1: Broken pipe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/753661/+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: - I've pushed this out to P, as it clearly won't complete in this cycle - [robbie.w] + I've pushed this out to P, as it clearly won't complete in this cycle [robbie.w] + I've released NUT 2.6.2 today... [aquette] Work items: - [fredericbohe] Implement device discovery tools / libs / binding in NUT: INPROGRESS - [aquette] Implement configuration library and tool for NUT: TODO + [fredericbohe] Implement device discovery tools / libs / binding in NUT: DONE + [aquette] Implement configuration library and tool for NUT: POSTPONED [aquette] Create Augeas lenses for configuration for NUT: DONE - [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 + [bigon] Distribute NUT Augeas lenses: DONE + [bigon] Distribute the new NUT documentation: DONE + [bigon] Create a NUT client only (upsmon) package: DONE + [aquette] Convert initscripts to upstart: POSTPONED [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 + [aquette] Implement a native NUT PSU (power supply unit) / IPMI driver, using FreeIPMI: DONE + [aquette] MIR for libfreeipmi and libipmimonitoring for nut-ipmi: POSTPONED + [aquette] Implement PowerChain in NUT: POSTPONED [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: POSTPONED - [aquette] Investigate PowerNap using NUT as a data broker: INPROGRESS + [aquette] Investigate PowerNap using NUT as a data broker: POSTPONED [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 850672] Re: port = auto does not work with bcmxcp_usb (powerware 5115)
2011/9/15 Tuomas Heino iheino...@cc.hut.fi After changing port back to auto it seems to work. System has not been rebooted since installing nut. Could this be some form of a race condition as speculated in other bug reports? not at all. the value of port, as for other NUT USB drivers, is not used. the auto keyword is simply a standard value, but you could put whatever you want, such as a physical path. I don't see any particular reason to the original failure, but having more info on the context would help. it could simply be that udevadm trigger has been run somehow, by you or another package installation... as for the race condition, I have to check other bug reports. 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/850672 Title: port = auto does not work with bcmxcp_usb (powerware 5115) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/850672/+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 850672] Re: port = auto does not work with bcmxcp_usb (powerware 5115)
2011/9/15 Tuomas Heino iheino...@cc.hut.fi After changing port back to auto it seems to work. System has not been rebooted since installing nut. Could this be some form of a race condition as speculated in other bug reports? not at all. the value of port, as for other NUT USB drivers, is not used. the auto keyword is simply a standard value, but you could put whatever you want, such as a physical path. I don't see any particular reason to the original failure, but having more info on the context would help. it could simply be that udevadm trigger has been run somehow, by you or another package installation... as for the race condition, I have to check other bug reports. 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/850672 Title: port = auto does not work with bcmxcp_usb (powerware 5115) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/850672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 839490] [NEW] NUT is not shutdown UPS
Hi Dmitriy, 2011/9/2 Dmitriy Altuhov d...@altuhov.su Public bug reported: Description:Ubuntu 11.04 Release:11.04 nut version 2.6.0-1ubuntu3 Problem: upsmon working under nut user (not root). nut user can't create file /etc/killpower upsmon forks 2 instances: - 1 running unprivileged (ie nut user), listening on the network interface - 1 running with root privileges to be able to launch upsmon.conf-SHUTDOWNCMD have a 2nd look at your processes list. Example: 1) Mains out. UPS on battery 2) Battery low. set FSD 3) upsmon executes shutdowncmd but fails to create /etc/killpower 4) /etc/init.d/halt executes /etc/init.d/ups-monitor poweroff 5) /etc/init.d/ups-monitor poweroff executes upsmon -K to check /etc/killpower (but file does not exist) 6) not sending shutdown command to UPS (upsdrvctl shutdown is not executed) 7) system halted, but UPS stays on battery 8) mains come back, ups going on mains, but load is not switched off/on 9) PC stay OFF (need manual start) I'll have to have another look, but I recently made a full test with 2.6.1 and everything was fine. I need more info on your setup, ie: - your .conf files (trimmed of passwords and sensitive info) - your ups name and type Moreover, have you checked your BIOS for the power setting (ie power on after a power failure or whatever its name is)? 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/839490 Title: NUT is not shutdown UPS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/839490/+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 839509] [NEW] nut can not log to syslog when shutdown
2011/9/2 Dmitriy Altuhov d...@altuhov.su Public bug reported: Ubuntu 11.04 NUT 2.6.0 System shutting down (battery low, FSD set) and executes /etc/init.d /ups-monitor poweroff ups-monitor script contains section poweroff. in this section we can see log_daemon_msg which sends info to syslog but rsyslogd already stopped. This is in syslog when shutdown: Sep 2 17:37:58 gwlin upsmon[1229]: Signal 10: User requested FSD Sep 2 17:37:58 gwlin upsd[1225]: Client local_mon@127.0.0.1 set FSD on UPS [ippon] Sep 2 17:37:58 gwlin upsmon[1229]: Executing automatic power-fail shutdown Sep 2 17:37:58 gwlin upsmon[1229]: Auto logout and shutdown proceeding Sep 2 17:38:03 gwlin kernel: Kernel logging (proc) stopped. Sep 2 17:38:03 gwlin rsyslogd: [origin software=rsyslogd swVersion=4.6.4 x-pid=374 x-info=http://www.rsyslog.com;] exiting on signal 15. I'm not sure if this can be considered as a bug (not that it's a feature!). log_*_msg are not only used to log in the syslog (when available), but also to display info on the console... by the time we reach the end of the shutdown process, FS are remounted read-only. so even if syslogd was still active, it would not be able to log in the FS syslog file! 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/839509 Title: nut can not log to syslog when shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/839509/+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 839509] Re: nut can not log to syslog when shutdown
hey Laurent, 2011/9/14 Laurent Bigonville bi...@ubuntu.com by the time we reach the end of the shutdown process, FS are remounted read-only. so even if syslogd was still active, it would not be able to log in the FS syslog file! Some could argue that syslog can be configured to send logs to a central server over the network /devil_advocate right, I forgot to mention that one, which is still in favor of marking this bug invalid... 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/839509 Title: nut can not log to syslog when shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/839509/+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 839490] [NEW] NUT is not shutdown UPS
Hi Dmitriy, 2011/9/2 Dmitriy Altuhov d...@altuhov.su Public bug reported: Description:Ubuntu 11.04 Release:11.04 nut version 2.6.0-1ubuntu3 Problem: upsmon working under nut user (not root). nut user can't create file /etc/killpower upsmon forks 2 instances: - 1 running unprivileged (ie nut user), listening on the network interface - 1 running with root privileges to be able to launch upsmon.conf-SHUTDOWNCMD have a 2nd look at your processes list. Example: 1) Mains out. UPS on battery 2) Battery low. set FSD 3) upsmon executes shutdowncmd but fails to create /etc/killpower 4) /etc/init.d/halt executes /etc/init.d/ups-monitor poweroff 5) /etc/init.d/ups-monitor poweroff executes upsmon -K to check /etc/killpower (but file does not exist) 6) not sending shutdown command to UPS (upsdrvctl shutdown is not executed) 7) system halted, but UPS stays on battery 8) mains come back, ups going on mains, but load is not switched off/on 9) PC stay OFF (need manual start) I'll have to have another look, but I recently made a full test with 2.6.1 and everything was fine. I need more info on your setup, ie: - your .conf files (trimmed of passwords and sensitive info) - your ups name and type Moreover, have you checked your BIOS for the power setting (ie power on after a power failure or whatever its name is)? 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/839490 Title: NUT is not shutdown UPS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/839490/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 839509] [NEW] nut can not log to syslog when shutdown
2011/9/2 Dmitriy Altuhov d...@altuhov.su Public bug reported: Ubuntu 11.04 NUT 2.6.0 System shutting down (battery low, FSD set) and executes /etc/init.d /ups-monitor poweroff ups-monitor script contains section poweroff. in this section we can see log_daemon_msg which sends info to syslog but rsyslogd already stopped. This is in syslog when shutdown: Sep 2 17:37:58 gwlin upsmon[1229]: Signal 10: User requested FSD Sep 2 17:37:58 gwlin upsd[1225]: Client local_mon@127.0.0.1 set FSD on UPS [ippon] Sep 2 17:37:58 gwlin upsmon[1229]: Executing automatic power-fail shutdown Sep 2 17:37:58 gwlin upsmon[1229]: Auto logout and shutdown proceeding Sep 2 17:38:03 gwlin kernel: Kernel logging (proc) stopped. Sep 2 17:38:03 gwlin rsyslogd: [origin software=rsyslogd swVersion=4.6.4 x-pid=374 x-info=http://www.rsyslog.com;] exiting on signal 15. I'm not sure if this can be considered as a bug (not that it's a feature!). log_*_msg are not only used to log in the syslog (when available), but also to display info on the console... by the time we reach the end of the shutdown process, FS are remounted read-only. so even if syslogd was still active, it would not be able to log in the FS syslog file! 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/839509 Title: nut can not log to syslog when shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/839509/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 839509] Re: nut can not log to syslog when shutdown
hey Laurent, 2011/9/14 Laurent Bigonville bi...@ubuntu.com by the time we reach the end of the shutdown process, FS are remounted read-only. so even if syslogd was still active, it would not be able to log in the FS syslog file! Some could argue that syslog can be configured to send logs to a central server over the network /devil_advocate right, I forgot to mention that one, which is still in favor of marking this bug invalid... 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/839509 Title: nut can not log to syslog when shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/839509/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Server Team, which is subscribed to nut in 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-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
