● Appendix B: Using and Reading the Cluster Lo - 荔园在线 | 深圳大学学生论坛,荔园晨风BBS,深大在线网站

荔园之美，在春之萌芽，在夏之绽放，在秋之收获，在冬之沉淀

发信人: Jobs (温少), 信区: WinNT
标  题: Appendix B: Using and Reading the Cluster Logfile
发信站: BBS 荔园晨风站 (Sun Nov 28 12:58:20 1999), 站内信件

Appendix B: Using and Reading the Cluster Logfile
CLUSTERLOG Environment Variable
If you set the CLUSTERLOG environment variable, the cluster will create a
logfile that contains diagnostic information using the path specified.
Important events during the operation of the Cluster Service will be logged in
this file. Because so many different events occur, the logfile may be somewhat
cryptic or hard to read. This document gives some hints about how to read the
logfile and information about what items to look for.

Note   Each time you attempt to start the Cluster Service, the log will be
cleared and a new logfile started. Each component of MSCS that places an entry
in the logfile will indicate itself by abbreviation in square brackets. For
example, the Node Manager component would be abbreviated [NM]. Logfile entries
will vary from one cluster to another. As a result, other logfiles may vary
from excerpts referenced in this document.

Note   Log entry lines in the following sections have been wrapped for space
constraints in this document. The lines do not normally wrap.

Operating System Version Number and Service Pack Level
Near the beginning of the logfile, notice the build number of MSCS, followed by
the operating system version number and service pack level. If you call for
support, engineers may ask for this information:

082::14-21:29:26.625 Cluster Service started - Cluster Version 1.224.
082::14-21:29:26.625   OS Version 4.0.1381 - Service Pack 3.

Cluster Service Startup
Following the version information, some initialization steps occur. Those steps
are followed by an attempt to join the cluster, if one node already exists in a
running state. If the Cluster Service could not detect any other cluster
members, it will attempt to form the cluster. Consider the following log
entries:

0b5::12-20:15:23.531 We're initing Ep...
0b5::12-20:15:23.531 [DM]: Initialization
0b5::12-20:15:23.531 [DM] DmpRestartFlusher: Entry
0b5::12-20:15:23.531 [DM] DmpStartFlusher: Entry
0b5::12-20:15:23.531 [DM] DmpStartFlusher: thread created
0b5::12-20:15:23.531 [NMINIT] Initializing the Node Manager...
0b5::12-20:15:23.546 [NMINIT] Local node name = NODEA.
0b5::12-20:15:23.546 [NMINIT] Local node ID = 1.
0b5::12-20:15:23.546 [NM] Creating object for node 1 (NODEA)
0b5::12-20:15:23.546 [NM] node 1 state 1
0b5::12-20:15:23.546 [NM] Initializing networks.
0b5::12-20:15:23.546 [NM] Initializing network interface facilities.
0b5::12-20:15:23.546 [NMINIT] Initialization complete.
0b5::12-20:15:23.546 [FM] Starting worker thread...
0b5::12-20:15:23.546 [API] Initializing
0a9::12-20:15:23.546 [FM] Worker thread running
0b5::12-20:15:23.546 [lm] :LmInitialize Entry.
0b5::12-20:15:23.546 [lm] :TimerActInitialize Entry.
0b5::12-20:15:23.546 [CS] Initializing RPC server.
0b5::12-20:15:23.609 [INIT] Attempting to join cluster MDLCLUSTER
0b5::12-20:15:23.609 [JOIN] Spawning thread to connect to sponsor
192.88.80.114
06c::12-20:15:23.609 [JOIN] Asking 192.88.80.114 to sponsor us.
0b5::12-20:15:23.609 [JOIN] Waiting for all connect threads to terminate.
06c::12-20:15:32.750 [JOIN] Sponsor 192.88.80.114 is not available,
status=1722.
0b5::12-20:15:32.750 [JOIN] All connect threads have terminated.
0b5::12-20:15:32.750 [JOIN] Unable to connect to any sponsor node.
0b5::12-20:15:32.750 [INIT] Failed to join cluster, status 53
0b5::12-20:15:32.750 [INIT] Attempting to form cluster MDLCLUSTER
0b5::12-20:15:32.750 [Ep]: EpInitPhase1
0b5::12-20:15:32.750 [API] Online read only
04b::12-20:15:32.765 [RM] Main: Initializing.

Note that the cluster service attempts to join the cluster. If it cannot
connect with an existing member, the software decides to form the cluster. The
next series of steps attempts to form groups and resources necessary to
accomplish this task. It is important to note that the cluster service must
arbitrate control of the quorum disk.

