On Mon, 2018-08-13 at 18:13 +0200, FeldHost™ Admin wrote:
> Hello, thanks for reply, so basiclly, can I leverage existing cli
> tools and do for ex. call crm node fence xyz?
Yes
>
> S pozdravem Kristián Feldsam
> Tel.: +420 773 303 353, +421 944 137 535
> E-mail.: supp...@feldhost.cz
>
>
Hello, thanks for reply, so basiclly, can I leverage existing cli tools and do
for ex. call crm node fence xyz?
S pozdravem Kristián Feldsam
Tel.: +420 773 303 353, +421 944 137 535
E-mail.: supp...@feldhost.cz
www.feldhost.cz - FeldHost™ – Hostingové služby prispôsobíme vám. Máte
špecifické
On 13/08/18 18:13 +0300, Vladislav Bogdanov wrote:
> 10.08.2018 19:52, Ulrich Windl wrote:
>>
>> A simple question: One of my RAs uses $HA_RSCTMP in SLES11 SP4, and it
>> reports the following problem:
>> WARNING: Unwritable HA_RSCTMP directory /var/run/resource-agents - using
>> /tmp
>
>
On 13/08/18 09:27 -0500, Ryan Thomas wrote:
> I've had similar problems in the past. In my case, it was because
> pacemaker was running as user 'hacluster' in group 'haclient', so it didn't
> have permission to access the root owned file. So to fix the problem, I
> changed the ownership of the
On Sat, 2018-08-11 at 17:38 +0200, FeldHost™ Admin wrote:
> Hi all, I have question:
>
> We have Corosync/Pacemaker cluster running for KVM virtualisation. VM
> Instances are managed by external software (Opennebula). To achieve
> automatic migration of running VMs from failed node, external sw
10.08.2018 19:52, Ulrich Windl wrote:
Hi!
A simple question: One of my RAs uses $HA_RSCTMP in SLES11 SP4, and it reports
the following problem:
WARNING: Unwritable HA_RSCTMP directory /var/run/resource-agents - using /tmp
Just make sure you avoid using that code in 'meta-data' action
I've had similar problems in the past. In my case, it was because
pacemaker was running as user 'hacluster' in group 'haclient', so it didn't
have permission to access the root owned file. So to fix the problem, I
changed the ownership of the file that was causing the permissions error.
e.g
On 13/08/18 09:00, Jan Friesse wrote:
> Chris Walker napsal(a):
>> Hello,
>>
>> Before Pacemaker can declare a node as 'offline', the Corosync layer
>> must first declare that the node is no longer part of the cluster
>> after waiting a full token timeout. For example, if I manually
>> STONITH a
>>> Jan Friesse schrieb am 13.08.2018 um 10:00 in
>>> Nachricht
<4ae1601b-2ce8-1f3b-90f3-773a2d842...@redhat.com>:
> Chris Walker napsal(a):
>> Hello,
>>
>> Before Pacemaker can declare a node as 'offline', the Corosync layer
>> must first declare that the node is no longer part of the cluster
Chris Walker napsal(a):
Hello,
Before Pacemaker can declare a node as 'offline', the Corosync layer
must first declare that the node is no longer part of the cluster after
waiting a full token timeout. For example, if I manually STONITH a node
with 'crm -F node fence node2', even if the
10 matches
Mail list logo
