> Could you please check whether watchdog is really running and whether > wd_keepalive was really stopped? Yes, only watchdog is running. debian:~# ps -ef | grep watch root 2846 1 0 12:35 ? 00:00:00 /usr/sbin/watchdog root 2952 2846 0 12:43 ? 00:00:00 [watchdog] root 2954 2895 0 12:43 pts/0 00:00:00 grep watch debian:~#
debian:~# ps -ef | grep wd_keepalive root 2962 2895 0 12:44 pts/0 00:00:00 grep wd_keepalive debian:~# >If you happen to have a system without either > one running you could try getting more info by replacing "--quiet" with > "--verbose" in the start-stop-daemon calls in /etc/init.d/watchdog. There also > should be more information in the corrsponfing syslog file. I enabled the "--verbose" option and here is what I get in syslog upon system starts: Mar 4 12:45:19 debian watchdog[2846]: stopping daemon (5.4) Mar 4 12:45:19 debian wd_keepalive[3004]: starting watchdog keepalive daemon (5.4): int=10 alive=(null) realtime=yes Mar 4 12:45:19 debian wd_keepalive[3004]: stopping watchdog keepalive daemon (5.4) Mar 4 12:46:22 debian watchdog[2850]: starting daemon (5.4): Mar 4 12:46:22 debian watchdog[2850]: int=10s realtime=yes sync=no soft=no mla=0 mem=0 Mar 4 12:46:22 debian watchdog[2850]: ping: 192.168.0.101 Mar 4 12:46:22 debian watchdog[2850]: file: no file to check Mar 4 12:46:22 debian watchdog[2850]: pidfile: no server process to check Mar 4 12:46:22 debian watchdog[2850]: interface: no interface to check Mar 4 12:46:22 debian watchdog[2850]: test=none(0) repair=none alive=none heartbeat=none temp=none to=root no_act=no Mar 4 12:47:10 debian watchdog[2850]: stopping daemon (5.4) Mar 4 12:47:10 debian wd_keepalive[2925]: starting watchdog keepalive daemon (5.4): int=10 alive=(null) realtime=yes Mar 4 12:47:10 debian wd_keepalive[2925]: stopping watchdog keepalive daemon (5.4) Mar 4 12:48:10 debian watchdog[2855]: starting daemon (5.4): Mar 4 12:48:10 debian watchdog[2855]: int=10s realtime=yes sync=no soft=no mla=0 mem=0 Mar 4 12:48:10 debian watchdog[2855]: ping: 192.168.0.101 Mar 4 12:48:10 debian watchdog[2855]: file: no file to check Mar 4 12:48:10 debian watchdog[2855]: pidfile: no server process to check Mar 4 12:48:10 debian watchdog[2855]: interface: no interface to check Mar 4 12:48:10 debian watchdog[2855]: test=none(0) repair=none alive=none heartbeat=none temp=none to=root no_act=no And here is the syslog output on Debian Etch: Mar 4 12:46:18 debian watchdog[2706]: stopping daemon (5.2) Mar 4 12:47:17 debian watchdog[2708]: starting daemon (5.2): Mar 4 12:47:17 debian watchdog[2708]: int=10s realtime=yes sync=no soft=no mla=3 mem=0 Mar 4 12:47:17 debian watchdog[2708]: ping: 192.168.0.101 Mar 4 12:47:17 debian watchdog[2708]: file: no file to check Mar 4 12:47:17 debian watchdog[2708]: pidfile: no server process to check Mar 4 12:47:17 debian watchdog[2708]: interface: no interface to check Mar 4 12:47:17 debian watchdog[2708]: test=none(0) repair=none alive=none heartbeat=none temp=none to=root no_act=no Mar 4 12:47:54 debian watchdog[2708]: stopping daemon (5.2) Mar 4 12:48:54 debian watchdog[2705]: starting daemon (5.2): Mar 4 12:48:54 debian watchdog[2705]: int=10s realtime=yes sync=no soft=no mla=3 mem=0 Mar 4 12:48:54 debian watchdog[2705]: ping: 192.168.0.101 Mar 4 12:48:54 debian watchdog[2705]: file: no file to check Mar 4 12:48:54 debian watchdog[2705]: pidfile: no server process to check Mar 4 12:48:54 debian watchdog[2705]: interface: no interface to check Mar 4 12:48:54 debian watchdog[2705]: test=none(0) repair=none alive=none heartbeat=none temp=none to=root no_act=no Also I installed the watchdog package from Etch on my Lenny system, and it seems to works well. As soon as I upgrade to Lenny's watchdog package, it fails to function as mentioned initially. Please let me know if you need more information. Kushal Koolwal I do blog at http://blogs.koolwal.net/ _________________________________________________________________ Windows Live™ Contacts: Organize your contact list. http://windowslive.com/connect/post/marcusatmicrosoft.spaces.live.com-Blog-cns!503D1D86EBB2B53C!2285.entry?ocid=TXT_TAGLM_WL_UGC_Contacts_032009 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
