Zitadel failed to start but no error

Hi,
I tried to install the newest release v4.7.1, but my service would not restart. It is stuck at the init part without error. So I added debug but it display only one line more :

Dec 09 16:49:04 azul zitadel[1581538]: time="2025-12-09T16:49:04+01:00" level=info msg="initialization started" caller="/home/runner/work/zitadel/zitadel/cmd/initialise/init.go:70"
Dec 09 16:49:04 azul zitadel[1581538]: time="2025-12-09T16:49:04+01:00" level=debug msg="failed to get oid for command type" caller="/home/runner/work/zitadel/zitadel/internal/eventstore/v3/eventstore.go:119" error="no rows in result set"
Dec 09 16:49:04 azul zitadel[1581538]: time="2025-12-09T16:49:04+01:00" level=info msg="verify user" caller="/home/runner/work/zitadel/zitadel/cmd/initialise/verify_user.go:40" username=zitadel
Dec 09 16:49:04 azul zitadel[1581538]: time="2025-12-09T16:49:04+01:00" level=info msg="verify database" caller="/home/runner/work/zitadel/zitadel/cmd/initialise/verify_database.go:40" database=zitadel
Dec 09 16:49:04 azul zitadel[1581538]: time="2025-12-09T16:49:04+01:00" level=info msg="verify grant" caller="/home/runner/work/zitadel/zitadel/cmd/initialise/verify_grant.go:35" database=zitadel user=zitadel
Dec 09 16:49:04 azul zitadel[1581538]: time="2025-12-09T16:49:04+01:00" level=info msg="verify zitadel" caller="/home/runner/work/zitadel/zitadel/cmd/initialise/verify_zitadel.go:80" database=zitadel
Dec 09 16:49:04 azul zitadel[1581538]: time="2025-12-09T16:49:04+01:00" level=info msg="verify system" caller="/home/runner/work/zitadel/zitadel/cmd/initialise/verify_zitadel.go:46"

Dec 09 16:49:04 azul zitadel[1581538]: time="2025-12-09T16:49:04+01:00" level=info msg="initialization started" caller="/home/runner/work/zitadel/zitadel/cmd/initialise/init.go:70"
Dec 09 16:49:04 azul zitadel[1581538]: time="2025-12-09T16:49:04+01:00" level=debug msg="failed to get oid for command type" caller="/home/runner/work/zitadel/zitadel/internal/eventstore/v3/eventstore.go:119" error="no rows in result set"
Dec 09 16:49:04 azul zitadel[1581538]: time="2025-12-09T16:49:04+01:00" level=info msg="verify user" caller="/home/runner/work/zitadel/zitadel/cmd/initialise/verify_user.go:40" username=zitadel
Dec 09 16:49:04 azul zitadel[1581538]: time="2025-12-09T16:49:04+01:00" level=info msg="verify database" caller="/home/runner/work/zitadel/zitadel/cmd/initialise/verify_database.go:40" database=zitadel
Dec 09 16:49:04 azul zitadel[1581538]: time="2025-12-09T16:49:04+01:00" level=info msg="verify grant" caller="/home/runner/work/zitadel/zitadel/cmd/initialise/verify_grant.go:35" database=zitadel user=zitadel
Dec 09 16:49:04 azul zitadel[1581538]: time="2025-12-09T16:49:04+01:00" level=info msg="verify zitadel" caller="/home/runner/work/zitadel/zitadel/cmd/initialise/verify_zitadel.go:80" database=zitadel
Dec 09 16:49:04 azul zitadel[1581538]: time="2025-12-09T16:49:04+01:00" level=info msg="verify system" caller="/home/runner/work/zitadel/zitadel/cmd/initialise/verify_zitadel.go:46"

Dec 09 16:49:04 azul zitadel[1581538]: time="2025-12-09T16:49:04+01:00" level=info msg="initialization started" caller="/home/runner/work/zitadel/zitadel/cmd/initialise/init.go:70"
Dec 09 16:49:04 azul zitadel[1581538]: time="2025-12-09T16:49:04+01:00" level=debug msg="failed to get oid for command type" caller="/home/runner/work/zitadel/zitadel/internal/eventstore/v3/eventstore.go:119" error="no rows in result set"
Dec 09 16:49:04 azul zitadel[1581538]: time="2025-12-09T16:49:04+01:00" level=info msg="verify user" caller="/home/runner/work/zitadel/zitadel/cmd/initialise/verify_user.go:40" username=zitadel
Dec 09 16:49:04 azul zitadel[1581538]: time="2025-12-09T16:49:04+01:00" level=info msg="verify database" caller="/home/runner/work/zitadel/zitadel/cmd/initialise/verify_database.go:40" database=zitadel
Dec 09 16:49:04 azul zitadel[1581538]: time="2025-12-09T16:49:04+01:00" level=info msg="verify grant" caller="/home/runner/work/zitadel/zitadel/cmd/initialise/verify_grant.go:35" database=zitadel user=zitadel
Dec 09 16:49:04 azul zitadel[1581538]: time="2025-12-09T16:49:04+01:00" level=info msg="verify zitadel" caller="/home/runner/work/zitadel/zitadel/cmd/initialise/verify_zitadel.go:80" database=zitadel
Dec 09 16:49:04 azul zitadel[1581538]: time="2025-12-09T16:49:04+01:00" level=info msg="verify system" caller="/home/runner/work/zitadel/zitadel/cmd/initialise/verify_zitadel.go:46"

