https://signoz.io logo
#support
Title
# support
j

Jay Ghiya

06/14/2023, 5:41 PM
hi team. facing this error while installing signoz on civo k8s cluster in k8s infra otel collector pods -
Copy code
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"}.
Copy code
where this error could be further debugged?
similar error in deployment pod of otel collector. there is a timeout that is happening . could not understand why
v

Vishal Sharma

06/14/2023, 6:08 PM
Looks like a network issue, please check if
10.43.248.80:4317
is accessible. cc: @Prashant Shahi
j

Jay Ghiya

06/14/2023, 6:25 PM
the call has to be made from which service? @Vishal Sharma also curl wont be installed by default right?
i

Ibrahim

06/19/2023, 3:23 PM
@Jay Ghiya Hello Jay, Wondering whether this issue was fixed or no 🙂 Having the same issue
v

Vishal Sharma

06/19/2023, 3:44 PM
@Prashant Shahi Can you please look into this?
j

Jay Ghiya

06/20/2023, 2:59 PM
@Ibrahim no issue is not fixed. currently did not have much time to investigate further.
p

Prashant Shahi

06/20/2023, 8:26 PM
@Jay Ghiya, @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.
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.
16 Views