On 25/07/2013, at 7:03 PM, Kazunori INOUE wrote:
> (13.07.25 11:00), Andrew Beekhof wrote:
>>
>> On 24/07/2013, at 7:40 PM, Kazunori INOUE
>> wrote:
>>
>>> (13.07.18 19:23), Andrew Beekhof wrote:
On 17/07/2013, at 6:53 PM, Kazunori INOUE
wrote:
> (13.07.16 21:18),
(13.07.25 18:03), Kazunori INOUE wrote:
(13.07.25 11:00), Andrew Beekhof wrote:
On 24/07/2013, at 7:40 PM, Kazunori INOUE wrote:
(13.07.18 19:23), Andrew Beekhof wrote:
On 17/07/2013, at 6:53 PM, Kazunori INOUE wrote:
(13.07.16 21:18), Andrew Beekhof wrote:
On 16/07/2013, at 7:04 PM,
(13.07.25 11:00), Andrew Beekhof wrote:
On 24/07/2013, at 7:40 PM, Kazunori INOUE wrote:
(13.07.18 19:23), Andrew Beekhof wrote:
On 17/07/2013, at 6:53 PM, Kazunori INOUE wrote:
(13.07.16 21:18), Andrew Beekhof wrote:
On 16/07/2013, at 7:04 PM, Kazunori INOUE wrote:
(13.07.15 11:00)
On 24/07/2013, at 7:40 PM, Kazunori INOUE wrote:
> (13.07.18 19:23), Andrew Beekhof wrote:
>>
>> On 17/07/2013, at 6:53 PM, Kazunori INOUE
>> wrote:
>>
>>> (13.07.16 21:18), Andrew Beekhof wrote:
On 16/07/2013, at 7:04 PM, Kazunori INOUE
wrote:
> (13.07.15 11:00),
(13.07.18 19:23), Andrew Beekhof wrote:
On 17/07/2013, at 6:53 PM, Kazunori INOUE wrote:
(13.07.16 21:18), Andrew Beekhof wrote:
On 16/07/2013, at 7:04 PM, Kazunori INOUE wrote:
(13.07.15 11:00), Andrew Beekhof wrote:
On 12/07/2013, at 6:28 PM, Kazunori INOUE wrote:
Hi,
I'm using p
On 17/07/2013, at 6:53 PM, Kazunori INOUE wrote:
> (13.07.16 21:18), Andrew Beekhof wrote:
>>
>> On 16/07/2013, at 7:04 PM, Kazunori INOUE
>> wrote:
>>
>>> (13.07.15 11:00), Andrew Beekhof wrote:
On 12/07/2013, at 6:28 PM, Kazunori INOUE
wrote:
> Hi,
>
>
(13.07.16 21:18), Andrew Beekhof wrote:
On 16/07/2013, at 7:04 PM, Kazunori INOUE wrote:
(13.07.15 11:00), Andrew Beekhof wrote:
On 12/07/2013, at 6:28 PM, Kazunori INOUE wrote:
Hi,
I'm using pacemaker-1.1.10.
When a pacemaker's process crashed, the node is sometimes fenced or is not
s
On 16/07/2013, at 7:04 PM, Kazunori INOUE wrote:
> (13.07.15 11:00), Andrew Beekhof wrote:
>>
>> On 12/07/2013, at 6:28 PM, Kazunori INOUE
>> wrote:
>>
>>> Hi,
>>>
>>> I'm using pacemaker-1.1.10.
>>> When a pacemaker's process crashed, the node is sometimes fenced or is not
>>> sometimes f
(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
(13.07.15 11:00), Andrew Beekhof wrote:
On 12/07/2013, at 6:28 PM, Kazunori INOUE wrote:
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?
Yes.
Sometimes the dev1 respawns the process
On 12/07/2013, at 6:28 PM, Kazunori INOUE wrote:
> 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?
Yes.
Sometimes the dev1 respawns the processes fast enough that dev2 gets th
On 12/07/13 04:28, Kazunori INOUE wrote:
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
attac
Hi
try to disable selinux
+++
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-3839da8a8c
13 matches
Mail list logo