Hello Ricardo,
On 2/21/20 9:59 AM, Dan Swartzendruber wrote:
I believe you in fact want each fence agent to run on the other node, yes.
On February 20, 2020, at 6:23 PM, Ricardo Esteves wrote:
Hi,
I have a question regarding fencing, i have 2 physical servers: node01,
node02, each one has
I believe you in fact want each fence agent to run on the other node, yes.
On February 20, 2020, at 6:23 PM, Ricardo Esteves wrote:
Hi,
I have a question regarding fencing, i have 2 physical servers: node01,
node02, each one has an ipmi card
so i create 2 fence devices:
fence_ipmi_node01
Hi,
I have a question regarding fencing, i have 2 physical servers: node01,
node02, each one has an ipmi card
so i create 2 fence devices:
fence_ipmi_node01 (with ip of ipmi card of server node01) - with
constraint to prefer to run on node01
fence_ipmi_node02 (with ip of ipmi card of server
Hi,
I'm using Fedora 31 (x86_64).
For apache i can use the ocf agent sure, but i have other resources for
who don't exist an ocf agent, so for them i need to use systemd.
All ocf and lsb type resources start ok on boot, only systemd resources
have this problem.
I already enabled debug for
On February 20, 2020 10:29:54 PM GMT+02:00, Maverick wrote:
>
>> Hi Maverick,
>>
>>
>> According this thread:
>>
>https://lists.clusterlabs.org/pipermail/users/2016-December/021053.html
>>
>> You have 'startup-fencing' is set to false.
>>
>> Check it out - maybe this is your reason.
>>
>> Best
Hi,
it seems systemd is stopping Apache, so the cluster is surprised:
Feb 20 19:40:01 boss1 systemd[1]: Stopping The Apache HTTP Server...
IMHO it's best to dump systemd, but that's just my opinion...
>>> Maverick 20.02.2020, 21:30 >>>
> Hi Maverick,
>
>
> According this thread:
>
> Hi Maverick,
>
>
> According this thread:
> https://lists.clusterlabs.org/pipermail/users/2016-December/021053.html
>
> You have 'startup-fencing' is set to false.
>
> Check it out - maybe this is your reason.
>
> Best Regards,
> Strahil Nikolov
Yes, i have stonith disabled, because as soon
On February 20, 2020 9:35:07 PM GMT+02:00, Maverick wrote:
>
>Manually it starts ok, no problems:
>
>pcs resource debug-start apache --full
>(unpack_config) warning: Blind faith: not fencing unseen nodes
>Operation start for apache (systemd::httpd) returned: 'ok' (0)
>
>
>On 20/02/2020 16:46,
Manually it starts ok, no problems:
pcs resource debug-start apache --full
(unpack_config) warning: Blind faith: not fencing unseen nodes
Operation start for apache (systemd::httpd) returned: 'ok' (0)
On 20/02/2020 16:46, Strahil Nikolov wrote:
> On February 20, 2020 12:49:43 PM GMT+02:00,
Hi folks,
My test system consists of two nodes running CentOS 7 and DRBD. The
Pacemaker configuration below results in a system with a preferred
master, bd3c7, and a slave, bd4c7, between which a set of resources
will fail over and later back, within about two seconds either way,
Strahil, you are correct - that was my bad typing.The status url is using the virtual_ip and is accessible from either node of the cluster but from nowhere else.___After this:pcs resource create ContentServer ocf:heartbeat:apache configfile=/usr/local/httpd/conf/httpd.conf port=1090
>>> Ulrich Windl schrieb am 19.02.2020 um 14:28 in Nachricht <5E4D37F4.D48 :
>>> 161 :
60728>:
> Hi!
>
> I wonder: Does there exist some RA to add/remove iptables rules?
> A quick check just brought up these:
> /usr/lib/ocf/resource.d/heartbeat/IPaddr2
>
On February 20, 2020 12:49:43 PM GMT+02:00, Maverick wrote:
>
>> You really need to debug the start & stop of tthe resource .
>>
>> Please try the debug procedure and provide the output:
>> https://wiki.clusterlabs.org/wiki/Debugging_Resource_Failures
>>
>> Best Regards,
>> Strahil Nikolov
>
>
Am 20.02.20 um 15:14 schrieb Rafael David Tinoco:
>
we run a 2-system cluster for Samba with Ubuntu 14.04 and Samba,
Corosync and Pacemaker from the Ubuntu repos. We wanted to update
to Ubuntu 16.04 but it failed:
>
> Quick question, perhaps unimportant to this forum, but, since
Rasca Gmelch napsal(a):
Am 19.02.20 um 19:20 schrieb Strahil Nikolov:
On February 19, 2020 6:31:19 PM GMT+02:00, Rasca wrote:
Hi,
we run a 2-system cluster for Samba with Ubuntu 14.04 and Samba,
Corosync and Pacemaker from the Ubuntu repos. We wanted to update
to Ubuntu 16.04 but it failed:
Hi,
This is a tentative schedule for resource-agents v4.5.0:
4.5.0-rc1: February 27.
4.5.0: March 5.
PostgreSQL 12 support has been added to the pgsql agent, so make sure
to give it some additional testing with v12 and older versions to
ensure it's working correctly.
I've modified the
>>> we run a 2-system cluster for Samba with Ubuntu 14.04 and Samba,
>>> Corosync and Pacemaker from the Ubuntu repos. We wanted to update
>>> to Ubuntu 16.04 but it failed:
Quick question, perhaps unimportant to this forum, but, since this is a
samba HA setup, why to update to 16.04 and not to
> You really need to debug the start & stop of tthe resource .
>
> Please try the debug procedure and provide the output:
> https://wiki.clusterlabs.org/wiki/Debugging_Resource_Failures
>
> Best Regards,
> Strahil Nikolov
Hi,
Correct me if i'm wrong, but i think that procedure doesn't work
Am 19.02.20 um 19:20 schrieb Strahil Nikolov:
> On February 19, 2020 6:31:19 PM GMT+02:00, Rasca
> wrote:
>> Hi,
>>
>> we run a 2-system cluster for Samba with Ubuntu 14.04 and Samba,
>> Corosync and Pacemaker from the Ubuntu repos. We wanted to update
>> to Ubuntu 16.04 but it failed:
>>
>> I
19 matches
Mail list logo
