Hi,
Pacemaker 1.0.9.1, Corosync 1.2.7
I have a sane master/slave configuration that gives me normal looking
notify() calls when I standby each node in turn.
However, when I configure the master/slave on a group of three
resources, things look pretty strange.
Note that I get no "post" calls at all.
Dejan,
Below I had:
primitive res_stonith stonith:apcmastersnmp \
params ipaddr="192.1.1.109" port="161" community="sps" \
op start interval="0" timeout="60s" \
op monitor interval="60s" timeout="60s" \
op stop interval="0" timeout="60s"
clone rc_res_stonith re
On 1 November 2010 09:19, Pavlos Parissis wrote:
> Hi,
>
> I have been using 1.1.3 on CentOS and I decided to downgrade to
> 1.0.9.1-1.15.el5.
>
> The procedure was the following
> stop heartbeat on all cluster members
>
> downgrade to 1.0.9 doing the following on all cluster memebrs
> yum downgr
Hi,
I have been using 1.1.3 on CentOS and I decided to downgrade to
1.0.9.1-1.15.el5.
The procedure was the following
stop heartbeat on all cluster members
downgrade to 1.0.9 doing the following on all cluster memebrs
yum downgrade pacemaker-1.0.9.1-1.15.el5 pacemaker-libs-1.0.9.1-1.15.el5
pacem
> I'd build it as a parallel package, f.e. glib224, with includes in
> /usr/include/glib-2.24 and .so symlinks in /usr/lib/glib-2.24. Thus
> you'll have everything in directories (separate from a "main" glib2
> package) which you should manually supply to pacemaker during build, and
> all other pac