Dear Users/Developers,
I'm running a pacemaker/corosync cluster on Debian 7:
Pacemaker 1.1.7.1
Corosync 1.4.2-3
Everything is smooth but the first monitor action after the start action on my
apache2 ressource fails - hence it ends up in a restart.
How can this be avoided?
Log attached.
I took a look at the include folders of pacemaker and corosync and I didn't
find there any explanation to functions. Did I look at a wrong place?
My goal is to manage cluster from my app, so I don't need to use crmsh or
pcs.
Any ideas are appreciated.
Hi all,
I am using pacemaker/openais and drbd to have a high-available MySQL server
which worked „for years“ (sind SLES 11 SP 0) without configuration chances.
Just two days ago I did an update (zypper up) which now leads to the issue
described below.
Although the subject of my email is quite
On 17 Jun 2014, at 4:21 pm, Bauer, Stefan (IZLBW Extern)
stefan.ba...@iz.bwl.de wrote:
Dear Users/Developers,
I’m running a pacemaker/corosync cluster on Debian 7:
Pacemaker 1.1.7.1
Corosync 1.4.2-3
Everything is smooth but the first monitor action after the start action on
my
On 17 Jun 2014, at 8:01 pm, Kostiantyn Ponomarenko
konstantin.ponomare...@gmail.com wrote:
I took a look at the include folders of pacemaker and corosync and I didn't
find there any explanation to functions. Did I look at a wrong place?
My goal is to manage cluster from my app, so I don't
On 18 Jun 2014, at 2:59 am, Krause, Markus kra...@biochem.mpg.de wrote:
Hi all,
I am using pacemaker/openais and drbd to have a high-available MySQL server
which worked „for years“ (sind SLES 11 SP 0) without configuration chances.
Just two days ago I did an update (zypper up) which now
I see:
Jun 5 15:11:45 server1 pengine: [1599]: WARN: unpack_rsc_op: Processing failed
op xenwin7_last_failure_0 on server1: unknown error (1)
but the actual error appears to have been before the logs start.
Later on there is:
Jun 5 15:12:05 server1 lrmd: [1596]: WARN: xenwin7:start process
Hi all,
I am trying to setup a basic pacemaker 1.1.10 on RHEL 6.5 with DRBD
8.3.16.
I've setup DRBD and configured one clustered LVM volume group using
that drbd resource as the PV. With DRBD configured alone, I can
stop/start pacemaker repeatedly without issue. However, when I add the
Andrew, many thanks!
On Jun 18, 2014 2:11 AM, Andrew Beekhof and...@beekhof.net wrote:
On 17 Jun 2014, at 8:01 pm, Kostiantyn Ponomarenko
konstantin.ponomare...@gmail.com wrote:
I took a look at the include folders of pacemaker and corosync and I
didn't find there any explanation to
