k around the issue with the empty hostlist I've altered the
agent to trick stonith(glue). It echos 0 instead of "" :)
--
Laurent
_______
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listi
disables the
> port list queries
>
> so I guess there's no need to fill a new ticket :)
> Thanks,
Hmm it still feels like there's something funny with this issue.
is the FenceAgentAPI relevant with pacemaker ?
I don't see why the fencing agent should return 1 when
k to the status action that was always returning rc=0
- gethosts returning rc=0 with an empty hostlist also disables the
port list queries
so I guess there's no need to fill a new ticket :)
Thanks,
--
Laurent
___
Pacemaker mailing list: Pa
27;ve just reproduced it again starting a new cluster from scratch and
using the above config.
Let's say the stonith agent runs on nodes 02, 03 and 04.
The first time I run stonith-admin -l "elasticsearch-01" on node 02,
03 or 04 it returns "No devices found". From the s
Hi,
I've just observed something weird.
A node is running a stonith resource for which gethosts gives an empty
node list. The result of stonith_admin -l does include it in the
device list !
result of "stonith_admin -l elasticsearch-05" run from
elasticsearch-06 :
stonith-xen-peatbull
stonith-x
uot; messages
>>>>
>>>> or "warning: attrd_cib_callback: Update
>>>> last-failure-vm-elasticsearch-02=(null) failed: No such device or
>>>> address"
>>>>
>>>> is that harmful ?
>>>
>>> No, but it probabl
st-failure-vm-elasticsearch-02=(null) failed: No such device or
>> address"
>>
>> is that harmful ?
>
> No, but it probably doesn't need to printed so often either
ok.
>>
>> 4) crm_mon -d -p /tmp/t.pid -h /tmp/t.html not creating the pid file
>> anym
David Vossel writes:
>> > When do you see this? Is pacemaker fencing a node when this
>> > occurs, or are you manually doing it using stonith_admin?
>>
>> oh sorry i forgot to say.
>> triggering it by stonith_admin -l nodename
>
> Yeah, looking at the code that should still work. Can you file
on this test setup, i'm pretty sure the
fencing was also failing for no apparent reason.
But that's something to be expected with a timeout that low.
--
Laurent
___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.
on)
Can you reproduce any of these issues ?
(been able to reproduce 1 and 3 with yesterday's head, i've not paid
attention to 2 and 4 at that time
I'd be ok to provide more info and fill tickets if you do.
--
Laurent
_______
Pacemaker mai
Andrew Beekhof writes:
>> I'm also impacted by this issue. (running pcmk 1.1.7 and corosync 1.4.4)
>> there's a closed bug report here :
>> http://bugs.clusterlabs.org/show_bug.cgi?id=5040
>> as far as i understand it's an issue with coroync.
>>
>> Pacemaker 1.1.8 is supposed to have workarounds
1.4.4
It's ok with pcmk 1.1.8 and corosync 2.1.0. But I do have some issues
with 1.1.8 that make it unsuitable for production env yet.
--
Laurent
___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/lis
where the other iscsi clone is running.
Could you tell me what's the behavior you're observing ?
Thanks in advance.
For more information, bug report is at:
http://developerbugs.linux-foundation.org/show_bug.cgi?id=2167
--
Laurent
___
Pacemaker mailing list
Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
alamd1 -> dualamd3)
pengine: [28017]: notice: LogActions: Leave resource
dom0-iscsi1-cnx1:0#011(Started dualamd3)
pengine: [28017]: notice: LogActions: Move resource
dom0-iscsi1-cnx1:1#011(Started dualamd1 -> cardhu)
Is it because of my rules, am I missing something ?
Should I add rules to make sur
14 matches
Mail list logo
