Troubleshooting Content Delivery
This section features typical issues you may encounter while working with or implementing Content Delivery, as well as suggestions on how to discover the causes of those issues.
- If you get a schema validation error when trying to start a microservice
Schema validation errors point to a problem in one of your configuration file. - Trace logging with Spring
Add trace logging to your active Spring profiles in order to get detailed trace logs for a microservice. Note that trace logging impairs the performance of your microservice, and should be enabled only as long as is necessary to track down the source of an issue. - Troubleshooting the rollout of a Content Deployer Extension
As you attempt to roll out a custom Content Deployer Extension you have created, you may encounter an error about duplicate Pipelines. - Getting an unencrypted Add-on configuration file
By default, the Add-on service encrypts any configuration files uploaded as part of an Add-on. But in a debugging scenario, you may want to see configuration files unencrypted. In order to achieve this, ensure that there is an environment variableaddonserviceencryptionflagset to the valuefalsein the machine on which your client for the Add-on service runs. - Troubleshooting an OpenSearch index with an ID containing non-ASCII characters
If you create an OpenSearch index whose ID contains non-ASCII characters, you may run into problems passing that ID to a Powershell script. One solution is to exclusively use OpenSearch indexes that contain only ASCII characters. The other solution is to change your regional settings.