----- Original Message -----
> From: "Peto Michalak" <[email protected]>
> To: [email protected], "linux-ha" <[email protected]>
> Sent: Wednesday, December 11, 2013 2:26:02 AM
> Subject: Re: [Linux-HA] pacemaker restarts services (on the same node) when 
> failed node returns
> 
> Hi David,
> 
> I've attached a crm_report which should show the restart of services, when
> failed node returns.
> 
> I will go through the report as well to see if I find something there.


The constraint in the xml below is what causes the restart. You are telling 
pacemaker place the PGServer on node drpg-02... When drpg-02 joins the cluster, 
PGserver restarts because it is being relocated to prpg-02. This should be 
expected. 

      <rsc_location id="cli-prefer-PGServer" rsc="PGServer">
        <rule id="cli-prefer-rule-PGServer" score="INFINITY" boolean-op="and">
          <expression id="cli-prefer-expr-PGServer" attribute="#uname" 
operation="eq" value="drpg-02" type="string"/>
        </rule>
      </rsc_location>


> 
> Thank you for your help.
> 
> Best Regards,
> -Peter
> 
> > Hello,
> >
> > I really searched for the answer before posting : ).
> >
> > I have a pacemaker setup + corosync + drbd in Active/Passive mode running
> > in 2 node cluster on Ubuntu 12.04.3.
> >
> > Everything works fine and on node failure the services are taken care of
> by
> > the other node (THANKS guys!), well the problem is that I've noticed, that
> > once the failed node comes back alive, the pacemaker restarts the
> > postgresql and virtual IP and that takes around 4-7 seconds (but keeps it
> > on the same node as I wanted, what's the point? :) ). Is this really
> > necessary, or I've messed up something in the configuration?
> 
> any chance you could provide us with a crm_report during the time frame of
> this unwanted restart?
> 
> -- Vossel
> 
> > My pacemaker config:
> >
> > node drpg-01 attributes standby="off"
> > node drpg-02 attributes standby="off"
> > primitive drbd_pg ocf:linbit:drbd \
> >         params drbd_resource="drpg" \
> >         op monitor interval="15" \
> >         op start interval="0" timeout="240" \
> >         op stop interval="0" timeout="120"
> > primitive pg_fs ocf:heartbeat:Filesystem \
> >         params device="/dev/drbd/by-res/drpg" directory="/db/pgdata"
> > options="noatime,nodiratime" fstype="xfs" \
> >         op start interval="0" timeout="60" \
> >         op stop interval="0" timeout="120"
> > primitive pg_lsb lsb:postgresql \
> >         op monitor interval="30" timeout="60" \
> >         op start interval="0" timeout="60" \
> >         op stop interval="0" timeout="60"
> > primitive pg_vip ocf:heartbeat:IPaddr2 \
> >         params ip="10.34.2.60" iflabel="pgvip" \
> >         op monitor interval="5"
> > group PGServer pg_fs pg_lsb pg_vip
> > ms ms_drbd_pg drbd_pg \
> >         meta master-max="1" master-node-max="1" clone-max="2"
> > clone-node-max="1" notify="true"
> > colocation col_pg_drbd inf: PGServer ms_drbd_pg:Master
> > order ord_pg inf: ms_drbd_pg:promote PGServer:start
> > property $id="cib-bootstrap-options" \
> >         dc-version="1.1.6-9971ebba4494012a93c03b40a2c58ec0eb60f50c" \
> >         cluster-infrastructure="openais" \
> >         expected-quorum-votes="2" \
> >         no-quorum-policy="ignore" \
> >         pe-warn-series-max="1000" \
> >         pe-input-series-max="1000" \
> >         pe-error-series-max="1000" \
> >         default-resource-stickiness=1000 \
> >         cluster-recheck-interval="5min" \
> >         stonith-enabled="false" \
> >         last-lrm-refresh="1385646505"
> >
> > Thank you.
> >
> > Best Regards,
> > -Peter
> > _______________________________________________
> > Linux-HA mailing list
> > [email protected]
> > http://lists.linux-ha.org/mailman/listinfo/linux-ha
> > See also: http://linux-ha.org/ReportingProblems
> >
> 
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Reply via email to