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

Suvrat

01/15/2024, 4:52 PM
I am getting containers with incomplete status: [signoz-schema-migrator-init] error no logs no additional info available. Can someone share similar issue faced and how you fixed
wget: bad address 'signoz-clickhouse:8123' Mon, Jan 15 2024 111758 pm waiting for clickhouseDB
Here is the error I see on the schema migrator init container. can someone help here wget: bad address 'signoz-clickhouse:8123' Mon, Jan 15 2024 111758 pm waiting for clickhouseDB
s

Srikanth Chekuri

01/16/2024, 3:43 AM
The migrator doesn't use http. Please use tcp port 9000. Example:
<tcp://localhost:9000>
p

Prashant Shahi

01/16/2024, 7:56 AM
can you check if the clickhouse cluster is available and ready? That error usually happens when the CHI pods are not there or the clickhouse cluster is no healthy.
s

Suvrat

01/16/2024, 8:19 AM
Clickhouse Cluster is in ready state. Schema migrator is trying to connect to bad address 'signoz-clickhouse:8123'. Where do I need to change this in yaml
p

Prashant Shahi

01/16/2024, 8:49 AM
Unless you changed it in override config, the default values should work. Can you share the output of the following?
Copy code
kubectl get pods -n platform
Also, do you only have that
waiting for clickhouseDB
in migrator pod or any other logs as well?
s

Suvrat

01/16/2024, 9:05 AM
This is only throwing error with bad address on migrator pod
s

Srivatsan Sundararajan

03/05/2024, 1:15 AM
I am running into the same issue when trying to bring up signoz. @Suvrat were you able to resolve it? If so, how?
I have components are stuck in Init
Copy code
my-release-signoz-alertmanager-0                            0/1     Init:0/1   0          39m
my-release-signoz-frontend-6c9d9f8898-687v2                 0/1     Init:0/1   0          39m
my-release-signoz-otel-collector-67996c94f9-7p98f           0/1     Init:0/1   0          39m
my-release-signoz-otel-collector-metrics-686fb5dfdx-gmbl9   0/1     Init:0/1   0          39m
my-release-signoz-query-service-0                           0/1     Init:0/1   0          39m
my-release-signoz-schema-migrator-init-qfcr3                0/1     Init:0/2   0          39m
p

Pedro Carvalho

03/05/2024, 9:20 AM
When this happened to me it was because they were waiting on the specific schema migrator job, and that was due to the migrator requiring a function that only existed on a latter version of clickhouse.
s

Srikanth Chekuri

03/05/2024, 9:25 AM
What version of ClickHouse are you using? Please use the 24.1.2+
p

Prashant Shahi

03/05/2024, 9:26 AM
@Srivatsan Sundararajan I see that CHI pod missing. This usually happens due to unclean deletion of previous ClickHouse cluster.
Other pods depend on the ClickHouse pod to be ready, hence they are stuck in init phase
@Srivatsan Sundararajan You could either try with
helm upgrade ...
first, if that doesn't work cleanup previously installed set up and re-install. Instructions to clean deletion: https://signoz.io/docs/operate/kubernetes/#uninstall-signoz-cluster