Are you running on a UNIX or Windows platform? There was an earlier discussion on mp2 on Windows faulting on occassions. Henrik S Hansen gave some insight into the cause of the crash, and it seems to point to the Perl dll not being able to release memory when it gets too large.
Hello, mod_perl is running on an up-to-date Gentoo Linux system. Could it be a similar problem though? - Grant
> Hello, I've been dealing with apache2 segfaults on my server for
> years. My consultant thinks it's a mod_perl problem of some sort.
> I'm currently using mod_perl-2.0.2.
>
> The segfaults definitely seem to coincide with increases in traffic.
> They look like this in error_log:
>
> [Fri Dec 08 09:45:02 2006] [notice] child pid 25294 exit signal
> Segmentation fault (11)
>
> and are sometimes accompanied by one of these:
>
> ALERT: bad pipe signal received for /page.html
>
> The ALERT comes from this portion of the Interchange::Link mod_perl
> module:
>
> sub die_page {
>
> my $r = shift;
> my $msg;
>
> warn "ALERT: bad pipe signal received for $ENV{SCRIPT_NAME}\n";
>
> $r->content_type ("text/html");
> $r->print (<<EOF);
> <html><head><title>Interrupted</title></head>
> <body bgcolor="#FFFFFF">
> <h3>Someone pressed stop...</h3>
> <p>
> We have aborted this request because someone terminated it.
> Please try again soon.
> </p>
> </body></html>
> EOF
>
> }
>
> Can anyone help me solve this?
>
> - Grant
Mail converted by mhonarc 2.6.15
This archive provided courtesy of JSW4.NET, Internet Hosting Services for Small Business.