Maestro member not Connection refused

Jonathan_Langle — Wed, 08 Jan 2025 17:02:21 GMT

We have a Maestro Security Group with 3 members, 2 of the 3 are sending telemetry data ok, the 3rd one is getting a connection refused from Prometheus it seems? TCP connection seems to establish ok, anyone run into this? Just installed Take 97 of the CP Collector.

2024-12-29T00:09:26.902-0500 error exporterhelper/queued_retry.go:391 Exporting failed. The error is not retryable. Dropping data. {"kind": "exporter", "data_type": "metrics", "name": "prometheusremotewrite", "error": "Permanent error: Permanent error: Post \"https://<HOSTNAME>:9090/api/v1/write\": dial tcp <IP>:9090: connect: connection refused", "dropped_items": 99}
go.opentelemetry.io/collector/exporter/exporterhelper.(*retrySender).send
go.opentelemetry.io/collector/exporter@v0.82.0/exporterhelper/queued_retry.go:391
go.opentelemetry.io/collector/exporter/exporterhelper.(*metricsSenderWithObservability).send
go.opentelemetry.io/collector/exporter@v0.82.0/exporterhelper/metrics.go:125
go.opentelemetry.io/collector/exporter/exporterhelper.(*queuedRetrySender).start.func1
go.opentelemetry.io/collector/exporter@v0.82.0/exporterhelper/queued_retry.go:195
go.opentelemetry.io/collector/exporter/exporterhelper/internal.(*boundedMemoryQueue).StartConsumers.func1
go.opentelemetry.io/collector/exporter@v0.82.0/exporterhelper/internal/bounded_memory_queue.go:47
2024-12-29T00:09:41.919-0500 error exporterhelper/queued_retry.go:391 Exporting failed. The error is not retryable. Dropping data. {"kind": "exporter", "data_type": "metrics", "name": "prometheusremotewrite", "error": "Permanent error: Permanent error: Post \"https://<HOSTNAME>:9090/api/v1/write\": dial tcp <IP>:9090: connect: connection refused", "dropped_items": 117}
go.opentelemetry.io/collector/exporter/exporterhelper.(*retrySender).send
go.opentelemetry.io/collector/exporter@v0.82.0/exporterhelper/queued_retry.go:391
go.opentelemetry.io/collector/exporter/exporterhelper.(*metricsSenderWithObservability).send
go.opentelemetry.io/collector/exporter@v0.82.0/exporterhelper/metrics.go:125
go.opentelemetry.io/collector/exporter/exporterhelper.(*queuedRetrySender).start.func1
go.opentelemetry.io/collector/exporter@v0.82.0/exporterhelper/queued_retry.go:195
go.opentelemetry.io/collector/exporter/exporterhelper/internal.(*boundedMemoryQueue).StartConsumers.func1
go.opentelemetry.io/collector/exporter@v0.82.0/exporterhelper/internal/bounded_memory_queue.go:47
2025-01-06T12:46:43.691-0500 info service/telemetry.go:76 Skipping telemetry setup. {"address": ":8888", "level": "None"}
2025-01-08T11:13:55.102-0500 info service/telemetry.go:76 Skipping telemetry setup. {"address": ":8888", "level": "None"}

HOTFIX_R81_10_JUMBO_HF_MAIN Take: 130

Re: Maestro member not Connection refused

Alexander_Wilke — Sat, 07 Jun 2025 22:58:12 GMT

To fix these type of issues I use:

## somehow resets the skyline config gexec -b all -c '/opt/CPotelcol/CPotelcolCli.sh set_dynamic_config "$(cat /opt/CPotelcol/config.json)"' sleep 3 ### add the new config gexec -b all -c 'sklnctl export --set "$(cat /home/admin/skyline_payload.json)"' sleep 3 ### CPview API restart g_all cpview -s off; sleep 3; g_all cpview -s on g_all cpview -a off; sleep 3; g_all cpview -a on ## Restart processes g_all /opt/CPotelcol/CPotelcolCli.sh stop; sleep 3; g_all /opt/CPotelcol/CPotelcolCli.sh start g_all /opt/CPotlpAgent/CPotlpagentCli.sh stop; sleep 3; g_all /opt/CPotlpAgent/CPotlpagentCli.sh start g_all /opt/CPviewExporter/CPviewExporterCli.sh stop; sleep 3; g_all /opt/CPviewExporter/CPviewExporterCli.sh start

topic Re: Maestro member not Connection refused in OpenTelemetry/Skyline

Maestro member not Connection refused

Re: Maestro member not Connection refused