From owner-freebsd-questions@FreeBSD.ORG Mon Dec 2 06:15:26 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 269FB371 for ; Mon, 2 Dec 2013 06:15:26 +0000 (UTC) Received: from mx01.qsc.de (mx01.qsc.de [213.148.129.14]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id DC878146E for ; Mon, 2 Dec 2013 06:15:25 +0000 (UTC) Received: from r56.edvax.de (port-92-195-106-241.dynamic.qsc.de [92.195.106.241]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx01.qsc.de (Postfix) with ESMTPS id 592393DD31; Mon, 2 Dec 2013 07:15:17 +0100 (CET) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id rB26F2F0001970; Mon, 2 Dec 2013 07:15:02 +0100 (CET) (envelope-from freebsd@edvax.de) Date: Mon, 2 Dec 2013 07:15:02 +0100 From: Polytropon To: dgmm Subject: Re: System reboots ~3am during daily periodic 450.status-security run Message-Id: <20131202071502.a72c0029.freebsd@edvax.de> In-Reply-To: <201312020027.18293.freebsd01@dgmm.net> References: <201312012352.01075.freebsd01@dgmm.net> <201312020027.18293.freebsd01@dgmm.net> Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list Reply-To: Polytropon List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Dec 2013 06:15:26 -0000 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. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...