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 - R&D 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]
