Description of problem: in case of ricci service crash rgmanager fail to see ans alert about the issue. 1. kill ricci service 853 ps -aux | grep ricci 854 kill -9 5638 [root@green-vdsb ~]# service ricci status ricci dead but pid file exists 2. the system will not alert about the issue. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
rgmanager is entirely configuration-driven; it does not monitor most things. ricci is an optional service which is not required to run rgmanager nor the rest of the cluster software. It's possible to make rgmanager monitor system-local services. For example, if you had a 3-node cluster and you wanted to start and monitor specific services on each of them (ex: ricci on all 3 nodes, httpd on node 2, ricci & nfsd on node3), you could do the following: <failoverdomains> <failoverdomain name="node1" restricted="1"> <failoverdomain name="node1" restricted="1"/> </failoverdomain> <failoverdomain name="node2" restricted="1"> <failoverdomain name="node2" restricted="1"/> </failoverdomain> <failoverdomain name="node3" restricted="1"> <failoverdomain name="node3" restricted="1"/> </failoverdomain> </failoverdomains> <rm> <resources> <script name="ricci" file="/etc/init.d/ricci" /> <script name="httpd" file="/etc/init.d/httpd" /> <script name="nfs" file="/etc/init.d/nfs" /> </resources> <service name="monitor-node1" domain="node1"> <script ref="ricci" /> </service> <service name="monitor-node2" domain="node2"> <script ref="ricci" /> <script ref="httpd" /> </service> <service name="monitor-node3" domain="node3"> <script ref="ricci" /> <script ref="nfs" /> </service> </rm> Note that services which you expect rgmanager to start and monitor, you should chkconfig off.