On 3/29/21 5:24 PM, Tomas Jelinek wrote:
If you stopped a node and you want it to start and reconnect to its
cluster, run 'pcs cluster start' on the node. You may also run 'pcs
cluster start --all' or (in your case) 'pcs cluster start node1' on
any cluster node.
Maybe for better understanding
Thank you.
Then, if a node disconnected then how it could back to the cluster chain?
On Monday, March 29, 2021, 06:13:09 PM GMT+4:30, Tomas Jelinek
wrote:
Hi Jason,
Regarding point 3:
Most pcs commands operate on the local node. If you stop a cluster on a
node, pcs is unable to conn
If you stopped a node and you want it to start and reconnect to its
cluster, run 'pcs cluster start' on the node. You may also run 'pcs
cluster start --all' or (in your case) 'pcs cluster start node1' on any
cluster node.
Tomas
Dne 29. 03. 21 v 16:25 Jason Long napsal(a):
Thank you.
Then, i
Hi Jason,
Regarding point 3:
Most pcs commands operate on the local node. If you stop a cluster on a
node, pcs is unable to connect to cluster daemons on the node (since
they are not running) and prints an error message denoting that. This is
expected behavior.
Regards,
Tomas
Dne 27. 03. 2
Thank you.
I have other questions:
1- How can I launch a test lab?
2- Why, when I stop node1 manually and then start it again, I can't browse
"http://127.0.0.1:2080";? I think when I stopped node1 then Pacemaker forget to
back to the chain!!!
3- Why, when I stopped node1, then "pcs status nodes"
Then, how can I sure my configuration is OK?
In a clustering environment, when a node disconnected then another node must
replace it. Am I right?
I did a test:
I defined a NAT interface for my VM2 (node2) and used port forwarding:
"127.0.0.1:2090" on Host FORWARDING TO 127.0.0.1:80 on Guest.
Whe
On Thu, 2021-03-25 at 14:44 +, Jason Long wrote:
> Then, how can I sure my configuration is OK?
> In a clustering environment, when a node disconnected then another
> node must replace it. Am I right?
> I did a test:
> I defined a NAT interface for my VM2 (node2) and used port
> forwarding: "12
Thank you so much.
> Now you can proceed with the "Add Apache HTTP" section.
What does it mean? I did all steps in the document.
> Once apache is set up as a cluster resource, you should be able to contact
>the web server at the floating IP...
# pcs cluster stop node1
node1: Stopping Cluster (pa
On 3/25/21 9:55 AM, Jason Long wrote:
Thank you so much.
Now you can proceed with the "Add Apache HTTP" section.
What does it mean? I did all steps in the document.
Once apache is set up as a cluster resource, you should be able to contact
the web server at the floating IP...
# pcs clus
On Wed, 2021-03-24 at 10:50 +, Jason Long wrote:
> Thank you.
> Form node1 and node2, I can ping the floating IP address
> (192.168.56.9).
> I stopped node1:
>
> # pcs cluster stop node1
> node1: Stopping Cluster (pacemaker)...
> node1: Stopping Cluster (corosync)...
>
> And from both machine
Thank you.
Form node1 and node2, I can ping the floating IP address (192.168.56.9).
I stopped node1:
# pcs cluster stop node1
node1: Stopping Cluster (pacemaker)...
node1: Stopping Cluster (corosync)...
And from both machines, I can ping the floating IP address:
[root@node1 ~]# ping 192.168.56.9
Thanks.
The floating IP address must not use by other machines. I have two VMs that
using "192.168.57.6" and "192.168.57.7". Could the floating IP address be
"192.168.57.8"?
Which part of my configuration is wrong? Why, when I disconnect node1, then
node2 doesn't replace it?
On Wednesday,
Thanks, but I want to have a cluster with two nodes and nothing more!
On Tuesday, March 23, 2021, 07:59:57 PM GMT+4:30, Klaus Wenninger
wrote:
On 3/23/21 4:07 PM, Jason Long wrote:
> Thank you.
> Thus, where I must define my node2 IP address? When node1 disconnected, I
> want node2 r
On Tue, 2021-03-23 at 20:15 +, Jason Long wrote:
> Thanks.
> The floating IP address must not use by other machines. I have two
> VMs that using "192.168.57.6" and "192.168.57.7". Could the floating
> IP address be "192.168.57.8"?
Yes, if it's in the same subnet and not already in use by some
On Tue, 2021-03-23 at 19:07 +, Jason Long wrote:
> Thanks, but I want to have a cluster with two nodes and nothing more!
The end result is to have 2 nodes with 3 IP addresses:
* The first node has a permanently assigned IP address that it brings
up when it boots; this address is not managed b
Thank you.
Thus, where I must define my node2 IP address? When node1 disconnected, I want
node2 replace it.
On Tuesday, March 23, 2021, 01:03:39 PM GMT+4:30, Klaus Wenninger
wrote:
On 3/23/21 9:13 AM, Jason Long wrote:
> Thank you.
> But:
> https://www.clusterlabs.org/pacemaker/doc/
On 3/23/21 4:07 PM, Jason Long wrote:
Thank you.
Thus, where I must define my node2 IP address? When node1 disconnected, I want
node2 replace it.
You just need a single IP address that you are assigning to the virtual
IP resource.
And pacemaker is gonna move that IP address - along with the we
Thank you.
But:
https://www.clusterlabs.org/pacemaker/doc/en-US/Pacemaker/1.1/html/Clusters_from_Scratch/ch06.html
?
The floating IP address is:
https://www.clusterlabs.org/pacemaker/doc/en-US/Pacemaker/1.1/html/Clusters_from_Scratch/_add_a_resource.html
In the "Warning" written: "The chosen add
On 3/23/21 9:13 AM, Jason Long wrote:
Thank you.
But:
https://www.clusterlabs.org/pacemaker/doc/en-US/Pacemaker/1.1/html/Clusters_from_Scratch/ch06.html
?
The floating IP address is:
https://www.clusterlabs.org/pacemaker/doc/en-US/Pacemaker/1.1/html/Clusters_from_Scratch/_add_a_resource.html
I
Thank you.
From chapter 1 to 6, I never saw anything about configuring the floating IP
address! Am I wrong?
On Monday, March 22, 2021, 07:06:47 PM GMT+4:30, Ken Gaillot
wrote:
On Mon, 2021-03-22 at 08:15 +, Jason Long wrote:
> Thank you.
>
> My test lab use VirtualBox with two V
On Mon, 2021-03-22 at 17:31 +, Jason Long wrote:
> Thank you.
> From chapter 1 to 6, I never saw anything about configuring the
> floating IP address! Am I wrong?
Hi,
Chapter 6 should be "Create an Active/Passive Cluster", which adds a
floating IP, then Chapter 7 is "Add Apache HTTP Server as
On Mon, 2021-03-22 at 08:15 +, Jason Long wrote:
> Thank you.
>
> My test lab use VirtualBox with two VMs as below:
> VM1: This VM has two NICs (NAT, Host-only Adapter)
> VM2: This VM has one NIC (Host-only Adapter)
>
> On VM1, I use the NAT interface for the port forwarding:
> "127.0.0.1:208
Thank you.
My test lab use VirtualBox with two VMs as below:
VM1: This VM has two NICs (NAT, Host-only Adapter)
VM2: This VM has one NIC (Host-only Adapter)
On VM1, I use the NAT interface for the port forwarding: "127.0.0.1:2080" on
Host FORWARDING TO 127.0.0.1:80 on Guest.
Yes, "systemctl"
Hi, Jason.
On Sun, Mar 21, 2021 at 5:21 AM Jason Long wrote:
> Hello,
> I used "Clusters from Scratch" to configuration two nodes. I got below
> error:
>
> # pcs status
> Cluster name: mycluster
> Cluster Summary:
> * Stack: corosync
> * Current DC: node1 (version 2.0.5-10.fc33-ba59be7122) -
Hello,
I used "Clusters from Scratch" to configuration two nodes. I got below error:
# pcs status
Cluster name: mycluster
Cluster Summary:
* Stack: corosync
* Current DC: node1 (version 2.0.5-10.fc33-ba59be7122) - partition with quorum
* Last updated: Sun Mar 21 15:35:18 2021
* Last change
25 matches
Mail list logo
