Product SiteDocumentation Site

C.2.2. Enabling Pacemaker For Corosync 1.x

Example C.3. Corosync 1.x configuration file for a cluster with all nodes on the network

  totem {
      version: 2
      secauth: off
      threads: 0
      interface {
          ringnumber: 0
          mcastport: 1234
  logging {
      fileline: off
      to_syslog: yes
      syslog_facility: daemon
  amf {
      mode: disabled

With corosync 1.x, the totem section contains the protocol version and options as with 2.x. However, nodes are also listed here, in the interface section. The bindnetaddr option is usually the network address, thus allowing the same configuration file to be used on all nodes. IPv4 or IPv6 addresses can be used with corosync.
The amf section refers to the Availability Management Framework and is not covered in this document.
The above corosync configuration is enough for corosync to operate by itself, but corosync 1.x additionally needs to be told when it is being used in conjunction with Pacemaker. This can be accomplished in one of two ways:
To use CMAN, consult its documentation.
To use the pacemaker corosync plugin, add the following fragment to the corosync configuration and restart the cluster.

Example C.4. Corosync 1._x_configuration fragment to enable Pacemaker plugin

aisexec {
    user:  root
    group: root
service {
    name: pacemaker
    ver: 0

The cluster needs to be run as root so that its child processes (the lrmd in particular) have sufficient privileges to perform the actions requested of it. After all, a cluster manager that can’t add an IP address or start apache is of little use.
The second directive is the one that actually instructs the cluster to run Pacemaker.