HP StorageWorks Clustered File System 3.2.1 Windows Storage Server Edition Administration Guide (February 2006)

Chapter 17: Other Cluster Maintenance 179
HP Clustered File System Exits Immediately
If the ClusterPulse process exits immediately on starting, first determine
whether the process is running. To do this, check the Services applet in
the Control Panel or run net start on the command line and check for the
HP StorageWorks Clustered File System service. Also use the Event
Viewer program (Start > Programs > Administrative Tools > Event
Viewer) to view the event log.
This problem typically occurs because either the hostname is not set
properly on the server or the main Ethernet interface is not installed. To
check this, consult the Networks applet (located in the Control Panel) and
the %WINDIR%\system32\drivers\etc\hosts file.
Troubleshoot Monitor Problems
You may encounter the following problems with service and device
monitors.
Monitor Status
If the monitor status is not reported as Up, check the last error message
string and the last event message string that monitor_agent returned to
HP Clustered File System for any service or device monitor on any server
in the cluster. The error or event message provides more status
information.
“Down” Status
The “Down” status indicates that the monitor finished its probe but it did
not complete successfully. Depending on the monitor type (such as HTTP
or SMTP), the service monitor probe may involve more than being able to
connect to the network service.
For many built-in service monitors, HP Clustered File System may
conclude that the monitor is down even if the TCP connection succeeds.
For example, if a Web server is available but the URL specified in the
HTTP service monitor was not found, the HTTP service monitor will be
reported as Down.