On Wed, 16 May 2018 21:18:14 +0200
Jehan-Guillaume de Rorthais wrote:
> On Wed, 16 May 2018 12:43:15 -0600
> Casey & Gina wrote:
> ...
> > fence_vmware - Fence agent for VMWare
>
> If I remember correctly, this fencing agent is able to connect to
> Thank you - I hadn't seen the "releases" link on github before and somehow
> missed that. Sorry for that. I thought there would be download links
> somewhere on the clusterlabs website. I will try compiling this today to try.
I finally managed to get pcs-0.9.164 compiled and installed.
> Here is a command to adapt that work to fence a VM connecting to an esxi
> server:
>
> pcs stonith create fence_vmware_soap \
>pcmk_host_check="static-list" pcmk_host_list="" \
>port="" ipaddr="" login="" \
>passwd="<>password" ssl="1"
> May 18 20:36:27 [4282] d-gp2-dbpg0-2 stonith-ng: warning: log_operation:
> vfencing:16264 [ Performing: stonith -t external/vcenter -T reset
> d-gp2-dbpg0-1 ]
> May 18 20:36:27 [4282] d-gp2-dbpg0-2 stonith-ng: warning: log_operation:
> vfencing:16264 [ failed: d-gp2-dbpg0-1 5 ]
> Having it started on one node is normal. Fence devices default to
> requires=quorum, meaning they can start on a new node even before the
> original node is fenced. It looks like that's what happened here, but
> something went wrong with the fencing, so the cluster assumes it's
> still active on
On Fri, 2018-05-18 at 12:01 -0600, Casey & Gina wrote:
> > > pcmk_host_list="" - not sure about this one - I'm
> > > guessing
> > > this would actually be the same input as the list I was inputting
> > > to
> > > the HOSTLIST parameter with the external/vcenter approach?
> > >
> > > port="" - not
On Fri, 2018-05-18 at 12:33 -0600, Casey & Gina wrote:
> I think that I finally managed to get fencing working! To do this,
> I've (for now) used the approach of using the stock Ubuntu package
> for pcs, but using crmsh to create the fencing resource. I've had a
> lot of trouble trying to get a
On Fri, 2018-05-18 at 10:22 -0600, Casey & Gina wrote:
> > Here is a command to adapt that work to fence a VM connecting to an
> > esxi server:
> >
> > pcs stonith create
> > fence_vmware_soap \
> > pcmk_host_check="static-list"
> > pcmk_host_list="" \
> >
>> pcmk_host_list="" - not sure about this one - I'm guessing
>> this would actually be the same input as the list I was inputting to
>> the HOSTLIST parameter with the external/vcenter approach?
>>
>> port="" - not sure about this one - with this approach would
>> I need to issue the above
I think that I finally managed to get fencing working! To do this, I've (for
now) used the approach of using the stock Ubuntu package for pcs, but using
crmsh to create the fencing resource. I've had a lot of trouble trying to get
a newer pcs compiled and working, and don't really know what
> So, then instead of powering off the VM in vSphere, I instead tried a
> `killall -9 corosync` on the primary. This resulted in the VIP coming up on
> node 3, and node 1 being rebooted. Great!
Unfortunately, things don't work at all when it comes to the PostgreSQL
resource agent... When I
On a couple clusters that have been running for a little while (without
fencing), I'm seeing runaway server.rb processes using 100% of a single CPU
core each.
When I look at ps, I can see that these have something to do with pcsd:
USER PID %CPU %MEMVSZ RSS TTY STAT START
12 matches
Mail list logo