Installation ClusterControl failed (script based on Rocky 8.8)
Hello,
Can you helpme with this?
I have installed ClusterControl via script
wget -O install-cc https://severalnines.com/scripts/install-cc?lEnWusa5guz5TSK%2BPvb63FB0phwaNA%3D%3D,
chmod +x install-cc
./install-cc
The script claims CluCo is installed, but the httpd service could not be started
Redirecting to /bin/systemctl restart httpd.service
Job for httpd.service failed because the control process exited with error code.
See "systemctl status httpd.service" and "journalctl -xe" for details.
2023-11-01 10:38:59 CET -- Unable to restart the Apache Server ...
2023-11-01 10:38:59 CET -- ClusterControl installation completed!
Open your web browser to https://192.168.122.226 and create a default Admin User.
journalctl -xe gives
Nov 01 10:43:55 srv226 httpd[7669]: AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using fe80>
Nov 01 10:43:55 srv226 httpd[7669]: (13)Permission denied: AH00072: make_sock: could not bind to address [::]:19501
Nov 01 10:43:55 srv226 httpd[7669]: (13)Permission denied: AH00072: make_sock: could not bind to address 0.0.0.0:19501
Nov 01 10:43:55 srv226 httpd[7669]: no listening sockets available, shutting down
Nov 01 10:43:55 srv226 httpd[7669]: AH00015: Unable to open logs
Nov 01 10:43:55 srv226 systemd[1]: httpd.service: Main process exited, code=exited, status=1/FAILURE
Nov 01 10:43:55 srv226 systemd[1]: httpd.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- The unit httpd.service has entered the 'failed' state with result 'exit-code'.
Nov 01 10:43:55 srv226 systemd[1]: Failed to start The Apache HTTP Server.
-- Subject: Unit httpd.service has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit httpd.service has failed.
--
-- The result is failed.
-
setenforce 0 to temporarily put selinux in permissive
install your product
analyze audit logs with setroubleshoot and generate the appropriate custom rules
setenforce 1 to enforce selinux again
In your case, port 19501 should be in the http port semanage acl. It is not and selinux is blocking your webserver from starting. In your case this should do the trick:
semanage port -a -t http_port_t -p tcp 19501
Please sign in to leave a comment.
Comments
2 comments