[Info-vax] delay in startup

[Phillip Helbig---undress to reply]

In article
<009d3b8b-dd40-44ab-b19d-d40f7f8f1091 at z31g2000vbt.googlegroups.com>,
John Wallace <johnwallace4 at yahoo.co.uk> writes: 

> Would it be safe to assume that you've disabled the operator logs on
> these systems? If you hadn't, they might have provided some clues as
> to what went on when.

No, I have operator logs.  Both start at the time the second node boots:

DISK$USER:[SYSTEM.MANAGER]OPERATOR_JANDER.LOG;30


%%%%%%%%%%%  OPCOM  13-MAR-2012 17:39:35.52  %%%%%%%%%%%
Logfile has been initialized by operator _JANDER$OPA0:
Logfile is JANDER::DISK$USER:[SYSTEM.MANAGER]OPERATOR_JANDER.LOG;30

%%%%%%%%%%%  OPCOM  13-MAR-2012 17:39:35.52  %%%%%%%%%%%
Operator status for operator JANDER::DISK$USER:[SYSTEM.MANAGER]OPERATOR_JANDER.LOG;30
CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS, NETWORK, CLUSTER, SECURITY,
LICENSE, OPER1, OPER2, OPER3, OPER4, OPER5, OPER6, OPER7, OPER8, OPER9, OPER10,
OPER11, OPER12

%%%%%%%%%%%  OPCOM  13-MAR-2012 17:39:35.52  %%%%%%%%%%%
OPCOM on JANDER is initializing the local node JANDER, csid 00010002, system 113
4

%%%%%%%%%%%  OPCOM  13-MAR-2012 17:39:35.52  %%%%%%%%%%%
OPCOM on JANDER recognizes node MINNIM, csid 00010001, system 1094
Attempting to establish communications, placing node in STARTING state.

%%%%%%%%%%%  OPCOM  13-MAR-2012 17:39:35.52  %%%%%%%%%%%

As you can see, the operator log files are not on the system disk, but
on a three-member shadow set (each member with a direct connection to 
one of the three nodes).  Normally, when some members are not available, 
the shadow set is formed with those which are (I don't have 
/POLICY=REQUIRE_MEMBERS).  No information here on what was going on.