[Info-vax] delay in startup
Phillip Helbig---undress to reply
helbig at astro.multiCLOTHESvax.de
Sat Mar 24 07:35:57 EDT 2012
While I was travelling, power went off for a few hours for
maintenance. (This is the first time I have ever experienced planned
outage and only the second or third unplanned.) I thought about logging
in and shutting everything down cleanly, but decided to use it as a hard
test instead. Two of three nodes came back up; that was expected since
the battery in one of the PWS is dead (now I know which one). Can this
be replaced by a standard off-the-shelf battery? Everything else came
up OK, but I am puzzled by this:
13-MAR-2012 17:35:38.00 MINNIM 13-MAR-2012 17:38:31.84
13-MAR-2012 14:46:40.00 JANDER 13-MAR-2012 17:38:59.19
These two lines are generated by the following code:
$ OPEN/APPEND/SHARE BOOT_HISTORY CLUSTER_MANAGER:BOOT.HISTORY
$ WRITE BOOT_HISTORY "''F$GETSYI("BOOTTIME")' ''NODENAME' ''F$TIME()"
$ CLOSE BOOT_HISTORY
The three minutes for MINNIM between booting and writing to the file is
about what I expect. JANDER waited for MINNIM to boot (quorum is 2), so
that explains the almost three-hour wait between booting and writing for
JANDER, but why did MINNIM boot almost three hours after JANDER? All
the nodes lost power at the same time.
Relevant system parameters seem to be:
SHADOW_MBR_TMO 300
MVTIMEOUT 3600
SHADOW_SYS_WAIT 480
RECNXINTERVAL 20
all of which are much shorter than three hours.
More information about the Info-vax
mailing list