On 05/02/16 14:22 -0500, nameless wrote:
> Hi
Hello >nameless<,
technical aspect aside, it goes without saying that engaging in
a community assumes some level of cultural and social compatibility.
Otherwise there is a danger the cluster will partition, and
that would certainly be unhelpful.
I've found two bugs in the fence_ec2 script found in this RPM:
fence_ec2-0.1-0.10.1.x86_64.rpm
I believe this is the latest and greatest, but I may be wrong. I'm not
sure where to post these fixes, so I'm starting here. If there is a better
place to post, please let me know.
The errors are:
1.
On 01/28/2016 10:27 PM, 飯田 雄介 wrote:
> Hi, Ken
>
> I have to get the log.
> shutdown the -r now ran to "03:00:22".
> rsyslog also "03:00:22" to receive a TERM appears to have stopped.
>
> Regards, Yusuke
Hello Yusuke,
I see in your logs that /var/log/messages does not have any messages at
all
> am configuring shared storage for 2 nodes (Cent 7) installed
> pcs/gfs2-utils/lvm2-cluster when creating resource unable to start dlm
>
> crm_verify -LV
>error: unpack_rsc_op:Preventing dlm from re-starting anywhere:
> operation start failed 'not configured' (6)
Are you using the
On 04.02.2016 15:43, Bogdan Dobrelya wrote:
> Hello.
> Regarding the original issue, good news are the resource-agents
> ocf-shellfuncs is no more causing fork bombs to the dummy OCF RA [0]
> after the fix [1] done. The bad news are that "self-forking" monitors
> issue seems remaining for the
