From owner-freebsd-questions@FreeBSD.ORG Sat May 21 15:32:48 2005 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 870BF16A4CE for ; Sat, 21 May 2005 15:32:48 +0000 (GMT) Received: from sccrmhc14.comcast.net (sccrmhc14.comcast.net [204.127.202.59]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1803D43D4C for ; Sat, 21 May 2005 15:32:48 +0000 (GMT) (envelope-from esheesle@bcpl.net) Received: from skynet (pcp0011865712pcs.parkvl01.md.comcast.net[69.251.125.202]) by comcast.net (sccrmhc14) with SMTP id <2005052115324601400icjnte>; Sat, 21 May 2005 15:32:47 +0000 From: "Eric Sheesley" To: Date: Sat, 21 May 2005 11:32:44 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.6353 In-Reply-To: <000401c55e15$ea000080$144da8c0@rtxnetworks.local> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527 Thread-Index: AcVeFeoAqES1fErJTIO1g8WCv1rUHgABEHpQ Message-Id: <20050521153248.1803D43D4C@mx1.FreeBSD.org> Subject: RE: Portupgrade breaks Apache13-modssl 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: Sat, 21 May 2005 15:32:48 -0000 That seemed to work. I removed the openssl extension from the php extensions.ini file and all seems to work fine now. Thanks, Eric -----Original Message----- From: owner-freebsd-questions@freebsd.org [mailto:owner-freebsd-questions@freebsd.org] On Behalf Of Tim Kellers Sent: Saturday, May 21, 2005 11:01 To: postmaster Cc: 'Kris Kennaway'; Eric Sheesley Subject: Re: Portupgrade breaks Apache13-modssl On Saturday 21 May 2005 10:39 am, Eric Sheesley wrote: > When I did the portupgrade I did 'portupgrade -arR'. Apache fails to > start at boot. If I run it manually with 'httpd' it works fine but if > I do 'httpd -DSSL' it fails. I've even rebuilt the apache13-modssl > port with no luck. Not sure what other details I can give besides the > messages log reports a core dump. > > -----Original Message----- > From: Kris Kennaway [mailto:kris@obsecurity.org] > Sent: Saturday, May 21, 2005 02:38 > To: Eric Sheesley > Cc: freebsd-questions@freebsd.org > Subject: Re: Portupgrade breaks Apache13-modssl > > On Sat, May 21, 2005 at 12:47:41AM -0400, Eric Sheesley wrote: > > I am running Freebsd 5.3 and just did a portupgrade(upgraded php, > > amavis, clamav, and cyrus-sasl. When I rebooted apache refused to > > start. I can get apache started with no ssl but not with it. I > > have apache13-modssl installed. It wasn't modified during the > > upgrade though. So it would seem taht teh ssl mod is crashing. Any ideas? > > Anyone else experience this? > > You need to > > * make sure you also update the ports that depend on those you > updated, e.g. by using portupgrade -a, -r, etc. > > * provide more details in your support requests. "It is crashing", > etc is not helpful. Show exact commands you are running and exact > output, and exact errors, if any. > > Thanks, > Kris > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "freebsd-questions-unsubscribe@freebsd.org" I have had upgrades to php mysteriously (that is with no apparent logfile error) break apache. Try commenting out the following lines from your httpd.conf file: LoadModule php4_module AddModule mod_php4.c and restart apache. If that works, look in /usr/local/etc/php/extensions.ini and see if there are any obvious php conflicting modules and comment them out --extension=recode.so has sometimes gotten placed back in that file even though it's a known conflict after an upgrade. Then restart apache. If there is no "obvious" conflict like the recode conflict, you may have to begin commenting out the extensions in that file one by one, restarting apache until it starts again. _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"