help on Resource Failure
Windows Server Forum Index Windows Server
Server discussion on Windows platform.
 
 FAQFAQ   MemberlistMemberlist     RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 
 
Google
 
Web winserverhelp.com
help on Resource Failure

 
Post new topic   Reply to topic    Windows Server Forum Index -> Clustering
Author Message
Jean
Guest
Posted: Fri Nov 04, 2005 9:50 pm    Post subject: help on Resource Failure Reply with quote
We have a two node windows 2000 cluster system here. Once everyday all the
service type resources in all the cluster groups failed at eactly same time,
and get restarted right away. I checked the cluster log. I am running out of
ideas. Any help would be greatly appcieated! Jean

cluster log entries...

Generic Service <GOES14 Disk Monitor>: Failed the IsAlive test. Current
State is 1.
Generic Service <GOES14 Disk Monitor>: Failed the IsAlive test. Current
State is 1.
Generic Service <GOES14 Auto Merge>: Failed the IsAlive test. Current State
is 1.
Generic Service <GOES14 Auto Merge>: Failed the IsAlive test. Current State
is 1.
Generic Service <GOES13 Disk Monitor>: Failed the IsAlive test. Current
State is 1.
Generic Service <GOES13 Disk Monitor>: Failed the IsAlive test. Current
State is 1.
Generic Service <GOES13 Auto Merge>: Failed the IsAlive test. Current State
is 1.
Generic Service <GOES13 Auto Merge>: Failed the IsAlive test. Current State
is 1.
[FM] NotifyCallBackRoutine: enqueuing event
[CP] CppResourceNotify for resource GOES14 Disk Monitor
[FM] NotifyCallBackRoutine: enqueuing event
[CP] CppResourceNotify for resource GOES14 Auto Merge
[FM] NotifyCallBackRoutine: enqueuing event
[CP] CppResourceNotify for resource GOES13 Disk Monitor
[FM] NotifyCallBackRoutine: enqueuing event
[CP] CppResourceNotify for resource GOES13 Auto Merge
[FM] FmpHandleResourceTransition: Resource Name =
44d0f1a6-ef84-4097-b3f2-51c02129f7ff old state=2 new state=4
[GUM] GumSendUpdate: Locker waiting type 0 context 8
[GUM] Thread 0x804 UpdateLock wait on Type 0
[GUM] DoLockingUpdate successful, lock granted to 2
[GUM] GumSendUpdate: Locker dispatching seq 1205115 type 0 context 8
[GUM] GumSendUpdate: Dispatching seq 1205115 type 0 context 8 to node 1
[GUM] GumSendUpdate: Locker updating seq 1205115 type 0 context 8
[GUM] GumpDoUnlockingUpdate releasing lock ownership
[GUM] GumSendUpdate: completed update seq 1205115 type 0 context 8
[FM] FmpPropagateResourceState: resource
44d0f1a6-ef84-4097-b3f2-51c02129f7ff failed event.
[FM] FmpHandleResourceFailure: taking resource
44d0f1a6-ef84-4097-b3f2-51c02129f7ff and dependents offline
Generic Service <GOES14 Disk Monitor>: Terminate request.
Generic Service <GOES14 Disk Monitor>: GenSvcTerminate : calling SCM
Generic Service <GOES14 Disk Monitor>: Service died; status = 1062.
[CP] CppResourceNotify for resource GOES14 Disk Monitor
[FM] RmTerminateResource: 44d0f1a6-ef84-4097-b3f2-51c02129f7ff is now offline
[FM] RestartResourceTree, Restart resource
44d0f1a6-ef84-4097-b3f2-51c02129f7ff
Back to top
Jean
Guest
Posted: Thu Nov 10, 2005 9:50 pm    Post subject: Re: help on Resource Failure Reply with quote
Thank you so much for the response. I have checked the backup jobs and
scheduled jobs and didn't find anything. Anything else I could look into?
Jean

"Rodney R. Fournier [MVP]" wrote:

Quote:
What else happens around your network at that time? Backups? Scheduled Jobs?

Cheers,

Rod

MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training

"Jean" <Jean@discussions.microsoft.com> wrote in message
news:F812E914-D7B2-41E7-A30F-F9F85D0D6146@microsoft.com...
We have a two node windows 2000 cluster system here. Once everyday all
the
service type resources in all the cluster groups failed at eactly same
time,
and get restarted right away. I checked the cluster log. I am running out
of
ideas. Any help would be greatly appcieated! Jean

cluster log entries...

