17 Dec 2019 12:59 AM - last edited on 18 May 2023 03:25 PM by Michal_Gebacki
We have custom nginx plugin that has a single directive that goes into nginx.conf. We usually place this directive right inside the http block.
http {
tcell_app_id xxxxxxxx;
...
This works fine without Dynatrace.
Running with Dynatrace, we get a strange error from nginx:
# sh -x dynatrace-agent64.sh nginx -g "daemon off;"
...
nginx: [emerg] "tcell_app_id" directive is duplicate in /usr/local/openresty/nginx/conf/nginx.conf:19
Strange because that directive is not duplicated and this works fine without Dynatrace.
Now if I move our directive down a bit inside the http { block, the error goes away when running with Dynatrace.
http {
...
...
tcell_app_id xxxxxxxx;
server {
So something in Dynatrace appears to be processing or writing this file before startup, and it is causing problems with custom directives.
Solved! Go to Solution.
17 Dec 2019 07:04 AM
Oneagent is modifying the configuration files at runtime (no persistent changes). As it causes issues with your NGINX configuration, I suggest opening a support ticket to get this investigated as this should not happen.
17 Dec 2019 06:45 PM