Bug#385694: nut: Fails to properly start on boot.
On Sat, Aug 04, 2007 at 02:25:18PM +0200, Arnaud Quette wrote: I do understand, and apologize for not having put much effort in this. nevertheless, the UPS communication stalling should not occur on a daily basis (few times a year is a maximum). and the situation has improved since. It seems to be working again now, so far. But I'm just at the point where I'll stop doing daily reboots again, so it might take a while before I see it again. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#385694: nut: Fails to properly start on boot.
2007/8/4, Kurt Roeckx [EMAIL PROTECTED]: On Fri, Aug 03, 2007 at 11:52:43PM +0200, Arnaud Quette wrote: tags 385694 upstream thanks Hi Kurt, Real life finally allow me to get back on bug triaging... any news on that bug on your side? I would really like to hunt this bug if it still exist! I was highly annoyed by it not working and ended up not starting it anymore. I think the problem is with the UPS itself that stops responding, and don't feel like pulling the plug from the ups every day. I do understand, and apologize for not having put much effort in this. nevertheless, the UPS communication stalling should not occur on a daily basis (few times a year is a maximum). and the situation has improved since. I'll try to see if I can get it working again soon. thanks a lot Kurt, and don't hesitate to ping me on my (cc'ed) @mge address. Arnaud -- Free Software Developer - http://arnaud.quette.free.fr/ Debian Developer - http://people.debian.org/~aquette/ Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Ubuntu Media Center (UMC) Project Leader - https://launchpad.net/~umc-team -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#385694: nut: Fails to properly start on boot.
tags 385694 upstream thanks Hi Kurt, Real life finally allow me to get back on bug triaging... any news on that bug on your side? I would really like to hunt this bug if it still exist! Can you report your current situation? Also, have you tried to change the NUT initscript now has a priority to 25? Many upstream and Debian enhancements in NUT 2.2.0 may solve your issue: - NUT initscript now has a priority of 50, which should give more time to udev - the newmge-shut might be worth a try. Though it's still beta. - various changes in both the drivers (*mge-shut) and upsd Finally note that 2.2.0-1 upload in Sid is underway (and overdue) thanks, Arnaud -- Free Software Developer - http://arnaud.quette.free.fr/ Debian Developer - http://people.debian.org/~aquette/ Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Ubuntu Media Center (UMC) Project Leader - https://launchpad.net/~umc-team -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#385694: nut: Fails to properly start on boot.
On Fri, Aug 03, 2007 at 11:52:43PM +0200, Arnaud Quette wrote: tags 385694 upstream thanks Hi Kurt, Real life finally allow me to get back on bug triaging... any news on that bug on your side? I would really like to hunt this bug if it still exist! I was highly annoyed by it not working and ended up not starting it anymore. I think the problem is with the UPS itself that stops responding, and don't feel like pulling the plug from the ups every day. I'll try to see if I can get it working again soon. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#385694: nut: Fails to properly start on boot.
2006/9/5, Arnaud Quette [EMAIL PROTECTED]: 2006/9/4, Kurt Roeckx [EMAIL PROTECTED]: Turning off the UPS and plugging out the power seems to have put it back in it's previous state, I'll look at it again later. right, when the communication get stucks, powering off the ups (power button + unplug the power cable) restore everything. Have you made some tests with the latest 2.0.4? Arnaud -- Linux / Unix Expert - MGE UPS SYSTEMS - RD Dpt Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://people.debian.org/~aquette/ OpenSource Developer - http://arnaud.quette.free.fr/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#385694: nut: Fails to properly start on boot.
On Tue, Jan 16, 2007 at 11:05:57AM +0100, Arnaud Quette wrote: 2006/9/5, Arnaud Quette [EMAIL PROTECTED]: 2006/9/4, Kurt Roeckx [EMAIL PROTECTED]: Turning off the UPS and plugging out the power seems to have put it back in it's previous state, I'll look at it again later. right, when the communication get stucks, powering off the ups (power button + unplug the power cable) restore everything. Have you made some tests with the latest 2.0.4? No, I'm still using 2.0.2-2. I'll try to do that if I have some time. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#385694: nut: Fails to properly start on boot.
2006/9/4, Kurt Roeckx [EMAIL PROTECTED]: On Mon, Sep 04, 2006 at 10:03:22AM +0200, Arnaud Quette wrote: Hi again Kurt, which system are you running (sarge, testing, ...)? This is a sarge system, but I took a slightly newer version from nut then what's in sarge. I seem to be using udev, and I have to wonder why myself, since I don't really like it. still better than hotplug This might be due to several things (serial perms settings, /var dir still offline when nut starts, ...) The nut user is part of the dialout group, so should have permissions to /dev/ttyS0, although I'm not really sure when udev decides to make that. I do have to see that makedev and nut both start at S20, but makedev just before nut. maybe a race cond. moving nut to S25 might be a good test to validate this. /var is on my /, so it shouldn't be a problem, and everything really should be mounted when nut starts. a good thing would be to replace the init.d/nut script redirection from /dev/null to something like /tmp/nut-trace.log and send it back for analysis. A good thing would be that that log in the script was actually used, so you could just change that. :) (Maybe that was fixed in a newer version?) there is something planned about logging improvement and default behavior that should address this Anyway, I've changed it, and I'll see when I need to reboot. I'll let you know. ok, thanks. Arnaud -- Linux / Unix Expert - MGE UPS SYSTEMS - RD Dpt Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://people.debian.org/~aquette/ OpenSource Developer - http://arnaud.quette.free.fr/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#385694: nut: Fails to properly start on boot.
Hi again Kurt, 2006/9/2, Kurt Roeckx [EMAIL PROTECTED]: Package: nut Version: 2.0.2-2 Severity: important Hi, Every time I reboot, nut fails to start proplery. If I then stop nut, and start it again, things work as expected. From the log: Sep 2 07:09:01 intrepid mge-shut[2540]: Startup successful Sep 2 07:09:01 intrepid upsd[2541]: Connected to UPS [myups]: mge-shut-ttyS0 Sep 2 07:09:05 intrepid upsd[2542]: Startup successful Sep 2 07:09:05 intrepid upsmon[2544]: Startup successful Sep 2 07:09:05 intrepid upsd[2542]: Connection from 127.0.0.1 Sep 2 07:09:05 intrepid upsd[2542]: Client [EMAIL PROTECTED] logged into UPS [myups] Sep 2 07:11:16 intrepid upsd[2542]: Data for UPS [myups] is stale - check driver Sep 2 07:11:20 intrepid upsmon[2545]: Poll UPS [EMAIL PROTECTED] failed - Data stale Sep 2 07:11:20 intrepid upsmon[2545]: Communications with UPS [EMAIL PROTECTED] lost Sep 2 07:11:25 intrepid upsmon[2545]: Poll UPS [EMAIL PROTECTED] failed - Data stale Sep 2 07:11:30 intrepid upsmon[2545]: Poll UPS [EMAIL PROTECTED] failed - Data stale Sep 2 07:11:35 intrepid upsmon[2545]: Poll UPS [EMAIL PROTECTED] failed - Data stale Sep 2 07:11:40 intrepid upsmon[2545]: Poll UPS [EMAIL PROTECTED] failed - Data stale Sep 2 07:11:45 intrepid upsmon[2545]: Poll UPS [EMAIL PROTECTED] failed - Data stale Sep 2 07:11:50 intrepid upsmon[2545]: Poll UPS [EMAIL PROTECTED] failed - Data stale Sep 2 07:11:55 intrepid upsmon[2545]: Poll UPS [EMAIL PROTECTED] failed - Data stale Sep 2 07:12:00 intrepid upsmon[2545]: Poll UPS [EMAIL PROTECTED] failed - Data stale Sep 2 07:12:10 intrepid last message repeated 2 times Sep 2 07:12:15 intrepid upsd[2542]: Signal 15: exiting Sep 2 07:12:15 intrepid upsmon[2545]: Signal 15: exiting Sep 2 07:12:15 intrepid upsmon[2544]: upsmon parent: read: Success Sep 2 07:12:26 intrepid mge-shut[2540]: Signal 15: exiting Sep 2 07:13:31 intrepid mge-shut[3092]: Startup successful Sep 2 07:13:31 intrepid upsd[3093]: Connected to UPS [myups]: mge-shut-ttyS0 Sep 2 07:13:35 intrepid upsd[3094]: Startup successful Sep 2 07:13:35 intrepid upsmon[3096]: Startup successful Sep 2 07:13:35 intrepid upsd[3094]: Connection from 127.0.0.1 Sep 2 07:13:35 intrepid upsd[3094]: Client [EMAIL PROTECTED] logged into UPS [myups] At this point things work properly. I have no idea why I need to stop it each time, or why it fails from the boot scripts and works when I start it manually. which system are you running (sarge, testing, ...)? This might be due to several things (serial perms settings, /var dir still offline when nut starts, ...) a good thing would be to replace the init.d/nut script redirection from /dev/null to something like /tmp/nut-trace.log and send it back for analysis. Arnaud -- Linux / Unix Expert - MGE UPS SYSTEMS - RD Dpt Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://people.debian.org/~aquette/ OpenSource Developer - http://arnaud.quette.free.fr/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#385694: nut: Fails to properly start on boot.
On Mon, Sep 04, 2006 at 10:03:22AM +0200, Arnaud Quette wrote: Hi again Kurt, which system are you running (sarge, testing, ...)? This is a sarge system, but I took a slightly newer version from nut then what's in sarge. I seem to be using udev, and I have to wonder why myself, since I don't really like it. This might be due to several things (serial perms settings, /var dir still offline when nut starts, ...) The nut user is part of the dialout group, so should have permissions to /dev/ttyS0, although I'm not really sure when udev decides to make that. I do have to see that makedev and nut both start at S20, but makedev just before nut. /var is on my /, so it shouldn't be a problem, and everything really should be mounted when nut starts. a good thing would be to replace the init.d/nut script redirection from /dev/null to something like /tmp/nut-trace.log and send it back for analysis. A good thing would be that that log in the script was actually used, so you could just change that. :) (Maybe that was fixed in a newer version?) Anyway, I've changed it, and I'll see when I need to reboot. I'll let you know. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#385694: nut: Fails to properly start on boot.
Package: nut Version: 2.0.2-2 Severity: important Hi, Every time I reboot, nut fails to start proplery. If I then stop nut, and start it again, things work as expected. From the log: Sep 2 07:09:01 intrepid mge-shut[2540]: Startup successful Sep 2 07:09:01 intrepid upsd[2541]: Connected to UPS [myups]: mge-shut-ttyS0 Sep 2 07:09:05 intrepid upsd[2542]: Startup successful Sep 2 07:09:05 intrepid upsmon[2544]: Startup successful Sep 2 07:09:05 intrepid upsd[2542]: Connection from 127.0.0.1 Sep 2 07:09:05 intrepid upsd[2542]: Client [EMAIL PROTECTED] logged into UPS [myups] Sep 2 07:11:16 intrepid upsd[2542]: Data for UPS [myups] is stale - check driver Sep 2 07:11:20 intrepid upsmon[2545]: Poll UPS [EMAIL PROTECTED] failed - Data stale Sep 2 07:11:20 intrepid upsmon[2545]: Communications with UPS [EMAIL PROTECTED] lost Sep 2 07:11:25 intrepid upsmon[2545]: Poll UPS [EMAIL PROTECTED] failed - Data stale Sep 2 07:11:30 intrepid upsmon[2545]: Poll UPS [EMAIL PROTECTED] failed - Data stale Sep 2 07:11:35 intrepid upsmon[2545]: Poll UPS [EMAIL PROTECTED] failed - Data stale Sep 2 07:11:40 intrepid upsmon[2545]: Poll UPS [EMAIL PROTECTED] failed - Data stale Sep 2 07:11:45 intrepid upsmon[2545]: Poll UPS [EMAIL PROTECTED] failed - Data stale Sep 2 07:11:50 intrepid upsmon[2545]: Poll UPS [EMAIL PROTECTED] failed - Data stale Sep 2 07:11:55 intrepid upsmon[2545]: Poll UPS [EMAIL PROTECTED] failed - Data stale Sep 2 07:12:00 intrepid upsmon[2545]: Poll UPS [EMAIL PROTECTED] failed - Data stale Sep 2 07:12:10 intrepid last message repeated 2 times Sep 2 07:12:15 intrepid upsd[2542]: Signal 15: exiting Sep 2 07:12:15 intrepid upsmon[2545]: Signal 15: exiting Sep 2 07:12:15 intrepid upsmon[2544]: upsmon parent: read: Success Sep 2 07:12:26 intrepid mge-shut[2540]: Signal 15: exiting Sep 2 07:13:31 intrepid mge-shut[3092]: Startup successful Sep 2 07:13:31 intrepid upsd[3093]: Connected to UPS [myups]: mge-shut-ttyS0 Sep 2 07:13:35 intrepid upsd[3094]: Startup successful Sep 2 07:13:35 intrepid upsmon[3096]: Startup successful Sep 2 07:13:35 intrepid upsd[3094]: Connection from 127.0.0.1 Sep 2 07:13:35 intrepid upsd[3094]: Client [EMAIL PROTECTED] logged into UPS [myups] At this point things work properly. I have no idea why I need to stop it each time, or why it fails from the boot scripts and works when I start it manually. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
