event log replication

  • Thread starter Thread starter seth
  • Start date Start date
S

seth

I noticed that after applying SP4, event logs are no longer being
replicated across the nodes. I saw article 224969 on how to manually
enable it, but was wondering if anyone else had this issue and if for
some stupid reason it is disabled after applying SP4.
 
-----Original Message-----
I noticed that after applying SP4, event logs are no longer being
replicated across the nodes. I saw article 224969 on how to manually
enable it, but was wondering if anyone else had this issue and if for
some stupid reason it is disabled after applying SP4.
.

No, I haven't seen it stop replicating after applying SP4
but I wish I had. Cluster event log replication is a
silly thing anyway, better install Sentry, ECM or some
other proper enterprise event log management system. I
disable event log replication manually on all clusters
with this command:

cluster /prop EnableEventLogReplication=0
 
I am experiencing exactly the same thing after installing SP4 on a
Windows 2000 cluster.

I have noticed that Event Log Replication occurs during the Cluster
Service start up but then stops. I get the EventID 1122, "The node
(re)established communication with cluster node '<node name>' on
network '<network name>'." events replicated to the clustered nodes,
but the final cluster startup event, EventID 1062, "Microsoft
Clustering Service successfully joined the cluster." does not get
replicated to the other nodes. In looking through cluster.log on the
node where the cluster service is starting I noticed the following
difference:

Start up for successful event log replication...
------------------------------------------------
00000434.00000438::2003/06/23-20:09:19.655 [FM] FmJoinPhase2 complete,
now online!
00000434.00000438::2003/06/23-20:09:19.655 [EVT] EvOnline
00000434.00000438::2003/06/23-20:09:19.655 [EVT] Set propagation state
to 0001
00000434.00000438::2003/06/23-20:09:19.655 [EVT] Node up: 1, new
UpNodeSet: 0001
00000434.00000438::2003/06/23-20:09:19.655 [EVT] EvOnline : calling
ElfRegisterClusterSvc
00000434.00000438::2003/06/23-20:09:19.670 [EVT] EvOnline:
pPackedEventInfo->ulSize=3428
pPackedEventInfo->ulNulEventsForLogFile=2
00000434.00000438::2003/06/23-20:09:19.670 [GUM] GumSendUpdate:
queuing update type 2 context 19
00000434.00000438::2003/06/23-20:09:19.670 [GUM] GumSendUpdate:
Dispatching seq 1278 type 2 context 19 to node 2
00000434.00000438::2003/06/23-20:09:19.670 [NM] Received update to set
extended state for node 2 to 0
00000434.00000438::2003/06/23-20:09:19.670 [NM] Issuing event 0.
00000434.00000438::2003/06/23-20:09:19.670 [GUM] GumSendUpdate:
completed update seq 1278 type 2 context 19
00000434.00000438::2003/06/23-20:09:19.670 [FM] FmJoinPhase3 entry...
00000434.00000438::2003/06/23-20:09:19.670 [FM] FmJoinPhase3 exit...
00000434.00000438::2003/06/23-20:09:19.670 [INIT] Working Set changed
to [1048576, 2097152].
00000434.00000438::2003/06/23-20:09:19.670 [INIT] Cluster started.
00000434.0000047c::2003/06/23-20:09:19.670 [EVT] s_ApiEvPropEvents:
Calling into EvpPropPendingEvents, size=628...
00000434.0000047c::2003/06/23-20:09:19.670 [EVT] s_ApiEvPropEvents:
Called EvpPropPendingEvents...

Start up for unsuccessful event log replication...
------------------------------------------------
000003f8.0000041c::2003/08/09-02:05:52.125 [FM] FmJoinPhase2 complete,
now online!
000003f8.0000041c::2003/08/09-02:05:52.125 [EVT] EvOnline
000003f8.0000041c::2003/08/09-02:05:52.125 [EVT] Set propagation state
to 0001
000003f8.0000041c::2003/08/09-02:05:52.125 [EVT] Node up: 1, new
UpNodeSet: 0001
000003f8.0000041c::2003/08/09-02:05:52.125 [EVT] EvOnline : calling
ElfRegisterClusterSvc
000003f8.0000041c::2003/08/09-02:05:52.140 [EVT] EvOnline:
pPackedEventInfo->ulSize=2824
pPackedEventInfo->ulNulEventsForLogFile=2
000003f8.0000041c::2003/08/09-02:05:52.140 [GUM] GumSendUpdate:
queuing update type 2 context 19
000003f8.0000041c::2003/08/09-02:05:52.140 [GUM] GumSendUpdate:
Dispatching seq 3385 type 2 context 19 to node 2
000003f8.0000041c::2003/08/09-02:05:52.140 [NM] Received update to set
extended state for node 2 to 0
000003f8.0000041c::2003/08/09-02:05:52.140 [NM] Issuing event 0.
000003f8.0000041c::2003/08/09-02:05:52.140 [GUM] GumSendUpdate:
completed update seq 3385 type 2 context 19
000003f8.0000041c::2003/08/09-02:05:52.140 [FM] FmJoinPhase3 entry...
000003f8.0000041c::2003/08/09-02:05:52.140 [FM] FmJoinPhase3 exit...
000003f8.0000041c::2003/08/09-02:05:52.140 [INIT] Failed to set our
Min WS to 1048576, Max WS to 2097152, Status 5.
000003f8.0000041c::2003/08/09-02:05:52.140 [INIT] Cluster started.

NOTE the difference in the line before [INIT] Cluster started. I have
not been able to determine what the failure actually is.
 
Back
Top