0b5::12-20:15:32.781 [FM] Creating group a1a13a86-0eaf-11d1-8427-
0000f8034599
0b5::12-20:15:32.781 [FM] Group a1a13a86-0eaf-11d1-8427-0000f8034599
contains a1a13a87-0eaf-11d1-8427-0000f8034599.
0b5::12-20:15:32.781 [FM] Creating resource a1a13a87-0eaf-11d1-8427-
0000f8034599
0b5::12-20:15:32.781 [FM] FmpAddPossibleEntry adding 1 to a1a13a87-0eaf-
11d1-8427-0000f8034599 possible node list
0b5::12-20:15:32.781 [FMX] Found the quorum resource a1a13a87-0eaf-11d1-
8427-0000f8034599.
0b5::12-20:15:32.781 [FM] All dependencies for a1a13a87-0eaf-11d1-8427-
0000f8034599 created
0b5::12-20:15:32.781 [FM] arbitrate for quorum resource id a1a13a87-0eaf-
11d1-8427-0000f8034599.
0b5::12-20:15:32.781 FmpRmCreateResource: creating resource a1a13a87-0eaf-
11d1-8427-0000f8034599 in shared resource monitor
0b5::12-20:15:32.812 FmpRmCreateResource: created resource a1a13a87-0eaf-
11d1-8427-0000f8034599, resid 1363016
0dc::12-20:15:32.828 Physical Disk <Disk D:>: Arbitrate returned status 0.
0b5::12-20:15:32.828 [FM] FmGetQuorumResource successful
0b5::12-20:15:32.828 FmpRmOnlineResource: bringing resource a1a13a87-0eaf-
11d1-8427-0000f8034599 (resid 1363016) online.
0b5::12-20:15:32.843 [CP] CppResourceNotify for resource Disk D:
0b5::12-20:15:32.843 [GUM] GumSendUpdate: Locker waiting
      type 0 context 8
0b5::12-20:15:32.843 [GUM] Thread 0xb5 UpdateLock wait on Type 0
0b5::12-20:15:32.843 [GUM] DoLockingUpdate successful, lock granted to 1
0b5::12-20:15:32.843 [GUM] GumSendUpdate: Locker dispatching seq 388
      type 0 context 8
0b5::12-20:15:32.843 [GUM] GumpDoUnlockingUpdate releasing lock ownership
0b5::12-20:15:32.843 [GUM] GumSendUpdate: completed update seq 388
      type 0 context 8
0b5::12-20:15:32.843 [GUM] GumSendUpdate: Locker waiting
      type 0 context 9
0b5::12-20:15:32.843 [GUM] Thread 0xb5 UpdateLock wait on Type 0
0b5::12-20:15:32.843 [GUM] DoLockingUpdate successful, lock granted to 1
0b5::12-20:15:32.843 [GUM] GumSendUpdate: Locker dispatching seq 389
      type 0 context 9
0b5::12-20:15:32.843 [GUM] GumpDoUnlockingUpdate releasing lock ownership
0b5::12-20:15:32.843 [GUM] GumSendUpdate: completed update seq 389
      type 0 context 9
0b5::12-20:15:32.843 FmpRmOnlineResource: Resource a1a13a87-0eaf-11d1-
8427-0000f8034599 pending
0e1::12-20:15:33.359 Physical Disk <Disk D:>: Online, created registry
watcher thread.
090::12-20:15:33.359 [FM] NotifyCallBackRoutine: enqueuing event
04d::12-20:15:33.359 [FM] WorkerThread, processing transition event for
a1a13a87-0eaf-11d1-8427-0000f8034599, oldState = 129, newState = 2.
04d::12-20:15:33.359 [FM] HandleResourceTransition: Resource Name =
a1a13a87-0eaf-11d1-8427-0000f8034599 old state=129 new state=2
04d::12-20:15:33.359 [DM] DmpQuoObjNotifyCb: Quorum resource is online
04d::12-20:15:33.375 [DM] DmpQuoObjNotifyCb: Own quorum resource, try open
the quorum log
04d::12-20:15:33.375 [DM] DmpQuoObjNotifyCb: the name of the quorum file
is D:\MSCS\quolog.log
04d::12-20:15:33.375 [lm] LogCreate : Entry FileName=D:\MSCS\quolog.log
MaxFileSize=0x00010000
04d::12-20:15:33.375 [lm] LogpCreate : Entry

In this case, the node forms the cluster group and quorum disk resource, gains
control of the disk, and opens the quorum logfile. From here, the cluster
performs operations with the logfile, and proceeds to form the cluster. This
involves configuring network interfaces and bringing them online.

