After failover Pacemaker moves resource back when node comes back
I'm using Pacemaker & Corosync for my cluster.
When a node dies pacemaker moving my resources to another online node. Everything ok here.
But when the dead node comes back, Pacemaker moving the resource back.
I don't have any "location" line in my config and also I tried with "unmove" command but nothing changed.
I failed at somewhere and need to find the reason.
crm configure sh
node 1: DEV1
node 2: DEV2
primitive poolip IPaddr2
params ip=10.1.60.33 nic=enp2s0f0 cidr_netmask=24
meta migration-threshold=2 target-role=Started
op monitor interval=20 timeout=20 on-fail=restart
primitive gui systemd:gui
op monitor interval=20s
meta target-role=Started
primitive gui-ip IPaddr2
params ip=10.1.60.35 nic=enp2s0f0 cidr_netmask=24
meta migration-threshold=2 target-role=Started
op monitor interval=20 timeout=20 on-fail=restart
colocation cluster-gui inf: gui gui-ip
order gui-after-ip Mandatory: gui-ip gui
property cib-bootstrap-options:
have-watchdog=false
dc-version=2.0.0-1-8cf3fe749e
cluster-infrastructure=corosync
cluster-name=mycluster
stonith-enabled=false
no-quorum-policy=ignore
last-lrm-refresh=1545920437
rsc_defaults rsc-options:
migration-threshold=10
resource-stickiness=100
pcs resource defaults
migration-threshold=10
resource-stickiness=100
pcs resource show gui
Resource: gui (class=systemd type=gui)
Meta Attrs: target-role=Started
Operations: monitor interval=20s (gui-monitor-20s)
linux cluster pacemaker corosync
asked 2 days ago
Morphinz
14111
|
show 2 more comments
I'm using Pacemaker & Corosync for my cluster.
When a node dies pacemaker moving my resources to another online node. Everything ok here.
But when the dead node comes back, Pacemaker moving the resource back.
I don't have any "location" line in my config and also I tried with "unmove" command but nothing changed.
I failed at somewhere and need to find the reason.
crm configure sh
node 1: DEV1
node 2: DEV2
primitive poolip IPaddr2
params ip=10.1.60.33 nic=enp2s0f0 cidr_netmask=24
meta migration-threshold=2 target-role=Started
op monitor interval=20 timeout=20 on-fail=restart
primitive gui systemd:gui
op monitor interval=20s
meta target-role=Started
primitive gui-ip IPaddr2
params ip=10.1.60.35 nic=enp2s0f0 cidr_netmask=24
meta migration-threshold=2 target-role=Started
op monitor interval=20 timeout=20 on-fail=restart
colocation cluster-gui inf: gui gui-ip
order gui-after-ip Mandatory: gui-ip gui
property cib-bootstrap-options:
have-watchdog=false
dc-version=2.0.0-1-8cf3fe749e
cluster-infrastructure=corosync
cluster-name=mycluster
stonith-enabled=false
no-quorum-policy=ignore
last-lrm-refresh=1545920437
rsc_defaults rsc-options:
migration-threshold=10
resource-stickiness=100
pcs resource defaults
migration-threshold=10
resource-stickiness=100
pcs resource show gui
Resource: gui (class=systemd type=gui)
Meta Attrs: target-role=Started
Operations: monitor interval=20s (gui-monitor-20s)
linux cluster pacemaker corosync
asked 2 days ago
Morphinz
14111
doespcs constraint showshow anything?
– Jenny D
2 days ago
I don't use pcs but i have installed for you. pcs constraint show ``` Location Constraints: Ordering Constraints: gui-ip then gui (kind:Mandatory) Colocation Constraints: gui with gui-ip (score:INFINITY) Ticket Constraints: ```
– Morphinz
2 days ago
It would help if you could click the "Edit" link below your question and edit the additional information into the question instead. It's hard to read the info when it's in a comment.
– Jenny D
2 days ago
I think you should have a look at stickiness. Since you've got pcs installed now, check it by runningpcs resource defaultsandpcs resource show gui
– Jenny D
2 days ago
1
Are you starting services at boot that Pacemaker is monitoring? If so, it's possible that Pacemaker notices the service is running in both places, and is stopping services on the current primary and leaving them running on the freshly rebooted node.
– Matt Kereczman
yesterday
|
show 2 more comments
I'm using Pacemaker & Corosync for my cluster.
When a node dies pacemaker moving my resources to another online node. Everything ok here.
But when the dead node comes back, Pacemaker moving the resource back.
I don't have any "location" line in my config and also I tried with "unmove" command but nothing changed.
I failed at somewhere and need to find the reason.
crm configure sh
node 1: DEV1
node 2: DEV2
primitive poolip IPaddr2
params ip=10.1.60.33 nic=enp2s0f0 cidr_netmask=24
meta migration-threshold=2 target-role=Started
op monitor interval=20 timeout=20 on-fail=restart
primitive gui systemd:gui
op monitor interval=20s
meta target-role=Started
primitive gui-ip IPaddr2
params ip=10.1.60.35 nic=enp2s0f0 cidr_netmask=24
meta migration-threshold=2 target-role=Started
op monitor interval=20 timeout=20 on-fail=restart
colocation cluster-gui inf: gui gui-ip
order gui-after-ip Mandatory: gui-ip gui
property cib-bootstrap-options:
have-watchdog=false
dc-version=2.0.0-1-8cf3fe749e
cluster-infrastructure=corosync
cluster-name=mycluster
stonith-enabled=false
no-quorum-policy=ignore
last-lrm-refresh=1545920437
rsc_defaults rsc-options:
migration-threshold=10
resource-stickiness=100
pcs resource defaults
migration-threshold=10
resource-stickiness=100
pcs resource show gui
Resource: gui (class=systemd type=gui)
Meta Attrs: target-role=Started
Operations: monitor interval=20s (gui-monitor-20s)
linux cluster pacemaker corosync
asked 2 days ago
Morphinz
14111
I'm using Pacemaker & Corosync for my cluster.
When a node dies pacemaker moving my resources to another online node. Everything ok here.
But when the dead node comes back, Pacemaker moving the resource back.
I don't have any "location" line in my config and also I tried with "unmove" command but nothing changed.
I failed at somewhere and need to find the reason.
crm configure sh
node 1: DEV1
node 2: DEV2
primitive poolip IPaddr2
params ip=10.1.60.33 nic=enp2s0f0 cidr_netmask=24
meta migration-threshold=2 target-role=Started
op monitor interval=20 timeout=20 on-fail=restart
primitive gui systemd:gui
op monitor interval=20s
meta target-role=Started
primitive gui-ip IPaddr2
params ip=10.1.60.35 nic=enp2s0f0 cidr_netmask=24
meta migration-threshold=2 target-role=Started
op monitor interval=20 timeout=20 on-fail=restart
colocation cluster-gui inf: gui gui-ip
order gui-after-ip Mandatory: gui-ip gui
property cib-bootstrap-options:
have-watchdog=false
dc-version=2.0.0-1-8cf3fe749e
cluster-infrastructure=corosync
cluster-name=mycluster
stonith-enabled=false
no-quorum-policy=ignore
last-lrm-refresh=1545920437
rsc_defaults rsc-options:
migration-threshold=10
resource-stickiness=100
pcs resource defaults
migration-threshold=10
resource-stickiness=100
pcs resource show gui
Resource: gui (class=systemd type=gui)
Meta Attrs: target-role=Started
Operations: monitor interval=20s (gui-monitor-20s)
linux cluster pacemaker corosync
linux cluster pacemaker corosync
asked 2 days ago
Morphinz
14111
asked 2 days ago
Morphinz
14111
edited 2 days ago
asked 2 days ago
Morphinz
14111
asked 2 days ago
Morphinz
14111
asked 2 days ago
Morphinz
14111
14111
doespcs constraint showshow anything?
– Jenny D
2 days ago
I don't use pcs but i have installed for you. pcs constraint show ``` Location Constraints: Ordering Constraints: gui-ip then gui (kind:Mandatory) Colocation Constraints: gui with gui-ip (score:INFINITY) Ticket Constraints: ```
– Morphinz
2 days ago
It would help if you could click the "Edit" link below your question and edit the additional information into the question instead. It's hard to read the info when it's in a comment.
– Jenny D
2 days ago
I think you should have a look at stickiness. Since you've got pcs installed now, check it by runningpcs resource defaultsandpcs resource show gui
– Jenny D
2 days ago
1
Are you starting services at boot that Pacemaker is monitoring? If so, it's possible that Pacemaker notices the service is running in both places, and is stopping services on the current primary and leaving them running on the freshly rebooted node.
– Matt Kereczman
yesterday
|
show 2 more comments
doespcs constraint showshow anything?
– Jenny D
2 days ago
I don't use pcs but i have installed for you. pcs constraint show ``` Location Constraints: Ordering Constraints: gui-ip then gui (kind:Mandatory) Colocation Constraints: gui with gui-ip (score:INFINITY) Ticket Constraints: ```
– Morphinz
2 days ago
It would help if you could click the "Edit" link below your question and edit the additional information into the question instead. It's hard to read the info when it's in a comment.
– Jenny D
2 days ago
I think you should have a look at stickiness. Since you've got pcs installed now, check it by runningpcs resource defaultsandpcs resource show gui
– Jenny D
2 days ago
1
Are you starting services at boot that Pacemaker is monitoring? If so, it's possible that Pacemaker notices the service is running in both places, and is stopping services on the current primary and leaving them running on the freshly rebooted node.
– Matt Kereczman
yesterday
does
pcs constraint show show anything?– Jenny D
2 days ago
does
pcs constraint show show anything?– Jenny D
2 days ago
I don't use pcs but i have installed for you. pcs constraint show ``` Location Constraints: Ordering Constraints: gui-ip then gui (kind:Mandatory) Colocation Constraints: gui with gui-ip (score:INFINITY) Ticket Constraints: ```
– Morphinz
2 days ago
I don't use pcs but i have installed for you. pcs constraint show ``` Location Constraints: Ordering Constraints: gui-ip then gui (kind:Mandatory) Colocation Constraints: gui with gui-ip (score:INFINITY) Ticket Constraints: ```
– Morphinz
2 days ago
It would help if you could click the "Edit" link below your question and edit the additional information into the question instead. It's hard to read the info when it's in a comment.
– Jenny D
2 days ago
It would help if you could click the "Edit" link below your question and edit the additional information into the question instead. It's hard to read the info when it's in a comment.
– Jenny D
2 days ago
I think you should have a look at stickiness. Since you've got pcs installed now, check it by running
pcs resource defaultsand pcs resource show gui– Jenny D
2 days ago
I think you should have a look at stickiness. Since you've got pcs installed now, check it by running
pcs resource defaultsand pcs resource show gui– Jenny D
2 days ago
1
1
Are you starting services at boot that Pacemaker is monitoring? If so, it's possible that Pacemaker notices the service is running in both places, and is stopping services on the current primary and leaving them running on the freshly rebooted node.
– Matt Kereczman
yesterday
Are you starting services at boot that Pacemaker is monitoring? If so, it's possible that Pacemaker notices the service is running in both places, and is stopping services on the current primary and leaving them running on the freshly rebooted node.
– Matt Kereczman
yesterday
|
show 2 more comments
1 Answer
1
active
oldest
votes
It sounds like you might be starting services at boot that only the cluster should be start/stop/monitoring.
Disable your services from starting at boot and then test your reboot again: systemctl disable gui
answered 1 hour ago
Matt Kereczman
50526
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f491994%2fafter-failover-pacemaker-moves-resource-back-when-node-comes-back%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
It sounds like you might be starting services at boot that only the cluster should be start/stop/monitoring.
Disable your services from starting at boot and then test your reboot again: systemctl disable gui
answered 1 hour ago
Matt Kereczman
50526
add a comment |
It sounds like you might be starting services at boot that only the cluster should be start/stop/monitoring.
Disable your services from starting at boot and then test your reboot again: systemctl disable gui
answered 1 hour ago
Matt Kereczman
50526
add a comment |
It sounds like you might be starting services at boot that only the cluster should be start/stop/monitoring.
Disable your services from starting at boot and then test your reboot again: systemctl disable gui
answered 1 hour ago
Matt Kereczman
50526
It sounds like you might be starting services at boot that only the cluster should be start/stop/monitoring.
Disable your services from starting at boot and then test your reboot again: systemctl disable gui
answered 1 hour ago
Matt Kereczman
50526
answered 1 hour ago
Matt Kereczman
50526
answered 1 hour ago
Matt Kereczman
50526
answered 1 hour ago
Matt Kereczman
50526
50526
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f491994%2fafter-failover-pacemaker-moves-resource-back-when-node-comes-back%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
does
pcs constraint showshow anything?– Jenny D
2 days ago
I don't use pcs but i have installed for you. pcs constraint show ``` Location Constraints: Ordering Constraints: gui-ip then gui (kind:Mandatory) Colocation Constraints: gui with gui-ip (score:INFINITY) Ticket Constraints: ```
– Morphinz
2 days ago
It would help if you could click the "Edit" link below your question and edit the additional information into the question instead. It's hard to read the info when it's in a comment.
– Jenny D
2 days ago
I think you should have a look at stickiness. Since you've got pcs installed now, check it by running
pcs resource defaultsandpcs resource show gui– Jenny D
2 days ago
1
Are you starting services at boot that Pacemaker is monitoring? If so, it's possible that Pacemaker notices the service is running in both places, and is stopping services on the current primary and leaving them running on the freshly rebooted node.
– Matt Kereczman
yesterday