- services with a dependency on another service that just recovered went in a recoverable state themselves even though
May 29 15:17:53 node1 rgmanager: Marking service service:nfs01 on down member 3 as stopped May 29 15:17:53 node1 rgmanager: Starting service:nfst01 on [ 1 2 5 4 6 ] May 29 15:18:27 node1 rgmanager: recover on oracledb "Q11" returned 1 (generic error) May 29 15:18:27 node1 rgmanager: Stopping service service:orat01
May 29 15:18:27 node2 rgmanager: recover on oracledb "SQ1" returned 1 (generic error) May 29 15:18:27 node2 rgmanager: Stopping service service:ora03
- We have services that are dependent on another service to start, but operationally oracle do not need it and should not fail when it fails. Since the dependency is soft, why were these affected when the depend service failed?
- Red Hat Enterprise Linux (RHEL) 6 with the High Availability Add On
- One or more services with a soft service dependency in `/etc/cluster/cluster.conf:
<service name="service1" ...> [...] <service name="service2" `depend="service:service1" depend_mode="soft" ...>
- The dependency service (
service1in the example above) has failed or the node it was running on was failed, leading to recovery
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.