[Info-vax] probably a simple issue...

[cyberdefensedave at gmail.com]

On Monday, February 17, 2014 7:33:18 AM UTC-5, Stephen Hoffman wrote:
> On 2014-02-17 12:18:01 +0000, Simon Clubley said:
> 
> 
> 
> > On 2014-02-17, cyberdefense> wrote:
> 
> >> 
> 
> >> Hmmm...  In the process of fixing this all I somehow have ended up with the
> 
> >> password to System on the 1.2 being changed, though I can still log into the
> 
> >> 1.3 host...  What's really weird about it is that I didn't touch sysuaf.dat.
> 
> >> 
> 
> > 
> 
> > Do you _know_ it's been changed or have you triggered breakin evasion 
> 
> > and are assuming the password has been changed because you cannot login 
> 
> > ?
> 
> 
> 
> A reboot would work.   Or try a different login and see if that works.
> 
> 
> 
> V7.3 is ancient, and predates the cluster-wide evasion support IIRC, 
> 
> which means that repeated entry of a bad password on one host in the 
> 
> cluster is a distinct possibility.
> 
> 
> 
> > Try rebooting node 1.2 and see if you can then login. If you cannot, 
> 
> > then the password really has been changed.
> 
> 
> 
> If the password works in one place and not another and if this is not a 
> 
> case of breakin evasion, then there are likely multiple SYSUAF files 
> 
> and the contents of those files are skewed; the common files are not 
> 
> configured as is typical for a cluster.
> 
> 
> 
> 
> 
> 
> 
> -- 
> 
> Pure Personal Opinion | HoffmanLabs LLC

Thanks!

It turned out to be a far simpler problem, and I think I've actually got this whole Decnet thing sorted out now.  Volumes mount, monitor cluster functions... whew.

Apparently 1.2 had not managed to complete its reboot.  I wandered down to the datacenter and realized that the captive accounts were being refused login as well, which I have seen happen in the past when something gets stuck during a shutdown/reboot.  Forced a dead sergeant, booted and all is well.  The renumbering of the node to 1.2 seems to have finally stuck!

Thanks all for your assistance. :)