immich-app/immich
1
0
Fork 0
mirror of https://github.com/immich-app/immich.git synced 2026-07-25 14:00:45 +03:00
Code Issues 783 Packages Projects Releases 22 Wiki Activity

immich_postgres healthcheck not working #3441

New Issue
Closed
opened 2026-02-05 08:28:32 +03:00 by OVERLORD · 9 comments
OVERLORD commented 2026-02-05 08:28:32 +03:00
Owner
Copy Link

Originally created by @PotatoPTT on GitHub (Jun 11, 2024).

The bug

In the latest dockercompose was added a healthcheck but in immich_postgres
SELECT SUM(checksum_failures) FROM pg_stat_database returns NULL not 0, so the healthcheck fails every time
For a temporary solution i just changed to SELECT COALESCE(SUM(checksum_failures), 0) FROM pg_stat_database

The OS that Immich Server is running on

Docker/Non Relatable

Version of Immich Server

v1.106.1

Version of Immich Mobile App

v1.106.1

Platform with the issue

  • Server
  • Web
  • Mobile

Your docker-compose.yml content

database:
    container_name: immich_postgres
    image: ${IMMICH_POSTGRES}
    env_file:
      - .env
    networks:
      - non_exposed
    environment:
      POSTGRES_PASSWORD: ${DB_PASSWORD}
      POSTGRES_USER: ${DB_USERNAME}
      POSTGRES_DB: ${DB_DATABASE_NAME}
      POSTGRES_INITDB_ARGS: '--data-checksums'
    volumes:
      - pgdata:/var/lib/postgresql/data
    healthcheck:
      test: pg_isready --dbname='${DB_DATABASE_NAME}' || exit 1; Chksum="$$(psql --dbname='${DB_DATABASE_NAME}' --username='${DB_USERNAME}' --tuples-only --no-align --command='SELECT SUM(checksum_failures) FROM pg_stat_database')"; echo "checksum failure count is $$Chksum"; [ "$$Chksum" = '0' ] || exit 1
      interval: 5m
      start_interval: 30s
      start_period: 5m
    command: ["postgres", "-c" ,"shared_preload_libraries=vectors.so", "-c", 'search_path="$$user", public, vectors', "-c", "logging_collector=on", "-c", "max_wal_size=2GB", "-c", "shared_buffers=512MB", "-c", "wal_compression=on"]
    restart: always
    labels:
      - 'wud.watch=false'

Your .env content

NON RELATABLE

Reproduction steps

1. Run the container
2. Wait 5 minutes
3. Healthcheck fails

Relevant log output

No response

Additional information

No response

Originally created by @PotatoPTT on GitHub (Jun 11, 2024). ### The bug In the latest dockercompose was added a healthcheck but in immich_postgres `SELECT SUM(checksum_failures) FROM pg_stat_database` returns NULL not 0, so the healthcheck fails every time For a temporary solution i just changed to `SELECT COALESCE(SUM(checksum_failures), 0) FROM pg_stat_database` ### The OS that Immich Server is running on Docker/Non Relatable ### Version of Immich Server v1.106.1 ### Version of Immich Mobile App v1.106.1 ### Platform with the issue - [X] Server - [ ] Web - [ ] Mobile ### Your docker-compose.yml content ```YAML database: container_name: immich_postgres image: ${IMMICH_POSTGRES} env_file: - .env networks: - non_exposed environment: POSTGRES_PASSWORD: ${DB_PASSWORD} POSTGRES_USER: ${DB_USERNAME} POSTGRES_DB: ${DB_DATABASE_NAME} POSTGRES_INITDB_ARGS: '--data-checksums' volumes: - pgdata:/var/lib/postgresql/data healthcheck: test: pg_isready --dbname='${DB_DATABASE_NAME}' || exit 1; Chksum="$$(psql --dbname='${DB_DATABASE_NAME}' --username='${DB_USERNAME}' --tuples-only --no-align --command='SELECT SUM(checksum_failures) FROM pg_stat_database')"; echo "checksum failure count is $$Chksum"; [ "$$Chksum" = '0' ] || exit 1 interval: 5m start_interval: 30s start_period: 5m command: ["postgres", "-c" ,"shared_preload_libraries=vectors.so", "-c", 'search_path="$$user", public, vectors', "-c", "logging_collector=on", "-c", "max_wal_size=2GB", "-c", "shared_buffers=512MB", "-c", "wal_compression=on"] restart: always labels: - 'wud.watch=false' ``` ### Your .env content ```Shell NON RELATABLE ``` ### Reproduction steps ```bash 1. Run the container 2. Wait 5 minutes 3. Healthcheck fails ``` ### Relevant log output _No response_ ### Additional information _No response_
OVERLORD commented 2026-02-05 08:28:42 +03:00
Author
Owner
Copy Link

@AngelaDMerkel commented on GitHub (Jun 11, 2024):

I am also experiencing this issue

@AngelaDMerkel commented on GitHub (Jun 11, 2024): I am also experiencing this issue
OVERLORD commented 2026-02-05 08:28:43 +03:00
Author
Owner
Copy Link

@dsquare86 commented on GitHub (Jun 11, 2024):

Same issue on micro services and postgres

