You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
kubectl logs my-collector-cloudwatch-collector-666665859f-7lrtq -n default
2022/05/12 01:17:51 AWS OTel Collector version: v0.17.0
2022/05/12 01:17:51 found no extra config, skip it, err: open /opt/aws/aws-otel-collector/etc/extracfg.txt: no such file or directory
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x8a664a]
Steps to reproduce
Not Reproducible. With a different EKS cluster I can't replicate the issue.
What did you expect to see?
I should see -
kubectl apply -f collector-config-cloudwatch.yaml
opentelemetrycollector.opentelemetry.io/my-collector-cloudwatch created
clusterrole.rbac.authorization.k8s.io/otel-prometheus-role created
clusterrolebinding.rbac.authorization.k8s.io/otel-prometheus-role-binding created
What did you see instead?
I saw -
2022/05/12 01:17:51 AWS OTel Collector version: v0.17.0
2022/05/12 01:17:51 found no extra config, skip it, err: open /opt/aws/aws-otel-collector/etc/extracfg.txt: no such file or directory
panic: runtime error: invalid memory address or nil pointer dereference
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.
Describe the bug
I am getting the following issue while deploying the ADOT collector for AWS CloudWatch based on the document - https://docs.aws.amazon.com/eks/latest/userguide/configure-cw.html
kubectl logs my-collector-cloudwatch-collector-666665859f-7lrtq -n default
2022/05/12 01:17:51 AWS OTel Collector version: v0.17.0
2022/05/12 01:17:51 found no extra config, skip it, err: open /opt/aws/aws-otel-collector/etc/extracfg.txt: no such file or directory
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x8a664a]
Steps to reproduce
Not Reproducible. With a different EKS cluster I can't replicate the issue.
What did you expect to see?
I should see -
kubectl apply -f collector-config-cloudwatch.yaml
opentelemetrycollector.opentelemetry.io/my-collector-cloudwatch created
clusterrole.rbac.authorization.k8s.io/otel-prometheus-role created
clusterrolebinding.rbac.authorization.k8s.io/otel-prometheus-role-binding created
What did you see instead?
I saw -
2022/05/12 01:17:51 AWS OTel Collector version: v0.17.0
2022/05/12 01:17:51 found no extra config, skip it, err: open /opt/aws/aws-otel-collector/etc/extracfg.txt: no such file or directory
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x8a664a]
goroutine 1 [running]:
go.uber.org/zap.(*Logger).check(0x0, 0x1, {0x3610ca9, 0x1b})
go.uber.org/[email protected]/logger.go:270 +0x6a
go.uber.org/zap.(*Logger).Warn(0x0, {0x3610ca9, 0x0}, {0xc0004337c0, 0x1, 0x1})
go.uber.org/[email protected]/logger.go:199 +0x3e
github.com/open-telemetry/opentelemetry-collector-contrib/exporter/awsemfexporter.(*Config).Validate(0xc0007dd180)
github.com/open-telemetry/opentelemetry-collector-contrib/exporter/[email protected]/config.go:97 +0x289
go.opentelemetry.io/collector/config.(*Config).Validate(0xc0006daf20)
go.opentelemetry.io/[email protected]/config/config.go:74 +0x2a8
go.opentelemetry.io/collector/service.(*configProvider).Get(0xc000481aa0, {0x3c16150, 0xc00012e000}, {0xc00070a3f0, 0xc00070a6c0, 0xc00070a960, 0xc00070a240})
go.opentelemetry.io/[email protected]/service/config_provider.go:167 +0x2de
go.opentelemetry.io/collector/service.(*Collector).setupConfigurationComponents(0xc000716000, {0x3c16150, 0xc00012e000})
go.opentelemetry.io/[email protected]/service/collector.go:171 +0xa3
go.opentelemetry.io/collector/service.(*Collector).Run(0xc000716000, {0x3c16150, 0xc00012e000})
go.opentelemetry.io/[email protected]/service/collector.go:221 +0x24e
main.newCommand.func1(0xc000710000, {0x35d8b36, 0x1, 0x1})
github.com/aws-observability/aws-otel-collector/cmd/awscollector/main.go:117 +0xf5
github.com/spf13/cobra.(*Command).execute(0xc000710000, {0xc000128010, 0x1, 0x1})
github.com/spf13/[email protected]/command.go:856 +0x60e
github.com/spf13/cobra.(*Command).ExecuteC(0xc000710000)
github.com/spf13/[email protected]/command.go:974 +0x3bc
github.com/spf13/cobra.(*Command).Execute(...)
github.com/spf13/[email protected]/command.go:902
main.runInteractive({{0xc00070a3f0, 0xc00070a6c0, 0xc00070a960, 0xc00070a240}, {{0x35f3e9b, 0x12}, {0x35f29a7, 0x12}, {0x3b32b10, 0x7}}, ...})
github.com/aws-observability/aws-otel-collector/cmd/awscollector/main.go:83 +0x5d
main.run({{0xc00070a3f0, 0xc00070a6c0, 0xc00070a960, 0xc00070a240}, {{0x35f3e9b, 0x12}, {0x35f29a7, 0x12}, {0x3b32b10, 0x7}}, ...})
github.com/aws-observability/aws-otel-collector/cmd/awscollector/main_others.go:42 +0xf8
main.main()
github.com/aws-observability/aws-otel-collector/cmd/awscollector/main.go:76 +0x2d8
What version did you use?
AWS OTel Collector version: v0.17.0
What config did you use?
Config: Same as given in the document
Environment
OS: (e.g., "Ubuntu 20.04") - Node is having AMI - ami-0e4286e3300d2ec0f (amazon-eks-node-1.20-v20220406)
Compiler(if manually compiled): (e.g., "go 14.2") : No
Additional context
Add any other context about the problem here.
Since it was giving error in the https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/exporter/awsemfexporter/config.go validate function due to some metrics, I changed the section for exporters from -
To -
It started working. Basically removed the last 4 lines. But my query is why it is not working with the metric_declarartions?
The text was updated successfully, but these errors were encountered: