From owner-freebsd-questions@FreeBSD.ORG Fri Jan 2 22:12:03 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 6B3CC10656D2 for ; Fri, 2 Jan 2009 22:12:03 +0000 (UTC) (envelope-from tajudd@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.228]) by mx1.freebsd.org (Postfix) with ESMTP id 392F18FC1B for ; Fri, 2 Jan 2009 22:12:02 +0000 (UTC) (envelope-from tajudd@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so7762916rvf.43 for ; Fri, 02 Jan 2009 14:12:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=ov4y4NYsYnicGTn+ef5Y3xV4ptiRnGnykmBSEBSI/g8=; b=ljJLGbdmLL8S++nmsqadN6/aNc2rjxFNyx/qxzb1ZHWdnbqDqYUFO54w9dYjebR+R7 btB2/UYZ4z5mKIrWA7/+1txduwDFkyVy2fkC6BX1KZ7pm7iH1zNjl2Wcw31+hYNr5WsS GXwpxH8W+w9QAnOqp4Za9eG4MsrVPMSq4etok= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=gg2hvNodMHvhNLlej7t43IbxDp84G4Qxlkqj5hqixML2X+jM6RIREpz+8REkgKDQmu l+G7f0yUwkaZsAgKWnlfD6MCjKWdG+Vy7BBd+ynQF1sJkV4cvYooP7A8yk9u+Fk5PZlN O++9OU8nq75AH4+WtYWpp5iK2eYfYtspUSdrg= Received: by 10.141.115.6 with SMTP id s6mr9014754rvm.235.1230934322732; Fri, 02 Jan 2009 14:12:02 -0800 (PST) Received: from ?192.168.4.44? (c-76-113-34-1.hsd1.nm.comcast.net [76.113.34.1]) by mx.google.com with ESMTPS id l31sm49402434rvb.2.2009.01.02.14.12.00 (version=SSLv3 cipher=RC4-MD5); Fri, 02 Jan 2009 14:12:01 -0800 (PST) Message-ID: <495E912A.9090102@gmail.com> Date: Fri, 02 Jan 2009 15:11:54 -0700 From: Tim User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: Leslie Jensen References: <495DDB6F.1000800@eskk.nu> In-Reply-To: <495DDB6F.1000800@eskk.nu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: 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 22:12:03 -0000 Leslie Jensen wrote: > 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 > > > Leslie, I've got a gateway (talking pc mfg, not role) that does that. It's always rebooted on a request to shutdown. A fix, if I remember it right, that didn't last long was to go into BIOS and toggle the BIOS power management features. IIRC, it was set to disable, and I enabled it. Since then, i haven't really used that gateway anymore. You have to consider that some PCI devices can power-on a box (think: Remote Wakeup [which is done over the LAN]). The times that it does actually do it, don't bother me, i'll get around to forcing it down with a power button or power cord when it bugs me enough that it's still powered on. >:) -- Tim Judd I will top-post when I feel like it. For those who are so demanding everyone bottom-post, You'll just have to forgive others when they choose to top-post.