This message was deleted.

Slackbot

02/26/2024, 11:02 PM

This message was deleted.

✅ 1

Nicolas Rakover

02/26/2024, 11:02 PM

Copy code

kubectl -n signoz get pods
NAME                                                       READY   STATUS     RESTARTS   AGE
signoz-release-1-alertmanager-0                            0/1     Init:0/1   0          168m
signoz-release-1-clickhouse-operator-68f766878c-xfx8c      2/2     Running    0          5m28s
signoz-release-1-frontend-c6cb6b5c9-mrwdj                  0/1     Init:0/1   0          168m
signoz-release-1-otel-collector-745d5c84c8-79b4p           0/1     Init:0/1   0          168m
signoz-release-1-otel-collector-metrics-6cdcf5b7cc-n7wqh   0/1     Init:0/1   0          168m
signoz-release-1-query-service-0                           0/1     Init:0/1   0          168m
signoz-release-1-schema-migrator-init-c4n4g                0/1     Init:0/2   0          8m16s
signoz-release-1-zookeeper-0                               1/1     Running    0          12m

nitya-signoz

02/27/2024, 3:01 AM

@Prashant Shahi ^

🙏 1

Prashant Shahi

02/27/2024, 3:03 AM

This behaviour is seen when previously installed clickhouse is not cleaned up properly. Can you follow through the cleanup instructions below and retry the installation? https://signoz.io/docs/operate/kubernetes/#uninstall-signoz-cluster

Nicolas Rakover

02/27/2024, 3:17 AM

@Prashant Shahi I'd rather not blow away all of our data and config -- if this is the only path at this point I'll do it, but to be clear the troubles started when doing a perfectly vanilla

helm upgrade

starting from a working Signoz installation (on

0.38.2

I believe)

Nicolas Rakover

02/27/2024, 3:20 AM

I didn't know about the Clickhouse

finalizers

-- will give that a shot. But I'd rather not delete the PVC unless necessary

Nicolas Rakover

02/27/2024, 3:23 AM

Hmm I actually don't have any

clickhouseinstallation

resources anymore. I had to jump through some hoops to forcibly delete the CH instance earlier

Prashant Shahi

02/27/2024, 3:48 AM

unclean uninstall is known is cause this issue of CHI or CHI pods disappearance.

Prashant Shahi

02/27/2024, 3:49 AM

You could

helm upgrade

to attemp re-create the CHI resources.

Prashant Shahi

02/27/2024, 3:49 AM

All others pods would be stuck in Init waiting for CHI pods.

Nicolas Rakover

02/27/2024, 6:07 PM

Doing a

helm upgrade

seemed to get it unstuck 🙌 Thanks @Prashant Shahi!

🙌 1

Open in Slack

Previous Next

SigNoz Community

SigNoz is an open-source APM. It helps developers monitor their applications & troubleshoot problems, an open-source alternative to DataDog, NewRelic, etc.