From owner-freebsd-questions@FreeBSD.ORG Fri Jan 2 09:16:36 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5B777106566B for ; Fri, 2 Jan 2009 09:16:36 +0000 (UTC) (envelope-from leslie@eskk.nu) Received: from mx1.bjare.net (mx1.bjare.net [212.31.160.3]) by mx1.freebsd.org (Postfix) with ESMTP id E27348FC12 for ; Fri, 2 Jan 2009 09:16:35 +0000 (UTC) (envelope-from leslie@eskk.nu) Received: from localhost (localhost [127.0.0.1]) by mx1.bjare.net (Postfix) with ESMTP id 7A0405E224 for ; Fri, 2 Jan 2009 10:16:34 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at mx1.bjare.net X-Spam-Flag: NO X-Spam-Score: 3.037 X-Spam-Level: *** X-Spam-Status: No, score=3.037 tagged_above=-999 required=5 tests=[AWL=-0.640, HELO_LH_HOME=3.169, RCVD_IN_PBL=0.509, SPF_PASS=-0.001] Received: from mx1.bjare.net ([127.0.0.1]) by localhost (mx1.bjare.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id wsfYP46mBl4l for ; Fri, 2 Jan 2009 10:16:32 +0100 (CET) X-BN-MX1: ja X-BN-MailInfo: BjareNet Received: from lesbsdpc.homenet.home (c-195-216-040-164.static.bjare.net [195.216.40.164]) by mx1.bjare.net (Postfix) with ESMTP id DB6E95E222 for ; Fri, 2 Jan 2009 10:16:31 +0100 (CET) Message-ID: <495DDB6F.1000800@eskk.nu> Date: Fri, 02 Jan 2009 10:16:31 +0100 From: Leslie Jensen User-Agent: Thunderbird 2.0.0.18 (X11/20081125) MIME-Version: 1.0 To: freebsd-questions@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Suddenly "shutdown -p now" produces a reboot X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Jan 2009 09:16:36 -0000 I have a Server with Squid, 7.0-RELEASE-p4 FreeBSD, squid-3.0.11, that has been running fine for the last six months, at least. It is shutdown every night at 7 PM via cron. Now suddenly the machine is rebooting instead, and I've made no changes whatsoever. I'm wondering if this is a symptom of a coming hardware failure or if I can do something to get the normal behaviour back. I did have a similar problem when I first put the machine into production, then it was clear from /var/log/messages that squid did not have enough time to shutdown and I solved it by changeing the parameter rcshutdown_timeout="90" i rc.conf. Here's a piece of /var/log/messages ----------- snip ------------ Jan 1 19:05:00 server01 shutdown: power-down by root: Jan 1 19:05:33 server01 squid[823]: Squid Parent: child process 826 exited with status 0 Jan 1 19:05:34 server01 named[718]: stopping command channel on 127.0.0.1#953 Jan 1 19:05:34 server01 named[718]: stopping command channel on ::1#953 Jan 1 19:05:34 server01 named[718]: exiting Jan 1 19:05:36 server01 syslogd: exiting on signal 15 Jan 1 19:07:29 server01 syslogd: kernel boot file is /boot/kernel/kernel Jan 1 19:07:29 server01 kernel: Copyright (c) 1992-2008 The FreeBSD Project. Jan 1 19:07:29 server01 kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1 989, 1991, 1992, 1993, 1994 Jan 1 19:07:29 server01 kernel: The Regents of the University of California. All rights reserved. ----------- snip ------------ Thanks /Leslie