Useful Corosync and Pacemaker Commands - Revision history

Rodolfojcj: Clarify that given commands need to be executed in only one cluster node

2022-01-04T16:19:29Z

Clarify that given commands need to be executed in only one cluster node

← Older revision		Revision as of 16:19, 4 January 2022
Line 76:		Line 76:
	might be handy.		might be handy.

	* Edit the cluster configuration with the ''cibadmin'' ~~command~~:		* Edit the cluster configuration with the ''cibadmin'' cluster tool:

	<pre>cibadmin --query > /tmp/old_cluster_configuration.xml		<pre>cibadmin --query > /tmp/old_cluster_configuration.xml
	cp /tmp/old_cluster_configuration.xml /tmp/new_cluster_configuration.xml		cp /tmp/old_cluster_configuration.xml /tmp/new_cluster_configuration.xml
Line 82:		Line 83:
	vim /tmp/new_cluster_configuration.xml		vim /tmp/new_cluster_configuration.xml
	cibadmin --replace --xml-file /tmp/new_cluster_configuration.xml</pre>		cibadmin --replace --xml-file /tmp/new_cluster_configuration.xml</pre>

			That sequence of commands needs to be executed in only one cluster node. After that, all the other nodes will receive and apply the updated configuration.

	* Set custom values for the ''monitoring interval'' and ''stop timeout'' for a ''systemd'' resource:		* Set custom values for the ''monitoring interval'' and ''stop timeout'' for a ''systemd'' resource:

Rodolfojcj at 16:13, 4 January 2022

2022-01-04T16:13:10Z

← Older revision		Revision as of 16:13, 4 January 2022
Line 64:		Line 64:
	crm resource stop <resource> # it won't stop as it's in maintenance-mode		crm resource stop <resource> # it won't stop as it's in maintenance-mode
	crm configure delete <resource>		crm configure delete <resource>
	crm configure show # ~~very~~ that all references to <resource> are gone		crm configure show # verify that all references to <resource> are gone
	crm resource reprobe # the cluster double checks the status of declared resources and verifies that everything is in order and <resource> doesn't exist anymore		crm resource reprobe # the cluster double checks the status of declared resources and verifies that everything is in order and <resource> doesn't exist anymore
	crm_mon -Arf1 # double check that everything is "started (unmanaged)" and <resource> is gone		crm_mon -Arf1 # double check that everything is "started (unmanaged)" and <resource> is gone

Rodolfojcj: Show ways to set custom values for the monitoring interval and stop timeout of a cluster resource

2022-01-04T13:03:39Z

Show ways to set custom values for the monitoring interval and stop timeout of a cluster resource

← Older revision		Revision as of 13:03, 4 January 2022
Line 82:		Line 82:
	vim /tmp/new_cluster_configuration.xml		vim /tmp/new_cluster_configuration.xml
	cibadmin --replace --xml-file /tmp/new_cluster_configuration.xml</pre>		cibadmin --replace --xml-file /tmp/new_cluster_configuration.xml</pre>

			* Set custom values for the ''monitoring interval'' and ''stop timeout'' for a ''systemd'' resource:

			In the following example a cluster resource of ''systemd'' type will be created, setting a ''monitoring interval'' of 30 seconds and a ''stop timeout'' of 40 seconds.

			<pre>crm configure primitive <resource name> \
			systemd:<sytemd name that corresponds to the cluster resource> \
			op monitor interval="30s" \
			op stop timeout="40s"
			</pre>

			If the cluster resource already exists, it could be edited to set those custom values, as illustrated in the previous examples.

Rodolfojcj at 12:49, 4 January 2022

2022-01-04T12:49:31Z

← Older revision		Revision as of 12:49, 4 January 2022
Line 81:		Line 81:
	# with any editor, e.g vim, apply any needed changes to the cluster configuration		# with any editor, e.g vim, apply any needed changes to the cluster configuration
	vim /tmp/new_cluster_configuration.xml		vim /tmp/new_cluster_configuration.xml
	cibadmin --replace --xml-file /tmp/new_cluster_configuration.xml		cibadmin --replace --xml-file /tmp/new_cluster_configuration.xml</pre>
	</pre>

Rodolfojcj: Show the usage of the cibadmin command to change the cluster configuration

2022-01-04T12:45:14Z

Show the usage of the cibadmin command to change the cluster configuration

← Older revision		Revision as of 12:45, 4 January 2022
Line 75:		Line 75:

	might be handy.		might be handy.

			* Edit the cluster configuration with the ''cibadmin'' command:
			<pre>cibadmin --query > /tmp/old_cluster_configuration.xml
			cp /tmp/old_cluster_configuration.xml /tmp/new_cluster_configuration.xml
			# with any editor, e.g vim, apply any needed changes to the cluster configuration
			vim /tmp/new_cluster_configuration.xml
			cibadmin --replace --xml-file /tmp/new_cluster_configuration.xml
			</pre>

Vlasis at 09:49, 13 October 2020

2020-10-13T09:49:11Z

← Older revision		Revision as of 09:49, 13 October 2020
Line 59:		Line 59:
	crm ra list ocf heartbeat		crm ra list ocf heartbeat
	crm ra list ocf pacemaker</pre>		crm ra list ocf pacemaker</pre>

			* Remove a resource from a group without disturbing the remaining resources:
			<pre>crm configure property maintenance-mode=true
			crm resource stop <resource> # it won't stop as it's in maintenance-mode
			crm configure delete <resource>
			crm configure show # very that all references to <resource> are gone
			crm resource reprobe # the cluster double checks the status of declared resources and verifies that everything is in order and <resource> doesn't exist anymore
			crm_mon -Arf1 # double check that everything is "started (unmanaged)" and <resource> is gone
			crm_simulate -S -L -VVV # optional, to check what would happen when leaving maintenance-mode
			crm configure property maintenance-mode=false</pre>

			If something goes wrong while in maintenance-mode then

			<pre>crm resource cleanup <resource></pre>

			might be handy.

