[Voyage-linux] Broken watchdog?

[Robert Rawlins]

Hi Dario,

 

Thanks for the reply on this. I’m glad you can confirm that it’s not my
watchdog.conf which is causing the problem. The watchdog script
(/etc/default/watchdog) on my box looks like this:

 

# Start watchdog at boot time? 0 or 1

run_watchdog=1

#

# Specify additional watchdog options here (see manpage).

 

Does that seem normal to you? Also, as a little additional information, the
syslog entry when the box first starts up for watchdog looks like this:

 

Sep 15 12:03:56 voyage watchdog[3290]: starting daemon (5.2):

Sep 15 12:03:56 voyage watchdog[3290]: int=15s realtime=yes sync=no soft=no
mla=0 mem=0

Sep 15 12:03:56 voyage watchdog[3290]: ping: no machine to check

Sep 15 12:03:56 voyage watchdog[3290]: file: no file to check

Sep 15 12:03:56 voyage watchdog[3290]: pidfile: /var/run/myapp.pid

Sep 15 12:03:56 voyage watchdog[3290]: interface: no interface to check

Sep 15 12:03:56 voyage watchdog[3290]: test=none(0) repair=none
alive=/dev/watchdog heartbeat=none temp=none to=root no_act=no

Sep 15 12:03:56 voyage watchdog[3290]: was able to ping process 3249
(/var/run/myapp.pid).

 

Again, is this what you would expect to see on a normal system
configuration?

 

Many thanks,

 

Robert

 

From: Dario Finardi [mailto:d.finardi at gear.it] 
Sent: 15 September 2008 09:04
To: Robert Rawlins
Subject: R: [Voyage-linux] Broken watchdog?

 

Using such a configuration my boards are working correctly.

 

have you turned-on the watchdog script modifing the status variable
run_watchdog=1?

 

 

  _____  

Da: voyage-linux-bounces+d.finardi=gear.it at list.voyage.hk
[mailto:voyage-linux-bounces+d.finardi=gear.it at list.voyage.hk] Per conto di
Robert Rawlins
Inviato: giovedì 11 settembre 2008 16.03
A: voyage-linux at voyage.hk
Oggetto: RE: [Voyage-linux] Broken watchdog?

Dario,

 

Thanks for your reply to and taking the time help out. Sorry for my late
reply, I’ve had my head buried in code the past couple of days.

 

My watchdog configuration file looks like this:

 

realtime             = yes

priority             = 1

pidfile              = /var/run/myapp.pid

watchdog-device      = /dev/watchdog

interval             = 15

 

That’s all there is too it. In syslog it logs all the checks as I detailed
in my original post but after the process crashes and watchdog cannot find
the process I get no more log entries from watchdog and the system is not
rebooted.

 

Let me know if you need anything else.

 

Thanks,

 

Robert

 

From: Dario Finardi [mailto:d.finardi at gear.it] 
Sent: 10 September 2008 14:32
To: Robert Rawlins; voyage-linux at voyage.hk; voyage-linux at voyage.hk
Subject: R: [Voyage-linux] Broken watchdog?

 

may you post your watchdog configuration?

 

  _____  

Da: voyage-linux-bounces+d.finardi=gear.it at list.voyage.hk
[mailto:voyage-linux-bounces+d.finardi=gear.it at list.voyage.hk] Per conto di
Robert Rawlins
Inviato: mercoledì 10 settembre 2008 12.12
A: voyage-linux at voyage.hk; voyage-linux at voyage.hk
Oggetto: [Voyage-linux] Broken watchdog?

Guys,

 

My watchdog doesn’t appear to be working quite correctly and I’m hoping you
can help me out. I have it watching a process for me to ensure its still
alive and I can see it logging this check in syslog like so:

 

Sep 10 08:50:11 voyage watchdog[3351]: still alive after 5661 interval(s)

Sep 10 08:50:11 voyage watchdog[3351]: was able to ping process 3250
(/var/run/myapp.pid).

Sep 10 08:50:26 voyage watchdog[3351]: still alive after 5662 interval(s)

Sep 10 08:50:26 voyage watchdog[3351]: pinging process 3250
(/var/run/myapp.pid) gave errno = 3 = 'No such process'

 

As you can see, it knows it cannot ping my process as it has crashed, yet
the system doesn’t appear to reboot itself. It just sits there like a dead
duck J

 

I’m sure this was working in the past but cannot be sure. This is using
Voyage 0.5 on an ALIX board.

 

I’d really appreciate some advice on this and how to debug if this is an
issue.

 

Robert

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.voyage.hk/pipermail/voyage-linux/attachments/20080915/6c221a2e/attachment-0001.html>