<div dir="ltr"><div dir="ltr">Hi, Jason.<br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, Mar 21, 2021 at 5:21 AM Jason Long <<a href="mailto:hack3rcon@yahoo.com">hack3rcon@yahoo.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hello,<br>
I used "Clusters from Scratch" to configuration two nodes. I got below error:<br>
<br>
# pcs status<br>
Cluster name: mycluster<br>
Cluster Summary:<br>
* Stack: corosync<br>
* Current DC: node1 (version 2.0.5-10.fc33-ba59be7122) - partition with quorum<br>
* Last updated: Sun Mar 21 15:35:18 2021<br>
* Last change: Sun Mar 21 15:29:38 2021 by root via cibadmin on node1<br>
* 2 nodes configured<br>
* 2 resource instances configured<br>
<br>
Node List:<br>
* Online: [ node1 node2 ]<br>
<br>
Full List of Resources:<br>
* WebSite (ocf::heartbeat:apache): Stopped<br>
* ClusterIP (ocf::heartbeat:IPaddr2): Started node1<br>
<br>
Failed Resource Actions:<br>
* WebSite_start_0 on node1 'error' (1): call=6, status='complete', exitreason='Failed to access httpd status page.', last-rc-change='2021-03-21 15:23:45 +03:30', queued=0ms, exec=1318ms<br>
* WebSite_start_0 on node2 'error' (1): call=6, status='complete', exitreason='Failed to access httpd status page.', last-rc-change='2021-03-21 15:23:47 +03:30', queued=0ms, exec=1380ms<br>
<br>
Daemon Status:<br>
corosync: active/enabled<br>
pacemaker: active/enabled<br>
pcsd: active/enabled<br>
<br>
<br>
*********<br>
I have some questions:<br>
<br>
1- In "Chapter 6. Add Apache HTTP Server as a Cluster Service", an important note said:<br>
"Do not enable the httpd service. Services that are intended to be managed via the cluster software should never be managed by the OS. It is often useful, however, to manually start the service, verify that it works, then stop it again, before adding it to the cluster. This allows you to resolve any non-cluster-related problems before continuing. Since this is a simple example, we’ll skip that step here."<br>
<br>
If the Apache service is not enabled they how can I connect to it via below command: <br></blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
# wget -O - <a href="http://localhost/server-status" rel="noreferrer" target="_blank">http://localhost/server-status</a><br>
--2021-03-21 15:38:39-- <a href="http://localhost/server-status" rel="noreferrer" target="_blank">http://localhost/server-status</a><br>
Resolving localhost (localhost)... 127.0.0.1, ::1<br>
Connecting to localhost (localhost)|127.0.0.1|:80... failed: Connection timed out.<br>
Connecting to localhost (localhost)|::1|:80... failed: Network is unreachable.<br></blockquote><div><br></div><div>Pacemaker starts the httpd service by starting the ocf:heartbeat:apache resource. The article is saying that the httpd.service systemd unit should not be enabled to start automatically at boot; it should only start when the cluster starts it. That is `systemctl is-enabled httpd.service` should print "disabled".</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
<br>
2- Below commands must be run on both nodes or just one node?<br>
<br>
# pcs resource create ClusterIP ocf:heartbeat:IPaddr2 ip="IP_That_Never_Used_In_The_Network" cidr_netmask=32 op monitor interval=30s<br>
<br>
# pcs resource create WebSite ocf:heartbeat:apache configfile=/etc/httpd/conf/httpd.conf statusurl="<a href="http://localhost/server-status" rel="noreferrer" target="_blank">http://localhost/server-status</a>" op monitor interval=20s<br></blockquote><div><br></div><div>Just one node.</div><div> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
<br>
3- Why "* WebSite (ocf::heartbeat:apache): Stopped" ?<br></blockquote><div><br></div><div>The apache resource agent ran a command similar to `wget -O- -q -L --no-proxy --bind-address=127.0.0.1 <status_url>` and got an error. It tried this on a start operation on each node, and it failed on both nodes. When a resource fails to start on a given node, the default response is to prevent it from starting on that node again until the failure is cleared.<br></div><div><br> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Logs are:<br>
<a href="https://paste.ubuntu.com/p/MtkfXyRX4P/" rel="noreferrer" target="_blank">https://paste.ubuntu.com/p/MtkfXyRX4P/</a><br>
<br>
<br>
Thank you.<br>
_______________________________________________<br>
Manage your subscription:<br>
<a href="https://lists.clusterlabs.org/mailman/listinfo/users" rel="noreferrer" target="_blank">https://lists.clusterlabs.org/mailman/listinfo/users</a><br>
<br>
ClusterLabs home: <a href="https://www.clusterlabs.org/" rel="noreferrer" target="_blank">https://www.clusterlabs.org/</a><br>
</blockquote></div><br clear="all"><br>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div>Regards,<br><br></div>Reid Wahl, RHCA<br></div><div>Senior Software Maintenance Engineer, Red Hat<br></div>CEE - Platform Support Delivery - ClusterHA</div></div></div></div></div></div></div></div></div></div></div></div></div></div></div>