Red Hat Satellite 6.11 WebUI or Capsule httpd fails to load after performing RHEL7 to RHEL8 Leap upgrade

Environment

• Red Hat Satellite 6.11
  • optionally Red Hat Capsule 6.11
• Red Hat Enterprise Linux 8

Issue

• After upgrading the Red Hat Satellite server underlying Operating System (OS) from RHEL 7 to RHEL 8, WebUI fails to load and 'hammer ping' returns the following error.

   [root@satellite ~]# hammer ping
   Could not load the API description from the server:
   Failed to open TCP connection to satellite.example.com:443 (Connection refused - connect(2) for "satellite.example.com" port 443)
    - is the server down?
    - was 'foreman-rake apipie:cache' run on the server when using apipie cache? (typical production settings)
   Warning: An error occured while loading module hammer_cli_foreman.
   Could not load the API description from the server:
   Failed to open TCP connection to satellite.example.com:443 (Connection refused - connect(2) for "satellite.example.com" port 443)
  

   May 17 09:35:47 satellite httpd[1344]: AH00534: httpd: Configuration error: More than one MPM loaded.
   May 17 09:35:47 satellite systemd[1]: httpd.service: Main process exited, code=exited, status=1/FAILURE
   May 17 09:35:47 satellite systemd[1]: httpd.service: Failed with result 'exit-code'.
   May 17 09:35:47 satellite systemd[1]: Failed to start The Apache HTTP Server.
  

• similar issue is hit after completing LEAPP upgrade of Satellite 6.11 from RHEL7 to RHEL8: httpd service affected similarly, Satellite's WebUI shows many errors when opening the Capsule's details page

Resolution

• Run the following satellite-installer command manually and restart the Red Hat Satellite/Capsule services.

      # satellite-installer
  
      # satellite-maintain service restart
  
  

• Run hammer ping (when fixing Satellite) or check Capsule details in WebUI (when fixing Capsule) to verify the remedy steps helped.

• For more KB articles/solutions related to Red Hat Satellite 6.x LEAPP Issues, please refer to the Consolidated Troubleshooting Article for Red Hat Satellite 6.x LEAPP Issues

Diagnostic Steps

• To verify the Red Hat Satellite/Capsule services are running properly, you can follow these steps:

  • Log in to the Red Hat Satellite/Capsule server as the root user.

  • Check the status of the services by running the following command:

     # systemctl status <service_name>
    

• Replace <service_name> with the name of the service you want to check. For example, to check the status of the Apache HTTP service, you would run:

   # systemctl status httpd
  

• Look for the Active: line in the output. If it says active (running), the service is running. If it says active (dead), the service is not running.

  • Repeat the above steps for each service you want to check.

  • If any of the services are not running, you can start them by running the following command:

     # systemctl start <service_name>
    

• If a service fails to start, check the logs for any error messages. The logs are usually located in the /var/log/ directory.

• By following these steps, you should be able to determine if ALL the Red Hat Satellite 6 services are running properly.

   # foreman-maintain health check
   # satellite-maintain service status -b
  

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.