From owner-freebsd-stable@FreeBSD.ORG Mon Sep 4 09:16:43 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9DD6C16A4DD for ; Mon, 4 Sep 2006 09:16:43 +0000 (UTC) (envelope-from stb@lassitu.de) Received: from koef.zs64.net (koef.zs64.net [212.12.50.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id 099D143D46 for ; Mon, 4 Sep 2006 09:16:42 +0000 (GMT) (envelope-from stb@lassitu.de) Received: (from stb@koef.zs64.net) (authenticated) by koef.zs64.net (8.13.8/8.13.8) with ESMTP id k849GSxZ000665 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO); Mon, 4 Sep 2006 11:16:30 +0200 (CEST) (envelope-from stb@lassitu.de) In-Reply-To: <00f701c6ce1a$9d9ea810$6508280a@tocnet28.jspoj.czf> References: <00f701c6ce1a$9d9ea810$6508280a@tocnet28.jspoj.czf> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=UTF-8; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: quoted-printable From: Stefan Bethke Date: Mon, 4 Sep 2006 11:16:41 +0200 To: dandee@volny.cz X-Mailer: Apple Mail (2.752.2) Cc: freebsd-stable@freebsd.org Subject: Re: watchdogd_flags followed by panic watchdog timeout, after reboot my rc.conf disappear X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Sep 2006 09:16:43 -0000 =1B[ Please do not crosspost. ] Am 02.09.2006 um 01:01 schrieb Daniel Dvo=C5=99=C3=A1k: > In the /etc/defaults/rc.conf there are not "watchdogd_flags=3D""" =20 > option, but > I tried to wrote it to my /etc/rc.conf in this way: > > watchdogd_enable=3D"YES" > watchdogd_flags=3D"-e ping 10.40.0.72 -s 2 -t 1" You probably would have wanted "-e 'ping 10.40.0.72 -s2 -t1'". =20 Without the single quotes, the command is just ping, which will exit =20 with 64 (EX_USAGE), so the command never completes successfully, and =20 the kernel watchdog timer is never reset. Hence the watchdog timeout. It's a bug in watchdogd that it does not complain about the extra =20 arguments. > I saved my rc.conf without any doubt. > > I did so, because I wanted to instruct watchdogd to execute my =20 > command, > common pinging some IP address. I was not satisfied with a trivial =20 > file > system check instead. > > After saving the rc.conf file, I restarted watchdogd deamon at once. > > ... and ... 2 seconds ... my ssh client was disconnected ... =20 > unexpected end > of ssh session. :) Most likely, the rc.conf changes had not been committed to disk when =20 the watchdog timeout occurred, so they got lost. The watchdog facility is meant to recover the machine from serious =20 problems (like deadlocks, livelocks, or similar). As such, it will =20 not do a proper shutdown, since the machine is probably in a state =20 where the shutdown would also hang. It's a last-ditch effort to get =20 the machine to be responsible again, even if there might be damage =20 due to the sudden panic/reboot. If you want to reboot your router when network connectivity is =20 problematic, I'd set up a cron job to run ping and invoke shutdown -r =20= if it fails instead. Stefan --=20 Stefan Bethke Fon +49 170 346 0140