From owner-freebsd-questions@FreeBSD.ORG Tue Sep 9 08:45:35 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5055B16A4C0 for ; Tue, 9 Sep 2003 08:45:35 -0700 (PDT) Received: from dragoncrest.jasnetworks.net (dragoncrest.jasnetworks.net [65.194.254.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1795B44001 for ; Tue, 9 Sep 2003 08:45:34 -0700 (PDT) (envelope-from dragoncrest@voyager.net) Received: from j2v6e9.voyager.net (works.jasnetworks.net [192.168.0.2]) h89Amb7T004910 for ; Tue, 9 Sep 2003 10:48:44 GMT (envelope-from dragoncrest@voyager.net) Message-Id: <5.2.0.9.2.20030909234909.00a1ad80@pop.voyager.net> X-Sender: dragoncrest@pop.voyager.net X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 Date: Tue, 09 Sep 2003 23:54:28 -0700 To: freebsd-questions@FreeBSD.ORG From: Dragoncrest Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: Mail server reboot while upgrading ports X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Sep 2003 15:45:35 -0000 Was just going about doing an upgrade to my primary mail server yesterday and right in the middle of it doing its thing I hear a beep, it stops, then reboots. No warnings, no errors, nothing. Just reboots. Tracking it back I was somewhere in the middle of upgrading /usr/ports/dns/p5-net-dns when it burped. It's done that to me before with python upgrades on a different box. I couldn't see what was actually happening at the console as I was across the room ssh'ed in when it did this. Logs don't show anything sadly enough and for some reason I can't get the box to log portupgrade or make so I can see when errors like this might happen. Anyone got any ideas what might be happening? I did get the port upgraded, but not before having to go in and clean up the mess that this reboot left. I can't say this was necessarily caused by the dns port I was upgrading cause it's done it in the past a couple of times with other ports nearly the same way. Yet after it reboots if I go in and install the port manually (usually have to as the port gets trashed because of whatever it is that reboots the machine) to fix it, then everything plays nice. I have no idea what's up. Anyone have any thoughts on this?