[Bug 1316357] Re: Network interface IP address not set on first boot if config drive used
Exact same bug as https://bugs.launchpad.net/ubuntu/+source/cloud- init/+bug/1315501 Workaround given by David Moreau Simard works: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1315501/comments/11 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1316357 Title: Network interface IP address not set on first boot if config drive used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1316357/+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 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 1026256] Re: pptpd.conf
Hello everyone, I just had this problem on a fresh Debian install. It really exists. It took me too much time to look after the problem, regarding to the solution ! pptpd v1.3.4 Cheers, -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pptpd in Ubuntu. https://bugs.launchpad.net/bugs/1026256 Title: pptpd.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pptpd/+bug/1026256/+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 1312936] Re: Post-installation script fails
Strange. I just tested this on a fresh 14.04 VM with 512Mb RAM. From the original message : AppArmor parser error for /etc/apparmor.d/usr.sbin.mysqld in /etc/apparmor.d/usr.sbin.mysqld at line 44: Could not open 'local/usr.sbin.mysqld', the apparmor problem seems clear. That doesn't mean there isn't something else wrong. On my new setup, MySQL 5.6 installed without trouble (created my empty file beforehand. I'll have to check it without) and runs. It requires 1.1 Gb of virtual RAM, but only occupies 440Mb at startup, so it runs fine (granted, it should run into trouble soon). Maybe the difference is what other packages you installed : apache2 itself would eat enough RAM to OOM a machine on Mysql install. The innodb buffer pool seems to be 128Mb on my machine, which is the official default value. mysqlcalculator states that RAM usage at 128Mb buffer pool is close to 700Mb (to be compared with the 576Mb RAM occupied by the previous 8Mb 5.5 default buffer pool) = Neither should be able to run out of the box with 512Mb RAM only. With small machines, I think your best bet would be to deploy a my.cnf file prior to the mysql package installation (or to put a file in /etc/mysql/conf.d) with some alterations to the configuration (max_connections = 50 alone shaves 200Mb off RAM requirements) to ensure mysql will start and run fine. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1312936 Title: Post-installation script fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1312936/+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 1314555] [NEW] mysql-client-5.6 should provide mysql-client
Public bug reported: mysql-client-5.6 (version 5.6.16-1~exp1) only provides the package virtual-mysql-client while the 5.5 version provided mysql-client and virtual-mysql-client. As a result, other packages like rsyslog-mysql which use the mysql client libraries provided by the mysql-client metapackage will uninstall mysql-client-5.6 and overwrite it with mysql-client-5.5. I think the mysql-client-5.6 should provide the same metapackages the older 5.5 version did. ** Affects: mysql-5.6 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1314555 Title: mysql-client-5.6 should provide mysql-client To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1314555/+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 1314555] Re: mysql-client -depending packages should depend on mysql-client | virtual-mysql-client instead
That's exactly why I submitted a question first : because I suspected that change in dependencies was there for a reason. If I understand the problem correctly, it's not an issue of the mysql5.6 packages, but of all the others and the same problem will occur with the mariadb packages until all dependent packages are corrected to include both dependencies? Right now, it makes it impossible to use mysql5.6/mariadb as replacements to mysql5.5 in Ubuntu 14.04. I've corrected the mysql5.6 source package and recompiled it on my side, so it's not a problem anymore, but I suspect other users will find this troublesome. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1314555 Title: mysql-client -depending packages should depend on mysql-client | virtual-mysql-client instead To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1314555/+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 1312936] Re: Post-installation script fails
I ran into this. The standard config needs the /etc/apparmor.d/local/usr.sbin.mysqld file to be present or mysql won't start. A simple touch /etc/apparmor.d/local/usr.sbin.mysqld solved the installation problem for me. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1312936 Title: Post-installation script fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1312936/+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
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
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 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
[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
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
[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 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 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 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
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 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 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
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)
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] [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
[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
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
[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
[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
[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
[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
[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
[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 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
[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
[Blueprint server-o-infra-power] Infrastructure power management
Blueprint changed by Arnaud Quette: Whiteboard changed: Work items: [fredericbohe] Implement device discovery tools / libs / binding in NUT: INPROGRESS [aquette] Implement configuration library and tool for NUT: TODO [aquette] Create Augeas lenses for configuration for NUT: DONE - [aquette] Distribute NUT Augeas lenses: INPROGRESS - [aquette] Distribute the new NUT documentation: INPROGRESS - [aquette] Create a NUT client only (upsmon) package: INPROGRESS + [bigon] Distribute NUT Augeas lenses: INPROGRESS + [bigon] Distribute the new NUT documentation: INPROGRESS + [bigon] Create a NUT client only (upsmon) package: INPROGRESS [aquette] Convert initscripts to upstart: TODO [aquette] Create Avahi publication script for : DONE [aquette] Implement a native NUT PSU (power supply unit) / IPMI driver, using FreeIPMI: INPROGRESS [aquette] MIR for libfreeipmi and libipmimonitoring for nut-ipmi: TODO [aquette] Implement PowerChain in NUT: INPROGRESS [zulcss] Investigate and implement NUT Puppet integration: TODO [zulcss] Investigate and implement NUT cobbler integration: TODO [zulcss] Investigate and implement NUT Orchestra integration: TODO [zulcss] Investigate and implement NUT Ensemble integration: TODO Investigate and implement NUT Ensemble integration: TODO [aquette] Implement improved PDU and power devices support in fence-agents: DONE [andreserl] provide fence-agents package (part of server-o-cluster-stack): DONE [andreserl] Investigate PowerNap using NUT as a data broker: INPROGRESS [aquette] Investigate PowerNap using NUT as a data broker: INPROGRESS [andreserl] Implement NUT client support in PowerWake: TODO [aquette] Implement NUT client support in PowerWake: TODO [bencer] Implement NUT support in Zentyal: TODO [aquette] Implement NUT support in Zentyal: TODO [cr3] Implement support for UPS testing in Checkbox using NUT: TODO [aquette] Implement support for UPS testing in Checkbox using NUT: TODO Remaining questions: - is Augeas support sufficient for configuration, or does it need a more advanced wrapper? - related to the above, is a configuration library / tool needed? - @zulcss: does Nagios nut plug-in offer sufficient features for your purpose? - MIR for FreeIPMI? == Items to consider == 1. Implement power support in Cloud schedulers using NUT: TODO (lack an assignee) 2. Create power consumption reports (not ready for billing, only informative) 3. Asset management support for power devices. Ie, Provide device information like manufacturer name and model, serial number, location, contact, service dates, ... -- Infrastructure power management https://blueprints.launchpad.net/ubuntu/+spec/server-o-infra-power -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 816414] [NEW] [MIR] nut (nut-doc, nut-client, nut-server)
moreover, it's part of the ServerOneiricInfraPower blueprint: https://blueprints.launchpad.net/ubuntu/+spec/server-o-infra-power cheers, Arnaud -- Linux / Unix Expert RD - Eaton - http://powerquality.eaton.com Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.free.fr/ -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in Ubuntu. https://bugs.launchpad.net/bugs/816414 Title: [MIR] nut (nut-doc, nut-client, nut-server) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/816414/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 815760] Re: 2.6.1-2ubuntu1 FTBFS on i386
Hi James, thanks for your report. 2011/7/25 James Page 815...@bugs.launchpad.net Reproduced locally in sbuild environment; a bit more information on the failure: xsltproc --stringparam callout.graphics 0 --stringparam navig.graphics 0 --stringparam admon.textlabel 1 --stringparam admon.graphics 0 --stringparam base.dir user-manual.chunked/ /etc/asciidoc/docbook-xsl/chunked.xsl /build/jamespage-nut_2.6.1-2ubuntu1-i386-VnuJ0Q/nut-2.6.1/docs/user-manual.xml warning: failed to load external entity http://docbook.sourceforge.net/release/xsl/current/xhtml/docbook.xsl; compilation error: file http://docbook.sourceforge.net/release/xsl/current/xhtml/chunk.xsl line 25 element import xsl:import : unable to load http://docbook.sourceforge.net/release/xsl/current/xhtml/docbook.xsl strange. Can you please try with the verbose version: $ ASCIIDOC_VERBOSE=-v make we should get more info, since the above is probably not the actual issue... cheers, Arnaud -- Linux / Unix Expert RD - Eaton - http://powerquality.eaton.com Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.free.fr/ -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in Ubuntu. https://bugs.launchpad.net/bugs/815760 Title: 2.6.1-2ubuntu1 FTBFS on i386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/815760/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 799448] Re: openvpn hangs system with etoken
I have exactly the same bug on my side, is there any way to avoid it? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvpn in Ubuntu. https://bugs.launchpad.net/bugs/799448 Title: openvpn hangs system with etoken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvpn/+bug/799448/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 578200] Re: (megatec_usb) error: Driver not connected
guys, this seems related to a udev issue. things to try: - stop nut (sudo service nut stop ; killall -9 megatec_usb) - start the driver and server as root (sudo /lib/nut/megatec_usb -u root -a belkin-ups sudo upsd -u root) - then check using upsc you should also try the blazer_usb driver, as it has since replaced megatec_usb. finally, using packages from natty or maverick may be an option -- You received this bug notification because you are a member of Ubuntu 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
Re: [Bug 608182] Re: problems with ups (mge pulsar es 8+)
2011/7/18 Dave Walker davewal...@ubuntu.com @Arnaud, I'm confused as to the current status of this bug. Is there anything that needs to be done? @Dave: I'm not completely sure. the user has found a workaround. IMHO, we are probably facing some race condition between upstart native script Vs sysV, and udev serial port privileges. @Wolfgang: any update on your issue? how have you configured privileges on your serial port? (refer to /usr/share/doc/nut/README.Debian.gz, (II) - (3) - (b)) have you tried moving up the NUT (sysV) script' priority? Ie $ sudo update-rc.d nut start 90 2 3 4 5 . stop 90 0 1 6 . and reboot the system... cheers, Arnaud -- Linux / Unix Expert RD - Eaton - http://powerquality.eaton.com Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.free.fr/ -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in Ubuntu. https://bugs.launchpad.net/bugs/608182 Title: problems with ups (mge pulsar es 8+) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/608182/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 811976] [NEW] Update nut to 2.6.1-2
Public bug reported: Debian (Laurent Bigonville) has released a package update: Changes: nut (2.6.1-2) unstable; urgency=low . * debian/nut.README.Debian: Adjust udev rules naming for permissions override (Closes: #529664) * Re-add and refresh debian/patches/0001-fix_spelling_and_typo.patch: Some typos and spelling errors remain. * Split nut package into nut-client and nut-server, keep nut package as metapackage * Generate PDF and html doc and install it in nut-doc package * debian/rules: - List non-installed files - Includes python-module.mk - Add flags to build documentation and install it * debian/control: - Add python-nut package and add python build-dependency - Set nut-powerman-pdu priority to extras - Add nut-monitor package - Add nut-doc package and add required C/R/P - Add libups-nut-perl package * debian/nut-server.prerm: Remove /var/run/nut during removal ** Affects: nut (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in Ubuntu. https://bugs.launchpad.net/bugs/811976 Title: Update nut to 2.6.1-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/811976/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint server-o-infra-power] Infrastructure power management
Blueprint changed by Arnaud Quette: Whiteboard changed: Work items: [fredericbohe] Implement device discovery tools / libs / binding in NUT: INPROGRESS [aquette] Implement configuration library and tool for NUT: TODO [aquette] Create Augeas lenses for configuration for NUT: DONE [aquette] Distribute NUT Augeas lenses: INPROGRESS [aquette] Distribute the new NUT documentation: INPROGRESS [aquette] Create a NUT client only (upsmon) package: INPROGRESS [aquette] Convert initscripts to upstart: TODO [aquette] Create Avahi publication script for : DONE [aquette] Implement a native NUT PSU (power supply unit) / IPMI driver, using FreeIPMI: INPROGRESS + [aquette] MIR for libfreeipmi and libipmimonitoring for nut-ipmi: TODO [aquette] Implement PowerChain in NUT: INPROGRESS [zulcss] Investigate and implement NUT Puppet integration: TODO [zulcss] Investigate and implement NUT cobbler integration: TODO [zulcss] Investigate and implement NUT Orchestra integration: TODO [zulcss] Investigate and implement NUT Ensemble integration: TODO Investigate and implement NUT Ensemble integration: TODO [aquette] Implement improved PDU and power devices support in fence-agents: DONE [andreserl] provide fence-agents package (part of server-o-cluster-stack): DONE [andreserl] Investigate PowerNap using NUT as a data broker: INPROGRESS [aquette] Investigate PowerNap using NUT as a data broker: INPROGRESS [andreserl] Implement NUT client support in PowerWake: TODO [aquette] Implement NUT client support in PowerWake: TODO [bencer] Implement NUT support in Zentyal: TODO [aquette] Implement NUT support in Zentyal: TODO [cr3] Implement support for UPS testing in Checkbox using NUT: TODO [aquette] Implement support for UPS testing in Checkbox using NUT: TODO Remaining questions: - is Augeas support sufficient for configuration, or does it need a more advanced wrapper? - related to the above, is a configuration library / tool needed? - @zulcss: does Nagios nut plug-in offer sufficient features for your purpose? - MIR for FreeIPMI? == Items to consider == 1. Implement power support in Cloud schedulers using NUT: TODO (lack an assignee) 2. Create power consumption reports (not ready for billing, only informative) 3. Asset management support for power devices. Ie, Provide device information like manufacturer name and model, serial number, location, contact, service dates, ... -- Infrastructure power management https://blueprints.launchpad.net/ubuntu/+spec/server-o-infra-power -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 779512] Re: nut-2.6.0-1ubuntu3 behavior regression
Hi Martin, 2011/6/27 Martin Ewing martin.s.ew...@gmail.com I have a very similar situation with my Belkin UPS on Natty (worked on previous release). See $ lsb_release -rd Description:Ubuntu 11.04 Release:11.04 martin@gimli:~$ aptitude show nut Package: nut State: installed Automatically installed: no Version: 2.6.0-1ubuntu3 ... sudo /lib/nut/usbhid-ups - -a mybelkin Network UPS Tools - Generic HID driver 0.35 (2.6.0) USB communication driver 0.31 0.00 debug level is '4' 0.000583 upsdrv_initups... 0.266176 Checking device (1D6B/0001) (008/001) 0.266219 - VendorID: 1d6b 0.266226 - ProductID: 0001 0.266232 - Manufacturer: unknown 0.266237 - Product: unknown 0.266242 - Serial Number: unknown 0.266247 - Bus: 008 0.266252 Trying to match device 0.266275 Device does not match - skipping 0.266285 Checking device (1D6B/0001) (007/001) 0.266303 - VendorID: 1d6b 0.266309 - ProductID: 0001 0.266315 - Manufacturer: unknown 0.266320 - Product: unknown 0.266325 - Serial Number: unknown 0.266330 - Bus: 007 0.266335 Trying to match device 0.266341 Device does not match - skipping 0.266349 Checking device (050D/1100) (006/002) 0.291945 - VendorID: 050d 0.291959 - ProductID: 1100 0.291966 - Manufacturer: Belkin 0.291972 - Product: Belkin UPS 0.291977 - Serial Number: unknown 0.291982 - Bus: 006 0.291987 Trying to match device 0.291995 Device matches (...) 0.383981 Entering libusb_get_report 0.388933 libusb_get_report: error sending control message: Operation not permitted ... Is this the same bug? I don't think so. the issue reported here was related to a code change, that resulted in a regression. yours seem to be with privileges. to validate this, try launching the driver with root privs (note the -u root): $ sudo /lib/nut/usbhid-ups -u root - -a mybelkin Is there a fix it's related to udev, and since there seems to be quite some similar issues, I'm wondering if there is a race condition between udev (started through upstart native scripts) and nut (started through upstart sysV compat script). cheers, Arnaud -- Linux / Unix Expert RD - Eaton - http://powerquality.eaton.com Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.free.fr/ -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in Ubuntu. https://bugs.launchpad.net/bugs/779512 Title: nut-2.6.0-1ubuntu3 behavior regression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/779512/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 779512] Re: nut-2.6.0-1ubuntu3 behavior regression
2011/7/13 Martin Ewing martin.s.ew...@gmail.com Arnaud, Thanks for the reply! I imagine you are correct. I ran the command you suggested (below). Apparently nut knows the device it should connect to, but that device is busy. And running as root doesn't overcome the problem... (And I don't know why I should have to make /var/run/nut, either.) this specific issue with claim is generally bound to another instance of the driver still running. I am not well versed in Ubuntu bug reporting. Do you think I need to submit this separately? Or should I just wait until the next release? (The lazy way out.) for now, we'll focus on hunting your issue here. if it goes beyond another 2 mails, then we'll check for creating a dedicated bug report, to be able to close it through 2.6.1 upload, while not forgiving you ;) cheers, Arnaud -- Linux / Unix Expert RD - Eaton - http://powerquality.eaton.com Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.free.fr/ -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in Ubuntu. https://bugs.launchpad.net/bugs/779512 Title: nut-2.6.0-1ubuntu3 behavior regression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/779512/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint server-o-infra-power] Infrastructure power management
Blueprint changed by Arnaud Quette: Whiteboard changed: Work items: [fredericbohe] Implement device discovery tools / libs / binding in NUT: INPROGRESS [aquette] Implement configuration library and tool for NUT: TODO [aquette] Create Augeas lenses for configuration for NUT: DONE - [aquette] Distribute NUT Augeas lenses: TODO - [aquette] Distribute the new NUT documentation: TODO - [aquette] Create a NUT client only (upsmon) package: TODO + [aquette] Distribute NUT Augeas lenses: INPROGRESS + [aquette] Distribute the new NUT documentation: INPROGRESS + [aquette] Create a NUT client only (upsmon) package: INPROGRESS [aquette] Convert initscripts to upstart: TODO [aquette] Create Avahi publication script for : INPROGRESS - [aquette] Implement a native NUT PSU (power supply unit) / IPMI driver, using OpenIPMI: TODO - [aquette] Implement PowerChain in NUT: TODO + [aquette] Implement a native NUT PSU (power supply unit) / IPMI driver, using OpenIPMI: INPROGRESS + [aquette] Implement PowerChain in NUT: INPROGRESS [zulcss] Investigate and implement NUT Puppet integration: TODO [zulcss] Investigate and implement NUT cobbler integration: TODO [zulcss] Investigate and implement NUT Orchestra integration: TODO [zulcss] Investigate and implement NUT Ensemble integration: TODO [kim0] Investigate and implement NUT Ensemble integration: TODO [aquette] Implement improved PDU and power devices support in fence-agents: DONE [andreserl] provide fence-agents package (part of server-o-cluster-stack): DONE [andreserl] Investigate PowerNap using NUT as a data broker: INPROGRESS [aquette] Investigate PowerNap using NUT as a data broker: INPROGRESS [andreserl] Implement NUT client support in PowerWake: TODO [aquette] Implement NUT client support in PowerWake: TODO [bencer] Implement NUT support in Zentyal: TODO [aquette] Implement NUT support in Zentyal: TODO [cr3] Implement support for UPS testing in Checkbox using NUT: TODO [aquette] Implement support for UPS testing in Checkbox using NUT: TODO Remaining questions: - is Augeas support sufficient for configuration, or does it need a more advanced wrapper? - related to the above, is a configuration library / tool needed? - @zulcss: does Nagios nut plug-in offer sufficient features for your purpose? == Items to consider == 1. Implement power support in Cloud schedulers using NUT: TODO (lack an assignee) 2. Create power consumption reports (not ready for billing, only informative) 3. Asset management support for power devices. Ie, Provide device information like manufacturer name and model, serial number, location, contact, service dates, ... -- Infrastructure power management https://blueprints.launchpad.net/ubuntu/+spec/server-o-infra-power -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint server-o-infra-power] Infrastructure power management
Blueprint changed by Arnaud Quette: Whiteboard changed: Work items: [aquette] Implement device discovery tools / libs / binding in NUT: INPROGRESS [aquette] Implement configuration library and tool for NUT: TODO [aquette] Create Augeas lenses for configuration for NUT: DONE [aquette] Distribute NUT Augeas lenses: TODO [aquette] Distribute the new NUT documentation: TODO [aquette] Create a NUT client only (upsmon) package: TODO - [?] Convert initscripts to upstart: TODO + [server-o-cluster-stack] Convert initscripts to upstart: TODO [aquette] Create Avahi publication script for : INPROGRESS [aquette] Implement a native NUT PSU (power supply unit) driver, using libsmbios: TODO [aquette] Implement a native NUT IPMI driver (remove the need for PowerMan) using OpenIPMI: TODO - [aquette] Implement the PowerPath (or PowerChain) notion in NUT, to be able to link for example PSU1 - PDU outlet2 - UPS1: TODO + [aquette] Implement PowerChain in NUT: TODO [zulcss] Investigate and implement NUT Puppet integration: TODO [zulcss] Investigate and implement NUT cobbler integration: TODO [zulcss] Investigate and implement NUT Orchestra integration: TODO [zulcss] Investigate and implement NUT Ensemble integration: TODO [kim0] Investigate and implement NUT Ensemble integration: TODO [aquette] Implement improved PDU and power devices support in fence-agents: TODO - [?] provide fence-agents package (separated from cman): TODO + [andreserl] provide fence-agents package (part of server-o-cluster-stack): TODO [andreserl] Investigate PowerNap using NUT as a data broker: INPROGRESS [aquette] Investigate PowerNap using NUT as a data broker: INPROGRESS [andreserl] Implement NUT client support in PowerWake: TODO [aquette] Implement NUT client support in PowerWake: TODO [bencer] Implement NUT support in Zentyal: TODO [aquette] Implement NUT support in Zentyal: TODO - [?] Implement power support in Cloud schedulers using NUT: TODO [cr3] Implement support for UPS testing in Checkbox using NUT: TODO [aquette] Implement support for UPS testing in Checkbox using NUT: TODO Remaining questions: - is Augeas support sufficient for configuration, or does it need a more advanced wrapper? - related to the above, is a configuration library / tool needed? - @zulcss: does Nagios nut plug-in offer sufficient features for your purpose? == Items to consider == - 1. Create power consumption reports (not ready for billing, only informative) - 2. Asset management support for power devices. Ie, Provide device information like manufacturer name and model, serial number, location, contact, service dates, ... + 1. Implement power support in Cloud schedulers using NUT: TODO (lack an assignee) + 2. Create power consumption reports (not ready for billing, only informative) + 3. Asset management support for power devices. Ie, Provide device information like manufacturer name and model, serial number, location, contact, service dates, ... -- Infrastructure power management https://blueprints.launchpad.net/ubuntu/+spec/server-o-infra-power -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint server-o-infra-power] Infrastructure power management
Blueprint changed by Arnaud Quette: Whiteboard changed: Work items: [aquette] Implement device discovery tools / libs / binding in NUT: INPROGRESS [aquette] Implement configuration library and tool for NUT: TODO [aquette] Create Augeas lenses for configuration for NUT: DONE [aquette] Distribute NUT Augeas lenses: TODO [aquette] Distribute the new NUT documentation: TODO [aquette] Create a NUT client only (upsmon) package: TODO - [server-o-cluster-stack] Convert initscripts to upstart: TODO + [aquette] Convert initscripts to upstart: TODO [aquette] Create Avahi publication script for : INPROGRESS - [aquette] Implement a native NUT PSU (power supply unit) driver, using libsmbios: TODO - [aquette] Implement a native NUT IPMI driver (remove the need for PowerMan) using OpenIPMI: TODO + [aquette] Implement a native NUT PSU (power supply unit) / IPMI driver, using OpenIPMI: TODO [aquette] Implement PowerChain in NUT: TODO [zulcss] Investigate and implement NUT Puppet integration: TODO [zulcss] Investigate and implement NUT cobbler integration: TODO [zulcss] Investigate and implement NUT Orchestra integration: TODO [zulcss] Investigate and implement NUT Ensemble integration: TODO [kim0] Investigate and implement NUT Ensemble integration: TODO [aquette] Implement improved PDU and power devices support in fence-agents: TODO [andreserl] provide fence-agents package (part of server-o-cluster-stack): TODO [andreserl] Investigate PowerNap using NUT as a data broker: INPROGRESS [aquette] Investigate PowerNap using NUT as a data broker: INPROGRESS [andreserl] Implement NUT client support in PowerWake: TODO [aquette] Implement NUT client support in PowerWake: TODO [bencer] Implement NUT support in Zentyal: TODO [aquette] Implement NUT support in Zentyal: TODO [cr3] Implement support for UPS testing in Checkbox using NUT: TODO [aquette] Implement support for UPS testing in Checkbox using NUT: TODO Remaining questions: - is Augeas support sufficient for configuration, or does it need a more advanced wrapper? - related to the above, is a configuration library / tool needed? - @zulcss: does Nagios nut plug-in offer sufficient features for your purpose? == Items to consider == 1. Implement power support in Cloud schedulers using NUT: TODO (lack an assignee) 2. Create power consumption reports (not ready for billing, only informative) 3. Asset management support for power devices. Ie, Provide device information like manufacturer name and model, serial number, location, contact, service dates, ... -- Infrastructure power management https://blueprints.launchpad.net/ubuntu/+spec/server-o-infra-power -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint server-o-infra-power] Infrastructure power management
Blueprint changed by Arnaud Quette: Whiteboard changed: Work items: - [aquette] Implement device discovery tools / libs / binding in NUT: INPROGRESS + [fredericbohe] Implement device discovery tools / libs / binding in NUT: INPROGRESS [aquette] Implement configuration library and tool for NUT: TODO [aquette] Create Augeas lenses for configuration for NUT: DONE [aquette] Distribute NUT Augeas lenses: TODO [aquette] Distribute the new NUT documentation: TODO [aquette] Create a NUT client only (upsmon) package: TODO [aquette] Convert initscripts to upstart: TODO [aquette] Create Avahi publication script for : INPROGRESS [aquette] Implement a native NUT PSU (power supply unit) / IPMI driver, using OpenIPMI: TODO [aquette] Implement PowerChain in NUT: TODO [zulcss] Investigate and implement NUT Puppet integration: TODO [zulcss] Investigate and implement NUT cobbler integration: TODO [zulcss] Investigate and implement NUT Orchestra integration: TODO [zulcss] Investigate and implement NUT Ensemble integration: TODO [kim0] Investigate and implement NUT Ensemble integration: TODO [aquette] Implement improved PDU and power devices support in fence-agents: TODO [andreserl] provide fence-agents package (part of server-o-cluster-stack): TODO [andreserl] Investigate PowerNap using NUT as a data broker: INPROGRESS [aquette] Investigate PowerNap using NUT as a data broker: INPROGRESS [andreserl] Implement NUT client support in PowerWake: TODO [aquette] Implement NUT client support in PowerWake: TODO [bencer] Implement NUT support in Zentyal: TODO [aquette] Implement NUT support in Zentyal: TODO [cr3] Implement support for UPS testing in Checkbox using NUT: TODO [aquette] Implement support for UPS testing in Checkbox using NUT: TODO Remaining questions: - is Augeas support sufficient for configuration, or does it need a more advanced wrapper? - related to the above, is a configuration library / tool needed? - @zulcss: does Nagios nut plug-in offer sufficient features for your purpose? == Items to consider == 1. Implement power support in Cloud schedulers using NUT: TODO (lack an assignee) 2. Create power consumption reports (not ready for billing, only informative) 3. Asset management support for power devices. Ie, Provide device information like manufacturer name and model, serial number, location, contact, service dates, ... -- Infrastructure power management https://blueprints.launchpad.net/ubuntu/+spec/server-o-infra-power -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 779512] Re: nut-2.6.0-1ubuntu3 behavior regression
2011/5/14 Mr. Muskrat 779...@bugs.launchpad.net Yes, I can confirm that this fixed the issue I reported. thanks for the confirmation Arnaud, thank you so much! my pleasure Matt :) Arnaud -- Linux / Unix Expert RD - Eaton - http://powerquality.eaton.com Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.free.fr/ -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in Ubuntu. https://bugs.launchpad.net/bugs/779512 Title: nut-2.6.0-1ubuntu3 behavior regression -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 779512] Re: nut-2.6.0-1ubuntu3 behavior regression
Hey Matt, 2011/5/13 Mr. Muskrat 779...@bugs.launchpad.net I thought I'd be able to just copy/paste the instructions one at a time but I hit a few snags. I installed the missing prereqs and continued on. (...) hem, sorry. I should have given you more info on build-deps and more generally well, the point is that you found your way (congrats) and that everything seems fixed on your side. can you please confirm? I'll do some more checking on my side, but 2.6.1 (soon to go out) will fix your issue. as a temporary solution, you may backup /lib/nut/usbhid-ups and replace it with drivers/usbhid-ups, while waiting for an updated package. cheers, Arnaud -- Linux / Unix Expert RD - Eaton - http://powerquality.eaton.com Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.free.fr/ -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in Ubuntu. https://bugs.launchpad.net/bugs/779512 Title: nut-2.6.0-1ubuntu3 behavior regression -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 779512] Re: nut-2.6.0-1ubuntu3 behavior regression
2011/5/11 Mr. Muskrat 779...@bugs.launchpad.net Certainly! excellent, here we go: $ svn co svn://svn.debian.org/nut/trunk $ ./autogen.sh $ ./configure --prefix=/usr \ --exec-prefix=/ \ --sysconfdir=/etc/nut \ --mandir=/usr/share/man \ --libdir=/lib \ --includedir=/usr/include \$ sudo --without-all \ --with-usb \ --enable-static \ --with-statepath=/var/run/nut \ --with-altpidpath=/var/run/nut \ --with-drvpath=/lib/nut \ --with-pidpath=/var/run/nut \ --datadir=/usr/share/nut \ --with-user=nut --with-group=nut $ sudo ./drivers/usbhid-ups -u root - -a cyberpower @Fred: can you please do the same with Troy, and send (only to) me the output. We should have sufficient validation with that. Note that a 2 mn run is sufficient... cheers, Arnaud -- Linux / Unix Expert RD - Eaton - http://powerquality.eaton.com Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.free.fr/ -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in Ubuntu. https://bugs.launchpad.net/bugs/779512 Title: nut-2.6.0-1ubuntu3 behavior regression -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 779512] Re: nut-2.6.0-1ubuntu3 behavior regression
2011/5/11 Mr. Muskrat 779...@bugs.launchpad.net Arnaud, I hope that I captured enough of the information for you. thanks Matt. I'm still trying to find a solution that would satisfy everybody. not that easy! would you be able to test an svn version (just a checkout and minimum compilation to run the driver in debug mode)? cheers, Arno -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in Ubuntu. https://bugs.launchpad.net/bugs/779512 Title: nut-2.6.0-1ubuntu3 behavior regression -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 779512] Re: nut-2.6.0-1ubuntu3 behavior regression
Hi Matt, 2011/5/10 Mr. Muskrat 779...@bugs.launchpad.net Arnaud, Here is what you have asked for. Matt •[x4linux:~] mmusgrove $ sudo service nut stop [sudo] password for mmusgrove: * Stopping Network UPS Tools [ OK ] •[x4linux:~] mmusgrove $ export USB_DEBUG=3 •[x4linux:~] mmusgrove $ sudo /lib/nut/usbhid-ups - -a cyberpower can you please try again with: $ sudo /lib/nut/usbhid-ups -u root - -a cyberpower I was thinking about the report size issue, but you're there hitting a permissions one... cheers, Arnaud -- Linux / Unix Expert RD - Eaton - http://powerquality.eaton.com Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.free.fr/ -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in Ubuntu. https://bugs.launchpad.net/bugs/779512 Title: nut-2.6.0-1ubuntu3 behavior regression -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 779512] [NEW] nut-2.6.0-1ubuntu3 behavior regression
2011/5/8 Mr. Muskrat 779...@bugs.launchpad.net Public bug reported: Binary package hint: nut Prior to upgrading to Natty, I had the nut-2.4.3-1ubuntu5 package and it was working correctly. right, but the fix made for the kind of devices you have (ie not fully complying to USB standards) broke other devices / features. the right fix would have to be in libusb, but since we're still on 0.1 (which is not maintained anymore), the solution may come from the port to libusb 1.0. After upgrading to Natty, I have the nut-2.6.0-1ubuntu3 package and it is not working correctly. Here's my release info: •[x4linux:~] mmusgrove $ lsb_release -rd Description:Ubuntu 11.04 Release:11.04 The symptom is that it can't initialize data from HID UPS and so the driver fails to start. •[x4linux:~] mmusgrove $ sudo upsdrvctl start Network UPS Tools - UPS driver controller 2.6.0 Network UPS Tools - Generic HID driver 0.35 (2.6.0) USB communication driver 0.31 Using subdriver: CyberPower HID 0.3 libusb_get_report: No error Can't initialize data from HID UPS Driver failed to start (exit status=1) (...) could you please do the following test and send back the output: - first, stop nut - then export USB_DEBUG=3 - start the driver using sudo /lib/nut/usbhid-ups - -a upsname where upsname is the one from ups.conf. - the output of dpkg -l '*libusb*' would also be useful. cheers, Arnaud -- Linux / Unix Expert RD - Eaton - http://powerquality.eaton.com Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.free.fr/ -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in Ubuntu. https://bugs.launchpad.net/bugs/779512 Title: nut-2.6.0-1ubuntu3 behavior regression -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 535583] Excessive logging by apcsmart program
2011/4/21 Michal Soltys sol...@ziu.info On 11-04-21 10:34, Arnaud Quette wrote: Hi Lupe, since we now have an apcsmart maintainer, I'm forwarding this issue to him. @Michal: could you please have a look at this issue [1], and give us your feeling? cheers, Arnaud -- [1] https://bugs.launchpad.net/bugs/535583 2011/2/15 Lupe Christoph l...@lupe-christoph.de mailto:l...@lupe-christoph.de The suggestions are pretty fine. - flushing stale input (though at driver level) Certainly. I even added some flushes earlier, but haven't touched the updateinfo and/or the functions it calls yet. I'll add it along with forthcoming patches (icanon mode and the rest). Looking at the strace, flushing post-failure might be good idea in certain cases as well. - reopening serial port If the upper layers of nut don't disallow this kind of behaviour for some reason - it's good idea as well. Should be helpful in weird cases, and at the very least wouldn't hurt at all. If it would help in this particular case, hard to say. none special. we already have to somehow do so with USB devices. - smartmode() TBH, I'm not sure why it diligently tries to enter SM 5 times. Pre-emptive flush + 'Y' + reasonable delay (icanon or not) should be all that is necessary. If we don't succeed, next attempt shouldn't miraculously (in theory) make much of a difference 1 second later ... Thanks for pointing out those issues. thanks for taking care of it ;-) cheers, Arnaud -- Linux / Unix Expert RD - Eaton - http://powerquality.eaton.com Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.free.fr/ -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in Ubuntu. https://bugs.launchpad.net/bugs/535583 Title: Excessive logging by apcsmart program -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 535583] Excessive logging by apcsmart program
Hi Lupe,
since we now have an apcsmart maintainer, I'm forwarding this issue to
him.
@Michal: could you please have a look at this issue [1], and give us your
feeling?
cheers,
Arnaud
--
[1] https://bugs.launchpad.net/bugs/535583
2011/2/15 Lupe Christoph l...@lupe-christoph.de
On Tuesday, 2011-02-15 at 13:16:58 -, Arnaud Quette wrote:
this is not the problem. This code is in the smartmode() function of
apcsmart.c:
http://svn.debian.org/wsvn/nut/trunk/drivers/apcsmart.c
we see the 5 attempts to go to smart mode ('Y' command), but my aim is to
understand why it is failing, and how to cleanly solve this without
impacting support for other units.
I found no code that does five attempts. But this code in main.c,
starting on Line 618:
while (!exit_flag) {
struct timeval timeout;
gettimeofday(timeout, NULL);
timeout.tv_sec += poll_interval;
upsdrv_updateinfo();
while (!dstate_poll_fds(timeout, extrafd) !exit_flag) {
/* repeat until time is up or extrafd has data */
upsdrv_updateinfo() calls smartmode().
dstate_poll_fds() checks if there is any file descriptor that is
available. In our case:
select(7, [4 5 6], NULL, NULL, {1, 999837}) = 1 (in [4], left {1, 999835})
FD 4 is the serial line, which is passed to dstate_poll_fds() as
extrafd.
When there is data that can be read from the UPS no code in
dstate_poll_fds() reads from extrafd, there is only code that reads
from the other input FDs. The outer loop above also ignores extrafd.
exit_flag is never set, so it continues. And because there is an active
file descriptor, the select returns immediately (actually it takes two
microseconds).
The solution is to add code that reads all data from extrafd and discards
it because nobody asked for it. I would also close and reopen the serial
line in smartmode(). I would prepare a patch if I knew more about the
I/O abstractions used in the nut driver code. Sorry.
HTH,
Lupe Christoph
--
| It is a well-known fact in any organisation that, if you want a job|
| done, you should give it to someone who is already very busy. |
| Terry Pratchett, Unseen Academicals |
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in Ubuntu.
https://bugs.launchpad.net/bugs/535583
Title:
Excessive logging by apcsmart program
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 753661] Re: upsd write() failed for 127.0.0.1: Broken pipe
so what if you issue again an upsc powercom? does it still broke the pipe? is your issue 100 % reproducible? my guess, is ATM, that the faulty end-of-line marker in battery.type is causing parseconf to close prematurely the connexion, while upsd is still sending data. which explains why unit requests works, while getting the whole tree fails... the only way to ensure this is the root cause is to fix the function that retrieve strings from the device's indexed table, to trim EOL, and check if it solves your issue. would you be ready to test a fix using subversion? cheers, Arno -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in Ubuntu. https://bugs.launchpad.net/bugs/753661 Title: upsd write() failed for 127.0.0.1: Broken pipe -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 753661] Re: upsd write() failed for 127.0.0.1: Broken pipe
2011/4/18 Virus 753...@bugs.launchpad.net yes, it 100 % reproducible. I also managed to reproduce it using dummy-ups (the simulation driver) and injecting the error on the same variable: adding a newline (ie \n) results in a broken pipe on upsc side. i am ready to test svn version. ok, here we go: 1) checkout an svn copy using: $ svn co svn://svn.debian.org/nut/trunk 2) configure it using (Debian arguments, limited for the current test scope ; should be sufficient): --prefix=/usr \ --exec-prefix=/ \ --sysconfdir=/etc/nut \ --mandir=/usr/share/man \ --libdir=/lib \ --includedir=/usr/include \ --without-all \ --with-usb \ --enable-static \ --with-statepath=/var/run/nut \ --with-altpidpath=/var/run/nut \ --with-drvpath=/lib/nut \ --with-pidpath=/var/run/nut \ --datadir=/usr/share/nut \ --with-pkgconfig-dir=/usr/lib/pkgconfig \ --with-user=nut --with-group=nut 3) apply the attached patch $ patch -p0 /path/to/virus.patch 4) make as usual, ie $ make 5) stop all previous NUT instances, then launch the new driver and upsd $ sudo drivers/usbhid-ups -a powercom $ sudo server/upsd -DDD 6) now issue your upsc of death $ upsc powercom everything should behave fine. Remember that it's a blind patch: I've not validated the above configure line, nor the patch itself! cheers, Arnaud -- Linux / Unix Expert RD - Eaton - http://powerquality.eaton.com Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.free.fr/ ** Attachment added: virus.patch https://bugs.launchpad.net/bugs/753661/+attachment/2059655/+files/virus.patch -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in Ubuntu. https://bugs.launchpad.net/bugs/753661 Title: upsd write() failed for 127.0.0.1: Broken pipe -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 753661] Re: upsd write() failed for 127.0.0.1: Broken pipe
2011/4/18 Virus 753...@bugs.launchpad.net It`s working great! Many thanks! excellent, thanks for the feedback. I've just committed it upstream (r2972) the changeset will be available on the NUT Trac mirror (just give it some minutes to sync): http://trac.networkupstools.org/projects/nut/changeset/2972 I'll leave up to our Ubuntu friends to generate an updated package. I have to note that importance is low since this should not affect the protection (ie upsmon is still working fine). @Virus: can you please confirm this point? cheers, Arnaud -- Linux / Unix Expert RD - Eaton - http://powerquality.eaton.com Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.free.fr/ -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in Ubuntu. https://bugs.launchpad.net/bugs/753661 Title: upsd write() failed for 127.0.0.1: Broken pipe -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 753661] Re: upsd write() failed for 127.0.0.1: Broken pipe
2011/4/16 Virus 753...@bugs.launchpad.net $ upsc battery.type Error: Unknown UPS $ upsc ups.status Error: Unknown UPS damn, I missed a bit (ie the device name): $ upsc powercom battery.type Error: Unknown UPS $ upsc powercom ups.status Error: Unknown UPS don't forget to run upsd in debug mode, as in the previous test. I need to see how it react. cheers Arno -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in Ubuntu. https://bugs.launchpad.net/bugs/753661 Title: upsd write() failed for 127.0.0.1: Broken pipe -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 753661] [NEW] upsd write() failed for 127.0.0.1: Broken pipe
2011/4/7 Virus 753...@bugs.launchpad.net Public bug reported: Binary package hint: nut I have Powercom UPS and trying configure it with NUT. lsusb: Bus 006 Device 002: ID 0d9f:0004 Powercom Co., Ltd ups.conf: [powercom] driver = usbhid-ups port = /dev/usb/hiddev0 putting auto is sufficient here productid = 0004 this productid should be added to the driver. before that, I need the output f an lsusb -v -d 0x0d9f:0004 desc = My UPS but when i trying run `upsc powercom` got this output: -- battery.charge: 99 battery.charge.low: 10 battery.charge.warning: 30 battery.date: 2009/12/23 battery.runtime: 24576 battery.type: PbAc -- and `upsd[24062]: write() failed for 127.0.0.1: Broken pipe` in /var/log/daemon.log how i can fix this? good question! is the driver still running? what is your start method (ie using invoke-rc.d or alike, or directly starting components manually)? what is the content of your upsd.conf? after having stopped previous instance (invoke-rc.d nut stop), what is the output of: $ sudo upsd -v then, stop upsd (sudo upsd -c stop) and start in 3 separate consoles: $ sudo upsd -DDD $ sudo /lib/nut/usbhid-ups -D -a powercom $ upsc powercom and send back the various output. cheers, Arnaud -- Linux / Unix Expert RD - Eaton - http://powerquality.eaton.com Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.free.fr/ -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in Ubuntu. https://bugs.launchpad.net/bugs/753661 Title: upsd write() failed for 127.0.0.1: Broken pipe -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 753661] Re: upsd write() failed for 127.0.0.1: Broken pipe
2011/4/16 Virus 753...@bugs.launchpad.net Seems driver respond correctly, but upsd return Broken pipe after: 25.768861 write: [destfd=6] [len=35] [VAR powercom battery.type PbAc ] Two lines? yup, but upsd sends everything. and upsc brokes the pipe. the driver is still there, so the issue is really between upsc and upsd. 2 more tests, still with upsd running in debug mode: $ upsc battery.type $ upsc ups.status cheers, Arno -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in Ubuntu. https://bugs.launchpad.net/bugs/753661 Title: upsd write() failed for 127.0.0.1: Broken pipe -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 743484] [NEW] libupsclient.pc contains unresolved symbols
Salut Fabrice
2011/3/27 Fabrice Coutadeur coutade...@gmail.com
Public bug reported:
Binary package hint: nut
Hi,
While I was investigating a FTBFS in collectd:
...
configure:22249: checking for upscli_connect in -lupsclient
configure:22274: i686-linux-gnu-gcc -o conftest -Wall -g -O2
-I/build/fabrice-collectd_4.10.1-2.1build1-i386-7yH3eE/collectd-4.10.1/debian/include
-DLT_LAZY_OR_NOW='RTLD_LAZY|RTLD_GLOBAL' -UCONFIGFILE
-DCONFIGFILE='/etc/collectd/collectd.conf' -Wl,-Bsymbolic-functions
@LIBSSL_LDFLAGS@ -L/lib -lupsclient conftest.c -lupsclient -ldl 5
i686-linux-gnu-gcc: @LIBSSL_LDFLAGS@: No such file or directory
I discovered that this reference to LIBSSL_LDFLAGS comes from
libupsclient.pc.
As you can see in actual .pc file, this reference has not been resolved at
compile time (content of more /usr/lib/pkgconfig/libupsclient.pc in a natty
schroot):
prefix=/usr
exec_prefix=/
libdir=/lib
includedir=/usr/include
sysconfdir=/etc/nut
statepath=/var/run/nut
nutuser=nut
Name: libupsclient
Description: UPS monitoring with Network UPS Tools
Version: 2.6.0
Libs: -L${libdir} -lupsclient @LIBSSL_LDFLAGS@
Cflags: -I${includedir}
This is because configure script and all makefile.in has been updated to
use and substitute LIBSSL_LIBS instead of LIBSSL_LDFLAGS, but
libupsclient.pc.in has not been updated.
By replacing LIBSSL_LDFLAGS with LIBSSL_LIBS in .in files, the generated
.pc file is correct.
fully right, thanks for investigation and patch.
For the sake of completion, lib/libupsclient-config.in (a replacement when
pkg-config is not present) also need to be fixed.
I've just applied it upstream (in NUT, commit r2960) while waiting for a new
Debian upload (I may lag a bit more, considering my current workload...):
http://trac.networkupstools.org/projects/nut/changeset/2960
Note that the above link may not yet be active by the reception of this
mail.
cheers,
Arnaud
--
Linux / Unix Expert RD - Eaton - http://powerquality.eaton.com
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.free.fr/
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in Ubuntu.
https://bugs.launchpad.net/bugs/743484
Title:
libupsclient.pc contains unresolved symbols
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
RE: [Bug 722007] Re: php5-fpm is missing in natty
Great!!! Thanks! -Original Message- Date: Thursday, February 24, 2011 7:31:00 am To: webo...@codealpha.net From: Chuck Short chuck.sh...@canonical.com Subject: [Bug 722007] Re: php5-fpm is missing in natty This is fixed again. ** Changed in: php5 (Ubuntu Natty) Status: Triaged = Fix Released -- You received this bug notification because you are a direct subscriber of the bug. https://bugs.launchpad.net/bugs/722007 Title: php5-fpm is missing in natty Status in ?php5? package in Ubuntu: Fix Released Status in ?php5? source package in Natty: Fix Released Bug description: Binary package hint: php5 php5-fpm is currently unavailable in Natty. This might be due to a change done in package php5 version 5.3.3-2 (see https://launchpad.net/ubuntu/natty/+source/php5/5.3.3-7ubuntu1) where building FPM has been disabled. The package had probably been merged into Ubuntu during debianImport. It seems that the latest version of php5 (3.5.3-1 see http://packages.debian.org/changelogs/pool/main/p/php5/current/changelog) from debian has reintroduced the build of PHP-FPM. Please also see bug 708504 which is the needs-packaging bug report for this 5.3.5 version of php5. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: php5 (not installed) ProcVersionSignature: Ubuntu 2.6.38-4.31-generic 2.6.38-rc5 Uname: Linux 2.6.38-4-generic x86_64 Architecture: amd64 Date: Sat Feb 19 21:05:47 2011 EcryptfsInUse: Yes InstallationMedia: Ubuntu 11.04 Natty Narwhal - Alpha amd64 (20110202) ProcEnviron: LC_MONETARY=en_US.utf8 PATH=(custom, user) LANG=fr_FR.utf8 SHELL=/bin/bash SourcePackage: php5 To unsubscribe from this bug, go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/722007/+subscribe -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php5 in ubuntu. https://bugs.launchpad.net/bugs/722007 Title: php5-fpm is missing in natty -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 708504] Re: [needs-packaging] PHP 5.3.5 is available.
It appears that 5.3.5 has recently been uploaded into Natty (https://launchpad.net/ubuntu/+source/php5). Can someone confirm? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php5 in ubuntu. https://bugs.launchpad.net/bugs/708504 Title: [needs-packaging] PHP 5.3.5 is available. -- 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 708504] Re: [needs-packaging] PHP 5.3.5 is available.
bug 722007 has been created for this issue with php5-fpm missing. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php5 in ubuntu. https://bugs.launchpad.net/bugs/708504 Title: [needs-packaging] PHP 5.3.5 is available. -- 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 708504] Re: [needs-packaging] PHP 5.3.5 is available.
I'm not sure the best way to go about this, but this package (5.3.5-1 in debian) will need to be synced before freeze so that we can have php5-fpm back into natty. Right now, php5-fpm is not available (probably since 5.3.3-2). -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php5 in ubuntu. https://bugs.launchpad.net/bugs/708504 Title: [needs-packaging] PHP 5.3.5 is available. -- 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 722007] [NEW] php5-fpm is missing in natty
Public bug reported: Binary package hint: php5 php5-fpm is currently unavailable in Natty. This might be due to a change done in package php5 version 5.3.3-2 (see https://launchpad.net/ubuntu/natty/+source/php5/5.3.3-7ubuntu1) where building FPM has been disabled. The package had probably been merged into Ubuntu during debianImport. It seems that the latest version of php5 (3.5.3-1 see http://packages.debian.org/changelogs/pool/main/p/php5/current/changelog) from debian has reintroduced the build of PHP-FPM. Please also see bug 708504 which is the needs-packaging bug report for this 5.3.5 version of php5. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: php5 (not installed) ProcVersionSignature: Ubuntu 2.6.38-4.31-generic 2.6.38-rc5 Uname: Linux 2.6.38-4-generic x86_64 Architecture: amd64 Date: Sat Feb 19 21:05:47 2011 EcryptfsInUse: Yes InstallationMedia: Ubuntu 11.04 Natty Narwhal - Alpha amd64 (20110202) ProcEnviron: LC_MONETARY=en_US.utf8 PATH=(custom, user) LANG=fr_FR.utf8 SHELL=/bin/bash SourcePackage: php5 ** Affects: php5 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug natty regression ** Description changed: Binary package hint: php5 php5-fpm is currently unavailable in Natty. - This might be due to package php5 5.3.3-2 (see https://launchpad.net/ubuntu/natty/+source/php5/5.3.3-7ubuntu1) where building FPM has been disabled. The package had probably been merged during debianImport. - It seems that the latest version of php5 (3.5.3-1) from debian has reintroduced the build of PHP-FPM. + This might be due to a change done in package php5 version 5.3.3-2 (see https://launchpad.net/ubuntu/natty/+source/php5/5.3.3-7ubuntu1) where building FPM has been disabled. The package had probably been merged into Ubuntu during debianImport. + It seems that the latest version of php5 (3.5.3-1 see http://packages.debian.org/changelogs/pool/main/p/php5/current/changelog) from debian has reintroduced the build of PHP-FPM. Please also see bug 708504 which is the needs-packaging bug report for this 5.3.5 version of php5. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: php5 (not installed) ProcVersionSignature: Ubuntu 2.6.38-4.31-generic 2.6.38-rc5 Uname: Linux 2.6.38-4-generic x86_64 Architecture: amd64 Date: Sat Feb 19 21:05:47 2011 EcryptfsInUse: Yes InstallationMedia: Ubuntu 11.04 Natty Narwhal - Alpha amd64 (20110202) ProcEnviron: - LC_MONETARY=en_US.utf8 - PATH=(custom, user) - LANG=fr_FR.utf8 - SHELL=/bin/bash + LC_MONETARY=en_US.utf8 + PATH=(custom, user) + LANG=fr_FR.utf8 + SHELL=/bin/bash SourcePackage: php5 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php5 in ubuntu. https://bugs.launchpad.net/bugs/722007 Title: php5-fpm is missing in natty -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 535583] Excessive logging by apcsmart program
2011/2/15 Lupe Christoph
On Monday, 2011-02-14 at 21:54:20 -, Arnaud Quette wrote:
I definitely need more info!
please reply to ALL:
- what is the exact model and date of manufacturing?
SmartUPS 300I NET. I have the serial number (GS9809283199) but no date.
it seems to be a recent model.
- are you sure this unit is ok?
You can't prove the absence of faults.
this was related to the following question...
- have you really checked the cabling or made the whole (cable + UPS)
work
somehow (using APC's software or apcupsd)?
Well, as I said this is working OK for days or weeks. Then something
happens that triggers a bug in apcsmart.
quickly reading back the thread, I can't find these info...
- what is the meantime between occurrences of these issues?
I don;t have enough data. It's in the range of weeks or months.
as per your previous posts, this seemed more to be a matter of minutes /
hours.
- is the device reachable (using upsc for example) between issues?
Sure, everything works fine.
A driver debug output is really needed!
I'm running it again, but no promises. Reboots are much more frequent
than this misbehaviour.
Note that I'm not the developer of this driver, nor have any acquaintance
with APC.
Same here. Though I will probably try to locate this bug if we don;t
make progress with the debugging output, either because it does not tell
us enough or because I don't manage to capture it.
I would have thought finding the place in the code where it is trying to
reset the UPS connection wouldn't be this hard.
this is not the problem. This code is in the smartmode() function of
apcsmart.c:
http://svn.debian.org/wsvn/nut/trunk/drivers/apcsmart.c
we see the 5 attempts to go to smart mode ('Y' command), but my aim is to
understand why it is failing, and how to cleanly solve this without
impacting support for other units.
Some more questions:
- how are you handling the device's permissions?
Refer to § II, section 3:
http://git.debian.org/?p=collab-maint/nut.git;a=blob_plain;f=debian/nut.README.Debian;hb=HEAD
cheers
Arnaud
--
Linux / Unix Expert RD - Eaton - http://powerquality.eaton.com
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.free.fr/
--
Conseiller Municipal - Saint Bernard du Touvet
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in ubuntu.
https://bugs.launchpad.net/bugs/535583
Title:
Excessive logging by apcsmart program
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 535583] Re: Excessive logging by apcsmart program
I definitely need more info! please reply to ALL: - what is the exact model and date of manufacturing? - are you sure this unit is ok? - have you really checked the cabling or made the whole (cable + UPS) work somehow (using APC's software or apcupsd)? - what is the meantime between occurrences of these issues? - is the device reachable (using upsc for example) between issues? A driver debug output is really needed! Note that I'm not the developer of this driver, nor have any acquaintance with APC. cheers Arnaud -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in ubuntu. https://bugs.launchpad.net/bugs/535583 Title: Excessive logging by apcsmart program -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 535583] Re: Excessive logging by apcsmart program
Hi Christoph, 2011/2/10 Lupe Christoph Since the supposed fix, I have had several ne incidents of this bug. I'm now running Maverick Meerkat, and the log shows this: Feb 10 14:10:14 alanya apcsmart[3238]: Communications with UPS lost: Communications with UPS lost - check cabling Feb 10 14:10:14 alanya apcsmart[3238]: smartmode: ser_send_char failed: Input/output error Feb 10 14:10:14 alanya apcsmart[3238]: last message repeated 9 times ... and nauseam, or until the /var/log partition fills up. The nut package is up to data (2.4.3-1ubuntu5). Please reopen this bug. could you please send us a driver debug output for investigation purpose. Ie, after having stopped the running NUT instance, launch: $ sudo /lib/nut/apcsmart -D -a device-id-from-ups.conf let it run for a few seconds / minutes (at least, have a couple of issue reproduction), then break using Ctrl+C. Don't forget to relaunch NUT then... cheers, Arnaud -- Linux / Unix Expert RD - Eaton - http://powerquality.eaton.com Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.free.fr/ -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in ubuntu. https://bugs.launchpad.net/bugs/535583 Title: Excessive logging by apcsmart program -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 705552] Re: 10.04 nut package is missing 52_nut-usbups.rules
2011/1/24 Hugh Saunders Apologies, I had forgotten about /lib/udev/rules.d. I have removed 52-nut-usbups.rules from /etc/udev/rules.d and it still works (see log below). There must have been some other configuration problem initially. I have marked this bug as invalid. (...) quite probably the udevadm trigger line that isn't sufficient to refresh privileges for already plugged devices. This won't be noticed if the device's USB cord is plugged after NUT installation, or if there is a reboot somewhere in the process... cheers, Arnaud -- Linux / Unix Expert RD - Eaton - http://powerquality.eaton.com Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.free.fr/ -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in ubuntu. https://bugs.launchpad.net/bugs/705552 Title: 10.04 nut package is missing 52_nut-usbups.rules -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 703211] [NEW] package mysql-server-5.1 5.1.37-1ubuntu5.4 failed to install/upgrade: le sous-processus nouveau script pre-removal a retourné une erreur de sortie d'état 1
Public bug reported: Préconfiguration des paquets... (Lecture de la base de données... 289546 fichiers et répertoires déjà installés.) Préparation du remplacement de mysql-server-5.1 5.1.37-1ubuntu5.4 (en utilisant .../mysql-server-5.1_5.1.37-1ubuntu5.5_i386.deb) ... * Stopping MySQL database server mysqld ...fail! invoke-rc.d: initscript mysql, action stop failed. dpkg : avertissement : ancien script pre-removal a retourné une erreur de sortie d'état 1 dpkg - tentative d'exécution du script du nouveau paquet à la place ... * Stopping MySQL database server mysqld ...fail! invoke-rc.d: initscript mysql, action stop failed. dpkg : erreur de traitement de /var/cache/apt/archives/mysql-server-5.1_5.1.37-1ubuntu5.5_i386.deb (--unpack) : le sous-processus nouveau script pre-removal a retourné une erreur de sortie d'état 1 * Stopping MySQL database server mysqld ...fail! invoke-rc.d: initscript mysql, action stop failed. * Starting MySQL database server mysqld ...done. Des erreurs ont été rencontrées pendant l'exécution : /var/cache/apt/archives/mysql-server-5.1_5.1.37-1ubuntu5.5_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Échec de l'installation d'un paquet. Tentative de récupération : ProblemType: Package AptOrdering: mysql-server-5.1: Install mysql-server-5.1: Configure Architecture: i386 Date: Sat Jan 15 09:48:35 2011 DistroRelease: Ubuntu 9.10 ErrorMessage: le sous-processus nouveau script pre-removal a retourné une erreur de sortie d'état 1 InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5) MySQLConf.etc.mysql.conf.d.mysqld.safe.syslog.cnf: [mysqld_safe] syslog MySQLVarLibDirListing: ['debian-5.1.flag', 'mysql_upgrade_info', 'ib_logfile0', 'mysql', 'ib_logfile1', 'ibdata1', 'sakila', 'dvd_collection'] NonfreeKernelModules: nvidia Package: mysql-server-5.1 5.1.37-1ubuntu5.4 ProcVersionSignature: Ubuntu 2.6.31-22.70-generic SourcePackage: mysql-dfsg-5.1 Title: package mysql-server-5.1 5.1.37-1ubuntu5.4 failed to install/upgrade: le sous-processus nouveau script pre-removal a retourné une erreur de sortie d'état 1 Uname: Linux 2.6.31-22-generic i686 ** Affects: mysql-dfsg-5.1 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-dfsg-5.1 in ubuntu. https://bugs.launchpad.net/bugs/703211 Title: package mysql-server-5.1 5.1.37-1ubuntu5.4 failed to install/upgrade: le sous-processus nouveau script pre-removal a retourné une erreur de sortie d'état 1 -- 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 703211] Re: package mysql-server-5.1 5.1.37-1ubuntu5.4 failed to install/upgrade: le sous-processus nouveau script pre-removal a retourné une erreur de sortie d'état 1
-- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-dfsg-5.1 in ubuntu. https://bugs.launchpad.net/bugs/703211 Title: package mysql-server-5.1 5.1.37-1ubuntu5.4 failed to install/upgrade: le sous-processus nouveau script pre-removal a retourné une erreur de sortie d'état 1 -- 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
