[Info-vax] inconsistent information about HBVS status

[Phillip Helbig---undress to reply]

In article <1PYmR1xVg022 at eisner.encompasserve.org>,
koehler at eisner.nospam.encompasserve.org (Bob Koehler) writes: 

> In article <iia0hk$n1p$1 at online.de>, helbig at astro.multiCLOTHESvax.de (Phillip Helbig---undress to reply) writes:
> > I had a DEC 3000 in my cluster freeze up today (if all goes well, I will 
> > have moved from 2 VAXen and 1 old ALPHA to 3 newer ALPHAs by this time 
> > next week), I don't know why.  It froze.  I had to do CTRL-P to get to 
> > the console.  Everything left OK.  BOOT hung soon after it rejoined the 
> > cluster.  Back to the console, TEST, and then it booted normally.  Maybe 
> > it's just getting old.
> 
>    Perhaps if you'ld done a CRASH instead, someone could figure out why
>    it hung and prevent it from doing so in the future.

I plan to replace it this weekend anyway, and wanted to get things back 
to normal as soon as possible.  The machine had the TCPIP cluster alias,
and, since it was still in the cluster, it did NOT migrate to another 
machine.  (It did as soon as I caused it to leave the cluster, and after 
a few minutes I had a few bounces from automatic rejection messages due 
to mail sent to non-existent users, which reminded me of one of the 
reasons I have to move the VAXen out of the cluster.)