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
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.
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
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
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.
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.
$ 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
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
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
--
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
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
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
productid = 0004
desc = My UPS
but
12 matches
Mail list logo