@dsquare86 commented on GitHub (Jun 11, 2024): Same issue on micro services and postgres
OVERLORD commented 2026-02-05 08:28:49 +03:00
Author
Owner
Copy Link

@PotatoPTT commented on GitHub (Jun 11, 2024):

Same issue on micro services and postgres

microservices it's no longer required release notes

@PotatoPTT commented on GitHub (Jun 11, 2024): > Same issue on micro services and postgres microservices it's no longer required [release notes](https://github.com/immich-app/immich/releases/tag/v1.106.1)
OVERLORD commented 2026-02-05 08:28:50 +03:00
Author
Owner
Copy Link

@zaggash commented on GitHub (Jun 11, 2024):

This is not a bug.
You are using running the DB without checksum.
So do not use the new test.

You can however, backup the DB, then create a new one with the new env POSTGRES_INITDB_ARGS: '--data-checksums'.
Then restore the DB.

You database will be recreated with checksum enabled and the new healthcheck will work.

@zaggash commented on GitHub (Jun 11, 2024): This is not a bug. You are using running the DB without checksum. So do not use the new test. You can however, backup the DB, then create a new one with the new env POSTGRES_INITDB_ARGS: '--data-checksums'. Then restore the DB. You database will be recreated with checksum enabled and the new healthcheck will work.
OVERLORD commented 2026-02-05 08:28:56 +03:00
Author
Owner
Copy Link

@lo97 commented on GitHub (Jun 11, 2024):

This is not a bug. You are using running the DB without checksum. So do not use the new test.

You can however, backup the DB, then create a new one with the new env POSTGRES_INITDB_ARGS: '--data-checksums'. Then restore the DB.

You database will be recreated with checksum enabled and the new healthcheck will work.

How should we backup the DB, create a new one and restore it? Does anyone have a step by step guide?

@lo97 commented on GitHub (Jun 11, 2024): > This is not a bug. You are using running the DB without checksum. So do not use the new test. > > You can however, backup the DB, then create a new one with the new env POSTGRES_INITDB_ARGS: '--data-checksums'. Then restore the DB. > > You database will be recreated with checksum enabled and the new healthcheck will work. How should we backup the DB, create a new one and restore it? Does anyone have a step by step guide?
OVERLORD commented 2026-02-05 08:28:58 +03:00
Author
Owner
Copy Link

@Tractor777 commented on GitHub (Jun 11, 2024):

This seems to work (backed up and restore) and the health check doesn't fail https://immich.app/docs/administration/backup-and-restore/#:~:text=The%20recommended%20way%20to%20backup,to%20use%20the%20pg_dumpall%20command.

@Tractor777 commented on GitHub (Jun 11, 2024): This seems to work (backed up and restore) and the health check doesn't fail https://immich.app/docs/administration/backup-and-restore/#:~:text=The%20recommended%20way%20to%20backup,to%20use%20the%20pg_dumpall%20command.
OVERLORD commented 2026-02-05 08:28:59 +03:00
Author
Owner
Copy Link

@PotatoPTT commented on GitHub (Jun 11, 2024):

This is not a bug. You are using running the DB without checksum. So do not use the new test.

You can however, backup the DB, then create a new one with the new env POSTGRES_INITDB_ARGS: '--data-checksums'. Then restore the DB.

You database will be recreated with checksum enabled and the new healthcheck will work.

@PotatoPTT commented on GitHub (Jun 11, 2024): > This is not a bug. You are using running the DB without checksum. So do not use the new test. > > You can however, backup the DB, then create a new one with the new env POSTGRES_INITDB_ARGS: '--data-checksums'. Then restore the DB. > > You database will be recreated with checksum enabled and the new healthcheck will work.
OVERLORD commented 2026-02-05 08:29:01 +03:00
Author
Owner
Copy Link

@mertalev commented on GitHub (Jun 12, 2024):

I think this should be fixed. The health check shouldn’t report Postgres as unhealthy unless it has a reason to think it is. Adding a COALESCE would make it more elegant for existing databases (and generally for users who disable checksums).

@mertalev commented on GitHub (Jun 12, 2024): I think this should be fixed. The health check shouldn’t report Postgres as unhealthy unless it has a reason to think it is. Adding a COALESCE would make it more elegant for existing databases (and generally for users who disable checksums).
OVERLORD commented 2026-02-05 08:29:07 +03:00
Author
Owner
Copy Link

@zaggash commented on GitHub (Jun 12, 2024):

It is written in the documentation FAQ
I agree it deserves more visibility

https://immich.app/docs/FAQ#how-can-i-verify-the-integrity-of-my-database

@zaggash commented on GitHub (Jun 12, 2024): It is written in the documentation FAQ I agree it deserves more visibility https://immich.app/docs/FAQ#how-can-i-verify-the-integrity-of-my-database
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
accessibility
changelog:enhancement
changelog:security
changelog:skip
changelog:translation
cli
date-time
dependencies
documentation
external-library
format
good first issue
mobile-beta
mobile-beta
mobile-beta
needs-answer
nice to have
pull-request
Mirrored from GitHub Pull Request
 sharing
tech-debt
📱mobile
🖥️web
🗄️server
🧠machine-learning
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: immich-app/immich#3441
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?