Logging When Running the Cluster Service With the –debug Option

If diagnostic logging is enabled and the Cluster service fails to start because of a logon error for the service account or another system-related error, the Cluster service might not have a chance to run, and the log file might be empty. If there was a previously existing log file, that file might persist.

An alternative is to run the Cluster service temporarily from a command prompt, with the -debug option set. Before running the Cluster service with the -debug option, consider the following:

• This method runs the Cluster service outside the normal environment provided by the Service Control Manager.
• To use these procedures, you must be logged on with administrative rights, so you must be logged on with the same account you usually use to run the Cluster service or with the computer's administrator account.
• Do not use the -debug option for normal use. The Cluster service does not run as efficiently when this option is set.

To run the Cluster service from a command prompt

1. Open a new command prompt window.
2. Change directories to the cluster directory on the local system.

   The local cluster directory is %SystemRoot%\luster.

3. At the command prompt, type the following:

   CLUSSVC -debug

   In the command prompt window, the Cluster service prints output similar to entries written when running the Cluster service without the -debug option.

To print the Cluster service output to a file

• At the command prompt, start the Cluster service by typing the following command:

  CLUSSVC -debug > c:\debug.log\

Note

When you run Clussvc.exe from a command window, the Resource Monitor does not output to that window. The Resource Monitor is a separate process and does not write to the window used by Clussvc.exe.

© 1985-2000 Microsoft Corporation. All rights reserved.