The Gateway Manager fails to access the Gateway Server after rebooting the system

When you reboot the system where the Gateway Server is installed, the Gateway Manager fails to access the Gateway Server from the TrueSight console. This problem occurs when the Gateway Server is configured to communicate in the HTTPS mode.

Resolution

The Apache web server is installed on the system when the Gateway Server is configured in the HTTPS mode. By default, this Apache server does not start after rebooting the system. Hence, the Gateway Manager cannot access the Gateway Server. To resolve this issue, restart the Apache server.

To start the Apache server automatically after the system reboot, add a call to apachectl in the startup files within the rc.N directory. However, this change starts Apache as a root. Therefore, you must review and configure your security and authentication settings before configuring the startup files.

To start the Apache server automatically after the system reboot:

1. Browse to /<installation_directory>/3rd_party/apache2/bin/httpd.
   where, installation_directory is the directory where TrueSight Capacity Optimization is installed. For example, /opt/bmc/Patrol3/.
2. Edit the HTTPD=/data/patrol_p4/p4build/bco_apache/<apache version number>/bld/bin/httpd line to HTTPD=/<installation_directory>/3rd_party/apache2/bin/httpd.

3. Add the LD_LIBRARY_PATH variable to the script as follows:

   LD_LIBRARY_PATH=/<installation_directory>/3rd_party/apache2/lib

4. Restart Apache using the following command:
   
   

    /<installation_directory>/3rd_party/apache2/bin/apachectl -f

   For more information about starting Apache after system reboot, see Starting Apache.