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 requests works, while getting the whole tree fails... the only way to ensure this is the root cause is to fix the function that retrieve strings from the device's indexed table, to trim EOL, and check if it solves your issue. would you be ready to test a fix using subversion? cheers, Arno -- 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 [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
