From owner-freebsd-hackers@FreeBSD.ORG  Wed Oct  2 00:25:45 2013
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@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 ESMTP id 61C70E8D
 for <freebsd-hackers@freebsd.org>; Wed,  2 Oct 2013 00:25:45 +0000 (UTC)
 (envelope-from michael.schuh@gmail.com)
Received: from mail-oa0-x236.google.com (mail-oa0-x236.google.com
 [IPv6:2607:f8b0:4003:c02::236])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 2EDB226A7
 for <freebsd-hackers@freebsd.org>; Wed,  2 Oct 2013 00:25:45 +0000 (UTC)
Received: by mail-oa0-f54.google.com with SMTP id n5so101365oag.41
 for <freebsd-hackers@freebsd.org>; Tue, 01 Oct 2013 17:25:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:date:message-id:subject:from:to:content-type;
 bh=qU/zgGne/HDTRXdWRQjzOTzdB3n8QXCQNik9McrfA/o=;
 b=DI+eYeARcYRORH8EYrWuLcZLtUXNDR767vL8pIN+WPs27Dt4XNeY/wZuhiZFPJSJXR
 PFgrIKpaAwbm/1EJac48Qa7aGFzH+DLaaEuhxDT6b4Cv3sCMAuLlT/SuZ345Cj8WbTD5
 DnNuR7DKUWe1GiDqrSSoVUp52TyhCvitqbmqE8QjtJFY3MnDtGIE35SAJdH1Yh9sXYPF
 rB4ZUtU+O5I25axPYSzqBO9zZjGbmBBhbrLsxYxUHihBvSFV3NwEaBDgVou5RVhnQghx
 KjM5XwB8g3QabSfIT4bNJFS0Ts5wf5b5TkCNF4bFcDmEvjmpS/dVswcUnCufWCQpG2Sg
 IrFw==
MIME-Version: 1.0
X-Received: by 10.60.70.134 with SMTP id m6mr30030490oeu.14.1380673544087;
 Tue, 01 Oct 2013 17:25:44 -0700 (PDT)
Received: by 10.60.52.7 with HTTP; Tue, 1 Oct 2013 17:25:44 -0700 (PDT)
Date: Wed, 2 Oct 2013 02:25:44 +0200
Message-ID: <CADwRVEazS+CSHAebGnuiNSzOxAS7ErmWZKb9SY4VEgQN7fVGcA@mail.gmail.com>
Subject: Re: cause of reboot
From: Michael Schuh <michael.schuh@gmail.com>
To: freebsd-hackers@freebsd.org
Content-Type: text/plain; charset=ISO-8859-1
X-Content-Filtered-By: Mailman/MimeDel 2.1.14
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
 <freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-hackers>, 
 <mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
 <mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Oct 2013 00:25:45 -0000

> Please help I need to find cause of reboot..
>
>
>
i would recommend the reconfigure of syslog too.

attention on "all.log" and/or "console.log"
there are examples with explanations

not all console messages flow into messages. ;-)

memory test,
disk tests
cpu temperature, i had exactly the same error caused by an
defective cpu-cooler. cpu got hot during the nightly periodc scripts and
silently rebooted.

watch the time of the reboot and compare it to the cron/periodic scripts.
determine whats running at the time of the reboot.

hth