Hi fellows,
It's always true that I'm more focused on upstream these years, than on
Debian an Ubuntu.
I'll try to make a summary to explain the what and how on this nut-scanner
feature, on the Debian ticket
cheers
Arno
--
Eaton Data Center Automation Solutions - Opensource Leader -
Hi guys,
this is very possibly a duplicate of #1483615
the error is probably due to an issue retrieving a string, and not handled in
the driver code.
To confirm, please start the driver in debug mode using (as root):
/lib/nut/usbhid-ups -u nut -DDD -a myups
then
/lib/nut/usbhid-ups -u root -DDD
** 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
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
** 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
Logged upstream, fixed and due with the next 2.7.3 release:
https://github.com/networkupstools/nut/issues/140
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1099947
Title:
driver unable to connect
: 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
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
I forgot: could you please confirm back, so that I can update NUT HCL.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1197878
Title:
SNMPv3 not working with APC
To manage notifications about this
: Confirmed = Fix Released
** Changed in: nut (Ubuntu)
Assignee: (unassigned) = Arnaud Quette (aquette)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1197878
Title:
SNMPv3 not working with APC
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
Have you tried without mentioning mibs=apcc in ups.conf?
Arno
--
(sent from my eeePad... please excuse my brevity)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1197878
Title:
SNMPv3 not working
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
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
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
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
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
This will be fixed with the next sync with Debian (nut-2.6.3-2 or
better, nut 2.6.4-1)
-- Arnaud
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/920844
Title:
nut-client is missing
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.
2012/6/9 Dmitry Andreychuk 915...@bugs.launchpad.net
I'll test it next week, as soon as i get to the hardware.
great, thanks.
cheers,
-- Arnaud
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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
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
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
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
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
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
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
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
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
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
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
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
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.
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.
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
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
** 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
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
in: nut (Ubuntu)
Assignee: (unassigned) = Arnaud Quette (aquette)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/575573
Title:
libusb_get_interrupt: Connection timed out
To manage notifications about
** Changed in: nut (Ubuntu)
Assignee: (unassigned) = Arnaud Quette (aquette)
** Changed in: nut (Ubuntu)
Status: New = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/920844
** 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
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
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
---
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
--
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
** 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
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
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
---
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
--
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
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
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
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:
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:
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
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
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
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
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
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
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
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
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
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
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
Can you please test with the blazer_usb driver and report back?
This one has replaced megatec_usb officially since 2.4.3, but was already
available in 2.4.1 (though not as mature).
cheers,
Arnaud
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
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
There is an effort underway to provide the needed foundations for adding
a decent debconf for generating a suitable configuration.
I will leave this bug open as a reminder.
thanks for your report,
Arnaud
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
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
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
2011/12/6 Fabio M. Di Nitto fabbi...@fabbione.net
On 12/6/2011 4:05 PM, Arnaud Quette wrote:
Hi Fabio,
2011/12/6 Fabio M. Di Nitto fabbi...@fabbione.net:
On 12/6/2011 2:27 PM, Arnaud Quette wrote:
Hi Cluster-devel list,
You will find attached a patch originating from Ubuntu (Andres
Hi Cluster-devel list,
You will find attached a patch originating from Ubuntu (Andres
Rodriguez), that fixes a few issues in manpages (namely fence_drac and
fence_scsi).
Please consider applying it.
As a side note, you may want to consider Asciidoc [1] to handle
generation of manpages, in groff
** Attachment added: fence-agents-manpages.diff
https://bugs.launchpad.net/bugs/809166/+attachment/2621786/+files/fence-agents-manpages.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/809166
Hi Fabio,
2011/12/6 Fabio M. Di Nitto fabbi...@fabbione.net:
On 12/6/2011 2:27 PM, Arnaud Quette wrote:
Hi Cluster-devel list,
You will find attached a patch originating from Ubuntu (Andres
Rodriguez), that fixes a few issues in manpages (namely fence_drac and
fence_scsi).
I wonder why
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
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
Hi Andres,
I'm sorry if my comment sound angry but I wasn't :).
ok, just wanted to be sure that there wasn't some pending problems ;-)
And the Debian maintainer has taken my changes now so I'll be updating
it. Thank you!
perfect! Though I've not seen a patch on cluster-devel to fix this
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
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
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
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
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
Hey Andres and all,
2011/11/23 Andres Rodriguez andres...@ubuntu-pe.org:
All,
I'll update fence-agents once the debian maintainer takes the Ubuntu
packaging changes into the debian packages.
take it easy Andres, you seem to be a little angry on this ;)
from an upstream and DD point of view:
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
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
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
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
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
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 =
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 =
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
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
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
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
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
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
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
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
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
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
1 - 100 of 427 matches
Mail list logo
