Hello folks! Seeking help / advice. 1. We have a s...
# support
p
Hello folks! Seeking help / advice. 1. We have a self-hosted docker stand-alone instance of Signoz (thanks to the devs + maintainers πŸ™‡ ). (
v.0.73.0
) 2. Did a
$ docker compose down
, post which when I tried to run
$ docker compose up
the signoz query service is failing.
Copy code
signoz-query-service    | {"level":"WARN","timestamp":"2025-09-17T10:11:15.424Z","caller":"query-service/main.go:161","msg":"No JWT secret key is specified."}                           
signoz-query-service    | {"level":"FATAL","timestamp":"2025-09-17T10:11:15.959Z","caller":"query-service/main.go:190","msg":"Failed to create server","error":"missing destination name 
updated_at in *[]model.Organization","stacktrace":"main.main\n\t/home/runner/work/signoz/signoz/ee/query-service/main.go:190\nruntime.main\n\t/home/runner/go/pkg/mod/golang.org/toolchai
n@v0.0.1-go1.22.7.linux-amd64/src/runtime/proc.go:271"}                                                                                                                                  
signoz-query-service exited with code 1                                                                                                                                                  
Gracefully stopping... (press Ctrl+C again to force)                                                                                                                                     
dependency failed to start: container signoz-query-service is unhealthy
Would really appreciate if someone can help me out / guide me to a direction to fix this. Thanks for your time! cc - @Astha Haryani
v
Can you provide the output of
select * from migration
?
p
Thanks for a quick response! @Vibhu Pandey Assuming you're referring to the clickhouse server, attaching the steps & outputs for clarity: 1. Attached an interactive shell for clickhouse server (
$ docker exec -it <container_id> clickhouse-client
2.
SHOW DATABASES;
& a quick query revealed that probably you're referring to
signoz_metadata
db's
schema_migrations_v2
table. 3. Further
SELECT * FROM signoz_metadata.schema_migrations_v2
returned-
Copy code
β”Œβ”€migration_id─┬─status───┬─error─┬────────────────────created_at─┬────────────────────updated_at─┐
β”‚         1000 β”‚ finished β”‚       β”‚ 2025-03-05 11:06:38.000000000 β”‚ 2025-03-05 11:06:39.000000000 β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”΄β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”΄β”€β”€β”€β”€β”€β”€β”€β”΄β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”΄β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
v
From the sqlite db
p
Hey, thanks for your response & time. This is sorted for now, we just recovered from a snapshot as we wanted to move ahead. Will revisit this later once, we were trying to upgrade our deployment & that is when we encountered this issue. Thanks!