#support

Installation Error in Civo K8s Cluster for SigNoz Otel Collector

TLDR Jay and Ibrahim report installation errors with SigNoz on Civo k8s cluster. vishal-signoz suggests checking network accessibility, Prashant thinks the issue might be due to ClickHouse taking time to get ready.

5mo

Join the chat

Jun 14, 2023 (6 months ago)

Photo of md5-4c9a57e5c00c733bd6dfdd3b2539c963

Jay

05:41 PM

hi team. facing this error while installing signoz on civo k8s cluster in k8s infra otel collector pods -

2023-06-14T17:16:58.774Z    info    exporterhelper/queued_retry.go:433    Exporting failed. Will retry the request after interval.    {"kind": "exporter", "data_type": "logs", "name": "otlp", "error": "rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing: dial tcp 10.43.248.80:4317: i/o timeout\"", "interval": "30.496229307s"}

2023-06-14T17:16:59.705Z    info    exporterhelper/queued_retry.go:433    Exporting failed. Will retry the request after interval.    {"kind": "exporter", "data_type": "metrics", "name": "otlp", "error": "rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing: dial tcp 10.43.248.80:4317: i/o timeout\"", "interval": "17.274408022s"}

2023-06-14T17:17:12.810Z    info    exporterhelper/queued_retry.go:433    Exporting failed. Will retry the request after interval.    {"kind": "exporter", "data_type": "logs", "name": "otlp", "error": "rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing: dial tcp 10.43.248.80:4317: i/o timeout\"", "interval": "18.948217314s"}.

where this error could be further debugged?

05:46

Jay

05:46 PM

similar error in deployment pod of otel collector. there is a timeout that is happening . could not understand why

Photo of md5-f936d3e5743d23344d6c60813189716f

vishal-signoz

06:08 PM

Looks like a network issue, please check if 10.43.248.80:4317 is accessible.
cc: Prashant

Jay

06:25 PM

the call has to be made from which service? vishal-signoz also curl wont be installed by default right?

Jun 19, 2023 (5 months ago)

Photo of md5-2f94b63d050dad6ced4a85316a658c61

Ibrahim

03:23 PM

Jay
Hello Jay,
Wondering whether this issue was fixed or no 🙂 Having the same issue

vishal-signoz

03:44 PM

Prashant Can you please look into this?

Jun 20, 2023 (5 months ago)

Jay

02:59 PM

Ibrahim no issue is not fixed. currently did not have much time to investigate further.

Photo of md5-1899629483c7ab1dccfbee6cc2f637b9

Prashant

08:26 PM

Jay, Ibrahim are you seeing this at the start during the installation? If yes, it is expected in the start to throw this since the k8s-infra collector is not able to connect to SigNoz collector since ClickHouse takes some time to get ready.

08:28

Prashant

08:28 PM

If this error is still coming afterwards, it means the SigNoz OtelCollector and/or ClickHouse CHI Pod is not healthy.

Logs of those components would be helpful. Do share if you see any warning, error or exception.

SigNoz Community

Built with ClickHouse as datastore, SigNoz is an open-source APM to help you find issues in your deployed applications & solve them quickly | Knowledge Base powered by Struct.AI

Indexed 1023 threads (61% resolved)

Join Our Community

Similar Threads

Troubleshooting Signoz Installation Issue on Cluster

Mayur is experiencing issues with connecting to an OTelCollectorEndpoint after a Signoz install, receiving connection errors. Solutions suggested by Prashant, such as including an ingress port and changing setup configurations, have not yet resolved the issue.

1mo

Troubleshooting SigNoz Auto-Instrumentation Configuration

igor is having trouble configuring auto-instrumentation for Java applications using SigNoz, with traces not appearing in the SigNoz UI. Prashant advises to check logs of the otel sidecar, use service name for endpoint, verify supported libraries, and test with telemetrygen. However, the issue still persists.

8mo

Issues with SigNoz Setup and Data Persistence in AKS

Vaibhavi experienced issues setting up SigNoz in AKS, and faced data persistence issues after installation. Srikanth provided guidance on ClickHouse version compatibility and resource requirements, helping Vaibhavi troubleshoot and resolve the issue.

8mo

Troubleshooting SigNoz Deployment in K8s

Mingyang encountered errors when deploying SigNoz in k8s. Leigh and nitya-signoz suggested checking for firewall issues and verifying if the certain URL is reachable respectively.

yesterday

External ClickHouse Server Installation Issue

Syed faced a connection error with an external ClickHouse server. Srikanth and Ankit suggested changing the cluster name to 'cluster'. The issue was resolved after updating the name.

8mo