apache13+mod_ssl portupgrade problem..

Steve Monkhouse stevem at protek.net.au
Thu Sep 22 01:08:07 PDT 2005


>> Hi guys..
>>
>> Ive been pulling my hair out for the last couple of hours over this to no
>> avail...
>>
>> FreeBSD 5.2.1-RELEASE-p8
>> P4 2.8
>> 512mb RAM
>>
>>
>> I 'had' a working apache13+modssl installation along with mod_perl.
>> Everything was working perfectly until I decided yesterday to portupgrade
>> the machine.
>>
>> I started off with perl being portupgraded via  'portupgrade -rR perl'
>>
>> Then I did the php modules via portupgrade php-*
>>
>> And anything else that I missed then got done as well..
>>
>> Everything now shows that its up-to-date eg..
>>
>> apache+mod_ssl-1.3.33+2.8.24_1      =   up-to-date with port
>>
>> however whenever I try to start apache with apachectl startssl it gives :
>>
>> /usr/local/sbin/apachectl startssl: httpd started
>>
>> but does not start.. nothing at all appears in the logs (error or access)
>> even with debug enabled.. the only message that appears is in messages
>>
>> Sep 22 17:44:23 server kernel: pid 77689 (httpd), uid 0: exited on signal
>> 11 (core dumped)
>>
>> Ive searched high and low for a solution, but to no avail..
>>
>> Ive deinstalled and reinstalled, deinstalled / install distclean etc etc
>> but no diff..
>>
>> The sad thing is that this was working perfectly yesterday albeit with
>> versions that haven't been updated for 2 months..
>>
>> What have I done wrong ? and how do I go about rectifying it ??
>>
>Try doing "apachectl configtest" to check your config files. I've seen
>apache 
>just bail with no errors on a bad config.

Unfortunately.. No.. 

root at server:/usr/local/etc/apache# apachectl configtest
Syntax OK
Segmentation fault (core dumped)

My config hasn't changed, and as I said was working perfectly before the
portupgrade.. 

Next idea ??

Steve











More information about the freebsd-questions mailing list