Re: [Pacemaker] Problems with Pacemaker 1.1.8 on F17

2013-02-25 Thread David Vossel
with Pacemaker 1.1.8 on F17 You'd think that would help, but https://bugzilla.redhat.com/show_bug.cgi?id=880035 suggests otherwise. I have one remaining fedora machine where KVM clusters still work, I don't think I'll ever update it now. Well, that was fascinating read

[Pacemaker] Problems with Pacemaker 1.1.8 on F17

2013-02-21 Thread Lars Kellogg-Stedman
Howdy all, I'm trying to run Pacemaker 1.1.8 (from http://clusterlabs.org/rpm-next/fedora-17/clusterlabs.repo) in a two-node configuration under Fedora 17. I'm running into a few different problems. I'm trying to create resources using the systemd: manager. If I run pcs resource standards I

Re: [Pacemaker] Problems with Pacemaker 1.1.8 on F17

2013-02-21 Thread Andrew Beekhof
On Fri, Feb 22, 2013 at 9:10 AM, Lars Kellogg-Stedman l...@oddbit.com wrote: Howdy all, I'm trying to run Pacemaker 1.1.8 (from http://clusterlabs.org/rpm-next/fedora-17/clusterlabs.repo) in a two-node configuration under Fedora 17. I'm running into a few different problems. I'm trying to

Re: [Pacemaker] Problems with Pacemaker 1.1.8 on F17

2013-02-21 Thread Lars Kellogg-Stedman
Did you define a recurring monitor action? You know, upon reflection, probably not. I started with op monitor interval=10s, but because of all the problems I ran into with pcs complaining about systemd: services I think I dropped everything except the service name and agent in order to

Re: [Pacemaker] Problems with Pacemaker 1.1.8 on F17

2013-02-21 Thread Andrew Beekhof
On Fri, Feb 22, 2013 at 1:00 PM, Lars Kellogg-Stedman l...@oddbit.com wrote: Did you define a recurring monitor action? You know, upon reflection, probably not. I started with op monitor interval=10s, but because of all the problems I ran into with pcs complaining about systemd: services I

Re: [Pacemaker] Problems with Pacemaker 1.1.8 on F17

2013-02-21 Thread Lars Kellogg-Stedman
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

Re: [Pacemaker] Problems with Pacemaker 1.1.8 on F17

2013-02-21 Thread Andrew Beekhof
On Fri, Feb 22, 2013 at 2:21 PM, Lars Kellogg-Stedman l...@oddbit.com wrote: The switch is a standard Linux bridge device, and the two systems are KVM virtual machines attached to the same bridge. You'd think that would help, but https://bugzilla.redhat.com/show_bug.cgi?id=880035 suggests

Re: [Pacemaker] Problems with Pacemaker 1.1.8 on F17

2013-02-21 Thread Lars Kellogg-Stedman
You'd think that would help, but https://bugzilla.redhat.com/show_bug.cgi?id=880035 suggests otherwise. I have one remaining fedora machine where KVM clusters still work, I don't think I'll ever update it now. Well, that was fascinating read. Using the udpu transport seems to have

Re: [Pacemaker] Problems with Pacemaker 1.1.8 on F17

2013-02-21 Thread Andrew Beekhof
On Fri, Feb 22, 2013 at 4:11 PM, Lars Kellogg-Stedman l...@oddbit.com wrote: You'd think that would help, but https://bugzilla.redhat.com/show_bug.cgi?id=880035 suggests otherwise. I have one remaining fedora machine where KVM clusters still work, I don't think I'll ever update it now.