Troubleshooting

This section lists some common errors and ways to troubleshoot them.

Issue Resolution

Foresight REST API Configuration

The request you have sent is valid, but the Foresight REST API is not configured properly. Sometimes the parameters are correct but some issues are found, such as Data Files are not present in the specified Directory path. In that case, HTTP response 200 Successful is sent to the submitter, and an error message is included in the body of the response.

Set RestDataPath correctly in FSREST.ini. This is applicable when the users deploy the war file directly to an application server, eg. Tomcat.

The recommended method is to set FSREST_DATADIR in the system variable to configure Foresight REST API in container environment.

Check for Instream and Translation Engines

During Startup

If the Instream bin directory or Translator bin directory is not included in the system variable LD_LIBRARY_PATH(Unix), you receive an error message as an output in the console log.

$$$$$ FSRESTApp checking engines!
$$$$$ iStatus = -1 iVersion = 'Error: Can't find Instream C++ Library (jHVInStream.dll/.so)'

or

$$$$$ tStatus = -1 tVersion = 'Error: Can't find Translator C++ Library (jTranslator.dll/.so)'

But the REST API engine starts.

While POSTing Job Operation

While POSTing a job operation, if the Instream bin directory or Translator bin directory is not included in the system PATH variable, you receive an error message as an output to POST response, with HTTP 400 Bad Request error.

The InStream engine is not found on the server.

or

The Translator engine is not found on the server.

If only one component is not found, POST operation for that component fails.

For example: When Translator is not found, "IT" operation fails, but "I" operation runs.

 Provide the file path for bin directory of Instream and Translator. Rerun build-fsrest-engine.sh.

Connection Errors

You receive connection errors in the following cases:

  • When your certificate expires.

  • When your certificate is revoked by the certificate authority.

  • When the Foresight REST API application does not trust the certificate authority.

  • When the TLS version is mismatched.

  • When TOMCAT uses an outdated encryption algorithm

Follow the given steps for troubleshooting:

  • Replace the expired certificate with a new one.

  • Check with the authority to understand the reason for certificate revocation.

  • Replace your certificate with a trusted certificate.

  • Avoid using an encryption algorithm which is not secure. Ensure that you use a secure encryption algorithm.