This bug was fixed in the package nut - 2.6.0-1ubuntu3
---
nut (2.6.0-1ubuntu3) natty; urgency=low
* debian/patches/backport-fix-lp753661.patch: Backport fix
to trim extraneous end-of-line, in buggy HID string tables,
which results in upsc breaking the communication pipe.
Yeah, upsmon working fine. I was checked it now by unplug power cable.
upsmon was generate alerts "UPS powercom@localhost on battery" and "UPS
powercom@localhost on line power" after plug cable back.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is su
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
It`s working great! Many thanks!
--
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-
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.
>
yes, it 100 % reproducible.
i am ready to test svn version.
--
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-serv
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
I was done:
$ for command in battery.charge battery.charge.low battery.charge.warning
battery
.date battery.runtime battery.type device.mfr device.model device.serial
device.type driver.name dr
iver.parameter.pollfreq driver.parameter.pollinterval driver.parameter.port
driver.parameter.produc
ti
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
$ upsc battery.type
Error: Unknown UPS
$ upsc ups.status
Error: Unknown UPS
--
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
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
Seems driver respond correctly, but upsd return "Broken pipe" after:
25.768861 write: [destfd=6] [len=35] [VAR powercom battery.type "PbAc
"]
Two lines?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in Ubuntu.
https://bugs.
Attachments not working correctly.
** Attachment added: "All files"
https://bugs.launchpad.net/ubuntu/+source/nut/+bug/753661/+attachment/2047202/+files/files.tar
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in Ubuntu.
http
lsusb
--
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.co
Files #3
--
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
Files #2
** Attachment added: "upsd -DDD"
https://bugs.launchpad.net/ubuntu/+source/nut/+bug/753661/+attachment/2047194/+files/upsd.txt
--
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/
Files
--
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.co
17 matches
Mail list logo
