Hi fellows,
It's always true that I'm more focused on upstream these years, than on
Debian an Ubuntu.
I'll try to make a summary to explain the what and how on this nut-scanner
feature, on the Debian ticket
cheers
Arno
--
Eaton Data Center Automation Solutions - Opensource Leader -
http://42ity.
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 -
Logged upstream, fixed and due with the next 2.7.3 release:
https://github.com/networkupstools/nut/issues/140
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1099947
Title:
driver unable to connect to
** 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 a
Status: Confirmed => Fix Released
** Changed in: nut (Ubuntu)
Assignee: (unassigned) => Arnaud Quette (aquette)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1197878
Title:
SNMPv3 not
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 bu
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 wi
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 fixed with the next sync with Debian (nut-2.6.3-2 or
better, nut 2.6.4-1)
-- Arnaud
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/920844
Title:
nut-client is missing /etc/init.d/ups-mo
ll 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
2012/6/9 Dmitry Andreychuk <915...@bugs.launchpad.net>
> I'll test it next week, as soon as i get to the hardware.
>
great, thanks.
cheers,
-- Arnaud
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/91
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 receive
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 me
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
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
he 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
ched 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
> wrote:
> > Hi Robert and Dmitry,
> >
> > I'm crossing
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
** 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/
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 notific
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 a
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
---
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
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 poi
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
** 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 a
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 de
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-
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 l
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 mem
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 bec
Hi Martin,
I'm adding the nut users list, since other may be interested in.
2011/12/16 Martin Ewing
> 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
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 subs
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 notifi
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
2011/12/6 Fabio M. Di Nitto
> On 12/6/2011 4:05 PM, Arnaud Quette wrote:
> > Hi Fabio,
> >
> > 2011/12/6 Fabio M. Di Nitto :
> >> On 12/6/2011 2:27 PM, Arnaud Quette wrote:
> >>> Hi Cluster-devel list,
> >>>
> >>> You will fin
Hi Fabio,
2011/12/6 Fabio M. Di Nitto :
> 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
>> fe
** 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 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
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
u
Hey Andres and all,
2011/11/23 Andres Rodriguez :
> All,
>
> I'll update fence-agents once the debian maintainer takes the Ubuntu
> packaging changes into the debian packages.
take it easy Andres, you seem to be a little angry on this ;)
from an upstream and DD point of view:
- FA Debian maintai
Hi Pavel,
2011/10/4 Павел Гуменюк :
> 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_0D9F&PID_0004&REV_0001).
> I had tryed all options with such config:
>
> PWCOM]
> driver = usbhid-ups
>
2011/9/15 Tuomas Heino
> 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 "
hey Laurent,
2011/9/14 Laurent Bigonville
> > 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
2011/9/2 Dmitriy Altuhov
> 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
Hi Dmitriy,
2011/9/2 Dmitriy Altuhov
> 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 unprivil
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
moreover, it's part of the ServerOneiricInfraPower blueprint:
https://blueprints.launchpad.net/ubuntu/+spec/server-o-infra-power
cheers,
Arnaud
--
Linux / Unix Expert R&D - Eaton - http://powerquality.eaton.com
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Develo
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 ad
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
> @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 seri
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
2011/7/13 Martin Ewing
> 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 sh
Hi Martin,
2011/6/27 Martin Ewing
> 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
> Automatic
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 notifica
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 R&D - Eaton - http://powerquality.eaton.com
Network UPS Tools (NUT) Proje
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
generall
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 \
--libd
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
compilatio
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 ]
> •[x4
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 stan
2011/4/21 Michal Soltys
> 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 g
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
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/ch
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.
>
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 req
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
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 ther
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/
Salut Fabrice
2011/3/27 Fabrice Coutadeur
> 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/f
2011/2/15 Lupe Christoph
> On Monday, 2011-02-14 at 21:54:20 -0000, 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
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
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
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 pro
2011/1/10 Laurent Bigonville
> I've found the issue.
>
> Actually the nut_check_*.m4 are setting *_LDFLAGS instead of *_LIBS, and
> due to a toolchain change this become visible (gcc -o testusb testusb.c
> -lusb is working but gcc -o testusb -lusb testusb.c is not working
> anymore)
>
> Any reaso
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, pleas
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 h
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 b
Hi Michael,
thanks for your feedback! I'm cc'ing the NUT users list for info.
I've also added an entry for your device (Powerwalker Line Interactive VI
1400, using blazer_usb).
Can you please send back an upsc output, and at least check for the shutdown
behavior, if not already done:
http://new.n
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
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/26 Wolfgang Lubowski
> I still get the same outputs with NUT-Monitor.
> my nut.conf looks now the following:
> MODE=standalone
>
> ps -efl | grep mge-utalk:
> 0 S root 2066 2002 0 80 0 - 1907 pipe_w 08:37 pts/000:00:00
> grep --color=auto mge-utalk
>
> upsc mgeups:
> Error:
2010/7/23 Wolfgang Lubowski
> this is the output for upsc mgeups:
> device.mfr: MGE UPS SYSTEMS
> device.model: Pulsar ES8+
> device.type: ups
> driver.name: mge-utalk
> driver.parameter.pollinterval: 2
> driver.parameter.port: /dev/ttyS0
> driver.version: 2.4.3
> driver.version.internal: 0.89
>
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 se
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:
> Trace
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 recent
guys,
I'd be interested in a driver debug output, ie:
$ export USB_DEBUG=3
$ /lib/nut/megatec_usb -D -a
let it run for a couple of minutes, then break it (using Ctrl+C) and send
back the trace.
cheers,
Arnaud
--
Linux / Unix Expert R&D - Eaton - http://www.eaton.com/mgeops
Network UPS Tool
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 notific
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 re
Hi Thierry,
2010/6/24 Thierry Carrez
> Public bug reported:
>
> Binary package hint: pwrkap
>
> pwrkap depends on python-matplotlib, which depends on graphical
> libraries. This pulls unnecessary slack on servers where pwrkap would be
> installed.
>
> It looks like only pwrkap-gui would need to
2010/5/3 Chuck Short
> Statement of Impact:
>
> nut in lucid was shipped with a bug that prevented some UPSes from
> connecting to the nut daemon. Checking google fedora was also affected
> by the same problem and has the same patch that we used.
>
> Explanation:
>
> This bug has been fixed by th
please try to unplug and plug back your UPS's USB cord, and then relaunch
nut.
cheers,
Arnaud
--
Linux / Unix Expert R&D - 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, DK
Hey Björn,
2009/10/26 Björn Torkelsson:
> I extracted the megatec_usb and blazer_usb from the 2.4.1-3ubuntu2 and
> tried them using the method in comment 5. No sucess though.
>
> ** Attachment added: "Test with the Blazer driver from karmic
> (2.4.1-3ubuntu2)"
> http://launchpadlibrarian.net/34
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 a
Expert R&D - Eaton - http://www.eaton.com/mgeops
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.free.fr/
** Changed in: nut (Ubuntu)
Status: New => Invalid
** Changed in:
hey Martin,
2009/8/26 Martin Pitt
> Any updates on this?
>
the current situation is that pm 2.3.5 is available (2.3.3 is both debian
and ubuntu), with the above mentioned fixes.
according to Jim's comment, the .dev files are really conffiles, so the
lintian override is to be removed.
now, I'm
2009/8/31 ilna
> Public bug reported:
>
> Binary package hint: nut
>
> Up to date Kubuntu Karmic is in use.
>
> Recently I have tried to install nut and faced with these problems:
>
> 1. hal starts 'hald-addon-hid-ups' process which is not compatible with
> nut. To prevent the starting I have add
hey there,
just to clarify the situation here... a bit
2009/6/16 Coljep
> Public bug reported:
>
> Binary package hint: nut
>
> I have been trying to install the MGE UPS-psp package. It worked with a
> previous Ubuntu installation, 8.04 but would not install in my new computer
> with 9.04 64bit
1 - 100 of 255 matches
Mail list logo
