Hasib Skrijelj comments

Results 7 comments of


                                            Hasib Skrijelj

"Not treating it as a GitHub deploy key"

> I'm having the same issue: > > Comment for (public) key '' does not match GitHub URL pattern. Not treating it as a GitHub deploy key. > > Where:...

[Bug]: Spamming LOG: [ddtrace] [error] Failed sending traces to the sidecar: Os { code: 32, kind: BrokenPipe, message: "Broken pipe" }

@bwoebi Yes I am using AWS ECS Fargate. For now the error disappeared after I did a new deployment. When the issue appears again I will try your solution.

[Bug]: Spamming LOG: [ddtrace] [error] Failed sending traces to the sidecar: Os { code: 32, kind: BrokenPipe, message: "Broken pipe" }

@bwoebi It happened again. I will deploy a new release with the env variable `DD_SPAWN_WORKER_USE_EXEC=1` and see if that helps.

[Bug]: Spamming LOG: [ddtrace] [error] Failed sending traces to the sidecar: Os { code: 32, kind: BrokenPipe, message: "Broken pipe" }

@bwoebi `DD_SPAWN_WORKER_USE_EXEC=1` did not solve the issue.

[Bug]: Spamming LOG: [ddtrace] [error] Failed sending traces to the sidecar: Os { code: 32, kind: BrokenPipe, message: "Broken pipe" }

@bwoebi I installed 1.6.3. I also enabled the debug logs but it generated so much logs that I had to disable it again because of cost. However what I found...

[Bug]: PHP message: [ddtrace] [error] Failed signaling lifecycle end: Os { code: 32, kind: BrokenPipe, message: "Broken pipe" }

I have the same issue on 1.5.1. I reverted back to 1.1.0 as suggested by @piotrekkr and the error is gone.

[Bug]: PHP message: [ddtrace] [error] Failed signaling lifecycle end: Os { code: 32, kind: BrokenPipe, message: "Broken pipe" }

@piotrekkr Hello, are you sure it is `DD_REMOTE_CONFIG_ENABLED` and not `DD_REMOTE_CONFIGURATION_ENABLED` like mentioned in the documentation ? Or is maybe the documentation wrong ? doc: https://docs.datadoghq.com/agent/remote_config/?tab=environmentvariable