On Sat, Jul 2, 2016 at 1:26 AM, Ken Gaillot wrote:
> On 07/01/2016 04:48 AM, Jan Pokorný wrote:
>> On 01/07/16 09:23 +0200, Ulrich Windl wrote:
>> Ken Gaillot schrieb am 30.06.2016 um 18:58 in
>> Nachricht
>>> <57754f9f.8070...@redhat.com>:
On Fri, Jul 1, 2016 at 7:48 PM, Jan Pokorný wrote:
> On 01/07/16 09:23 +0200, Ulrich Windl wrote:
> Ken Gaillot schrieb am 30.06.2016 um 18:58 in
> Nachricht
>> <57754f9f.8070...@redhat.com>:
>>> I've been meaning to address the implementation
Oh, and I forgot to add that when I try to create the LUN with the
implementation=”lio” parameter, I see the following:
[root@hdc1anas002 ec2-user]# pcs resource create hdcvbnas_lun0
ocf:heartbeat:iSCSILogicalUnit
target_iqn="iqn.2016-07.local.hsinawsdev:hdcvadbs-witness" lun="0"
I’m having some difficulty setting up a PCS/Corosync HA iSCSI target. I’m able
to create the iSCSI target resource (it spins up the target service properly
when the pcs command is issued. However, when I attempt to create a LUN, I get
nothing but error messages. This works:
pcs resource create
On 13/07/16 12:50 +0200, emmanuel segura wrote:
> using pcs resource unmanage leave the monitoring resource actived, I
> usually set the monitor interval=0 :)
Some time ago, I've filed a bug against pcs for it to perform these
two steps in one go: https://bugzilla.redhat.com/1303969
This slowly
On 07/13/2016 09:56 AM, emmanuel segura wrote:
> enabled=false works with every pacemaker versions?
It was introduced in Pacemaker 1.0.2, so realistically, yes :)
> 2016-07-13 16:48 GMT+02:00 Ken Gaillot :
>> On 07/13/2016 05:50 AM, emmanuel segura wrote:
>>> using pcs
On 07/13/2016 05:50 AM, emmanuel segura wrote:
> using pcs resource unmanage leave the monitoring resource actived, I
> usually set the monitor interval=0 :)
Yep :)
An easier way is to set "enabled=false" on the monitor, so you don't
have to remember what your interval was later. You can set it
Am 13.07.2016 um 13:17 schrieb Heiko Reimer:
Am 13.07.2016 um 11:09 schrieb Klaus Wenninger:
On 07/13/2016 09:24 AM, Heiko Reimer wrote:
Am 13.07.2016 um 09:09 schrieb Li Junliang:
在 2016-07-13三的 08:59 +0200,Heiko Reimer写道:
Hi,
i try to setup pacemaker apache resource with
On 07/13/2016 03:10 AM, Ulrich Windl wrote:
Ken Gaillot schrieb am 12.07.2016 um 21:19 in
Nachricht
> <578542bf.9010...@redhat.com>:
>> On 07/12/2016 01:16 AM, Ulrich Windl wrote:
>
> [...]
>>> What I mean is: there is no "success status" for STONITH; it is
"Lentes, Bernd" writes:
> Starting or stopping drbd with start/stop does not work neither for the ms
> ressource nor for the primitive.
> If i try to stop it keeps running. Also if i do a cleanup before (for both
> resources).
> Which resource should i stop
Hi,
i'm new to HA-cluster. I'm currently establishing a two-node cluster and
playing around with it.
I habe a primitive drdb resource and a corresponding ms one:
crm(live)resource# status
Master/Slave Set: ms_drbd_r0 [prim_drbd_r0]
Masters: [ sunhb58820 ]
Slaves: [ sunhb65278 ]
Am 13.07.2016 um 11:09 schrieb Klaus Wenninger:
On 07/13/2016 09:24 AM, Heiko Reimer wrote:
Am 13.07.2016 um 09:09 schrieb Li Junliang:
在 2016-07-13三的 08:59 +0200,Heiko Reimer写道:
Hi,
i try to setup pacemaker apache resource with ocf:heartbeat:apache.
But
when pacemaker try to start the
using pcs resource unmanage leave the monitoring resource actived, I
usually set the monitor interval=0 :)
2016-07-11 10:43 GMT+02:00 Tomas Jelinek :
> Dne 9.7.2016 v 06:39 jaspal singla napsal(a):
>>
>> Hello Everyone,
>>
>> I need little help, if anyone can give some
On 07/13/2016 09:24 AM, Heiko Reimer wrote:
>
> Am 13.07.2016 um 09:09 schrieb Li Junliang:
>> 在 2016-07-13三的 08:59 +0200,Heiko Reimer写道:
>>> Hi,
>>>
>>> i try to setup pacemaker apache resource with ocf:heartbeat:apache.
>>> But
>>> when pacemaker try to start the resource i get
>>>
>>> Failed
Am 13.07.2016 um 09:09 schrieb Li Junliang:
在 2016-07-13三的 08:59 +0200,Heiko Reimer写道:
Hi,
i try to setup pacemaker apache resource with ocf:heartbeat:apache.
But
when pacemaker try to start the resource i get
Failed Actions:
* apache2_start_0 on node1 'not installed' (5): call=186,
15 matches
Mail list logo