Seg Faults on connect outta nowhere

Hello. After doing a 'service httpd restart', prior to which my apache-fp
was working just fine and dandy, then, after restarting httpd everytime I
try to connect to :80 or :8090 (fp admin) it just adds a [notice] line about
a seg fault. I have no idea why this jsut suddenly started happening. I even
tried rebootign the whole system to no avail.

Notes:
I had recently (about a week ago) used apt-get to do a system wide upgrade,
but apache was working just fine all week till today, and I had restarted
httpd a few times this week, so I don't think it was a result of that.

The system is a RH 7.3 which was upgraded recently with Apt.
uname -a
Linux SRLINUX 2.4.18-3 #1 Thu Apr 18 07:31:07 EDT 2002 i686 unknown

Apache info:
Apache/1.3.27 (Unix) (Red-Hat/Linux)
mod_ssl/2.8.7
OpenSSL/0.9.6b
PHP/4.1.2 mod_perl/1.26
FrontPage/5.0.2.2510
mod_perl-1.26-5

I also have Apache::ASP too.

I had mod_ssl-2.8.12-3 but I down graded back to my original to see if that
would fix it but nothing changed.


Doing a tail -f on error_log:

[Fri Sep 26 22:08:21 2003] [notice] Apache/1.3.27 (Unix) (Red-Hat/Linux)
mod_ssl/2.8.7 OpenSSL/0.9.6b PHP/4.1.2 mod_perl/1.26 FrontPage/5.0.2.2510
configured -- resuming normal operations
[Fri Sep 26 22:08:21 2003] [notice] suEXEC mechanism enabled (wrapper:
/usr/sbin/suexec)
[Fri Sep 26 22:08:21 2003] [notice] Accept mutex: sysvsem (Default: sysvsem)
[Fri Sep 26 22:10:02 2003] [notice] child pid 2005 exit signal Segmentation
fault (11)
[Fri Sep 26 22:10:02 2003] [notice] child pid 2004 exit signal Segmentation
fault (11)
[Fri Sep 26 22:10:09 2003] [notice] child pid 2007 exit signal Segmentation
fault (11)
[Fri Sep 26 22:10:09 2003] [notice] child pid 2006 exit signal Segmentation
fault (11)

I even tried commenting out different modules (mod_*) entries like ssl, php,
perl, dav, etc.

Thank for any help.

--
Trent Curry

Trent Curry <tcurrey DeleteThis @no.no.i.said.no> wrote:
 > [Fri Sep 26 22:10:02 2003] [notice] child pid 2005 exit signal Segmentation
 > fault (11)

This is usually due to a conflicting module, I had the same using
mod_ssl and mod_jrun to connect to a JRun application server.

I'd try to disable all the modules and then adding them one at a time
and see which ones are conflicting.

Note that most of the time the only solution is just not use the two
conflicting modules togheter.

Davide<!-- ~MESSAGE_AFTER~ -->