Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. The Cluster services fail on all nodes after you shut down the cluster node that owns the quorum disk resource in Windows Server 2008 SP2

The Cluster services fail on all nodes after you shut down the cluster node that owns the quorum disk resource in Windows Server 2008 SP2

View products that this article applies to.

Symptoms

Consider the following scenario:
  • You configure a failover cluster on some computers that are running Windows Server 2008 Service Pack 2 (SP2).
  • You use the No Majority: Disk Only quorum mode in the cluster.
  • The node that owns the cluster group that has a quorum disk resource tries to stop the Cluster service.
In this scenario, the Cluster outage occurs on all nodes.

Additionally, an instance of event ID 7024 that resembles the following is logged in the System log:

↑ Back to the top

Cause

This issue occurs because of a deadlock that causes a timer to expire. This timer terminates the Cluster services.

The timer that terminates the Cluster services is set when the quorum disk resource is offline on a node. The Cluster service on the cluster node that owns the quorum disk resource enters a deadlock state during the shutdown process. However, the Cluster services on all nodes fail if the quorum disk resource is not online on another node when the timer expires. Therefore, the Cluster services on all nodes fail when the quorum disk resource is not online when the timer expires.

Note This timer that terminates the Cluster services is called "death timer" in the Cluster logs.

↑ Back to the top

Resolution

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must be running Windows Server 2008 SP2 on the computer. Additionally, the failover cluster feature must be installed on the computer.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows Server 2008 file information notes
Important Windows Vista hotfixes and Windows Server 2008 hotfixes are included in the same packages. However, only "Windows Vista" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows Vista" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
  • The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.
    VersionProductSR_LevelService branch
    6.0.600
    2.
    22xxx    		Windows Vista and Windows Server 2008SP2LDR
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008" section. MUM files and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintaining the state of the updated component. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows Server 2008
File nameFile versionFile sizeDateTimePlatform
Clussvc.exe6.0.6002.223482,338,30425-Feb-201013:24x86
For all supported x64-based versions of Windows Server 2008
File nameFile versionFile sizeDateTimePlatform
Clussvc.exe6.0.6002.223483,864,57625-Feb-201013:35x64
For all supported IA-64-based versions of Windows Server 2008
File nameFile versionFile sizeDateTimePlatform
Clussvc.exe6.0.6002.223486,469,63225-Feb-201013:31IA-64

↑ Back to the top

Workaround

Workaround for Windows Server 2008

To work around this issue, increase the value for the QuorumArbitrationTimeMax setting. To set the value for the QuorumArbitrationTimeMax setting explicitly, at the command prompt, type the following command, and then press ENTER:
cluster /prop quorumarbitrationtimemax=90
Note The value of this setting depends on the environment. Therefore, the value may have to be adjusted to a larger value. If you increase the value to 120, and if this issue still occurs, install this hotfix because this workaround cannot resolve the issue.

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top

More Information

For more information about the cluster command, visit the following Microsoft Web site:
General information about cluster command
For more information about the quorum modes, visit the following Microsoft Web site:
General information about quorum modes
For more information about how to configure the quorum in a failover cluster, visit the following Microsoft Web site:
Step-by-step guide to configure the quorum in a failover cluster
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Additional file information

Additional file information for Windows Server 2008

Additional files for all supported x86-based versions of Windows Server 2008
File nameUpdate.mum
File versionNot applicable
File size2,224
Date (UTC)26-Feb-2010
Time (UTC)01:08
PlatformNot applicable
File nameX86_5f10021605c22a9c2444dae29a471933_31bf3856ad364e35_6.0.6002.22348_none_296c6306fc1968c1.manifest
File versionNot applicable
File size711
Date (UTC)26-Feb-2010
Time (UTC)01:08
PlatformNot applicable
File nameX86_microsoft-windows-f..overcluster-clussvc_31bf3856ad364e35_6.0.6002.22348_none_bc0e841eb7e8eecd.manifest
File versionNot applicable
File size15,117
Date (UTC)25-Feb-2010
Time (UTC)17:47
PlatformNot applicable
Additional files for all supported x64-based versions of Windows Server 2008
File nameAmd64_7a8adc3f13c2bde700ff5aed2d0235fb_31bf3856ad364e35_6.0.6002.22348_none_8289eabf326ba975.manifest
File versionNot applicable
File size1,072
Date (UTC)26-Feb-2010
Time (UTC)01:08
PlatformNot applicable
File nameAmd64_microsoft-windows-f..overcluster-clussvc_31bf3856ad364e35_6.0.6002.22348_none_182d1fa270466003.manifest
File versionNot applicable
File size15,155
Date (UTC)25-Feb-2010
Time (UTC)17:24
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size2,240
Date (UTC)26-Feb-2010
Time (UTC)01:08
PlatformNot applicable
File nameWow64_microsoft-windows-f..overcluster-clussvc_31bf3856ad364e35_6.0.6002.22348_none_2281c9f4a4a721fe.manifest
File versionNot applicable
File size4,510
Date (UTC)25-Feb-2010
Time (UTC)17:37
PlatformNot applicable
Additional files for all supported IA-64-based versions of Windows Server 2008
File nameIa64_e9f0268b80c5f42a6ec292cb99479202_31bf3856ad364e35_6.0.6002.22348_none_175041df87868371.manifest
File versionNot applicable
File size1,070
Date (UTC)26-Feb-2010
Time (UTC)01:08
PlatformNot applicable
File nameIa64_microsoft-windows-f..overcluster-clussvc_31bf3856ad364e35_6.0.6002.22348_none_bc102814b7e6f7c9.manifest
File versionNot applicable
File size15,136
Date (UTC)25-Feb-2010
Time (UTC)17:06
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size1,581
Date (UTC)26-Feb-2010
Time (UTC)01:08
PlatformNot applicable
File nameWow64_microsoft-windows-f..overcluster-clussvc_31bf3856ad364e35_6.0.6002.22348_none_2281c9f4a4a721fe.manifest
File versionNot applicable
File size4,510
Date (UTC)25-Feb-2010
Time (UTC)17:37
PlatformNot applicable

↑ Back to the top

Logging information

The following is a sample of the Cluster log when the issue occurs:
00000264.00000938::2009/08/04-19:03:00.727 INFO  [QUORUM] Node 3: quorum is arbitrated by node 1

00000264.00000938::2009/08/04-19:06:10.379 INFO  [QUORUM] Node 3: quorum is not owned by anyone
00000264.00000938::2009/08/04-19:06:10.379 WARN  [QUORUM] Node 3: One off quorum (1 2 3)
00000264.00000938::2009/08/04-19:06:10.379 INFO  [QUORUM] Node 3: death timer is started at 2009/08/04-19:06:10.379 and expires in 20 seconds
00000264.00001b3c::2009/08/04-19:06:31.357 ERR   [QUORUM] Node 3: Death timer expired after 20 seconds (death timer started at 2009/08/04-19:06:10.379). Lost quorum.
00000264.00001b3c::2009/08/04-19:06:31.357 ERR   lost quorum (status = 5925)
00000264.00001b3c::2009/08/04-19:06:31.357 ERR   FatalError is Calling Exit Process.
00000264.00000734::2009/08/04-19:06:31.358 INFO  [CS] About to exit process...

↑ Back to the top

Keywords: kb, kbclustering, kbsurveynew, kbexpertiseadvanced, kbqfe, kbautohotfix, kbhotfixserver, kbfix

↑ Back to the top

Article Info
Article ID : 975486
Revision : 1
Created on : 1/7/2017
Published on : 10/10/2011
Exists online : False
Views : 189