SigNoz / signoz

SigNoz is an open-source observability platform native to OpenTelemetry with logs, traces and metrics in a single application. An open-source alternative to DataDog, NewRelic, etc. 🔥 🖥. 👉 Open source Application Performance Monitoring (APM) & Observability tool
https://signoz.io
Other
18.11k stars 1.15k forks source link

Runtime error: invalid memory address or nil pointer dereference #3011

Open yash-ghelani-dsw opened 1 year ago

yash-ghelani-dsw commented 1 year ago

Hi, I am trying to deploy signoz on azure vm (RHEL 8) using following guide I have added the sample dashboard into signoz user interface from here

For Configuring the Opentelementry collector, I have used binary method mentioned here

Currently I am facing an issue when I run the following

tail -f -n 50 otelcol-output.log

error details are mentioned here:

2023-06-30T09:38:10.152Z info pipelines/pipelines.go:86 Starting processors... 2023-06-30T09:38:10.152Z info pipelines/pipelines.go:90 Processor is starting... {"kind": "processor", "name": "batch", "pipeline": "traces"} 2023-06-30T09:38:10.152Z info pipelines/pipelines.go:94 Processor started. {"kind": "processor", "name": "batch", "pipeline": "traces"} 2023-06-30T09:38:10.152Z info pipelines/pipelines.go:90 Processor is starting... {"kind": "processor", "name": "batch", "pipeline": "logs"} 2023-06-30T09:38:10.152Z info pipelines/pipelines.go:94 Processor started. {"kind": "processor", "name": "batch", "pipeline": "logs"} 2023-06-30T09:38:10.152Z info pipelines/pipelines.go:90 Processor is starting... {"kind": "processor", "name": "batch", "pipeline": "metrics"} 2023-06-30T09:38:10.152Z info pipelines/pipelines.go:94 Processor started. {"kind": "processor", "name": "batch", "pipeline": "metrics"} 2023-06-30T09:38:10.152Z info pipelines/pipelines.go:90 Processor is starting... {"kind": "processor", "name": "batch", "pipeline": "metrics/internal"} 2023-06-30T09:38:10.152Z info pipelines/pipelines.go:94 Processor started. {"kind": "processor", "name": "batch", "pipeline": "metrics/internal"} 2023-06-30T09:38:10.152Z info pipelines/pipelines.go:90 Processor is starting... {"kind": "processor", "name": "resourcedetection", "pipeline": "metrics/internal"} 2023-06-30T09:38:10.152Z info internal/resourcedetection.go:136 began detecting resource information {"kind": "processor", "name": "resourcedetection", "pipeline": "metrics/internal"} 2023-06-30T09:38:10.153Z info internal/resourcedetection.go:150 detected resource information {"kind": "processor", "name": "resourcedetection", "pipeline": "metrics/internal", "resource": {"host.name":"UnifyAI-Dev-Main-RHEL-3","os.type":"linux"}} 2023-06-30T09:38:10.153Z info pipelines/pipelines.go:94 Processor started. {"kind": "processor", "name": "resourcedetection", "pipeline": "metrics/internal"} 2023-06-30T09:38:10.153Z info pipelines/pipelines.go:98 Starting receivers... 2023-06-30T09:38:10.153Z info pipelines/pipelines.go:102 Receiver is starting... {"kind": "receiver", "name": "otlp", "pipeline": "traces"} 2023-06-30T09:38:10.153Z warn internal/warning.go:51 Using the 0.0.0.0 address exposes this server to every network interface, which may facilitate Denial of Service attacks {"kind": "receiver", "name": "otlp", "pipeline": "traces", "documentation": "https://github.com/open-telemetry/opentelemetry-collector/blob/main/docs/security-best-practices.md#safeguards-against-denial-of-service-attacks"} 2023-06-30T09:38:10.153Z info otlpreceiver@v0.66.0/otlp.go:71 Starting GRPC server {"kind": "receiver", "name": "otlp", "pipeline": "traces", "endpoint": "0.0.0.0:4317"} 2023-06-30T09:38:10.153Z info service/service.go:115 Starting shutdown... 2023-06-30T09:38:10.153Z info healthcheck/handler.go:129 Health Check state change {"kind": "extension", "name": "health_check", "status": "unavailable"} 2023-06-30T09:38:10.153Z info pipelines/pipelines.go:118 Stopping receivers... panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x476757d]

please find the config.yaml config here: config.txt

welcome[bot] commented 1 year ago

Thanks for opening this issue. A team member should give feedback soon. In the meantime, feel free to check out the contributing guidelines.