[2265] in SIPB-AFS-requests
Re: Status of the cell, and possible plans to revert to 3.2
daemon@ATHENA.MIT.EDU (jweiss@MIT.EDU)
Tue Jan 30 01:51:01 1996
From: jweiss@MIT.EDU
To: ghudson@MIT.EDU
Cc: sipb-afsreq@MIT.EDU
In-Reply-To: Your message of "Tue, 30 Jan 1996 01:38:10 EST."
<9601300638.AA00894@hodge-podge.MIT.EDU>
Date: Tue, 30 Jan 1996 01:50:49 EST
It should be noted that sys-support has seen the dying bosserver and
other server process problem, although only rarely. (I'm not sure if
syssupport has seen it on a 3.3a server).
>> Following is my plan for reverting the cell to 3.2, if necessary:
>>
>> * Shutting down the cell
>> * Killing the bosserver on both machines
>> * Moving the bin.32 and db.32 directories into place, as well
>> as /etc/fsck.32, on both machines
I would be tempted to reboot here, or at least start the bos server
witht he following invocation:
cd /
/usr/afs/bin/bosserver < /dev/null >& /dev/null &
This is how I was told to start it the first time I dealt with the
dying bosserver problem, and am somewhat superstitous about the I/O
redirection.
>> * Restarting the cell
>> * Running vos syncvldb to sync the vldb with any changes made
>> since the upgrade
>>
>> I don't believe this is any more dangerous than starting the servers
>> with empty vldbs, and will cause much less of an outage.
I agree
Jonathon
