<div dir="ltr">The "switch" is a standard Linux bridge device, and the two systems are KVM virtual machines attached to the same bridge. Are there known problems with this configuration? I' can't get corosync to stay up for more than a few minutes. I would simply use a vrrp or carp solution, but I need a service to follow the vip and there aren't many alternatives out there.<div>
<br></div><div style>I'll see if using udpu stabilizes things.</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Feb 21, 2013 at 10:16 PM, Andrew Beekhof <span dir="ltr"><<a href="mailto:andrew@beekhof.net" target="_blank">andrew@beekhof.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On Fri, Feb 22, 2013 at 1:00 PM, Lars Kellogg-Stedman <<a href="mailto:lars@oddbit.com">lars@oddbit.com</a>> wrote:<br>
><br>
>> Did you define a recurring monitor action?<br>
>><br>
><br>
> You know, upon reflection, probably not. I started with "op monitor<br>
> interval=10s", but because of all the problems I ran into with pcs<br>
> complaining about systemd: services I think I dropped everything except the<br>
> service name and agent in order to simplify the problem. I'll try it again<br>
> with an explicit monitor action.<br>
><br>
>><br>
>> What does corosync.conf look like?<br>
><br>
><br>
> Like this: <a href="https://gist.github.com/larsks/5010169" target="_blank">https://gist.github.com/larsks/5010169</a><br>
><br>
> This was generated using the "pcs corosync configure puppet puppet0<br>
> puppet1".<br>
><br>
<br>
</div></div>Perhaps enable udpu (unicast) there. Corosync doesn't seem to like your switch.<br>
</blockquote></div><br></div>