On Sun, 2020-11-15 at 21:32 -0800, Reid Wahl wrote: > ocf:heartbeat:db2inst isn't a resource agent that ClusterLabs > maintains, so we have no insight into how it works and why it's in > Started state. I don't know based on the output what resource agent > db2_db2ins11_db2ins11_QUERYDB is using. > > I recommend that you take a look at the resource agent's monitor > function and see what it's actually checking. Then you can determine > why the monitor operation is succeeding, and you can modify the > function so that the monitor operation will fail when the DB is down.
And make sure that you actually configured a recurring monitor. By default Pacemaker doesn't care what happens to a resource after it's started; you need a monitor to periodically check its status in order to recover it after a failure. Also, make sure fencing is enabled, configured, and tested. For certain failure scenarios, such as a failed stop operation or an unreachable node, fencing is the only safe way to recover. > On Sun, Nov 15, 2020 at 8:52 AM Guy Przytula < > guy.przyt...@infocura.be> wrote: > > I have installed latest version of pacemaker on redhat 8 > > I wanted to test it out for a cluster for IBM Db2 > > There is only one issue : > > I have 2 nodes : nodep and nodes > > the database/instance resource are primary on nodep > > if I stop the process (db2) on nodes : it is automatically started > > : ok > > now I renamed the startup command, so the process can not startup > > anymore > > I see the process is down : but the status of cluster is normal > > in the screen you can see : msg : no start database .... > > go to root : execute crm status : all started .... > > > > -- > > Best Regards, Beste Groeten, Meilleures Salutations > > Guy Przytula > > > > Tel. GSM : +32 (0)475-33.81.86 > > > > Email : Guy Przytula > > > > > > > > > > > > > > Infocura - Tel : +32 (0) 478 32 83 54 -- Ken Gaillot <kgail...@redhat.com> _______________________________________________ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/