[Voyage-linux] Watchdog Not Rebooting.
Robert Rawlins - Think Blue
(spam-protected)
Fri Jun 5 02:54:49 HKT 2009
Hello Guys,
I've got a voyage 0.6.0 build running on an ALIX board, today I replace the
CF card after we had a data corruption issue. I tested this card in other
ALIX systems earlier this week and the watchdog appeared to work great! I
also know than this current board with the old CF card also had a working
watchdog.
All I can tell you at the moment is that the daemon is logging to
/var/log/syslog like so:
Jun 4 18:48:22 voyage watchdog[3188]: still alive after 36 interval(s)
Jun 4 18:48:22 voyage watchdog[3188]: was able to ping process 3130
(/var/run/obex-data-server.pid).
Jun 4 18:48:22 voyage watchdog[3188]: was able to ping process 3162
(/var/run/thinkblue.pid).
Jun 4 18:48:22 voyage watchdog[3188]: was able to ping process 2911
(/var/run/dbus/pid).
Jun 4 18:48:22 voyage watchdog[3188]: was able to ping process 3011
(/var/run/mysqld/mysqld.pid).
Now, say I kill one of these processes, I then get a log entry like so:
Jun 4 18:49:52 voyage watchdog[3188]: still alive after 45 interval(s)
Jun 4 18:49:52 voyage watchdog[3188]: was able to ping process 3130
(/var/run/obex-data-server.pid).
Jun 4 18:49:52 voyage watchdog[3188]: cannot open /var/run/thinkblue.pid
(errno = 2 = 'No such file or directory')
I then get no further log entries from the watchdog, however the system does
not reboot!
Can someone help me diagnose and solve the issue? I'd really appreciate that
J Like I say I know for sure that:
A) The ALIX board is functional, it was working on the old CF card.
B) My /etc/watchdog.conf is just fine, it's the same config I use on
other systems.
C) My /init.d/watchdog is just fine, this has only been modified to
have '-v' to log the output.
Thanks chaps,
Rob
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.voyage.hk/pipermail/voyage-linux/attachments/20090604/cc585bcd/attachment-0001.html>
More information about the Voyage-linux
mailing list