From owner-freebsd-questions@freebsd.org Tue Apr 18 13:19:15 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 05F29D4368F; Tue, 18 Apr 2017 13:19:15 +0000 (UTC) (envelope-from bah@bananmonarki.se) Received: from feeder.usenet4all.se (1-1-1-38a.far.sth.bostream.se [82.182.32.53]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6D1001F87; Tue, 18 Apr 2017 13:19:13 +0000 (UTC) (envelope-from bah@bananmonarki.se) Received: from testbox.news4all.se (testbox.usenet4all.se [10.0.0.3]) by feeder.usenet4all.se (8.13.1/8.13.1) with ESMTP id v3ICLr3n002445; Tue, 18 Apr 2017 14:21:53 +0200 (CEST) (envelope-from bah@bananmonarki.se) Subject: Re: 10.3-stable random server reboots - finding the reason To: tech-lists , freebsd-stable@freebsd.org References: Cc: freebsd-questions@freebsd.org From: Bernt Hansson Message-ID: Date: Tue, 18 Apr 2017 14:21:53 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Apr 2017 13:19:15 -0000 On 2017-04-18 13:59, tech-lists wrote: > Hello stable@ > > I have an up-to-date 10.3 server that is randomly rebooting, after being > up for days. Previously it had been up for many months. The problem is, > nothing seems to be left in the logs to indicate why it's doing this. I > have all.log and console.log enabled. > > So, what I'm asking is, how can I capture its last gasp? > > many thanks, That sounds very much like a hardware issue. Capacitors, memory is what i would check. Those errors won't be logged.