From owner-freebsd-questions@FreeBSD.ORG Mon Sep 30 15:29:10 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 ESMTP id 2C35C4F0; Mon, 30 Sep 2013 15:29:10 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 067532F92; Mon, 30 Sep 2013 15:29:09 +0000 (UTC) Received: from jre-mbp.elischer.org (ppp121-45-245-177.lns20.per2.internode.on.net [121.45.245.177]) (authenticated bits=0) by vps1.elischer.org (8.14.6/8.14.6) with ESMTP id r8UFSt1o050498 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Mon, 30 Sep 2013 08:28:58 -0700 (PDT) (envelope-from julian@freebsd.org) Message-ID: <524998B1.60706@freebsd.org> Date: Mon, 30 Sep 2013 23:28:49 +0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: Jason Hellenthal Subject: Re: cause of reboot References: <519911380551058@web20j.yandex.ru> <96AD54CD-4EA8-46A4-A0C1-36B7E6F0B52E@dataix.net> <80361380553221@web8g.yandex.ru> <21CB70DD-F2F1-43F4-9730-FB12C46317B0@dataix.net> <97A9E80E-15D2-48BA-AD6A-B580157BECAE@dataix.net> In-Reply-To: <97A9E80E-15D2-48BA-AD6A-B580157BECAE@dataix.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-hackers@freebsd.org" , =?UTF-8?B?RW1yZSDDh2FtYWxhbg==?= , FreeBSD quest X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Sep 2013 15:29:10 -0000 On 9/30/13 11:08 PM, Jason Hellenthal wrote: > Also . . . grep -ri . . . > > > > On Sep 30, 2013, at 11:06, Jason Hellenthal wrote: > > And /etc/ ? > And /var/cron ? > > > > On Sep 30, 2013, at 11:00, Emre Çamalan wrote: > > Yes I checked also it , such as ; > "grep -i 'reboot' /root/scripts/* -R" > "grep -i 'halt' /root/scripts/* -R" > "grep -i 'shutdown' /root/scripts/* -R" > > > 30.09.2013, 17:33, "Jason Hellenthal" : >> Did you check for the command reboot in all of the periodic scripts and cron jobs as well as the command shutdown ? >> >> On Sep 30, 2013, at 10:24, Emre Çamalan wrote: >> >> Hi, >> my server reboots every night and same o'clock last 10 days. But this machine's uptime was 96days. >> >> Suddenly reboot this machine and now this continue every night again and again. >> >> I didn't find any reason and I didn't change anything else. >> >> I looked "last" command, >> reboot ~ ~ AM 03.15 ~ >> >> I checked "dmesg -a" , it has only generic things no other things. >> >> I checked "/var/log/messages" >> >> I wrote script and checked swapinfo , cpu and memory but all of them was normal before reboot. >> >> I checked crontab and scripts. >> >> I checked "crashinfo" but no dump from kernel. >> >> I didn't find any useful info from this commands. >> >> I checked "praudit /var/audir/20130930..CrashRecovery" >> and I didn't understand very well from this file but I think this means my machine crash and reboot isn't it?? >> >> And How can I understand what is the reason of rebooting my FreeBSD8.3 server. >> >> Please help I need to find cause of reboot.. >> _______________________________________________ >> freebsd-hackers@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" Firstly, does this machine have the kernel debugger installed? if not then a kernel page fault will look like a reboot. if you know when this is going to occur, then I suggest that you set up some logging of every new process run, to a second machine, or possibly you might just ssh int the machine and leave 'top' running when it reboots you shoud get a snapshot of what's going on. you could just rename 'reboot' and see if it still happens. If not, then replace reboot (and friends) with a script that reports who called it.