Portupgrade breaks Apache13-modssl

Eric Sheesley esheesle at bcpl.net
Sat May 21 08:32:48 PDT 2005


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 at freebsd.org
[mailto:owner-freebsd-questions at 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 at obsecurity.org]
> Sent: Saturday, May 21, 2005 02:38
> To: Eric Sheesley
> Cc: freebsd-questions at 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 at freebsd.org mailing list 
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to
> "freebsd-questions-unsubscribe at 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 at freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscribe at freebsd.org"






More information about the freebsd-questions mailing list