crash on Perlbal 1.51

[Del Raco]

Forgot to include the list.  

--- dormando <dormando at rydia.net> wrote:

> I meant that the error you got was the same as the
> one we saw. Also, our 
> perlbal instances would take anywhere from 30
> seconds to 30 minutes to 
> crash under load. Wasn't all immediate.
> 
> -Dormando
> 
> >> --- dormando <dormando at rydia.net> wrote:
> >> 1.41 worked, but I think I had other crash fixes
> in
> >> there... I can't 
> >> recall. My tiny patch has been holding the
> >> latest-and-greatest running 
> >> stably under a few thousand hits per second for
> two
> >> months now.
> >>
> >> I'm pretty sure it's the same issue, since it's
> the
> >> same results. Our 
> >> perlbal instances get a *lot* of traffic, on the
> >> order of hundreds of 
> >> hits per second per process. So it's more likely
> >> that we'd hit it 
> >> quickly than you would.
> >>
> >> -Dormando
> >>
> >> Del Raco wrote:
> >>> Hi Dormando,
> >>>
> >>> I saw your message too, but wasn't sure if it
> >> applies,
> >>> since you saw crashes immediately after startup.
> >>>
> >>> In one of your messages, you mentioned rolling
> >> back to
> >>> 1.41.  Is that the most recent stable release? 
> I
> >>> don't need to run the latest and greatest, just
> >>> something stable.
> >>>
> >>> Thanks.
> >>>
> >>>
> >>> --- dormando <dormando at rydia.net> wrote:
> >>>
> >>>> Kevin Rosenberg wrote:
> >>>>> Del Raco wrote:
> >>>>>> Has anyone seen the following error on
> Perlbal
> >>>> 1.51? 
> >>>>>> Nov 28 03:10:37 app-200 perlbal[16356]: crash
> >>>> log:
> >>>>>> Can't call method "req_keep_alive" on an
> >>>> undefined
> >>>>>> value at
> >>>>>>
> >
>
/usr/local/share/perl/5.8.7/Perlbal/ClientHTTPBase.pm
> >>>>>> line 124.
> >>>>> Yes.
> >>>>>
> >>>>>> Any help would be appreciated.  Thanks.
> >>>>> I quickly hacked a workaround, but I don't
> >>>> understand the true cause of
> >>>>> the error:
> >>>>>
> >>>> We had the same issue back in october, fixed
> with
> >> a
> >>>> slightly different 
> >>>> patch (and a little insight as to what might've
> >> been
> >>>> happening). But I 
> >>>> don't have the time to dig into it further
> right
> >>>> now.
> >>>>
> >>>>
> >
>
http://lists.danga.com/pipermail/perlbal/2006-October/000328.html
> >>>> The root of the problem appears to be a few
> cases
> >>>> where the code allows 
> >>>> a client to reset without telling its attached
> >>>> backend that it's reset. 
> >>>> The backend object blindly uses its reference
> to
> >> the
> >>>> client once the 
> >>>> next event happens. I don't think I properly
> >> caught
> >>>> all of the cases 
> >>>> where that happens, so I submitted a kludge
> patch
> >>>> instead.
> >>>>
> >>>> -Dormando
> >>>>
> >>>
> >>>
> >>>  
> >>>
> >
>
____________________________________________________________________________________
> >>> Do you Yahoo!?
> >>> Everyone is raving about the all-new Yahoo! Mail
> >> beta.
> >>> http://new.mail.yahoo.com
> >>
> > 
> > 
> > 
> >  
> >
>
____________________________________________________________________________________
> > Yahoo! Music Unlimited
> > Access over 1 million songs.
> > http://music.yahoo.com/unlimited
> 
> 



 
____________________________________________________________________________________
Do you Yahoo!?
Everyone is raving about the all-new Yahoo! Mail beta.
http://new.mail.yahoo.com