Our experience has been the same. Occasionally, a bosserver (afs 3.3a) will
simply disappear, leaving all other afs server processes on the same server
still running. It must be an afs 3.3a problem.
-Steven McElwee
--
---------------------------------------------------------------------------
Steven McElwee | Email --> | [EMAIL PROTECTED]
OIT/System Adm | <-- US Snail Mail |
Duke University |------------------------|-------------------------
417 North Building | (919) 660-6914 (Work) | (919) 660-7029 (Fax)
Durham, NC 27706 | | (919) 971-0781 (Cellular)
---------------------------------------------------------------------------
-- original message follows --
> From: [EMAIL PROTECTED] (W. Phillip Moore)
> To: [EMAIL PROTECTED]
> Subject: Re: restart of bos server
> Date: 15 Feb 1996 08:15:15 -0500
> >>>>> "Steve" == Steve Kalinowski <[EMAIL PROTECTED]> writes:
>
> Steve> We have disabled the restart. Our servers are a mix of SPARC
> Steve> Classic servers and SPARCserver 10/40 servers running SunOS
> Steve> 4.1.3_U1 and AFS 3.3a software. For reasons we've yet to
> Steve> understand, the bosserver seems to exit w/o a trace after about
> Steve> 200 days. Being an academic institution, it isn't too hard to
> Steve> plan to restart all of the servers during term breaks.
>
> Aha!! So I'm not going crazy....
>
> We experienced the same phenomenon on two of our machines here within
> the last two weeks. In both cases, the machines had been up 250 and
> 220 days each.
>
> I have no idea when the bosserver vanished, since the child processes
> (just the vlserver and ptserver in these cases) were running fine.
>
> Here's hoping this is fixed in 3.4a.
>
> Phil
