Error Code details
Severity: Warning 
Component: Cluster Server 
Retry Interval is %s at fault %s

The hashadow process generates this message. When the Veritas Cluster Server (VCS) high availability daemon (HAD) dies, hashadow restarts it after a specific time interval. If the restart fails, hashadow tries again, but with each failure the time interval increases by a fixed amount. The default is 10 seconds.  You would see messages similar to the following:

2010/11/29 13:56:55 VCS WARNING V-16-1-11277 Retry Interval is 10 at fault 1
2010/11/29 13:57:20 VCS WARNING V-16-1-11277 Retry Interval is 20 at fault 2
2010/11/29 13:58:06 VCS WARNING V-16-1-11277 Retry Interval is 30 at fault 3
2010/11/29 13:58:45 VCS WARNING V-16-1-11277 Retry Interval is 40 at fault 4
2010/11/29 13:59:44 VCS WARNING V-16-1-11277 Retry Interval is 50 at fault 5


These messages show the intervals hashadow waits before it restarts HAD. The limit is 5 restarts. If the restart fails 6 times, hashadow does not restart HAD and VCS exits.


Veritas solutions
Solution 1 Vote: [Useful] [Not useful]
Last Modified: 2014-10-11 03:24:14 PDT
Platform: Generic
Release: Generic

To determine the possible cause of the HAD failure, do the following:


  • Go to the /var/VRTSvcs/diag directory and examine any core files whose filenames start with had.
  • Investigate the admin logs and look for messages related to Global Atomic Broadcast (GAB) around the time of the failure.


If HAD restarts fail 6 times, identify the problem from the core and log files, fix the problem, and restart VCS. If the problem persists, report it to Symantec Technical Support.

For more information on this message, see:


User solutions
No user solutions yet.


Read and accept Terms of Service