From owner-freebsd-questions@freebsd.org Fri Aug 12 14:24:11 2016 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 EE8FCBB756B for ; Fri, 12 Aug 2016 14:24:11 +0000 (UTC) (envelope-from robert@webtent.org) Received: from mx2.webtent.net (mx2.webtent.net [216.139.202.4]) by mx1.freebsd.org (Postfix) with ESMTP id CD47711AF for ; Fri, 12 Aug 2016 14:24:11 +0000 (UTC) (envelope-from robert@webtent.org) Received: from localhost (localhost [127.0.0.1]) by mx2.webtent.net (WebTent ESMTP Postfix Internet Mail Exchange) with ESMTP id 83F08D7D42 for ; Fri, 12 Aug 2016 10:17:02 -0400 (EDT) Received: from mx2.webtent.net ([127.0.0.1]) by localhost (mx2.webtent.net [127.0.0.1]) (maiad, port 10024) with ESMTP id 44570-01 for ; Fri, 12 Aug 2016 10:17:02 -0400 (EDT) Received: from [192.168.1.105] (unknown [96.254.71.164]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: robert@mx2.webtent.net) by mx2.webtent.net (WebTent ESMTP Postfix Internet Mail Exchange) with ESMTPSA id 2DB8FD7D1F for ; Fri, 12 Aug 2016 10:17:02 -0400 (EDT) Message-ID: <57ADDA5F.4000405@webtent.org> Date: Fri, 12 Aug 2016 10:17:03 -0400 From: Robert Fitzpatrick User-Agent: Postbox 4.0.8 (Windows/20151105) MIME-Version: 1.0 To: FreeBSD Subject: Monitoring server for crashes Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: WebTent Mailguard 1.0.3 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Aug 2016 14:24:12 -0000 We have a FreeBSD 10 server that keeps crashing every night. I have dumpdev set to AUTO in rc.conf, but I get nothing in the /var/crash folder, I don't have dumpdir defined. The messages log just cuts off with no evidence of kernel panic. Perhaps it is a memory or power issue, how can I monitor for the cause? -- Robert