(13.07.12 22:48), emmanuel segura wrote:
Hi


try to disable selinux

Though I tried it, the result did not change.

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Jul 12 16:46:10 dev1 setroubleshoot: SELinux is preventing /usr/bin/virsh
from getattr access on the file /usr/bin/ssh. For complete SELinux
messages. run sealert -l 3d5afba4-40a5-41ff-9530-3839da8a8c4e
Jul 12 16:46:10 dev1 setroubleshoot: SELinux is preventing /usr/bin/ssh
from execute access on the file /usr/bin/ssh. For complete SELinux
messages. run sealert -l 9ba75cc7-cde9-4b76-ba44-142199e119e4
Jul 12 16:46:11 dev1 setroubleshoot: SELinux is preventing /usr/bin/ssh
from execute access on the file /usr/bin/ssh. For complete SELinux
messages. run sealert -l 9ba75cc7-cde9-4b76-ba44-142199e119e4
Jul 12 16:46:11 dev1 setroubleshoot: SELinux is preventing /usr/bin/ssh
from execute access on the file /usr/bin/ssh. For complete SELinux
messages. run sealert -l 9ba75cc7-cde9-4b76-ba44-142199e119e4
Jul 12 16:46:22 dev1 setroubleshoot: SELinux is preventing /usr/bin/ping
from using the setcap access on a process. For complete SELinux messages.
run sealert -l
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++


Why you did two group for your stonith resource?, i know this is not the
problem, but i'm curious

Originally I made grouping because I used libvirt and other stonith resources.

group grpStonith1 \
  prmStonith1-1 \   <- plugin which we made
  prmStonith1-2 \   <- libvirt
  prmStonith1-3     <- meatware

"group" is a trace when I left only libvirt to simplify an event.

Thanks



Thanks



2013/7/12 Kazunori INOUE <inouek...@intellilink.co.jp>


Hi,

I'm using pacemaker-1.1.10.
When a pacemaker's process crashed, the node is sometimes fenced or is not
sometimes fenced.
Is this the assumed behavior?

procedure:
$ systemctl start pacemaker
$ crm configure load update test.cli
$ pkill -9 lrmd

attachment:
STONITH.tar.bz2 : it's crm_report when fenced
notSTONITH.tar.bz2 : it's crm_report when not fenced

Best regards.

_______________________________________________
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

_______________________________________________
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

Reply via email to