From owner-freebsd-questions@FreeBSD.ORG Mon Dec 2 20:40:15 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 84251AE5 for ; Mon, 2 Dec 2013 20:40:15 +0000 (UTC) Received: from know-smtprelay-omc-10.server.virginmedia.net (know-smtprelay-omc-10.server.virginmedia.net [80.0.253.74]) by mx1.freebsd.org (Postfix) with ESMTP id EB40813D4 for ; Mon, 2 Dec 2013 20:40:14 +0000 (UTC) Received: from amd.asgard.uk ([92.238.71.115]) by know-smtprelay-10-imp with bizsmtp id wkgC1m01f2VE8Jc01kgDKB; Mon, 02 Dec 2013 20:40:13 +0000 X-Originating-IP: [92.238.71.115] X-Spam: 0 X-Authority: v=2.1 cv=Qfbov6rv c=1 sm=1 tr=0 a=kgu37eZCuzjHC/BLjkfnNA==:117 a=kgu37eZCuzjHC/BLjkfnNA==:17 a=mSnCZvPJBnkA:10 a=g8DGSEr-gRIA:10 a=z6OmtuC8ihAA:10 a=8nJEP1OIZ-IA:10 a=U4kjxnpeAAAA:8 a=RIXHdJ6alCwA:10 a=sJkTq2K36ST8_bpfWQ0A:9 a=wPNLvfGTeEIA:10 From: dgmm To: freebsd-questions@freebsd.org Subject: Re: System reboots ~3am during daily periodic 450.status-security run Date: Mon, 2 Dec 2013 20:40:11 +0000 User-Agent: KMail/1.13.7 (FreeBSD/9.1-RELEASE-p7; KDE/4.10.5; amd64; ; ) References: <201312012352.01075.freebsd01@dgmm.net> <20131202071502.a72c0029.freebsd@edvax.de> <529C4213.2010307@sdf.org> In-Reply-To: <529C4213.2010307@sdf.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201312022040.11070.freebsd01@dgmm.net> X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Dec 2013 20:40:15 -0000 On Monday 02 December 2013 08:17:23 cary wrote: > Polytropon wrote: > > On Mon, 2 Dec 2013 00:27:18 +0000, dgmm wrote: > >> On Sunday 01 December 2013 23:52:00 dgmm wrote: > >>> My system reboots at 3am when /etc/periodic/daily/450.status-security > >> > >> I've now narrowed it down to: > >> > >> /etc/periodic/security/100.chksetuid > >> > >> ...but have no idea why it might a catastophic crash/reboot. > > > > A wild guess: File system damage side effect that is being > > triggered by something "non-obvious". To make sure this is > > _not_ the case, reboot into SUM or via live media and perform > > a forced (!) file system check. Note that just in case you > > might think "but I run background fsck and preen, that should > > be sufficient" - it's not; there are few things that only a > > full, _normal_ file system check can detect and repair. > > > > I'm mentioning this because similar situations have been > > discussed on this list, and finally there was some strange > > file system defect responsible... > > > > But also make sure system power is good, and the system does > > not become unstable when on load. > > Had a 3 a.m. reboot last week. > /usr was corrupted because of my own > errors made while compiling ports. > > $ fsck -t ufs -fv /dev/{usr-partition} Thanks both of you. I now know why the phrase "blindingly obvious" was coined. fsck found an error on / and another on /home. (Yes,I followed the advice in the handbook to not go with seperate /usr and /var. I think if I ever rebuild from scratch I'll go back to the old way.) I've manually run /etc/periodic/security/100.chksetuid twice without incident. This does bring to mind something I'd not previously thought of. Except for the rare times I leave a job running overnight, periodic never runs. I'll have a to make a decision on what to do about that. I have a coupleof options in mind, all of which have ups and downs. -- Dave