From owner-freebsd-questions@freebsd.org  Tue Apr 18 13:17:22 2017
Return-Path: <owner-freebsd-questions@freebsd.org>
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 7D133D43467;
 Tue, 18 Apr 2017 13:17:22 +0000 (UTC) (envelope-from lists@opsec.eu)
Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 464B71D10;
 Tue, 18 Apr 2017 13:17:22 +0000 (UTC) (envelope-from lists@opsec.eu)
Received: from pi by home.opsec.eu with local (Exim 4.87 (FreeBSD))
 (envelope-from <lists@opsec.eu>)
 id 1d0SKu-000Bkm-6Q; Tue, 18 Apr 2017 14:34:24 +0200
Date: Tue, 18 Apr 2017 14:34:24 +0200
From: Kurt Jaeger <lists@opsec.eu>
To: tech-lists <tech-lists@zyxst.net>
Cc: freebsd-stable@freebsd.org, freebsd-questions@freebsd.org
Subject: Re: 10.3-stable random server reboots - finding the reason
Message-ID: <20170418123424.GD74780@home.opsec.eu>
References: <a7f787f8-486f-8221-ef8a-4535c4e1ae0c@zyxst.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <a7f787f8-486f-8221-ef8a-4535c4e1ae0c@zyxst.net>
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions/>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Apr 2017 13:17:22 -0000

> 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?

Do you have a serial port on that server ? Use it as a console port:

1)
    echo '-Dh -S115200' > /boot.config
2)
    vi /boot/loader.conf
------------
console="comconsole"
comconsole_speed=115200
------------

Then: connect it to some kermit session from a different box,
and write a session log. This might capture some last gasp.

-- 
pi@opsec.eu            +49 171 3101372                         3 years to go !