Hi. I presume your name is Dave... Well, first of, I can't seems to reproduce your bug. I just setup a cluster and they come online both nodes and a DC is elected. Logs don't show any of the behavior. Now, I was thinking, given that you have upgraded... maybe there's a file that has been overwritten by the new packages, such as:
/etc/default/corosync /etc/corosync/corosync.conf Or, there's something wrong with the keys. First, I'd recommend you check if above files are with the correct values (/etc/default/corosync with "yes" and /etc/corosync/corosync.conf the network is the same on both nodes). If everything is configured as expected, try recreating the keys with 'corosync-keygen', make sure the permissions are the correct ones, and copy the key to the other node (root:root and has 400). Let me know afterwards Thank you for reporting bugs. -- do_lrm_control: Failed to sign on to the LRM after upgrade to Maverick https://bugs.launchpad.net/bugs/676391 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
