-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
panic: runtime error: invalid memory address or nil pointer dereference #25125
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
@semihural-tomtom can you break the logs into separate lines? |
I don't see any indication that there was a problem with the filelog receiver. Based on the logged error, it appears to be the loki translator.
|
@djaglowski agreed |
Pinging code owners for pkg/translator/loki: @gouthamve @jpkrohling @mar4uk. See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Pinging code owners for exporter/loki: @gramidt @gouthamve @jpkrohling @mar4uk. See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Pinging code owners for translator/loki: @gouthamve @jpkrohling @mar4uk. See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Seems the issue is related to the below attributes.
|
@semihural-tomtom could you please enable UPDATE |
Thank you @semihural-tomtom for reporting this bug! The fix is on the way #25142 |
Component(s)
receiver/filelog
What happened?
Description
I tried to deploy otel-collector via helm chart with the below configuration with
daemonset
mode. But the collector podBack-off restarting failed due to below error.
Collector version
0.82.0
Environment information
Environment
OS: (e.g., "Ubuntu 20.04")
Compiler(if manually compiled): (e.g., "go 14.2")
OpenTelemetry Collector configuration
Log output
Additional context
No response
The text was updated successfully, but these errors were encountered: