From owner-freebsd-ports@FreeBSD.ORG Mon Feb 21 03:12:03 2005 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5438916A4CE for ; Mon, 21 Feb 2005 03:12:03 +0000 (GMT) Received: from dreadlock.phreakout.net (dreadlock.phreakout.net [208.51.56.115]) by mx1.FreeBSD.org (Postfix) with SMTP id 7EA4143D58 for ; Mon, 21 Feb 2005 03:12:02 +0000 (GMT) (envelope-from bob@phreakout.net) Received: (qmail 17091 invoked from network); 21 Feb 2005 03:18:05 -0000 Received: from 24-52-224-96.kntnny.adelphia.net (HELO ?192.168.102.101?) (24.52.224.96) by dreadlock.phreakout.net with SMTP; 21 Feb 2005 03:18:05 -0000 Message-ID: <4219517C.1090403@phreakout.net> Date: Sun, 20 Feb 2005 22:11:56 -0500 From: Bob Ababurko User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-ports@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-questions@FreeBSD.org Subject: apache wont start after mhash install X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Feb 2005 03:12:03 -0000 Hello- I have a box that is running 5.2.1 on sparc64 hardware. After installing php4-mhash-4.3.8_2 via ports, apache will not start again after it is stopped. It will return to normal after I uninstall the port of coarse. The only error message I get is this in /var/log/messages: Feb 20 21:54:05 web1 kernel: pid 71512 (httpd), uid 0: exited on signal 11 (core dumped) What is the next step to determine the problem? Do I need to do a core dump analysis to figure this out? If so, what is the way or best way? Also, I noticed that it seems like I have both versions of apache installed. I do not believe that I did this so I am thinking that somehow the ports did it. I found it when I did a pkg_info:... apache+mod_ssl-1.3.31+2.8.19. This is one thing that I found odd, so I thought it may be somehow contributing. -Bob