0b5::12-20:15:33.718 [NM] Beginning form process.
0b5::12-20:15:33.718 [NM] Synchronizing node information.
0b5::12-20:15:33.718 [NM] Creating node objects.
0b5::12-20:15:33.718 [NM] Configuring networks & interfaces.
0b5::12-20:15:33.718 [NM] Synchronizing network information.
0b5::12-20:15:33.718 [NM] Synchronizing interface information.
0b5::12-20:15:33.718 [dm] DmBeginLocalUpdate Entry
0b5::12-20:15:33.718 [dm] DmBeginLocalUpdate Exit, pLocalXsaction=0x00151c20
dwError=0x00000000
0b5::12-20:15:33.718 [NM] Setting database entry for interface a1a13a7f-
0eaf-11d1-8427-0000f8034599
0b5::12-20:15:33.718 [dm] DmCommitLocalUpdate Entry
0b5::12-20:15:33.718 [dm] DmCommitLocalUpdate Exit, dwError=0x00000000
0b5::12-20:15:33.718 [dm] DmBeginLocalUpdate Entry
0b5::12-20:15:33.875 [dm] DmBeginLocalUpdate Exit,
pLocalXsaction=0x00151c20 dwError=0x00000000
0b5::12-20:15:33.875 [NM] Setting database entry for interface a1a13a81-
0eaf-11d1-8427-0000f8034599
0b5::12-20:15:33.875 [dm] DmCommitLocalUpdate Entry
0b5::12-20:15:33.875 [dm] DmCommitLocalUpdate Exit, dwError=0x00000000
0b5::12-20:15:33.875 [NM] Matched 2 networks, created 0 new networks.
0b5::12-20:15:33.875 [NM] Resynchronizing network information.
0b5::12-20:15:33.875 [NM] Resynchronizing interface information.
0b5::12-20:15:33.875 [NM] Creating network objects.
0b5::12-20:15:33.875 [NM] Creating object for network a1a13a7e-0eaf-11d1-
8427-0000f8034599
0b5::12-20:15:33.875 [NM] Creating object for network a1a13a80-0eaf-11d1-
8427-0000f8034599
0b5::12-20:15:33.875 [NM] Creating interface objects.
0b5::12-20:15:33.875 [NM] Creating object for interface a1a13a7f-0eaf-
11d1-8427-0000f8034599.
0b5::12-20:15:33.875 [NM] Registering network a1a13a7e-0eaf-11d1-8427-
0000f8034599 with cluster transport.
0b5::12-20:15:33.875 [NM] Registering interfaces for network a1a13a7e-
0eaf-11d1-8427-0000f8034599 with cluster transport.
0b5::12-20:15:33.875 [NM] Registering interface a1a13a7f-0eaf-11d1-8427-
0000f8034599 with cluster transport, addr 9.9.9.2, endpoint 3003.
0b5::12-20:15:33.890 [NM] Instructing cluster transport to bring network
a1a13a7e-0eaf-11d1-8427-0000f8034599 online.
0b5::12-20:15:33.890 [NM] Creating object for interface a1a13a81-0eaf-
11d1-8427-0000f8034599.
0b5::12-20:15:33.890 [NM] Registering network a1a13a80-0eaf-11d1-8427-
0000f8034599 with cluster transport.
0b5::12-20:15:33.890 [NM] Registering interfaces for network a1a13a80-
0eaf-11d1-8427-0000f8034599 with cluster transport.
0b5::12-20:15:33.890 [NM] Registering interface a1a13a81-0eaf-11d1-8427-
0000f8034599 with cluster transport, addr 192.88.80.190, endpoint 3003.
0b5::12-20:15:33.890 [NM] Instructing cluster transport to bring network
a1a13a80-0eaf-11d1-8427-0000f8034599 online.

After initializing network interfaces, the cluster will continue formation with
the enumeration of cluster nodes. In this case, as a newly formed cluster, the
cluster will contain only one node. If this session had been joining an
existing cluster, the node enumeration would show two nodes. Next, the cluster
will bring the Cluster IP address and Cluster Name resources online.

0b5::12-20:15:34.015 [FM] OnlineGroup: setting group state to Online for
f901aa29-0eaf-11d1-8427-0000f8034599
069::12-20:15:34.015 IP address <Cluster IP address>: Created NBT
interface \Device\NetBt_If6 (instance 355833456).
0b5::12-20:15:34.015 [FM] FmpAddPossibleEntry adding 1 to a1a13a87-0eaf-
11d1-8427-0000f8034599 possible node list
0b5::12-20:15:34.015 [FM] FmFormNewClusterPhase2 complete.

--
☆ 来源:．BBS 荔园晨风站 bbs.szu.edu.cn．[FROM: bbs@192.168.11.73]

荔园在线首页友情链接：深圳大学深大招生荔园晨风BBS S-Term软件网络书店