I'm using CentOS.
Thus, I must use my Apache web server IP instead of node2?
About resource group, is you mean
"https://clusterlabs.org/pacemaker/doc/en-US/Pacemaker/2.0/html-single/Pacemaker_Explained/index.html#group-resources;
?
On Wednesday, March 17, 2021, 01:10:33 AM GMT+3:30, Reid
Thanks.
Excuse me, did you read how did I set my cluster up? Please look at:
https://paste.ubuntu.com/p/Nx2ptqZjFg/
Which part of my configuration is wrong?
Both of the main and secondary servers are an Apache Reverse Proxy Server. I
want when main server failed, then the secondary server handle
Thanks.
I changed it to the IP address of node2 and I can see my Apache Web Server.
$ sudo pcs resource update floating_ip ocf:heartbeat:IPaddr2 ip=192.168.1.10
cidr_netmask=24 op monitor interval=5s
Now, I want to test my cluster and stop node1. On node1 I did:
# pcs cluster stop http_server
Thank you so much.
I forgot to ask a question. In below command, what should be the ip="IP" value?
Is it the IP address of my Apache or node2?
$ sudo pcs resource create floating_ip ocf:heartbeat:IPaddr2 ip="IP"
cidr_netmask=24 op monitor interval=5s
Logs are:
On Tue, Mar 16, 2021 at 3:13 PM Jason Long wrote:
> I'm using CentOS.
>
Ah okay. I think I had made an assumption based on the pastebins URLs.
Thus, I must use my Apache web server IP instead of node2?
>
Yes, it's never a good idea to configure a node's constant IP address
within an IPaddr2
On Tue, Mar 16, 2021 at 1:47 PM Jason Long wrote:
> Thanks.
> Excuse me, did you read how did I set my cluster up? Please look at:
> https://paste.ubuntu.com/p/Nx2ptqZjFg/
> Which part of my configuration is wrong?
>
1. You configured the IPaddr2 resource to use node2's IP address
On Tue, Mar 16, 2021 at 1:03 PM Jason Long wrote:
> Thanks.
> I changed it to the IP address of node2 and I can see my Apache Web Server.
>
Like I said, you don't want to do that. You should change it to an IP
address that you want the cluster to manage. If you set it to node2's IP
address,
On Tue, Mar 16, 2021 at 12:11 PM Jason Long wrote:
> Thank you so much.
> I forgot to ask a question. In below command, what should be the ip="IP"
> value? Is it the IP address of my Apache or node2?
>
> $ sudo pcs resource create floating_ip ocf:heartbeat:IPaddr2 ip="IP"
> cidr_netmask=24 op
On 3/16/21 3:18 PM, Ken Gaillot wrote:
On Tue, 2021-03-16 at 09:42 +, Jason Long wrote:
Hello,
I want to launch a Clustering for my Apache Web Server. I have three
servers:
1- Main server that acts as a Reverse Proxy
2- The secondary server that when my main server stopped, work as a
On Tue, 2021-03-16 at 13:24 +0100, damiano giuliani wrote:
> Could be an idea to let your cluster start it on all your nodes
>
> Br
That does sound like a good idea. That way the cluster can monitor it
(with the equivalent of systemctl status) and restart it if needed, and
constraints can be
On Tue, 2021-03-16 at 09:42 +, Jason Long wrote:
> Hello,
> I want to launch a Clustering for my Apache Web Server. I have three
> servers:
>
> 1- Main server that acts as a Reverse Proxy
> 2- The secondary server that when my main server stopped, work as a
> Reverse Proxy
> 3- Apache Web
Hello,
I want to launch a Clustering for my Apache Web Server. I have three servers:
1- Main server that acts as a Reverse Proxy
2- The secondary server that when my main server stopped, work as a Reverse
Proxy
3- Apache Web Server
The client ---> Reverse Proxy Server ---> Apache Web Server
> On Tue, 16 Mar 2021, 09:58 井上和徳, wrote:
>
> > Hi!
> >
> > Cluster (corosync and pacemaker) can be started with pcs,
> > but corosync-notifyd needs to be started separately with systemctl,
> > which is not easy to use.
Maybe you can add to the [Install] section of corosync-notifyd a dependency
Could be an idea to let your cluster start it on all your nodes
Br
On Tue, 16 Mar 2021, 09:58 井上和徳, wrote:
> Hi!
>
> Cluster (corosync and pacemaker) can be started with pcs,
> but corosync-notifyd needs to be started separately with systemctl,
> which is not easy to use.
>
> # pcs cluster
Hi!
Cluster (corosync and pacemaker) can be started with pcs,
but corosync-notifyd needs to be started separately with systemctl,
which is not easy to use.
# pcs cluster start --all
rhel83-1: Starting Cluster...
rhel83-2: Starting Cluster...
rhel83-3: Starting Cluster...
# ssh rhel83-1 systemctl
15 matches
Mail list logo