Generic Service <GOES14 Disk Monitor>: Failed the IsAlive test. Current
State is 1.
Generic Service <GOES14 Disk Monitor>: Failed the IsAlive test. Current
State is 1.
Generic Service <GOES14 Auto Merge>: Failed the IsAlive test. Current
State
is 1.
Generic Service <GOES14 Auto Merge>: Failed the IsAlive test. Current
State
is 1.
Generic Service <GOES13 Disk Monitor>: Failed the IsAlive test. Current
State is 1.
Generic Service <GOES13 Disk Monitor>: Failed the IsAlive test. Current
State is 1.
Generic Service <GOES13 Auto Merge>: Failed the IsAlive test. Current
State
is 1.
Generic Service <GOES13 Auto Merge>: Failed the IsAlive test. Current
State
is 1.
[FM] NotifyCallBackRoutine: enqueuing event
[CP] CppResourceNotify for resource GOES14 Disk Monitor
[FM] NotifyCallBackRoutine: enqueuing event
[CP] CppResourceNotify for resource GOES14 Auto Merge
[FM] NotifyCallBackRoutine: enqueuing event
[CP] CppResourceNotify for resource GOES13 Disk Monitor
[FM] NotifyCallBackRoutine: enqueuing event
[CP] CppResourceNotify for resource GOES13 Auto Merge
[FM] FmpHandleResourceTransition: Resource Name =
44d0f1a6-ef84-4097-b3f2-51c02129f7ff old state=2 new state=4
[GUM] GumSendUpdate: Locker waiting type 0 context 8
[GUM] Thread 0x804 UpdateLock wait on Type 0
[GUM] DoLockingUpdate successful, lock granted to 2
[GUM] GumSendUpdate: Locker dispatching seq 1205115 type 0 context 8
[GUM] GumSendUpdate: Dispatching seq 1205115 type 0 context 8 to node 1
[GUM] GumSendUpdate: Locker updating seq 1205115 type 0 context 8
[GUM] GumpDoUnlockingUpdate releasing lock ownership
[GUM] GumSendUpdate: completed update seq 1205115 type 0 context 8
[FM] FmpPropagateResourceState: resource
44d0f1a6-ef84-4097-b3f2-51c02129f7ff failed event.
[FM] FmpHandleResourceFailure: taking resource
44d0f1a6-ef84-4097-b3f2-51c02129f7ff and dependents offline
Generic Service <GOES14 Disk Monitor>: Terminate request.
Generic Service <GOES14 Disk Monitor>: GenSvcTerminate : calling SCM
Generic Service <GOES14 Disk Monitor>: Service died; status = 1062.
[CP] CppResourceNotify for resource GOES14 Disk Monitor
[FM] RmTerminateResource: 44d0f1a6-ef84-4097-b3f2-51c02129f7ff is now
offline
[FM] RestartResourceTree, Restart resource
44d0f1a6-ef84-4097-b3f2-51c02129f7ff


Back to top
Rodney R. Fournier [MVP]
Guest
Posted: Thu Nov 10, 2005 9:50 pm    Post subject: Re: help on Resource Failure Reply with quote
What else happens around your network at that time? Backups? Scheduled Jobs?

Cheers,

Rod

MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training

"Jean" <Jean@discussions.microsoft.com> wrote in message
news:F812E914-D7B2-41E7-A30F-F9F85D0D6146@microsoft.com...
Quote:
We have a two node windows 2000 cluster system here. Once everyday all
the
service type resources in all the cluster groups failed at eactly same
time,
and get restarted right away. I checked the cluster log. I am running out
of
ideas. Any help would be greatly appcieated! Jean

cluster log entries...

Generic Service <GOES14 Disk Monitor>: Failed the IsAlive test. Current
State is 1.
Generic Service <GOES14 Disk Monitor>: Failed the IsAlive test. Current
State is 1.
Generic Service <GOES14 Auto Merge>: Failed the IsAlive test. Current
State
is 1.
Generic Service <GOES14 Auto Merge>: Failed the IsAlive test. Current
State
is 1.
Generic Service <GOES13 Disk Monitor>: Failed the IsAlive test. Current
State is 1.
Generic Service <GOES13 Disk Monitor>: Failed the IsAlive test. Current
State is 1.
Generic Service <GOES13 Auto Merge>: Failed the IsAlive test. Current
State
is 1.
Generic Service <GOES13 Auto Merge>: Failed the IsAlive test. Current
State
is 1.
[FM] NotifyCallBackRoutine: enqueuing event
[CP] CppResourceNotify for resource GOES14 Disk Monitor
[FM] NotifyCallBackRoutine: enqueuing event
[CP] CppResourceNotify for resource GOES14 Auto Merge
[FM] NotifyCallBackRoutine: enqueuing event
[CP] CppResourceNotify for resource GOES13 Disk Monitor
[FM] NotifyCallBackRoutine: enqueuing event
[CP] CppResourceNotify for resource GOES13 Auto Merge
[FM] FmpHandleResourceTransition: Resource Name =
44d0f1a6-ef84-4097-b3f2-51c02129f7ff old state=2 new state=4
[GUM] GumSendUpdate: Locker waiting type 0 context 8
[GUM] Thread 0x804 UpdateLock wait on Type 0
[GUM] DoLockingUpdate successful, lock granted to 2
[GUM] GumSendUpdate: Locker dispatching seq 1205115 type 0 context 8
[GUM] GumSendUpdate: Dispatching seq 1205115 type 0 context 8 to node 1
[GUM] GumSendUpdate: Locker updating seq 1205115 type 0 context 8
[GUM] GumpDoUnlockingUpdate releasing lock ownership
[GUM] GumSendUpdate: completed update seq 1205115 type 0 context 8
[FM] FmpPropagateResourceState: resource
44d0f1a6-ef84-4097-b3f2-51c02129f7ff failed event.
[FM] FmpHandleResourceFailure: taking resource
44d0f1a6-ef84-4097-b3f2-51c02129f7ff and dependents offline
Generic Service <GOES14 Disk Monitor>: Terminate request.
Generic Service <GOES14 Disk Monitor>: GenSvcTerminate : calling SCM
Generic Service <GOES14 Disk Monitor>: Service died; status = 1062.
[CP] CppResourceNotify for resource GOES14 Disk Monitor
[FM] RmTerminateResource: 44d0f1a6-ef84-4097-b3f2-51c02129f7ff is now
offline
[FM] RestartResourceTree, Restart resource
44d0f1a6-ef84-4097-b3f2-51c02129f7ff
Back to top
 
Post new topic   Reply to topic    Windows Server Forum Index -> Clustering All times are GMT
Page 1 of 1

 
 You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum




New Topics Powered by phpBB