>> > Hello, I've been plagued by apache2 segfaults ever since I started
>> > using Interchange::Link years ago. The latest Link.pm has ALERT
>> > messages accompanying the segfaults in error_log:
>> >
>> > ALERT: bad pipe signal received for /page.html
>> > [Sat Dec 09 10:27:55 2006] [notice] child pid 21337 exit signal
>> > Segmentation fault (11)
>> >
>> > Does anyone have any advice on solving this? I'm using
>> apache-2.0.58
>> > and mod_perl-2.0.2 in Gentoo Linux.
>>
>> Also, here is the portion of Link.pm that the ALERT seems to come
>> from:
>>
>> # Return this message to the browser when the server is not running.
>> # Log an error log entry if set to notify
>>
>> 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.
>> </BODY></HTML>
>> EOF
>>
>> }
>>
>> Please let me know if you have any ideas.
>
> The segfaults are eliminated by commenting out the $r stuff in the
> die_page sub. I still get the ALERTs though. Does anyone have any
> advice on figuring out why I'm having the bad pipe problem? Is there
> an easy way to add extra debugging info to the sub?
>
> Also, restarting IC with PERL_SIGNALS=unsafe increases the ALERTs
> 50 fold.
I've been seeing this too, on my Apache 2 and latest Link.pm. I also
had to use PERL_SIGNALS=unsafe and so I get quite a lot of these.
The visible effect on the browser is that the page or image (which
Link.pm apparently still has some part in delivering) does not load.
I get them myself when browsing and testing my websites, and I have
never stopped loading a page or had any other problems on non-IC
sites I host.
I was told the problem stems from either the browser and a stop
button or some other network fault. I may go back to Apache 1.3 to
get around this.
Sounds like the exact same problem I'm having. I don't use the UI so I don't have an interchange-5/ folder. If I request an admin page, the html loads and my error_log is suddenly filled with errors like this: ALERT: bad pipe signal received for /interchange-5 It happens every single time. After that, bad pipe alerts appear much more frequently until apache2 is restarted. I wonder if this is a clue. - Grant
Josh Lavin
_______________________________________________ interchange-users mailing list suppressed http://www.icdevgroup.org/mailman/listinfo/interchange-users
Mail converted by mhonarc 2.6.15
This archive provided courtesy of JSW4.NET, Internet Hosting Services for Small Business.