Event ID 1567 — Verbose Cluster Logging

Updated: November 25, 2009

Applies To: Windows Server 2008 R2

yellow

You can turn on verbose cluster logging to provide additional detail in logs for troubleshooting. However, a failover cluster can function regardless of whether verbose cluster logging is turned on.

Event Details

Product: Windows Operating System
ID: 1567
Source: Microsoft-Windows-FailoverClustering
Version: 6.1
Symbolic Name: SERVICE_FAILED_TO_CHANGE_LOG_SIZE
Message: Cluster service failed to change the trace log size. Please verify the ClusterLogSize setting with the 'Get-Cluster | Format-List *' PowerShell cmdlet. Also, use the Performance Monitor snapin to verify the event trace session settings for FailoverClustering.

Resolve

Check cluster log size settings

The Cluster service either failed to start the cluster log trace session, or failed to change the trace log size. If you do not currently have Event Viewer open, to view the event message, see "Opening Event Viewer and viewing events related to failover clustering." If the event contains an error code that you have not yet looked up, see "Finding more information about error codes that some event messages contain."

To capture detailed logs of events on a node in a failover cluster, see "Using Reliability and Performance Monitor to ensure that Event Trace Sessions are started on a node in a failover cluster." To check the current setting for the cluster log size, see "Using a command to check the setting for the cluster log size."

To perform the following procedures, you must be a member of the local Administrators group on the node in the failover cluster, or you must have been delegated the equivalent authority.

Opening Event Viewer and viewing events related to failover clustering

To open Event Viewer and view events related to failover clustering:

  1. If Server Manager is not already open, click Start, click Administrative Tools, and then click Server Manager. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  2. In the console tree, expand Diagnostics, expand Event Viewer, expand Windows Logs, and then click System.
  3. To filter the events so that only events with a Source of FailoverClustering are shown, in the Actions pane, click Filter Current Log. On the Filter tab, in the Event sources box, select FailoverClustering. Select other options as appropriate, and then click OK.
  4. To sort the displayed events by date and time, in the center pane, click the Date and Time column heading.

Finding more information about the error codes that some event messages contain

To find more information about the error codes that some event messages contain:

  1. View the event, and note the error code.
  2. Look up more information about the error code in one of two ways:

Using Reliability and Performance Monitor to ensure that Event Trace Sessions are started on a node in a failover cluster

To use Reliability and Performance Monitor to ensure that Event Trace Sessions are started on a node in a failover cluster:

  1. To open Reliability and Performance Monitor, click Start, click Administrative Tools, and then click Reliability and Performance Monitor. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  2. In the console tree, expand Data Collector Sets and then click Event Trace Sessions.
  3. In the list of event trace sessions, find the status for FailoverClustering. If it is not Running, right-click it and then click Start.

Using a command to check the setting for the cluster log size

To use a command to check the setting for the cluster log size:

  1. On the node that you are checking, click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
  2. Type:

    CLUSTER /PROP:CLUSTERLOGSIZE

Verify

To perform the following procedure, you must be a member of the local Administrators group on each clustered server, and the account you use must be a domain account, or you must have been delegated the equivalent authority.

To start the Cluster service on a node and confirm that it runs without a cluster log size error:

  1. To open the failover cluster snap-in, click Start, click Administrative Tools, and then click Failover Cluster Management. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  2. In the Failover Cluster Management snap-in, if the cluster you want to manage is not displayed, in the console tree, right-click Failover Cluster Management, click Manage a Cluster, and then select or specify the cluster that you want.
  3. If the console tree is collapsed, expand the tree under the cluster you want to manage, and then click Nodes.
  4. For each node that you want to start, right-click the node, click More Actions, and then click Start Cluster Service.
  5. In the center pane, view the status for each node. If a node reaches a status of Up, the Cluster service is started on that node.
  6. In the console tree, click Cluster Events. Confirm that events related to cluster log size are not recurring.

Related Management Information

Verbose Cluster Logging

Failover Clustering

Community Additions

ADD
Show: