ON THIS PAGE:
Sentinel Configuration Service Connection Error
Problem: The Sentinel configuration service cannot be contacted.
Description: The message is: The Sentinel configuration service cannot be contacted at address 'https://machinename/Sentinel'. Please check it is running and that the request is not breaking cross-domain policy.
Cause: A firewall is preventing the Sentinel User Interface from connecting to the Sentinel Configuration Service.
Resolution: You can take either of the following actions to resolve this issue:
- Disable any firewalls that may be preventing the connection between the Sentinel configuration service and the user interface.
- Set a rule to allow inbound traffic.
Emails Not Sending Over SSL
Problem: Emails do not send and the monitor presents a Remote Certificate error.
Description: Emails do not send when Sentinel communicates with the configured mail server using an SSL connection. The full message is: The remote certificate is invalid according to the validation procedure.
Cause: Sentinel has been configured to communicate with the mail server using an SSL connection but a trusted certificate issued for the mail server is not installed on the Sentinel server, or the certificate is invalid.
Resolution: The System Administrator should obtain a copy of the relevant SSL certificate for the mail server and install it on the Sentinel server. On Windows Server 2008 R2 certificates can be viewed and installed by clicking the Start button, typing certmgr.msc into the Search box and then pressing ENTER.
If the certificate is installed, the System Administrator should verify that the issuer matches the host name of the mail server and that the certificate has not expired.
Process Values Fetched before Precondition is Processed
Problem: User expects the precondition to prevent Sentinel from reading null values
Description: An error relating to the input data appears, despite the precondition not being met.
For example, the following error message appears “Test [test name]: Error Fetching Source Data: Datums returned from the fetch for entity [entity] were not of a consistent data type. Expected data type 'Double', Value was 'null'”. However, the precondition for this particular test should have failed under these data conditions.
Cause: Sentinel reads primary input data before running the precondition. This is by design, and plays an important role in Sentinel’s processing optimisation. In the scenario outlined above, the process encountered errors with data before it could even reach the precondition processing.
Resolution: It is helpful to understand the way Sentinel processes data, and in what order, before building tests with effective preconditions. For an overview of monitor processing, read the section Monitor Behaviour, and for a more detailed description, see The Sentinel Engine.