> Ok, some more details. It reboots shortly after starting wd_keepalive, > early in the boot sequence. Maybe it is failing to keep up because of > all the disk activity during boot?
Maybe. The default is that the device has to be triggered once a minute which seems like quite a lot of time for a program to not being scheduled at all. > After booting single-user, I was able to both start and stop watchdog > without any issues. > > > Could you please try with verbose on and send me the log entries? > > The "-v" option in /etc/default/watchdog did not produce any output. > Maybe it was too early in the boot sequence? Sorry, my bad, should have explained better. wd_keepalive does not react on most options. To get more information you have to start watchdog itself. The only reason for it to start late is that it can be used to monitor server processes. Unless you use this you can start it very early, at about the time wd_keepalive is started. Once the real daemon is running (and syslog) we get significantly more information in the logs. Michael -- Michael Meskes Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org ICQ: 179140304, AIM/Yahoo/Skype: michaelmeskes, Jabber: [email protected] VfL Borussia! Forca Barca! Go SF 49ers! Use: Debian GNU/Linux, PostgreSQL -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
