[ClusterLabs] Corosync & pacemaker quit between boot and login

Russell Martin russell_martin at yahoo.com
Tue Oct 20 16:06:05 EDT 2015


Thanks for the reply. Like you were thinking, I turned on logging and configured things to log to a corosync log file instead of the system log. Unfortunately, that didn't shed any light on it for me.
Also, like you were thinking I decided it might be something to do with the desktop version instead of the server version. So, yesterday, I wiped my two boxes (I'm not very far into this project) and installed Ubuntu Server and setup corosync and pacemaker again. Now, the cluster is working like it does in my virtual machines. I'm waiting for drbd to finish syncing /dev/sdb and then I will be trying to figure out how to get some managed resources configured.
Thanks again for your response.

     On Monday, October 19, 2015 10:31 AM, Matthias Ferdinand <mf at 14v.de> wrote:

 On Fri, Oct 16, 2015 at 06:25:29PM +0200, users-request at clusterlabs.org wrote:
> From: Russell Martin <russell_martin at yahoo.com>
> Subject: [ClusterLabs] Corosync & pacemaker quit between boot and login
> ...
> Both corosync and pacemaker seem to start fine during boot (they both say "[OK]")
> However, once logged in, neither daemon is running.


since you are using a Desktop install, could it be that NetworkManager
interferes with your network configuration?

Otherwise you would have to look through /var/log/corosync/corosync.log
for a hint.


Users mailing list: Users at clusterlabs.org

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20151020/3b1d0077/attachment-0003.html>

More information about the Users mailing list