Vlasis at 12:03, 3 August 2020

2020-08-03T12:03:33Z

← Older revision		Revision as of 12:03, 3 August 2020
Line 28:		Line 28:

	<pre>crm resource stop <resource name></pre>		<pre>crm resource stop <resource name></pre>

			* Restart a resource or a resource group (if the resource is in a resource group then the whole group will be restarted):

			<pre>crm resource restart <resource name></pre>

	* Edit a resource, which allows its reconfiguration:		* Edit a resource, which allows its reconfiguration:

Vlasis at 09:10, 8 July 2020

2020-07-08T09:10:07Z

← Older revision		Revision as of 09:10, 8 July 2020
Line 37:		Line 37:
	<pre>crm configure delete <resource name></pre>		<pre>crm configure delete <resource name></pre>

	* Migrate a resource to another node:		* Migrate the enswitch resource group to another node (avoid migrating specific resources separately, migrate the whole enswitch group instead):

	<pre>crm resource migrate ~~<resource name>~~ <node name></pre>		<pre>crm resource migrate enswitch <node name></pre>

	* Configuring a cluster to not manage a resource:		* Configuring a cluster to not manage a resource:

Vlasis at 16:07, 5 April 2018

2018-04-05T16:07:01Z

← Older revision		Revision as of 16:07, 5 April 2018
Line 1:		Line 1:
	List of useful commands to for Corosync and Pacemaker clusters.		List of useful commands for Corosync and Pacemaker clusters.

	* View the real-time status of nodes and resources:		* View the real-time status of nodes and resources:

	crm_mon		<pre>crm_mon</pre>

	* View one-off status of nodes and resources:		* View one-off status of nodes and resources:

	crm status		<pre>crm status</pre>

	* View cluster configuration:		* View cluster configuration:

	crm configure show		<pre>crm configure show</pre>

	* Set a node to standby mode~~, which~~ can be used to simulate a node becoming unavailable:		* Set a node to standby mode (can also be used to simulate a node becoming unavailable):

	crm node standby <node name>		<pre>crm node standby <node name></pre>

	* Set a node's status from standby to online:		* Set a node's status from standby to online:

	crm node online <node name>		<pre>crm node online <node name></pre>

	* Start a resource or a resource group:		* Start a resource or a resource group:

	crm resource start <resource name>		<pre>crm resource start <resource name></pre>

	* Stop a resource or a resource group:		* Stop a resource or a resource group:

	crm resource stop <resource name>		<pre>crm resource stop <resource name></pre>

	* Edit a resource, which allows ~~you~~ ~~to reconfigure it~~:		* Edit a resource, which allows its reconfiguration:

	crm configure edit <resource name>		<pre>crm configure edit <resource name></pre>

	* Delete a resource (must be stopped before it is deleted):		* Delete a resource (must be stopped before it is deleted):

	crm configure delete <resource name>		<pre>crm configure delete <resource name></pre>

	* Migrate a resource to another node:		* Migrate a resource to another node:

	crm resource migrate <resource name> <node name>		<pre>crm resource migrate <resource name> <node name></pre>

	* Configuring a cluster to not manage a resource:		* Configuring a cluster to not manage a resource:

	crm_resource --resource <resource name> --set-parameter is-managed --meta --parameter-value false		<pre>crm_resource --resource <resource name> --set-parameter is-managed --meta --parameter-value false</pre>

	* Clear a resource that is stuck in "(unmanaged) FAILED" state, e.g. due to a failed stop action:		* Clear a resource that is stuck in "(unmanaged) FAILED" state, e.g. due to a failed stop action:

	crm_resource -P		<pre>crm_resource -P
	crm resource cleanup <resource name>		crm resource cleanup <resource name></pre>

	* List resource agents by type:		* List resource agents by type:
	crm ra list lsb		<pre>crm ra list lsb
	crm ra list systemd		crm ra list systemd
	crm ra list ocf heartbeat		crm ra list ocf heartbeat
	crm ra list ocf pacemaker		crm ra list ocf pacemaker</pre>

Vlasis: Created page with "List of useful commands to for Corosync and Pacemaker clusters. * View the real-time status of nodes and resources: crm_mon * View one-off status of nodes and resources: c..."

2018-04-05T16:03:06Z

Created page with "List of useful commands to for Corosync and Pacemaker clusters. * View the real-time status of nodes and resources: crm_mon * View one-off status of nodes and resources: c..."

New page

List of useful commands to for Corosync and Pacemaker clusters.

* View the real-time status of nodes and resources:

crm_mon

* View one-off status of nodes and resources:

crm status

* View cluster configuration:

crm configure show

* Set a node to standby mode, which can be used to simulate a node becoming unavailable:

crm node standby <node name>

* Set a node's status from standby to online:

crm node online <node name>

* Start a resource or a resource group:

crm resource start <resource name>

* Stop a resource or a resource group:

crm resource stop <resource name>

* Edit a resource, which allows you to reconfigure it:

crm configure edit <resource name>

* Delete a resource (must be stopped before it is deleted):

crm configure delete <resource name>

* Migrate a resource to another node:

crm resource migrate <resource name> <node name>

* Configuring a cluster to not manage a resource:

crm_resource --resource <resource name> --set-parameter is-managed --meta --parameter-value false

* Clear a resource that is stuck in "(unmanaged) FAILED" state, e.g. due to a failed stop action:

crm_resource -P
crm resource cleanup <resource name>

* List resource agents by type:
crm ra list lsb
crm ra list systemd
crm ra list ocf heartbeat
crm ra list ocf pacemaker