Skip to content

Endless restarting of immich-server on v1.132.1 #17874

Closed
@DJFriar

Description

@DJFriar

I have searched the existing issues, both open and closed, to make sure this is not a duplicate report.

  • Yes

The bug

I'm running Docker on a Mac mini M1

The OS that Immich Server is running on

macOS Sequoia 15.3

Version of Immich Server

v1.132.1

Version of Immich Mobile App

N/A

Platform with the issue

  • Server
  • Web
  • Mobile

Your docker-compose.yml content

#
# WARNING: To install Immich, follow our guide: https://immich.app/docs/install/docker-compose
#
# Make sure to use the docker-compose.yml of the current release:
#
# https://github.com/immich-app/immich/releases/latest/download/docker-compose.yml
#
# The compose file on main may not be compatible with the latest release.

name: immich

services:
  immich-server:
    container_name: immich_server
    image: ghcr.io/immich-app/immich-server:${IMMICH_VERSION:-release}
    # extends:
    #   file: hwaccel.transcoding.yml
    #   service: cpu # set to one of [nvenc, quicksync, rkmpp, vaapi, vaapi-wsl] for accelerated transcoding
    volumes:
      # Do not edit the next line. If you want to change the media storage location on your system, edit the value of UPLOAD_LOCATION in the .env file
      - ${UPLOAD_LOCATION}:/usr/src/app/upload
      - /etc/localtime:/etc/localtime:ro
    env_file:
      - .env
    ports:
      - '2283:2283'
    depends_on:
      - redis
      - database
    restart: always
    healthcheck:
      disable: false

  immich-machine-learning:
    container_name: immich_machine_learning
    # For hardware acceleration, add one of -[armnn, cuda, rocm, openvino, rknn] to the image tag.
    # Example tag: ${IMMICH_VERSION:-release}-cuda
    image: ghcr.io/immich-app/immich-machine-learning:${IMMICH_VERSION:-release}
    # extends: # uncomment this section for hardware acceleration - see https://immich.app/docs/features/ml-hardware-acceleration
    #   file: hwaccel.ml.yml
    #   service: cpu # set to one of [armnn, cuda, rocm, openvino, openvino-wsl, rknn] for accelerated inference - use the `-wsl` version for WSL2 where applicable
    volumes:
      - model-cache:/cache
    env_file:
      - .env
    restart: always
    healthcheck:
      disable: false

  redis:
    container_name: immich_redis
    image: docker.io/valkey/valkey:8-bookworm@sha256:42cba146593a5ea9a622002c1b7cba5da7be248650cbb64ecb9c6c33d29794b1
    healthcheck:
      test: redis-cli ping || exit 1
    restart: always

  database:
    container_name: immich_postgres
    image: docker.io/tensorchord/pgvecto-rs:pg14-v0.2.0@sha256:739cdd626151ff1f796dc95a6591b55a714f341c737e27f045019ceabf8e8c52
    environment:
      POSTGRES_PASSWORD: ${DB_PASSWORD}
      POSTGRES_USER: ${DB_USERNAME}
      POSTGRES_DB: ${DB_DATABASE_NAME}
      POSTGRES_INITDB_ARGS: '--data-checksums'
    volumes:
      # Do not edit the next line. If you want to change the database storage location on your system, edit the value of DB_DATA_LOCATION in the .env file
      - ${DB_DATA_LOCATION}:/var/lib/postgresql/data
    healthcheck:
      test: >-
        pg_isready --dbname="$${POSTGRES_DB}" --username="$${POSTGRES_USER}" || exit 1; Chksum="$$(psql --dbname="$${POSTGRES_DB}" --username="$${POSTGRES_USER}" --tuples-only --no-align --command='SELECT COALESCE(SUM(checksum_failures), 0) 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

volumes:
  model-cache:

Your .env content

# You can find documentation for all the supported env variables at https://immich.app/docs/install/environment-variables

# The location where your uploaded files are stored
UPLOAD_LOCATION="/Volumes/4TB G-Drive/Photos/Immich"
# The location where your database files are stored
DB_DATA_LOCATION=./postgres

# To set a timezone, uncomment the next line and change Etc/UTC to a TZ identifier from this list: https://en.wikipedia.org/wiki/List_of_tz_database_time_zones#List
TZ=America/Chicago

# The Immich version to use. You can pin this to a specific version like "v1.71.0"
IMMICH_VERSION=release

# Connection secret for postgres. You should change it to a random password
# Please use only the characters `A-Za-z0-9`, without special characters or spaces
DB_PASSWORD=postgres

# The values below this line do not need to be changed
###################################################################################
DB_USERNAME=postgres
DB_DATABASE_NAME=immich

Reproduction steps

  1. Execute docker compose pull && docker compose up -d to get v1.132.1
  2. If you catch the server while it is running, you will see an Immich error that says "Importing a module script failed. - 500 undefined"
  3. If you monitor the docker logs for immesh-server you will see that it restarts every 8-10 seconds, though no errors are logged.
    ...

Relevant log output

[Nest] 17  - 04/25/2025, 4:00:32 AM     LOG [Api:RouterExplorer] Mapped {/api/view/folder/unique-paths, GET} route
[Nest] 17  - 04/25/2025, 4:00:32 AM     LOG [Api:RouterExplorer] Mapped {/api/view/folder, GET} route
[Nest] 17  - 04/25/2025, 4:00:32 AM     LOG [Api:NestApplication] Nest application successfully started
[Nest] 17  - 04/25/2025, 4:00:32 AM     LOG [Api:Bootstrap] Immich Server is listening on http://[::1]:2283 [v1.132.1] [production] 
Initializing Immich v1.132.1
Detected CPU Cores: 8
Starting api worker
Starting microservices worker
Initializing Immich v1.132.1
Detected CPU Cores: 8
Starting api worker
Starting microservices worker
[Nest] 7  - 04/25/2025, 4:01:03 AM     LOG [Microservices:EventRepository] Initialized websocket server
[Nest] 17  - 04/25/2025, 4:01:03 AM     LOG [Api:EventRepository] Initialized websocket server
[Nest] 7  - 04/25/2025, 4:01:03 AM     LOG [Microservices:DatabaseRepository] Running migrations, this may take a while
[Nest] 7  - 04/25/2025, 4:01:03 AM     LOG [Microservices:MetadataService] Bootstrapping metadata service
[Nest] 7  - 04/25/2025, 4:01:03 AM     LOG [Microservices:MetadataService] Initializing metadata service

Additional information

In the log I attached you will see that the server becomes reachable, however 30 seconds later it has begun the startup process again indicated an exception is crashing the whole app.

Reverting to v.1.132.0 causes the error described in #17818 . Reverting to v.1.131.3 restored functionality again.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions