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
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
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
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
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
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
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
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
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
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
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
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
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
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:
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
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:
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
Public bug reported:
fence-agents 3.1.5 has been released on 08-Jul-2011:
https://fedorahosted.org/releases/f/e/fence-agents/
Please consider an update Andres ;-)
cheers,
Arnaud
** Affects: fence-agents (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug
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
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
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
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
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
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
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
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
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 \
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 \
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
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
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:~]
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:~]
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)
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)
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
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
, 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
, 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
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
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,
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):
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
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,
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):
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
2011/1/10 Laurent Bigonville bi...@bigon.be
I've found the issue.
Actually the nut_check_*.m4 are setting *_LDFLAGS instead of *_LIBS, and
due to a toolchain change this become visible (gcc -o testusb testusb.c
-lusb is working but gcc -o testusb -lusb testusb.c is not working
anymore)
2011/1/10 Laurent Bigonville bi...@bigon.be
I've found the issue.
Actually the nut_check_*.m4 are setting *_LDFLAGS instead of *_LIBS, and
due to a toolchain change this become visible (gcc -o testusb testusb.c
-lusb is working but gcc -o testusb -lusb testusb.c is not working
anymore)
2010/12/19 Alf Aedan 692...@bugs.launchpad.net
Public bug reported:
Binary package hint: nut
Whenever I boot my system (running Ubuntu 10.10), I get these errors in my
boot.log and on the screen if I'm on the console:
udevd[458]: BUS= will be removed in a future udev version, please use
2010/12/19 Alf Aedan 692...@bugs.launchpad.net
Public bug reported:
Binary package hint: nut
Whenever I boot my system (running Ubuntu 10.10), I get these errors in my
boot.log and on the screen if I'm on the console:
udevd[458]: BUS= will be removed in a future udev version, please use
Hi Dave,
thanks for your report and logs.
this is strange, since there is only a minor libusb update, which seems not
to break compatibility.
but the fact is that AC_CHECK_FUNCS doesn't find usb_init() anymore, so
there is actually something wrong.
I'm currently busy preparing 2.6.0, so don't
Hi Dave,
thanks for your report and logs.
this is strange, since there is only a minor libusb update, which seems not
to break compatibility.
but the fact is that AC_CHECK_FUNCS doesn't find usb_init() anymore, so
there is actually something wrong.
I'm currently busy preparing 2.6.0, so don't
Hi Michael,
thanks for your feedback! I'm cc'ing the NUT users list for info.
I've also added an entry for your device (Powerwalker Line Interactive VI
1400, using blazer_usb).
Can you please send back an upsc output, and at least check for the shutdown
behavior, if not already done:
FYI
@Arjen: anything else required?
cheers,
Arnaud
-- Forwarded message --
From: MichaelE 662...@bugs.launchpad.net
Date: 2010/10/20
Subject: [Bug 662435] Re: megatec_usb driver stopped working after upgrade
from 8.04 to 10.04
To: aquette@gmail.com
I tested the shutdown
Hi Michael,
thanks for your feedback! I'm cc'ing the NUT users list for info.
I've also added an entry for your device (Powerwalker Line Interactive VI
1400, using blazer_usb).
Can you please send back an upsc output, and at least check for the shutdown
behavior, if not already done:
FYI
@Arjen: anything else required?
cheers,
Arnaud
-- Forwarded message --
From: MichaelE 662...@bugs.launchpad.net
Date: 2010/10/20
Subject: [Bug 662435] Re: megatec_usb driver stopped working after upgrade
from 8.04 to 10.04
To: aquette@gmail.com
I tested the shutdown
2010/10/18 MichaelE 662...@bugs.launchpad.net
Public bug reported:
Binary package hint: nut
I was using nut with the megatec_usb driver for years without problems.
Now I upgraded my server to 10.04 and the driver stopped to work with
nut_2.4.3-1ubuntu3.1. Here is the ups.conf I am using
2010/10/18 MichaelE 662...@bugs.launchpad.net
Public bug reported:
Binary package hint: nut
I was using nut with the megatec_usb driver for years without problems.
Now I upgraded my server to 10.04 and the driver stopped to work with
nut_2.4.3-1ubuntu3.1. Here is the ups.conf I am using
** Attachment added: replacement /etc/init.d/nut for debug / investigation
purpose
http://launchpadlibrarian.net/52657944/nut
--
problems with ups (mge pulsar es 8+)
https://bugs.launchpad.net/bugs/608182
You received this bug notification because you are a member of Ubuntu
Server Team,
2010/7/28 Wolfgang Lubowski
there are no results for mge-utalk in /var/log/messages
any (driver(s) failed) message during the boot?
if I don't start nut manually with /etc/init.d/nut start, I always get the
following message:
Broadcast Message from n...@l4
(somewhere) at 10:40 ...
** Attachment added: replacement /etc/init.d/nut for debug / investigation
purpose
http://launchpadlibrarian.net/52657944/nut
--
problems with ups (mge pulsar es 8+)
https://bugs.launchpad.net/bugs/608182
You received this bug notification because you are a member of Ubuntu
Bugs, which is
2010/7/28 Wolfgang Lubowski
there are no results for mge-utalk in /var/log/messages
any (driver(s) failed) message during the boot?
if I don't start nut manually with /etc/init.d/nut start, I always get the
following message:
Broadcast Message from n...@l4
(somewhere) at 10:40 ...
2010/7/26 Wolfgang Lubowski w@gmx.at
I still get the same outputs with NUT-Monitor.
my nut.conf looks now the following:
MODE=standalone
ps -efl | grep mge-utalk:
0 S root 2066 2002 0 80 0 - 1907 pipe_w 08:37 pts/000:00:00
grep --color=auto mge-utalk
upsc mgeups:
2010/7/26 Wolfgang Lubowski w@gmx.at
I still get the same outputs with NUT-Monitor.
my nut.conf looks now the following:
MODE=standalone
ps -efl | grep mge-utalk:
0 S root 2066 2002 0 80 0 - 1907 pipe_w 08:37 pts/000:00:00
grep --color=auto mge-utalk
upsc mgeups:
2010/7/23 Wolfgang Lubowski w@gmx.at
this is the output for upsc mgeups:
device.mfr: MGE UPS SYSTEMS
device.model: Pulsar ES8+
device.type: ups
driver.name: mge-utalk
driver.parameter.pollinterval: 2
driver.parameter.port: /dev/ttyS0
driver.version: 2.4.3
driver.version.internal:
2010/7/23 Wolfgang Lubowski w@gmx.at
this is the output for upsc mgeups:
device.mfr: MGE UPS SYSTEMS
device.model: Pulsar ES8+
device.type: ups
driver.name: mge-utalk
driver.parameter.pollinterval: 2
driver.parameter.port: /dev/ttyS0
driver.version: 2.4.3
driver.version.internal:
Hi Wolfgang,
I'm cc'ing NUT-Monitor author, for info
2010/7/22 Wolfgang Lubowski
sorry for bothering you again
autoshutdown works fine, thank you :)
but a graphical tool would be nice too, and nut-monitor doesn't work up to
now:
if I start it from terminal, I get the following:
Traceback
2010/7/22 Wolfgang Lubowski 608...@bugs.launchpad.net
and there is another thing I don't really understand:
these ups-things aren't started completely, after reboot I get UPS
mge...@localhost is unavailable, so I have to run /etc/init.d/nut start
and then it works.
there can be several
Hi Wolfgang,
I'm cc'ing NUT-Monitor author, for info
2010/7/22 Wolfgang Lubowski
sorry for bothering you again
autoshutdown works fine, thank you :)
but a graphical tool would be nice too, and nut-monitor doesn't work up to
now:
if I start it from terminal, I get the following:
Traceback
2010/7/22 Wolfgang Lubowski 608...@bugs.launchpad.net
and there is another thing I don't really understand:
these ups-things aren't started completely, after reboot I get UPS
mge...@localhost is unavailable, so I have to run /etc/init.d/nut start
and then it works.
there can be several
Hi Wolfgang,
a first and quick comment: this is not a NUT bug, but rather a PSP one!
2010/7/21 Wolfgang Lubowski
oops, doesn't work like I expected :)
nut.conf:
MODE=none
apart from some binary issues with PSP, this one is still sitting on NUT 2.2
compatibility.
On Debian, I've recently
Hi Wolfgang,
a first and quick comment: this is not a NUT bug, but rather a PSP one!
2010/7/21 Wolfgang Lubowski
oops, doesn't work like I expected :)
nut.conf:
MODE=none
apart from some binary issues with PSP, this one is still sitting on NUT 2.2
compatibility.
On Debian, I've recently
guys,
I'd be interested in a driver debug output, ie:
$ export USB_DEBUG=3
$ /lib/nut/megatec_usb -D -a upsname
let it run for a couple of minutes, then break it (using Ctrl+C) and send
back the trace.
cheers,
Arnaud
--
Linux / Unix Expert RD - Eaton - http://www.eaton.com/mgeops
Network
guys,
I'd be interested in a driver debug output, ie:
$ export USB_DEBUG=3
$ /lib/nut/megatec_usb -D -a upsname
let it run for a couple of minutes, then break it (using Ctrl+C) and send
back the trace.
cheers,
Arnaud
--
Linux / Unix Expert RD - Eaton - http://www.eaton.com/mgeops
Network
2010/7/5 Thierry Carrez
@Arnaud: python-matplotlib is still a depends from pwrkap in 7.30-4:
ooch, I did it.
-5 uploaded, and actually fixing it (double² checked)
Arno
--
Only pwrkap-gui should depend on python-matplotlib
https://bugs.launchpad.net/bugs/598028
You received this bug
2010/6/25 Thierry Carrez
Thanks Arnaud, will do !
you're welcome.
-4 is now in unstable, so ready for the sync:
http://packages.qa.debian.org/p/pwrkap/news/20100624T190215Z.html
cheers,
Arno
--
Only pwrkap-gui should depend on python-matplotlib
https://bugs.launchpad.net/bugs/598028
You
Hi Thierry,
2010/6/24 Thierry Carrez thierry.car...@ubuntu.com
Public bug reported:
Binary package hint: pwrkap
pwrkap depends on python-matplotlib, which depends on graphical
libraries. This pulls unnecessary slack on servers where pwrkap would be
installed.
It looks like only
2010/5/3 Chuck Short chuck.sh...@canonical.com
Statement of Impact:
nut in lucid was shipped with a bug that prevented some UPSes from
connecting to the nut daemon. Checking google fedora was also affected
by the same problem and has the same patch that we used.
Explanation:
This bug has
2010/5/3 Chuck Short chuck.sh...@canonical.com
Statement of Impact:
nut in lucid was shipped with a bug that prevented some UPSes from
connecting to the nut daemon. Checking google fedora was also affected
by the same problem and has the same patch that we used.
Explanation:
This bug has
please try to unplug and plug back your UPS's USB cord, and then relaunch
nut.
cheers,
Arnaud
--
Linux / Unix Expert RD - Eaton - http://www.eaton.com/mgeops
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://www.debian.org
Free Software Developer
please try to unplug and plug back your UPS's USB cord, and then relaunch
nut.
cheers,
Arnaud
--
Linux / Unix Expert RD - Eaton - http://www.eaton.com/mgeops
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://www.debian.org
Free Software Developer
guys,
2010/3/9 Chuck Short:
Unfortunately it hasnt been tested by me. I rather get Arnaud's thoughts
on this.
I've not been able to do much testing on DK-p and none UPower.
what I can say for the DK-p side (which theoretically should be
applicable to UPower) is:
- if a USB UPS is plugged,
guys,
2010/3/9 Chuck Short:
Unfortunately it hasnt been tested by me. I rather get Arnaud's thoughts
on this.
I've not been able to do much testing on DK-p and none UPower.
what I can say for the DK-p side (which theoretically should be
applicable to UPower) is:
- if a USB UPS is plugged,
Hey Björn,
2009/10/26 Björn Torkelsson:
I extracted the megatec_usb and blazer_usb from the 2.4.1-3ubuntu2 and
tried them using the method in comment 5. No sucess though.
** Attachment added: Test with the Blazer driver from karmic
(2.4.1-3ubuntu2)
Hey Björn,
2009/10/26 Björn Torkelsson:
I extracted the megatec_usb and blazer_usb from the 2.4.1-3ubuntu2 and
tried them using the method in comment 5. No sucess though.
** Attachment added: Test with the Blazer driver from karmic
(2.4.1-3ubuntu2)
Hi Björn,
2009/10/9 Björn Torkelsson
Public bug reported:
Binary package hint: nut
I have recently upgraded from hardy to intrepid to jaunty. After
upgrading to Intrepid the megatec_usb stopped recognizing my Trust PW-
4130M ups, it still does not work on Jaunty. It worked without any
101 - 200 of 427 matches
Mail list logo
