perl-modperl mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Grant <emailgr...@gmail.com>
Subject Re: mod_perl-2.0.2 causing segfaults
Date Mon, 11 Dec 2006 16:49:08 GMT
> > Actually, the only place die_page is called in the module is:
> >
> > $SIG{PIPE} = sub { die_page($r); };
> >
> > What does that mean?
>
> Have a look here:
> http://perldoc.perl.org/perlipc.html#Using-open()-for-IPC
>
> There is an error reading from or writing to a pipe.

The way my config works, apache2 hands all requests to the interchange
(icdevgroup.org) daemon via a socket by way of the mod_perl module
(Interchange::Link).

So the error is caused by the mod_perl module trying to read or write
to or from the interchange daemon and failing?  If that's correct, it
sounds like the next thing to do is find out why it's failing?  Can it
be said whether it's a problem with mod_perl, Interchange::Link,
interchange, or something else at this point?

Also, I tried restarting the interchange daemon with
PERL_SIGNALS=unsafe and the ALERT/segfaults came MUCH MUCH more
frequently.  Does that tell us anything?

- Grant

Mime
View raw message