Hi,
Have you tried to set the restart_type to restart ?
refer to crm.dtd
* restart_type
Used when the other side of an ordering dependency is restarted/moved.
* ignore : the default.
Don't do anything extra.
* restart
Use this for example to have a restart of your database also
trigger a restart of your web-server.
2008/1/22, Cousin Marc <[EMAIL PROTECTED]>:
> Hi,
>
> I'm testing ordering constraints.
>
> I've put these 2 constraints:
> <rsc_order action="start"
> symmetrical="true"
> id="postgresr2_avantr1"
> from="postgresr2"
> to="applisr1"
> type="before"/>
> <rsc_order action="start"
> symmetrical="true"
> id="postgresr2_avantr3"
> from="postgresr2"
> to="applisr3"
> type="before"/>
>
> The idea is that we have applisr1 and applisr3 depending on postgresr2 being
> already online.
> If postgresr2 has to be migrated to another node or restarted, I need both
> applisr1 and applisr3 to be restarted (it's the application's limitation).
>
> These constraints work perfectly in case I put the node hosting postgresr2 on
> standby. Both the applications are shutdown, then postgresr2 moves to another
> node, and both applications are restarted.
>
> If I kill the node hosting postgresr2, postgresr2 migrates to another node,
> but applisr1 and applisr3 aren't restarted. Is it normal ? What could I do to
> solve this ?
>
> Thanks a lot for your help.
>
> Cheers.
> Marc Cousin
> _______________________________________________
> 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
