Once again I botched the obfuscation. The corosync.conf should in fact
be 'node1.mydomain.com' and 'node2.mydomain.com' (i.e., it matches the
rest of the configuration).
Thanks!
Dan
On 12/4/2018 12:48 PM, Daniel Ragle wrote:
I *think* the two nodes of my cluster shot each other in the head
I *think* the two nodes of my cluster shot each other in the head this
weekend and I can't figure out why.
Looking at corosync.log on node1 I see this:
[143747] node1.mydomain.com corosyncnotice [TOTEM ] A processor failed,
forming new configuration.
[143747] node1.mydomain.com
On 10/11/2018 5:00 PM, Valentin Vidic wrote:
On Thu, Oct 11, 2018 at 01:25:52PM -0400, Daniel Ragle wrote:
For the 12 second window it *does* work in, it appears as though it works
only on one of the two servers (and always the same one). My twelve seconds
of pings runs continuously
I'm adding a VIP to my active/active two node cluster using IPaddr2.
These are on updated CentOS 7.5 machines.
When I bring up the IP, I'm able to ping it from an external machine for
about 12 seconds and then I get no further responses. This happens each
time I restart the VIP clone.
I can
Thanks for the comments. Replies within.
On 9/11/2018 1:52 PM, Ken Gaillot wrote:
On Fri, 2018-09-07 at 16:07 -0400, Dan Ragle wrote:
On an active-active two node cluster with DRBD, dlm, filesystem
mounts, a Web Server, and some crons I can't figure out how to have
the crons jump from node to
