** Description changed: 16.04.2 LTS for Ubuntu, 1.1.14 for pacemaker and 0.9.149 for pcs. - - Error when enabling Pacemaker service - - # sudo systemctl enable pacemaker - Synchronizing state of pacemaker.service with SysV init with /lib/systemd/systemd-sysv-install... - Executing /lib/systemd/systemd-sysv-install enable pacemaker - update-rc.d: error: pacemaker Default-Start contains no runlevels, aborting. - - - Error when starting the cluster - - sudo pcs cluster start --all - mbubuntu1: Starting Cluster... + + + Install Pacemaker packages: + sudo apt-get install pacemaker pcs fence-agents resource-agents + + Set the password for the default user: + sudo passwd hacluster + + #To clear files + sudo pcs cluster destroy + + Enable and start pcsd/pacemaker: + sudo systemctl enable pcsd + sudo systemctl start pcsd + sudo systemctl enable pacemaker + + + sudo pcs cluster auth pacemaker-1 pacemaker-2 -u hacluster -p haclusterpassword + sudo pcs cluster setup --name hacluster pacemaker-1 pacemaker-2 + sudo pcs cluster start + **FAILS*** + Starting Cluster... Job for corosync.service failed because the control process exited with error code. See "systemctl status corosync.service" and "journalctl -xe" for details. - mbubuntu2: Starting Cluster... - Job for corosync.service failed because the control process exited with error code. See "systemctl status corosync.service" and "journalctl -xe" for details. - - And the output of the log file is: - - ● corosync.service - Corosync Cluster Engine - Loaded: loaded (/lib/systemd/system/corosync.service; disabled; vendor preset: enabled) - Active: failed (Result: exit-code) since Thu 2017-03-16 11:13:17 PDT; 29s ago - Process: 22052 ExecStart=/usr/sbin/corosync -f $OPTIONS (code=exited, status=7) - Main PID: 22052 (code=exited, status=7) - - Mar 16 11:13:17 mbubuntu2 systemd[1]: Starting Corosync Cluster Engine... - Mar 16 11:13:17 mbubuntu2 corosync[22052]: parse error in config: Can't open logfile '/var/log/cluster/corosync.log' for reason: No such file or directory (2). - Mar 16 11:13:17 mbubuntu2 systemd[1]: corosync.service: Main process exited, code=exited, status=7/NOTRUNNING - Mar 16 11:13:17 mbubuntu2 systemd[1]: Failed to start Corosync Cluster Engine. - Mar 16 11:13:17 mbubuntu2 systemd[1]: corosync.service: Unit entered failed state. - Mar 16 11:13:17 mbubuntu2 systemd[1]: corosync.service: Failed with result 'exit-code'. - ~ - + + Error: unable to start corosync + + + Workaround + On both nodes, Replace the line: + logfile: /var/log/cluster/corosync.log + with + logfile: /var/log/corosync/corosync.log + + (or create the expected log file. + + Errors are very easy to repro and consistent
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1673579 Title: Corosync/Pacemaker: Error when enabling Pacemaker service,Error when starting the cluster To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1673579/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
