On 04/25/2017 09:32 AM, Bratislav Petkovic wrote:
> I want to make active/active cluster with two physical servers.
>
> On the servers are installed: oraclelinux-release-7.2-1.0.5.el7.x86_64,
>
> Pacemaker 1.1.13-10.el7, Corosync Cluster Engine, version '2.3.4',
>
> pcs 0.9.143. Cluster starts
On 04/25/2017 04:32 PM, Bratislav Petkovic wrote:
>
> I want to make active/active cluster with two physical servers.
>
> On the servers are installed: oraclelinux-release-7.2-1.0.5.el7.x86_64,
>
> Pacemaker 1.1.13-10.el7, Corosync Cluster Engine, version '2.3.4',
>
> pcs 0.9.143. Cluster starts
On 04/25/2017 09:14 AM, Lentes, Bernd wrote:
>
>
> - On Apr 24, 2017, at 11:11 PM, Ken Gaillot kgail...@redhat.com wrote:
>
>> On 04/24/2017 02:33 PM, Lentes, Bernd wrote:
>>>
>>> - On Apr 24, 2017, at 9:11 PM, Ken Gaillot kgail...@redhat.com wrote:
>>>
>> primitive
I want to make active/active cluster with two physical servers.
On the servers are installed: oraclelinux-release-7.2-1.0.5.el7.x86_64,
Pacemaker 1.1.13-10.el7, Corosync Cluster Engine, version '2.3.4',
pcs 0.9.143. Cluster starts without a problem and I create a resource
ClusterIP that is in the
- On Apr 24, 2017, at 11:11 PM, Ken Gaillot kgail...@redhat.com wrote:
> On 04/24/2017 02:33 PM, Lentes, Bernd wrote:
>>
>> - On Apr 24, 2017, at 9:11 PM, Ken Gaillot kgail...@redhat.com wrote:
>>
> primitive prim_vnc_ip_mausdb IPaddr \
>params ip=146.107.235.161
On 18/04/17 15:40, Ken Gaillot wrote:
On 04/18/2017 09:14 AM, lejeczek wrote:
On 18/04/17 14:45, Digimer wrote:
On 18/04/17 07:31 AM, lejeczek wrote:
.. device_block & device_unblock in dmesg.
and I see that the LVM resource would fail.
This to me seems to happen randomly, or I fail to
- On Apr 25, 2017, at 8:08 AM, Ulrich Windl
ulrich.wi...@rz.uni-regensburg.de wrote:
> Berdn
>
> you are long enough on this list to know that the reason for your failure is
> most likely to be found in the logs which you did not provide. Couldn't you
> find out yourself from the logs?
>
On Tue, Apr 25, 2017 at 10:27:43AM +0200, Jehan-Guillaume de Rorthais wrote:
> On Tue, 25 Apr 2017 10:02:21 +0200
> Lars Ellenberg wrote:
>
> > On Mon, Apr 24, 2017 at 03:08:55PM -0500, Ken Gaillot wrote:
> > > Hi all,
> > >
> > > Pacemaker 1.1.17 will have a feature
On Tue, 25 Apr 2017 10:02:21 +0200
Lars Ellenberg wrote:
> On Mon, Apr 24, 2017 at 03:08:55PM -0500, Ken Gaillot wrote:
> > Hi all,
> >
> > Pacemaker 1.1.17 will have a feature that people have occasionally asked
> > for in the past: the ability to start a node in
On Mon, Apr 24, 2017 at 03:08:55PM -0500, Ken Gaillot wrote:
> Hi all,
>
> Pacemaker 1.1.17 will have a feature that people have occasionally asked
> for in the past: the ability to start a node in standby mode.
I seem to remember that at some deployment,
we set the node instance attribute
>>> Ken Gaillot schrieb am 24.04.2017 um 22:08 in
>>> Nachricht
:
> Hi all,
>
> Pacemaker 1.1.17 will have a feature that people have occasionally asked
> for in the past: the ability to start a node in standby mode.
>
> It
Ken Gaillot writes:
> Hi all,
>
> Pacemaker 1.1.17 will have a feature that people have occasionally asked
> for in the past: the ability to start a node in standby mode.
>
> It will be controlled by an environment variable (set in
> /etc/sysconfig/pacemaker,
Berdn
you are long enough on this list to know that the reason for your failure is
most likely to be found in the logs which you did not provide. Couldn't you
find out yourself from the logs?
Regards,
Ulrich
>>> "Lentes, Bernd" schrieb am 24.04.2017
um
13 matches
Mail list logo