unexpected offline of a resource is not logged as FAULTED in the engine log
Here is a simpletest . Ihave a fileonoff resource . i delete the file .The resource becomes faulted. In the enginelog there is no mention of the resource being faulted.and the clean action is taken This does not matter if the resource is a critical or not also the type of the resource. this happens in 4.0, 4.1 and 5.0 as well but when the DBG_TRACEis added it displays as RESOURCEFAULTED. Steps to reproduce the issue 1. create a sg with one fileonoff resource 2. online the SG . 3. rm the file configured. check the engine log ass tags halog -addtags DBG_TRACE Now perform the same operation you can see the difference. Noticed that only when "monitor times out" the faulted message is in the engine log. From the user's guide it is not that clear whether it will hog the FAULTEDmessage of not: VCS considers a resource faulted in the following situations: ■ When the resource state changes unexpectedly. For example, an online resource going offline. <<<< ■ When a required state change does not occur. For example, a resource failing to go online or offline when commanded to do so. In many situations, VCS agents take predefined actions to correct the issue before reporting resource failure to the engine. For example, the agent may try to bring a resource online several times before declaring a fault. When a resource faults, VCS takes automated actions to “clean up the faulted resource. The Clean function makes sure the resource is completely shut down before bringing it online on another node. This prevents concurrency violations. When a resource faults, VCS takes all resources dependent on the faulted resource offline. The fault is thus propagated in the service group