Dec 09 16:49:04 azul zitadel[1581538]: time="2025-12-09T16:49:04+01:00" level=info msg="initialization started" caller="/home/runner/work/zitadel/zitadel/cmd/initialise/init.go:70"
Dec 09 16:49:04 azul zitadel[1581538]: time="2025-12-09T16:49:04+01:00" level=debug msg="failed to get oid for command type" caller="/home/runner/work/zitadel/zitadel/internal/eventstore/v3/eventstore.go:119" error="no rows in result set"
Dec 09 16:49:04 azul zitadel[1581538]: time="2025-12-09T16:49:04+01:00" level=info msg="verify user" caller="/home/runner/work/zitadel/zitadel/cmd/initialise/verify_user.go:40" username=zitadel
Dec 09 16:49:04 azul zitadel[1581538]: time="2025-12-09T16:49:04+01:00" level=info msg="verify database" caller="/home/runner/work/zitadel/zitadel/cmd/initialise/verify_database.go:40" database=zitadel
Dec 09 16:49:04 azul zitadel[1581538]: time="2025-12-09T16:49:04+01:00" level=info msg="verify grant" caller="/home/runner/work/zitadel/zitadel/cmd/initialise/verify_grant.go:35" database=zitadel user=zitadel
Dec 09 16:49:04 azul zitadel[1581538]: time="2025-12-09T16:49:04+01:00" level=info msg="verify zitadel" caller="/home/runner/work/zitadel/zitadel/cmd/initialise/verify_zitadel.go:80" database=zitadel
Dec 09 16:49:04 azul zitadel[1581538]: time="2025-12-09T16:49:04+01:00" level=info msg="verify system" caller="/home/runner/work/zitadel/zitadel/cmd/initialise/verify_zitadel.go:46"

It may not be related to the version since my dev stack is working on this one and rollback do not change anything
Has someone an idea ?

Ask Inkeep•12/9/25, 4:03 PM

Hi @Wolfbergen, I'm an AI assistant for ZITADEL. While a team member reviews this question, I'll see if I can find relevant sources for your question.

Ask Inkeep•12/9/25, 4:03 PM

Answer

---

I wasn't able to find a direct answer for this specific startup issue with v4.7.1 in the available sources. However, here are some potentially relevant resources:

[Bug]: start-from-setup fails with relation "eventstore.events" does not exist on clean Postgres database (1) :

This discusses a similar initialization issue where the eventstore tables weren't being created properly. The resolution was to use start-from-initstart-from-init instead of start-from-setupstart-from-setup.

Configuration Options in ZITADEL (2) :

Contains the full runtime configuration options including database connection settings that might help verify your PostgreSQL configuration is correct.

The debug message "failed to get oid for command type""failed to get oid for command type" with "no rows in result set""no rows in result set" suggests a potential database schema or migration issue. Since rollback doesn't help and your dev stack works, this could indicate a database state inconsistency on that specific environment.

I'd recommend clicking the "Ask for help" button to have a team member review this, as this appears to be a specific edge case that may require deeper investigation into your database state.

Ask Inkeep•12/9/25, 4:03 PM

To learn more, see the sources I considered:

[1] [Bug]: start-from-setup fails with relation "eventstore.events" does not exist on clean Postgres database
[2] Configuration Options in ZITADEL

Ask Inkeep•12/9/25, 4:03 PM

Feel free to tag @Ask Inkeep with additional questions.

AAsk Inkeep To learn more, see the sources I considered: [[1] [Bug]: start-from-setup fai...

Ask InkeepAPP•12/9/25, 4:04 PM

Got it. Tagging @Rajat for additional help.

WolfbergenOP•12/10/25, 9:18 AM

After some time, I got :

level=fatal msg="unable to initialize ZITADEL" caller="/home/runner/work/zitadel/zitadel/cmd/initialise/init.go:66" error="ERROR: canceling statement due to global lock timeout (SQLSTATE 55P03)"

level=fatal msg="unable to initialize ZITADEL" caller="/home/runner/work/zitadel/zitadel/cmd/initialise/init.go:66" error="ERROR: canceling statement due to global lock timeout (SQLSTATE 55P03)"

and it restart again and again with this FATAL after 10mn timeout.

I delete the lock and it restart properly.
It is OK now

AAsk Inkeep To learn more, see the sources I considered: [[1] [Bug]: start-from-setup fai...

Ask InkeepAPP•12/10/25, 9:18 AM

Glad I could be helpful. Feel free to create a new thread with any new questions you may have.