[SOLVED] Pacemaker Resource showing as "unrunnable start (blocked)" for each cluster resource

tooreply · 05-12-2020, 10:09 AM

OS and Pacemaker Versions:

PRETTY_NAME="SUSE Linux Enterprise Server 12 SP4"
CPE_NAME="cpe:/o:suse:sles_sap:12:sp4"

# pacemakerd --version
Pacemaker 1.1.19+20181105.ccd6b5b10-3.16.1

# corosync -v
Corosync Cluster Engine, version '2.3.6'

When cluster resources are running on glbgvldbies01, everything is fine, but when glbgvldbies01 is rebooted or down for some reason, the resource are not able to start on glbgvldbies02, We are getting the following error

Resource showing as "unrunnable start (blocked)"

Pacemaker Log:

https://drive.google.com/open?id=1qf...TDsNjLyVZ1f7TI

TB0ne · 05-12-2020, 10:55 AM

Quote:

Originally Posted by tooreply

OS and Pacemaker Versions:

PRETTY_NAME="SUSE Linux Enterprise Server 12 SP4"
CPE_NAME="cpe:/o:suse:sles_sap:12:sp4"

# pacemakerd --version
Pacemaker 1.1.19+20181105.ccd6b5b10-3.16.1

# corosync -v
Corosync Cluster Engine, version '2.3.6'

When cluster resources are running on glbgvldbies01, everything is fine, but when glbgvldbies02 is rebooted or down for some reason, the resource are not able to start on glbgvldbies02, We are getting the following error

Resource showing as "unrunnable start (blocked)"

Pacemaker Log:
https://drive.google.com/open?id=1qf...TDsNjLyVZ1f7TI

Related to your other thread, which you didn't follow up in?
https://www.linuxquestions.org/quest...on-4175672653/

Again, have you contacted Suse support, since you're using Suse Enterprise??? And if you'd like any assistance here, you need to post the RELEVANT parts of your logs here...asking volunteers to chase down links, and pull through your log files for free to help you diagnose your problem isn't good. Also your question is plain confusing....you're saying when you take down host glbgvldbies02 that things aren't able to run on it. Which sounds EXACTLY RIGHT...services can't run on a server that's being rebooted or is down, can they??