Windows Server

dfemiani · Guest

We have 2 nodes on a cluster currently managed via cluadmin (Windows Server
2003). Both servers on the cluster were needing a restart, and I restarted
the inactive node first. When that server came back up, I ran cluadmin and I
got an error saying that the Cluster Service wasn't started, would you like
to start it? I click yes and it works for about 1 minute and then I get the
following errors:

|| Could not start the Cluster Service service on LOCAL

Error 1053: The service did not respond to the start or control request in a
timely fashion ||

I click OK then get the following:

|| An error occured attempting to start the Cluser Service on node LOCAL.

The service did not respond to the start or control request in a timely
fashion.

Error ID: -2147023843 (8007041d). ||

In the event log have the following two events:

|| The node cannot join the server cluster because it cannot communicate
with node NODE2 over any network configured for internal server cluster
communication. Check the network configuration of the node and the server
cluster. ||

|| The Cluster Service service terminated unexpectedly. It has done this 18
time(s). The following corrective action will be taken in 960000
milliseconds: Restart the service. ||

Any thoughts or help would be greatly appreciated!

Dave

IWSEC · Guest

Hi
The errors indicate that there is a problem with the internal
communications stopping the inactive node from communicating with the active
node - possible issues could be:

1. No network connectivity - NIC card or cable fault
2. The NIC's have differnet speed and duplex settings - this can be a
problem if you have the NIC's set to autodetect. It's best to set them to
specific settings e.g. 100Mb Full.

I'd check the internal NIC to see if it can ping or browse the active node
first.

Cheers
iwsec

"dfemiani" wrote:

	Windows Server Forum Index -> Clustering	All times are GMT
Page 1 of 1