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

SigNoz Community

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 &lt;your signoz namespace&gt; get jobs`), it should be safe to explicitly delete the vestigial job resource via `kubectl -n &lt;your signoz namespace&gt; delete jobs/&lt;name of schema migrator job&gt;`

Once you've cleaned that up, doing the `helm` upgrade _should_ succeed (at least this worked for me)

Thanks for helping Saad  <@U066J253G6M> :+1:

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

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?)

Is it safe to use
schemaMigrator:
  enabled: false

for the first time?

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