tamis0583
tamis0583•13mo ago

ERROR unrecognized enable_durable_locking_for_serializable

I have the following setup using docker compose: 
 yaml
services:
  cockroachdb:
    container_name: cockroach
    image: cockroachdb/cockroach:v23.1.25
    command: start-single-node --insecure
    ports:
      - "8080:8080"   # User interface
      - "26257:26257" # Main port
    environment:
      - COCKROACH_DB=defaultdb
    volumes:
      - ./data/cockroach:/cockroach/cockroach-data
    healthcheck:
      test: ["CMD", "curl", "-f", "http://localhost:8080/health"]
      interval: 2s
      timeout: 2s
      retries: 5
      start_period: 0s
    restart: always

 zitadel:
    image: ghcr.io/zitadel/zitadel:v2.59.1
    environment:
      ZITADEL_DATABASE_COCKROACH_HOST: cockroachdb
      ZITADEL_DATABASE_COCKROACH_PORT: 26257
      ZITADEL_DATABASE_COCKROACH_DATABASE: zitadel
      ZITADEL_DATABASE_COCKROACH_USER_SSL_MODE: disable
      ZITADEL_DATABASE_COCKROACH_ADMIN_SSL_MODE: disable
      ZITADEL_EXTERNALSECURE: false
    ports:
      - '3001:8080'
    command: 'start-from-init --masterkey "MasterkeyNeedsToHave32Characters" --tlsMode disabled'
    restart: 'always'
    depends_on:
      cockroachdb:
        condition: 'service_healthy'
 yaml
services:
  cockroachdb:
    container_name: cockroach
    image: cockroachdb/cockroach:v23.1.25
    command: start-single-node --insecure
    ports:
      - "8080:8080"   # User interface
      - "26257:26257" # Main port
    environment:
      - COCKROACH_DB=defaultdb
    volumes:
      - ./data/cockroach:/cockroach/cockroach-data
    healthcheck:
      test: ["CMD", "curl", "-f", "http://localhost:8080/health"]
      interval: 2s
      timeout: 2s
      retries: 5
      start_period: 0s
    restart: always

 zitadel:
    image: ghcr.io/zitadel/zitadel:v2.59.1
    environment:
      ZITADEL_DATABASE_COCKROACH_HOST: cockroachdb
      ZITADEL_DATABASE_COCKROACH_PORT: 26257
      ZITADEL_DATABASE_COCKROACH_DATABASE: zitadel
      ZITADEL_DATABASE_COCKROACH_USER_SSL_MODE: disable
      ZITADEL_DATABASE_COCKROACH_ADMIN_SSL_MODE: disable
      ZITADEL_EXTERNALSECURE: false
    ports:
      - '3001:8080'
    command: 'start-from-init --masterkey "MasterkeyNeedsToHave32Characters" --tlsMode disabled'
    restart: 'always'
    depends_on:
      cockroachdb:
        condition: 'service_healthy'
Which results in the following zitadel errors: 
 
...
time="2024-08-23T07:31:26Z" level=info msg="verify database" caller="/home/runner/work/zitadel/zitadel/cmd/initialise/verify_database.go:39" database=zitadel
time="2024-08-23T07:31:26Z" level=info msg="verify grant" caller="/home/runner/work/zitadel/zitadel/cmd/initialise/verify_grant.go:34" database=zitadel user=zitadel
time="2024-08-23T07:31:26Z" level=info msg="verify settings" caller="/home/runner/work/zitadel/zitadel/cmd/initialise/verify_settings.go:40" database=zitadel user=zitadel
time="2024-08-23T07:31:26Z" level=fatal msg="unable to initialize the database" caller="/home/runner/work/zitadel/zitadel/cmd/initialise/init.go:68" error="ERROR: unrecognized configuration parameter \"enable_durable_locking_for_serializable\" (SQLSTATE 42704)"
 
...
time="2024-08-23T07:31:26Z" level=info msg="verify database" caller="/home/runner/work/zitadel/zitadel/cmd/initialise/verify_database.go:39" database=zitadel
time="2024-08-23T07:31:26Z" level=info msg="verify grant" caller="/home/runner/work/zitadel/zitadel/cmd/initialise/verify_grant.go:34" database=zitadel user=zitadel
time="2024-08-23T07:31:26Z" level=info msg="verify settings" caller="/home/runner/work/zitadel/zitadel/cmd/initialise/verify_settings.go:40" database=zitadel user=zitadel
time="2024-08-23T07:31:26Z" level=fatal msg="unable to initialize the database" caller="/home/runner/work/zitadel/zitadel/cmd/initialise/init.go:68" error="ERROR: unrecognized configuration parameter \"enable_durable_locking_for_serializable\" (SQLSTATE 42704)"
3 Replies
FFO
FFO•13mo ago
Uhm maybe @adlerhurst knows whats up here.
adlerhurst
adlerhurst•13mo ago
I think you are looking for this https://zitadel.com/docs/support/advisory/a10009
ZITADEL Docs
Date and Version
tamis0583
tamis0583OP•13mo ago
@adlerhurst doesn't the zitadel docker container run the init command the first time it starts? And thus this should be set? "Because enabling flags requires admin privileges the statement must be executed manually or by executing zitadel init command."

Did you find this page helpful?