On 3 Aug 2014, at 4:07 pm, Liron Amitzi wrote:
> When I run "service pacemaker stop" it takes a long time, I see that it
> stops all the resources, then starts them on the other node, and only
> then the "stop" command is completed.
Ahhh! It was the DC.
It app
On 4 Aug 2014, at 1:40 pm, Dharmesh wrote:
> Hi,
>
> I am trying to implement following Scenario :-
>
> i am having a 2 node cluster. Both the nodes are having PostgreSQL as
> Database & database replication is on from primary PostgreSQL node to
> secondary PostgreSQL node.
>
> Test Scenar
- Original Message -
>
>
> Hi,
>
> I’m working with SLES 11 SP3 and pacemaker 1.1.10-0.15.25
>
>
>
> I’m looking to define constraints that can allow multiple NFSV4
> filesystem/exports to be started concurrently (they belong to the same LVM).
> I also have multiple access points. M
Hi,
On Tue, Aug 05, 2014 at 09:29:45AM +0200, Jeroen Groenewegen van der Weyden
wrote:
> Hi,
>
> I used the adjusted RA resource script as well and I get the same error
>
> "2014-07-09T10:52:39.679297+02:00 xen01 lrmd[3443]: notice:
> operation_finished: dnsdhcp_start_0:31734:stderr [
> /ro
Hi,
I'm working with SLES 11 SP3 and pacemaker 1.1.10-0.15.25
I'm looking to define constraints that can allow multiple NFSV4
filesystem/exports to be started concurrently (they belong to the same LVM). I
also have multiple access points. My model looks like this:
| FS1 -
Hi,
I used the adjusted RA resource script as well and I get the same error
"2014-07-09T10:52:39.679297+02:00 xen01 lrmd[3443]: notice:
operation_finished: dnsdhcp_start_0:31734:stderr [
/root/xen_storage/dns_dhcp/dnsdhcp.xen:24: config parsing error near
`dnsdhcp': syntax error, unexpected
