>> > > > > > 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?
>> > > > >
>> > > > >
>> > > > > It would make sense that, when you have high load, there is
On Mon, 11 Dec 2006, Grant wrote:
> > > > > 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?
> > > >
> > > >
> > > > It would make sense that, when you have
> >> > > 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?
> >> >
> >> >
> >> > It would make sense that, when you have high load, there is a problem
> >> > processing
> 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
>> > > 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?
>> >
>> >
>> > It would make sense that, when you have high load, there is a problem
>> > processing many concurre
>> > 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 f
On Mon, 11 Dec 2006, Philip M. Gollucci wrote:
Grant wrote:
> > 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?
>
>
> It would make sense that, when you have high load, th
Grant wrote:
> 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 faili
> 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
> 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'
> 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 han
> 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.
>
> - Grant
_
>> you need to find out why die_page is being called.
>
> Do you have any advice on the best way to do that?
You could start by using caller():
my ($package, $filename, $line) = caller;
within the sub, in order to see where it's being
called from.
Actually, the only place die_page is calle
On Sun, 10 Dec 2006, Grant wrote:
[ ... ]
you need to find out why die_page is being called.
Do you have any advice on the best way to do that?
You could start by using caller():
my ($package, $filename, $line) = caller;
within the sub, in order to see where it's being
called from.
--
be
14 matches
Mail list logo