perlbal crashes

[Brad Fitzpatrick]

Things I remembered after I sent this email:

  -- you must use Perl 5.8.  Perl 5.6 is known to leak memory like crazy.

  -- the latest cvs version of Perlbal requires the latest Danga::Socket,
     also in cvs.  Without it, it'll kinda work, but you'll get weird
     errors/crashes/warnings.

  -- I consider any Perl warning a bug.  Please report.



On Sat, 13 Aug 2005, Brad Fitzpatrick wrote:

> Again,
>
> You're kinda on your own if you're following cvs.  Did you also notice
> 100% CPU usage during the memory usage?  I remember fixing a CPU spin
> recently (but only related to buffered uploads) and maybe that CPU spin
> was also a memory leak and I just killed it before it was a problem.
>
> All I can say is try tonight's cvs.  Things have been changing incredibly
> quickly the past week.
>
> Sorry about all this.... I won't be making another official release of
> Perlbal until we run it in production for a couple days ourselves.
> Releasing 1.3 without field testing was my mistake.
>
> - Brad
>
>
> On Sat, 13 Aug 2005, Kevin Lewandowski wrote:
>
> > Update on this:
> >
> > now perlbal crashes after a few minutes with out of memory messages:
> >
> > Out of Memory: Killed process 24339 (mogstored).
> > Out of Memory: Killed process 24338 (mogstored).
> > Out of Memory: Killed process 24340 (mogstored).
> > Out of Memory: Killed process 24341 (mogstored).
> >
> > (note, I'm running mogstored but modified the config to add a
> > revserse proxy. That is what's causing the crash).
> >
> > On Aug 13, 2005, at 9:05 PM, Kevin Lewandowski wrote:
> >
> > > Okay, I was running cvs from about a week ago. Tried 1.3 and had
> > > the same problem. Now I'm running the latest cvs and there is no
> > > crash so far but I see this message every few seconds:
> > >
> > > Use of uninitialized value in numeric lt (<) at /usr/local/share/
> > > perl/5.8.4/Perlbal/ClientProxy.pm line 487.
> > > Use of uninitialized value in sysread at /usr/local/share/perl/
> > > 5.8.4/Danga/Socket.pm line 981.
> > > Use of uninitialized value in numeric lt (<) at /usr/local/share/
> > > perl/5.8.4/Perlbal/ClientProxy.pm line 487.
> > > Use of uninitialized value in sysread at /usr/local/share/perl/
> > > 5.8.4/Danga/Socket.pm line 981.
> > >
> > > Kevin
> > >
> > > On Aug 13, 2005, at 7:17 PM, Brad Fitzpatrick wrote:
> > >
> > >
> > >> What version?  1.2, 1.3, cvs?
> > >>
> > >> I'm pretty sure that bug was both introduced and fixed in cvs.  If
> > >> it's
> > >> present in an actual release, uh, that'd suck.  You might try
> > >> updating to
> > >> the latest cvs?  cvs should be stable right now, except for
> > >> buffered-to-disk uploads which are undergoing some refactoring right
> > >> now.
> > >>
> > >> - Brad
> > >>
> > >> On Sat, 13 Aug 2005, Kevin Lewandowski wrote:
> > >>
> > >>
> > >>
> > >>> Hello,
> > >>>
> > >>> I'm running Perlbal in reverse proxy mode and it is crashing quite
> > >>> frequently. I get the crash message:
> > >>>
> > >>> crash log: Can't call method "request_method" on an undefined value
> > >>> at /usr/local/share/perl/5.8.4/Perlbal/HTTPHeaders.pm line 367.
> > >>>
> > >>> My Perlbal config is:
> > >>>
> > >>> --
> > >>> CREATE POOL apache
> > >>>    POOL apache ADD 10.10.10.23:81
> > >>>
> > >>> CREATE SERVICE proxy
> > >>>    SET proxy.listen = 10.10.10.23:80
> > >>>    SET proxy.role = reverse_proxy
> > >>>    SET proxy.pool = apache
> > >>>    SET proxy.persist_client = on
> > >>>    SET proxy.persist_backend = on
> > >>>    SET proxy.verify_backend = on
> > >>> ENABLE proxy
> > >>> --
> > >>>
> > >>> This Perlbal is feeding Apache behind it. I looked into the code and
> > >>> it has something to do with Keepalive. The crash happens after a few
> > >>> hours when keepalive is disabled in apache, and almost immediately
> > >>> when keepalive is enabled in Apache.
> > >>>
> > >>> Any ideas on what is wrong? thanks
> > >>>
> > >>> Kevin
> > >>>
> > >>>
> > >>>
> > >>>
> > >>
> > >>
> > >>
> > >
> > >
> > >
> >
> >
>
>