[OpenAFS] bosserver death

Miles Davis miles@CS.Stanford.EDU
Sat, 24 Sep 2005 15:35:12 -0700


On Thu, Sep 22, 2005 at 08:22:16AM -0400, Steve Devine wrote:
> Miles Davis wrote:
> 
> >On Wed, Sep 21, 2005 at 07:05:19PM -0700, Russ Allbery wrote:
> > 
> >
> >>Miles Davis <miles@CS.Stanford.EDU> writes:
> >>
> >>   
> >>
> >>>Wow, bosserver just died on every single one of my AFS servers running 
> >>>1.2.13 within the past hour. 1.3.x servers seem to be ok. My bad luck, 
> >>>or another counter bug?
> >>>     
> >>>
> >>We're running 1.2.13 and everything looks fine so far here.
> >>   
> >>
> >
> >Bugger. Wish I had more info, but of course bosserver died silently. On 
> >a few of the systems, volserver died with it, which reminds me of an 
> >old problem I and some others had on earlier 1.3.x's. Assuming Mike 
> >Newton hasn't found some Rx killer plugin for nessus, I'll just hope for 
> >the best as I sit here and watch the callback breaks. :)
> >
> >
> > 
> >
> I had this over and over again running 1.2.13 on Suse9.0
> turned out to be a wierd bug that killed the bosservers after a set 
> number of seconds had elapsed. (23 ~24 days)
> Here is the bug id .. don't know if the link is still good.
> http://grand.central.org/rt/Ticket/Display.html?id=17990
> However upgrading to 1.3.82 fixed it.
> /sd

Looks like it was that issue, only 248 days as noted in the bug. 


-- 
// Miles Davis - miles@cs.stanford.edu - http://www.cs.stanford.edu/~miles
// Computer Science Department - Computer Facilities
// Stanford University