>>> Jorge Fábregas schrieb am 08.09.2015 um 17:45
in
Nachricht <55ef029c.3000...@gmail.com>:
> Hi,
>
> I've read about how important is the relationship between the different
> parameters of the SBD device (msgwait & watchdog timeout) & Pacemaker's
> stonith timeout. However I've just encountere
On 08/09/15 09:46 PM, Justin Pryzby wrote:
> In case it helps, I take that to mean:
>
> fence_virsh is a python program, which is attempting to run ssh, but failing.
>
> Can you check:
>
> which ssh # make sure it's not strange ssh in a /usr/local or such;
> ls -Z `which fence_virsh` `which ssh`
Hi all,
I've been using KVM-based VMs as a testbed for clusters for ages,
always using fence_virsh.
I noticed today though that fence_virsh is now being blocked by
selinux (rhel 6.7, fully updated as of today):
type=AVC msg=audit(1441752343.878:3269): avc: denied { execute } for
pid=8848 c
On 09/08/2015 05:33 PM, Andrew Beekhof wrote:
>
>> On 9 Sep 2015, at 12:13 am, Ken Gaillot wrote:
>>
>> On 09/07/2015 07:48 AM, Jorge Fábregas wrote:
>>> On 09/07/2015 03:27 AM, Digimer wrote:
And this is why I am nervous; It is always ideal to have a primary fence
method that has a met
> On 9 Sep 2015, at 12:13 am, Ken Gaillot wrote:
>
> On 09/07/2015 07:48 AM, Jorge Fábregas wrote:
>> On 09/07/2015 03:27 AM, Digimer wrote:
>>> And this is why I am nervous; It is always ideal to have a primary fence
>>> method that has a method of confirming the 'off' state. IPMI fencing can
>
On 09/07/2015 08:42 PM, Jorge Fábregas wrote:
> If anyone from SUSE here could recreate it that would be great.
Please open an SR - there are SUSE folks on this list but with an SR you
get the right people working on the bug.
greetings
Kai Dupke
Senior Product Manager
Server Product Line
--
Sell
Hi Yan,
Thank you for comment.
> Sounds weird. I've never encountered the issue before. Actually I
> haven't run it with heartbeat for years ;-) We'd probably have to find
> the pattern and produce it.
We still just began an investigation.
If there is the point that you think to be the cause
On 08/09/15 11:23 AM, Ken Gaillot wrote:
> Pacemaker's upstream master branch has a new feature that will be part
> of the eventual 1.1.14 release.
>
> Fencing topology is used when a node requires multiple fencing devices
> (in combination or as fallbacks). Currently, topologies must be
> specifi
On 09/08/2015 10:13 AM, Ken Gaillot wrote:
> Good news/bad news:
>
> Yes, pacemaker supports complex hierarchies of multiple fencing devices,
> which it calls "fencing topology". There is a small example at
> http://clusterlabs.org/doc/en-US/Pacemaker/1.1-pcs/html-single/Pacemaker_Explained/index.
Hi,
I've read about how important is the relationship between the different
parameters of the SBD device (msgwait & watchdog timeout) & Pacemaker's
stonith timeout. However I've just encountered something that I never
considered: the time elapsed until a node is fully up (after being
fenced) aga
Pacemaker's upstream master branch has a new feature that will be part
of the eventual 1.1.14 release.
Fencing topology is used when a node requires multiple fencing devices
(in combination or as fallbacks). Currently, topologies must be
specified by node name (or a regular expression matching nod
Hi Hideo,
On 09/08/2015 04:28 AM, renayama19661...@ybb.ne.jp wrote:
> Hi All,
>
> A problem produced us in Pacemaker1.0.13.
>
> * RHEL6.4(kernel-2.6.32-358.23.2.el6.x86_64)
> * SNMP：
>* net-snmp-libs-5.5-49.el6_5.1.x86_64
>* hp-snmp-agents-9.50-2564.40.rhel6.x86_64
>* net-snmp-uti
On 09/07/2015 07:48 AM, Jorge Fábregas wrote:
> On 09/07/2015 03:27 AM, Digimer wrote:
>> And this is why I am nervous; It is always ideal to have a primary fence
>> method that has a method of confirming the 'off' state. IPMI fencing can
>> do this, as can hypervisor-based fence methods like fence
>>> Jorge Fábregas schrieb am 08.09.2015 um 15:41
in
Nachricht <55eee59e.6060...@gmail.com>:
> On 09/08/2015 09:29 AM, Jorge Fábregas wrote:
>> Who's feeding the watchdog timer? What or where's the watchdog timer
>> since there's none defined?
>
> Arrgh. It was kdump. By doing "chkconfig b
>>> "Ulrich Windl" schrieb am 08.09.2015 um
> blocks to grep. As grep is designed to read from streads there is not much
s/streads/streams/ # Sorry!
___
Users mailing list: Users@clusterlabs.org
http://clusterlabs.org/mailman/listinfo/users
Project
On 09/08/2015 09:29 AM, Jorge Fábregas wrote:
> Who's feeding the watchdog timer? What or where's the watchdog timer
> since there's none defined?
Arrgh. It was kdump. By doing "chkconfig boot.kdump off" and
restarting then I got the expected behavior (permanent freeze without
rebooting).
Hi,
I'm doing some tests with SBD on SLES 11 SP4 (specially on how it
behaves with the "hardware" watchdog timer) but I went back to a prior
snapshot (fresh installation) where I removed the Intel 6300esb timer
definition from qemu & I disabled nmi_watchdog by putting the proper
argument to GRUB's
08.09.2015 15:18, Ulrich Windl wrote:
Vladislav Bogdanov schrieb am 08.09.2015 um 14:05 in
Nachricht <55eecefb.8050...@hoster-ok.com>:
Hi,
just discovered very interesting issue.
If there is a system user with very big UID (8002 in my case),
then crm_report (actually 'grep' it runs) consu
>>> Vladislav Bogdanov schrieb am 08.09.2015 um 14:05 in
Nachricht <55eecefb.8050...@hoster-ok.com>:
> Hi,
>
> just discovered very interesting issue.
> If there is a system user with very big UID (8002 in my case),
> then crm_report (actually 'grep' it runs) consumes too much RAM.
>
> Relev
Hi,
just discovered very interesting issue.
If there is a system user with very big UID (8002 in my case),
then crm_report (actually 'grep' it runs) consumes too much RAM.
Relevant part of the process tree at that moment looks like (word-wrap off):
USER PID %CPU %MEMVSZ RSS TTY
Hi All,
We intend to change some patches.
We withdraw this patch.
Best Regards,
Hideo Yamauchi.
- Original Message -
> From: "renayama19661...@ybb.ne.jp"
> To: ClusterLabs-ML
> Cc:
> Date: 2015/9/7, Mon 09:06
> Subject: [ClusterLabs] [Patch][glue][external/libvirt] Conversion to a lo
21 matches
Mail list logo
