Troubleshooting and accessing logs

Access various logs to troubleshoot and identify the failure reasons.

Code Signing logs

If any of the ECC queue records is not signed by the Code Signing Tracker API, the unsigned messages and the required details are displayed in the Code Signing module. Navigate to System Logs > System Log > Code Signing to access the list of records that are not trusted.

For additional debug node logs, enable com.glide.codesigning.tracking.debug and set its value to true.

REST message signature validation failure on MID Server

Access the error message regarding to the signature validation failure, by navigating to System Web Services > Outbound > REST Message and opening the required REST message record.

Figure 1. Signature validation failure on MID Server

Note:

Error messages related to the ECC firewall rejections start with ECC message execution denied.

Figure 2. ECC queue when signature validation fails on MID Server

Figure 3. Error message when ECC message is blocked by the user rule

JDBC probe

When a JDBC data source with an invalid or missing signature is executed on a MID Server, an error message with the required details is displayed.

Source also displays the details of the error message.

MID Server logs

To enable the detailed ECC firewall logging, increase the log level by setting the value of the MID Server configuration parameter, mid.log.level, to TRACE. The detailed logs provide information about:

• Rules that the MID Server loaded from the boot configuration file.
• Granular execution trace of rules.
• Specific rule due to which an ECC message is to be accepted or rejected.

Note:

If boot-config.xml is invalid, the MID Server fails to start and the failure details are logged in the MID agent logs.