Troubleshooting

Elasticsearch

Issue	Resolution
When trying to confirm Elasticsearch is running by connecting to localhost:9200 in a browser the following message is displayed: This site can’t be reached.	Elasticsearch has probably not finished initialising. Wait, then click Reload to try again. If this does not work after several attempts, verify the Elasticsearch service is actually running.
After configuring Elasticsearch and then trying to access it using https://localhost:9200 in a browser the following message is displayed: This site can’t provide a secure connection localhost sent an invalid response. Try running Windows Network Diagnostics. ERR_SSL_PROTOCOL_ERROR	Try restarting the Elasticsearch service and verify it is actually running. Or, run the service in an Admin Command Prompt window to see the logs.

Kibana

Issue	Resolution
When trying to confirm Kibana is running by connecting to localhost:5601 in a browser the following message is displayed: Kibana server is not ready yet.	Kibana has probably not finished initialising. Wait, then click Reload to try again. If this does not work after several attempts, verify the Kibana service is actually running.
When trying to confirm Kibana is running by connecting to localhost:5601 in a browser the following message is displayed: This site can’t be reached.	Kibana has probably not finished initialising. Wait, then click Reload to try again. If this does not work after several attempts, verify the Kibana service is actually running.

Tika

Issue	Resolution
When trying to confirm that Tika is running by connecting to localhost:9998 in a browser, a message is displayed saying the site can’t be reached.	Tika has probably not finished initialising. Wait, then click Reload to try again. If this does not work after several attempts, verify the Tika service is actually running.

Apache

Issue	Resolution
When connecting to the Admin or Search App, the Apache Test Page is displayed.	Comment out all lines in /etc/httpd/conf.d/welcome.conf and restart Apache. Or remove the file entirely (it can be restored when packages are updated).
When connecting to the Admin or Search App, a directory listing is displayed.	The URL used to access the server does not match the IM_PUBLIC_ADDRESS defined in the RC file. Update name resolution and/or the value of IM_PUBLIC_ADDRESS so they match.
When connecting to the Admin or Search App, a certificate warning is displayed.	The URL used to access the server does not match the subject name or a subject alternative name in the HTTPS certificate.
When starting Apache, warnings are displayed stating that the environment variables are not set and the system control unit for httpd.service does not reference /etc/sysconfig/httpd.	Edit the httpd.service control unit by running: systemctl edit --full httpd.service In the [Service] section add: EnvironmentFile=/etc/sysconfig/httpd Then save the file and run: systemctl daemon-reload systemctl restart httpd
When logging into Workplace AI Control Hub or Search App a HTTP 500 error is received.	Edit the /etc/httpd/config/httpd.conf file. Change each proxy entry from http://localhost to https://<FQDN> where <FQDN> is the fully qualified domain name of the server running the apache daemon. Then update the SSL cert entries in the same file with a valid trusted cert for the FQDN above. Make sure the correct SSL cert and URL are used for the Remoteapi section of the /opt/insightmaker/Apps/Admin/api/appsettings.json and /opt/insightmaker/Apps/Search/api/appsettings.json files.