This message was deleted.

Slackbot

11/27/2023, 6:04 PM

This message was deleted.

Nicolas Rakover

11/27/2023, 6:31 PM

I've seen this due to a

schema-migrator

job failing to get cleaned up after a previous upgrade. If the job has finished (which you can check via

kubectl -n <your signoz namespace> get jobs

), it should be safe to explicitly delete the vestigial job resource via

kubectl -n <your signoz namespace> delete jobs/<name of schema migrator job>

Nicolas Rakover

11/27/2023, 6:31 PM

Once you've cleaned that up, doing the

helm

upgrade should succeed (at least this worked for me)

Saad Ansari

11/27/2023, 7:48 PM

yea it worked

Saad Ansari

11/27/2023, 7:48 PM

thanks

👍 1

Pranay

11/28/2023, 4:47 AM

Thanks for helping Saad @Nicolas Rakover 👍

Nicolas Rakover

11/28/2023, 5:12 PM

you got it dude

efajunk

11/29/2023, 10:12 PM

Hi! I'm trying to make a fresh install with helm, and this migrator has stuck and doesn't let it happen)

efajunk

11/29/2023, 10:14 PM

I just get: signoz-schema-migrator-init wget: bad address 'signoz-clickhouse:8123' signoz-schema-migrator-init waiting for clickhouseDB indefinitely in job's log Is there any way to skip it when it's just the first deploy?)

efajunk

11/29/2023, 10:17 PM

Is it safe to use schemaMigrator: enabled: false for the first time?

efajunk

11/29/2023, 10:24 PM

Well, temporary disabling the migrator was helpful. Thanks :D

186 Views

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.