I

Immich•6/18/25, 7:49 AM

:wave: Hey @Quafley,

Thanks for reaching out to us. Please carefully read this message and follow the recommended actions. This will help us be more effective in our support effort and leave more time for building Immich :immich:.

References

Container Logs:
```
docker compose logs
```
```
docker compose logs
```
docs
Container Status:
```
docker ps -a
```
```
docker ps -a
```
docs
Reverse Proxy: https://immich.app/docs/administration/reverse-proxy
Code Formatting https://support.discord.com/hc/en-us/articles/210298617-Markdown-Text-101-Chat-Formatting-Bold-Italic-Underline#h_01GY0DAKGXDEHE263BCAYEGFJA

I

Immich•6/18/25, 7:49 AM

Checklist

I have...

:ballot_box_with_check: verified I'm on the latest release(note that mobile app releases may take some time).
:ballot_box_with_check: read applicable release notes.
:ballot_box_with_check: reviewed the FAQs for known issues.
:ballot_box_with_check: reviewed Github for known issues.
:ballot_box_with_check: tried accessing Immich via local ip (without a custom reverse proxy).
:blue_square: uploaded the relevant information (see below).
:ballot_box_with_check: tried an incognito window, disabled extensions, cleared mobile app cache, logged out and back in, different browsers, etc. as applicable

(an item can be marked as "complete" by reacting with the appropriate number)

Information

In order to be able to effectively help you, we need you to provide clear information to show what the problem is. The exact details needed vary per case, but here is a list of things to consider:

Your docker-compose.yml and .env files.
Logs from all the containers and their status (see above).
All the troubleshooting steps you've tried so far.
Any recent changes you've made to Immich or your system.
Details about your system (both software/OS and hardware).
Details about your storage (filesystems, type of disks, output of commands like
```
fdisk -l
```
```
fdisk -l
```
and
```
df -h
```
```
df -h
```
).
The version of the Immich server, mobile app, and other relevant pieces.
Any other information that you think might be relevant.

Please paste files and logs with proper code formatting, and especially avoid blurry screenshots.
Without the right information we can't work out what the problem is. Help us help you ;)

If this ticket can be closed you can use the

/close

/close

command, and re-open it later if needed.

Q

QuafleyOP•6/18/25, 7:49 AM

Providing additional info in a sec

Q

QuafleyOP•6/18/25, 7:49 AM

Compose file

Quafley · 2025-06-18T07:49:06.587Z

Hello everyone, I've had immich running stable on the 134 release for quite some time, since it was released. This morning I uploaded images and videos to immich from my tablet. Quite a lot of files, but immich managed. All of the sudden the upload stopped, I looked at the logs of the immich postgres container to find the following. I am unable to find out what has happened, what can I do to remedy this? The database container is now in a continues loop.

version: "3.8"

name: immich

services:
  immich-server:
    container_name: immich_server
    image: ghcr.io/immich-app/immich-server:${IMMICH_VERSION:-release}
    volumes:
      - ${UPLOAD_LOCATION}:/usr/src/app/upload
      - /etc/localtime:/etc/localtime:ro
    env_file:
      - .env
    devices:
      - /dev/dri:/dev/dri
    ports:
      - 2283:2283
    networks:
      hypnosnet:
        ipv4_address: 172.18.0.134
    depends_on:
      - redis
      - database
    restart: always
    healthcheck:
      disable: false
      
  immich-machine-learning:
    container_name: immich_machine_learning
    image: ghcr.io/immich-app/immich-machine-learning:${IMMICH_VERSION:-release}
    volumes:
      - /mnt/user/appdata/immich/model-cache:/cache
    networks:
      hypnosnet:
        ipv4_address: 172.18.0.135
    env_file:
      - .env
    restart: always
    healthcheck:
      disable: false
      
  redis:
    container_name: immich_redis
    image: docker.io/valkey/valkey:8-bookworm@sha256:42cba146593a5ea9a622002c1b7cba5da7be248650cbb64ecb9c6c33d29794b1
    networks:
      hypnosnet:
        ipv4_address: 172.18.0.136
    healthcheck:
      test: redis-cli ping || exit 1
    restart: always

  database:
    container_name: immich_postgres
    image: ghcr.io/immich-app/postgres:14-vectorchord0.3.0-pgvectors0.2.0
    env_file:
      - .env
    environment:
      POSTGRES_PASSWORD: ${DB_PASSWORD}
      POSTGRES_USER: ${DB_USERNAME}
      POSTGRES_DB: ${DB_DATABASE_NAME}
      # Uncomment the DB_STORAGE_TYPE: 'HDD' var if your database isn't stored on SSDs
      # DB_STORAGE_TYPE: 'HDD'
    networks:
      hypnosnet:
        ipv4_address: 172.18.0.137
    volumes:
      - /mnt/user/appdata/immich_postgres:/var/lib/postgresql/data
    restart: always

volumes:
  model-cache:
    driver_opts:
      type: none
      device: /mnt/user/appdata/immich/model_cache
      o: bind

networks:
  hypnosnet:
    external: true
    name: "hypnosnet"

version: "3.8"

name: immich

services:
  immich-server:
    container_name: immich_server
    image: ghcr.io/immich-app/immich-server:${IMMICH_VERSION:-release}
    volumes:
      - ${UPLOAD_LOCATION}:/usr/src/app/upload
      - /etc/localtime:/etc/localtime:ro
    env_file:
      - .env
    devices:
      - /dev/dri:/dev/dri
    ports:
      - 2283:2283
    networks:
      hypnosnet:
        ipv4_address: 172.18.0.134
    depends_on:
      - redis
      - database
    restart: always
    healthcheck:
      disable: false
      
  immich-machine-learning:
    container_name: immich_machine_learning
    image: ghcr.io/immich-app/immich-machine-learning:${IMMICH_VERSION:-release}
    volumes:
      - /mnt/user/appdata/immich/model-cache:/cache
    networks:
      hypnosnet:
        ipv4_address: 172.18.0.135
    env_file:
      - .env
    restart: always
    healthcheck:
      disable: false
      
  redis:
    container_name: immich_redis
    image: docker.io/valkey/valkey:8-bookworm@sha256:42cba146593a5ea9a622002c1b7cba5da7be248650cbb64ecb9c6c33d29794b1
    networks:
      hypnosnet:
        ipv4_address: 172.18.0.136
    healthcheck:
      test: redis-cli ping || exit 1
    restart: always

  database:
    container_name: immich_postgres
    image: ghcr.io/immich-app/postgres:14-vectorchord0.3.0-pgvectors0.2.0
    env_file:
      - .env
    environment:
      POSTGRES_PASSWORD: ${DB_PASSWORD}
      POSTGRES_USER: ${DB_USERNAME}
      POSTGRES_DB: ${DB_DATABASE_NAME}
      # Uncomment the DB_STORAGE_TYPE: 'HDD' var if your database isn't stored on SSDs
      # DB_STORAGE_TYPE: 'HDD'
    networks:
      hypnosnet:
        ipv4_address: 172.18.0.137
    volumes:
      - /mnt/user/appdata/immich_postgres:/var/lib/postgresql/data
    restart: always

volumes:
  model-cache:
    driver_opts:
      type: none
      device: /mnt/user/appdata/immich/model_cache
      o: bind

networks:
  hypnosnet:
    external: true
    name: "hypnosnet"

version: "3.8"

name: immich

services:
  immich-server:
    container_name: immich_server
    image: ghcr.io/immich-app/immich-server:${IMMICH_VERSION:-release}
    volumes:
      - ${UPLOAD_LOCATION}:/usr/src/app/upload
      - /etc/localtime:/etc/localtime:ro
    env_file:
      - .env
    devices:
      - /dev/dri:/dev/dri
    ports:
      - 2283:2283
    networks:
      hypnosnet:
        ipv4_address: 172.18.0.134
    depends_on:
      - redis
      - database
    restart: always
    healthcheck:
      disable: false
      
  immich-machine-learning:
    container_name: immich_machine_learning
    image: ghcr.io/immich-app/immich-machine-learning:${IMMICH_VERSION:-release}
    volumes:
      - /mnt/user/appdata/immich/model-cache:/cache
    networks:
      hypnosnet:
        ipv4_address: 172.18.0.135
    env_file:
      - .env
    restart: always
    healthcheck:
      disable: false
      
  redis:
    container_name: immich_redis
    image: docker.io/valkey/valkey:8-bookworm@sha256:42cba146593a5ea9a622002c1b7cba5da7be248650cbb64ecb9c6c33d29794b1
    networks:
      hypnosnet:
        ipv4_address: 172.18.0.136
    healthcheck:
      test: redis-cli ping || exit 1
    restart: always

  database:
    container_name: immich_postgres
    image: ghcr.io/immich-app/postgres:14-vectorchord0.3.0-pgvectors0.2.0
    env_file:
      - .env
    environment:
      POSTGRES_PASSWORD: ${DB_PASSWORD}
      POSTGRES_USER: ${DB_USERNAME}
      POSTGRES_DB: ${DB_DATABASE_NAME}
      # Uncomment the DB_STORAGE_TYPE: 'HDD' var if your database isn't stored on SSDs
      # DB_STORAGE_TYPE: 'HDD'
    networks:
      hypnosnet:
        ipv4_address: 172.18.0.137
    volumes:
      - /mnt/user/appdata/immich_postgres:/var/lib/postgresql/data
    restart: always

volumes:
  model-cache:
    driver_opts:
      type: none
      device: /mnt/user/appdata/immich/model_cache
      o: bind

networks:
  hypnosnet:
    external: true
    name: "hypnosnet"

version: "3.8"

name: immich

services:
  immich-server:
    container_name: immich_server
    image: ghcr.io/immich-app/immich-server:${IMMICH_VERSION:-release}
    volumes:
      - ${UPLOAD_LOCATION}:/usr/src/app/upload
      - /etc/localtime:/etc/localtime:ro
    env_file:
      - .env
    devices:
      - /dev/dri:/dev/dri
    ports:
      - 2283:2283
    networks:
      hypnosnet:
        ipv4_address: 172.18.0.134
    depends_on:
      - redis
      - database
    restart: always
    healthcheck:
      disable: false
      
  immich-machine-learning:
    container_name: immich_machine_learning
    image: ghcr.io/immich-app/immich-machine-learning:${IMMICH_VERSION:-release}
    volumes:
      - /mnt/user/appdata/immich/model-cache:/cache
    networks:
      hypnosnet:
        ipv4_address: 172.18.0.135
    env_file:
      - .env
    restart: always
    healthcheck:
      disable: false
      
  redis:
    container_name: immich_redis
    image: docker.io/valkey/valkey:8-bookworm@sha256:42cba146593a5ea9a622002c1b7cba5da7be248650cbb64ecb9c6c33d29794b1
    networks:
      hypnosnet:
        ipv4_address: 172.18.0.136
    healthcheck:
      test: redis-cli ping || exit 1
    restart: always

  database:
    container_name: immich_postgres
    image: ghcr.io/immich-app/postgres:14-vectorchord0.3.0-pgvectors0.2.0
    env_file:
      - .env
    environment:
      POSTGRES_PASSWORD: ${DB_PASSWORD}
      POSTGRES_USER: ${DB_USERNAME}
      POSTGRES_DB: ${DB_DATABASE_NAME}
      # Uncomment the DB_STORAGE_TYPE: 'HDD' var if your database isn't stored on SSDs
      # DB_STORAGE_TYPE: 'HDD'
    networks:
      hypnosnet:
        ipv4_address: 172.18.0.137
    volumes:
      - /mnt/user/appdata/immich_postgres:/var/lib/postgresql/data
    restart: always

volumes:
  model-cache:
    driver_opts:
      type: none
      device: /mnt/user/appdata/immich/model_cache
      o: bind

networks:
  hypnosnet:
    external: true
    name: "hypnosnet"

Q

QuafleyOP•6/18/25, 7:51 AM

message.txt4.9KB

Q

QuafleyOP•6/18/25, 7:53 AM

bullet 2: the other containers rely on the database, so they don't start (anymore)

[Nest] 7  - 06/18/2025, 7:52:33 AM     LOG [Microservices:EventRepository] Initialized websocket server
microservices worker error: Error: getaddrinfo ENOTFOUND immich_postgres, stack: Error: getaddrinfo ENOTFOUND immich_postgres
    at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:120:26)
microservices worker exited with code 1
Killing api process
Initializing Immich v1.134.0
Detected CPU Cores: 8

[Nest] 7  - 06/18/2025, 7:52:33 AM     LOG [Microservices:EventRepository] Initialized websocket server
microservices worker error: Error: getaddrinfo ENOTFOUND immich_postgres, stack: Error: getaddrinfo ENOTFOUND immich_postgres
    at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:120:26)
microservices worker exited with code 1
Killing api process
Initializing Immich v1.134.0
Detected CPU Cores: 8

[Nest] 7  - 06/18/2025, 7:52:33 AM     LOG [Microservices:EventRepository] Initialized websocket server
microservices worker error: Error: getaddrinfo ENOTFOUND immich_postgres, stack: Error: getaddrinfo ENOTFOUND immich_postgres
    at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:120:26)
microservices worker exited with code 1
Killing api process
Initializing Immich v1.134.0
Detected CPU Cores: 8

[Nest] 7  - 06/18/2025, 7:52:33 AM     LOG [Microservices:EventRepository] Initialized websocket server
microservices worker error: Error: getaddrinfo ENOTFOUND immich_postgres, stack: Error: getaddrinfo ENOTFOUND immich_postgres
    at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:120:26)
microservices worker exited with code 1
Killing api process
Initializing Immich v1.134.0
Detected CPU Cores: 8

[06/18/25 07:43:08] INFO     Starting gunicorn 23.0.0                           
[06/18/25 07:43:08] INFO     Listening at: http://[::]:3003 (8)                 
[06/18/25 07:43:08] INFO     Using worker: immich_ml.config.CustomUvicornWorker 
[06/18/25 07:43:08] INFO     Booting worker with pid: 9                         
[06/18/25 07:43:20] INFO     Started server process [9]                         
[06/18/25 07:43:20] INFO     Waiting for application startup.                   
[06/18/25 07:43:20] INFO     Created in-memory cache with unloading after 300s  
                             of inactivity.                                     
[06/18/25 07:43:20] INFO     Initialized request thread pool with 8 threads.    
[06/18/25 07:43:20] INFO     Application startup complete.

[06/18/25 07:43:08] INFO     Starting gunicorn 23.0.0                           
[06/18/25 07:43:08] INFO     Listening at: http://[::]:3003 (8)                 
[06/18/25 07:43:08] INFO     Using worker: immich_ml.config.CustomUvicornWorker 
[06/18/25 07:43:08] INFO     Booting worker with pid: 9                         
[06/18/25 07:43:20] INFO     Started server process [9]                         
[06/18/25 07:43:20] INFO     Waiting for application startup.                   
[06/18/25 07:43:20] INFO     Created in-memory cache with unloading after 300s  
                             of inactivity.                                     
[06/18/25 07:43:20] INFO     Initialized request thread pool with 8 threads.    
[06/18/25 07:43:20] INFO     Application startup complete.

[06/18/25 07:43:08] INFO     Starting gunicorn 23.0.0                           
[06/18/25 07:43:08] INFO     Listening at: http://[::]:3003 (8)                 
[06/18/25 07:43:08] INFO     Using worker: immich_ml.config.CustomUvicornWorker 
[06/18/25 07:43:08] INFO     Booting worker with pid: 9                         
[06/18/25 07:43:20] INFO     Started server process [9]                         
[06/18/25 07:43:20] INFO     Waiting for application startup.                   
[06/18/25 07:43:20] INFO     Created in-memory cache with unloading after 300s  
                             of inactivity.                                     
[06/18/25 07:43:20] INFO     Initialized request thread pool with 8 threads.    
[06/18/25 07:43:20] INFO     Application startup complete.

[06/18/25 07:43:08] INFO     Starting gunicorn 23.0.0                           
[06/18/25 07:43:08] INFO     Listening at: http://[::]:3003 (8)                 
[06/18/25 07:43:08] INFO     Using worker: immich_ml.config.CustomUvicornWorker 
[06/18/25 07:43:08] INFO     Booting worker with pid: 9                         
[06/18/25 07:43:20] INFO     Started server process [9]                         
[06/18/25 07:43:20] INFO     Waiting for application startup.                   
[06/18/25 07:43:20] INFO     Created in-memory cache with unloading after 300s  
                             of inactivity.                                     
[06/18/25 07:43:20] INFO     Initialized request thread pool with 8 threads.    
[06/18/25 07:43:20] INFO     Application startup complete.

Q

QuafleyOP•6/18/25, 7:56 AM

Bullet 3: I have not messed with the database as I am not familiar enough and I am afraid to break it.
bullet 4: only uploaded about 100GB from my tablet to the server, and moved the postgres database from my cache to my app_data drive
Bullet 5: Unraid 7.1.3 using docker compose.
bullet 6:

Filesystem      Size  Used Avail Use% Mounted on
rootfs           32G  2.1G   30G   7% /
tmpfs           128M  4.5M  124M   4% /run
/dev/sda1        15G  1.9G   13G  13% /boot
overlay          32G  2.1G   30G   7% /usr
overlay          32G  2.1G   30G   7% /lib
tmpfs           128M  1.8M  127M   2% /var/log
devtmpfs        8.0M     0  8.0M   0% /dev
tmpfs            32G     0   32G   0% /dev/shm
efivarfs        256K   72K  180K  29% /sys/firmware/efi/efivars
/dev/md1p1       15T   13T  2.3T  85% /mnt/disk1
/dev/md2p1      9.1T  6.9T  2.3T  75% /mnt/disk2
/dev/md3p1      9.1T  6.0T  3.1T  66% /mnt/disk3
/dev/md4p1       19T   14T  4.6T  76% /mnt/disk4
/dev/sdc1       932G  291G  637G  32% /mnt/app_data
/dev/nvme0n1p1  932G  566G  364G  61% /mnt/cache
shfs             51T   39T   13T  77% /mnt/user0
shfs             51T   39T   13T  77% /mnt/user
tmpfs           6.3G     0  6.3G   0% /run/user/0

Filesystem      Size  Used Avail Use% Mounted on
rootfs           32G  2.1G   30G   7% /
tmpfs           128M  4.5M  124M   4% /run
/dev/sda1        15G  1.9G   13G  13% /boot
overlay          32G  2.1G   30G   7% /usr
overlay          32G  2.1G   30G   7% /lib
tmpfs           128M  1.8M  127M   2% /var/log
devtmpfs        8.0M     0  8.0M   0% /dev
tmpfs            32G     0   32G   0% /dev/shm
efivarfs        256K   72K  180K  29% /sys/firmware/efi/efivars
/dev/md1p1       15T   13T  2.3T  85% /mnt/disk1
/dev/md2p1      9.1T  6.9T  2.3T  75% /mnt/disk2
/dev/md3p1      9.1T  6.0T  3.1T  66% /mnt/disk3
/dev/md4p1       19T   14T  4.6T  76% /mnt/disk4
/dev/sdc1       932G  291G  637G  32% /mnt/app_data
/dev/nvme0n1p1  932G  566G  364G  61% /mnt/cache
shfs             51T   39T   13T  77% /mnt/user0
shfs             51T   39T   13T  77% /mnt/user
tmpfs           6.3G     0  6.3G   0% /run/user/0

Filesystem      Size  Used Avail Use% Mounted on
rootfs           32G  2.1G   30G   7% /
tmpfs           128M  4.5M  124M   4% /run
/dev/sda1        15G  1.9G   13G  13% /boot
overlay          32G  2.1G   30G   7% /usr
overlay          32G  2.1G   30G   7% /lib
tmpfs           128M  1.8M  127M   2% /var/log
devtmpfs        8.0M     0  8.0M   0% /dev
tmpfs            32G     0   32G   0% /dev/shm
efivarfs        256K   72K  180K  29% /sys/firmware/efi/efivars
/dev/md1p1       15T   13T  2.3T  85% /mnt/disk1
/dev/md2p1      9.1T  6.9T  2.3T  75% /mnt/disk2
/dev/md3p1      9.1T  6.0T  3.1T  66% /mnt/disk3
/dev/md4p1       19T   14T  4.6T  76% /mnt/disk4
/dev/sdc1       932G  291G  637G  32% /mnt/app_data
/dev/nvme0n1p1  932G  566G  364G  61% /mnt/cache
shfs             51T   39T   13T  77% /mnt/user0
shfs             51T   39T   13T  77% /mnt/user
tmpfs           6.3G     0  6.3G   0% /run/user/0

Filesystem      Size  Used Avail Use% Mounted on
rootfs           32G  2.1G   30G   7% /
tmpfs           128M  4.5M  124M   4% /run
/dev/sda1        15G  1.9G   13G  13% /boot
overlay          32G  2.1G   30G   7% /usr
overlay          32G  2.1G   30G   7% /lib
tmpfs           128M  1.8M  127M   2% /var/log
devtmpfs        8.0M     0  8.0M   0% /dev
tmpfs            32G     0   32G   0% /dev/shm
efivarfs        256K   72K  180K  29% /sys/firmware/efi/efivars
/dev/md1p1       15T   13T  2.3T  85% /mnt/disk1
/dev/md2p1      9.1T  6.9T  2.3T  75% /mnt/disk2
/dev/md3p1      9.1T  6.0T  3.1T  66% /mnt/disk3
/dev/md4p1       19T   14T  4.6T  76% /mnt/disk4
/dev/sdc1       932G  291G  637G  32% /mnt/app_data
/dev/nvme0n1p1  932G  566G  364G  61% /mnt/cache
shfs             51T   39T   13T  77% /mnt/user0
shfs             51T   39T   13T  77% /mnt/user
tmpfs           6.3G     0  6.3G   0% /run/user/0

immich is stored on

/mnt/app_data

/mnt/app_data

/mnt/app_data

/mnt/app_data this includes the database.
bullet 7:1.134.0
bullet 8 ..

Q

QuafleyOP•6/18/25, 11:35 AM

I am currently trying to restore the database, and I am having a very hard time. Perhaps one of you can help me out.
I make my database backups by just pg_dumping the database, resulting in a .sql file.
I then do:

sed -i '/DROP DATABASE/d;/CREATE DATABASE/d;/DROP ROLE/d;/CREATE ROLE/d' immich-database_mess.sql

sed -i '/DROP DATABASE/d;/CREATE DATABASE/d;/DROP ROLE/d;/CREATE ROLE/d' immich-database_mess.sql

sed -i '/DROP DATABASE/d;/CREATE DATABASE/d;/DROP ROLE/d;/CREATE ROLE/d' immich-database_mess.sql

sed -i '/DROP DATABASE/d;/CREATE DATABASE/d;/DROP ROLE/d;/CREATE ROLE/d' immich-database_mess.sql
After which

sed -i '/\\connect/d' ./immich-database_mess.sql

sed -i '/\\connect/d' ./immich-database_mess.sql

sed -i '/\\connect/d' ./immich-database_mess.sql

sed -i '/\\connect/d' ./immich-database_mess.sql

I then copy the database into the immich postgres container:

docker cp /mnt/user/appdata/immich_backups/immich-database_mess.sql immich_postgres:/immich-database_mess.sql

docker cp /mnt/user/appdata/immich_backups/immich-database_mess.sql immich_postgres:/immich-database_mess.sql

docker cp /mnt/user/appdata/immich_backups/immich-database_mess.sql immich_postgres:/immich-database_mess.sql

docker cp /mnt/user/appdata/immich_backups/immich-database_mess.sql immich_postgres:/immich-database_mess.sql

I then try to build it up again doing:

docker exec -u postgres -it immich_postgres psql -U root -d immich -f /immich-database_mess.sql

docker exec -u postgres -it immich_postgres psql -U root -d immich -f /immich-database_mess.sql

docker exec -u postgres -it immich_postgres psql -U root -d immich -f /immich-database_mess.sql

docker exec -u postgres -it immich_postgres psql -U root -d immich -f /immich-database_mess.sql

However, it does everything well, but at the end it says this:

------------
 
(1 row)

SET
SET
SET
SET
psql:/immich-database_mess.sql:694030: ERROR:  database "root" does not exist
SET
SET
SET
SET
SET
 set_config 
------------
 
(1 row)

SET
SET
SET
SET

------------
 
(1 row)

SET
SET
SET
SET
psql:/immich-database_mess.sql:694030: ERROR:  database "root" does not exist
SET
SET
SET
SET
SET
 set_config 
------------
 
(1 row)

SET
SET
SET
SET

------------
 
(1 row)

SET
SET
SET
SET
psql:/immich-database_mess.sql:694030: ERROR:  database "root" does not exist
SET
SET
SET
SET
SET
 set_config 
------------
 
(1 row)

SET
SET
SET
SET

------------
 
(1 row)

SET
SET
SET
SET
psql:/immich-database_mess.sql:694030: ERROR:  database "root" does not exist
SET
SET
SET
SET
SET
 set_config 
------------
 
(1 row)

SET
SET
SET
SET

Q

QuafleyOP•6/18/25, 11:37 AM

I just started the other containers up, and it seems that I can access all my assets and also the web GUI.

I uploaded about 100GB worth of video and photo's after the time I restored this. what happens with these entries?

QQuafley I just started the other containers up, and it seems that I can access all my as...

A

Alex Tran•6/18/25, 11:38 AM

You can probably reupload them

Q

QuafleyOP•6/18/25, 11:39 AM

startup after a fresh rebuild:

PostgreSQL Database directory appears to contain a database; Skipping initialization
2025-06-18 11:38:35.309 GMT [1] LOG:  skipping missing configuration file "/var/lib/postgresql/data/postgresql.override.conf"
2025-06-18 11:38:35.310 GMT [1] LOG:  skipping missing configuration file "/var/lib/postgresql/data/postgresql.override.conf"
2025-06-18 11:38:41.543 UTC [1] LOG:  starting PostgreSQL 14.17 (Debian 14.17-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
2025-06-18 11:38:41.544 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2025-06-18 11:38:41.545 UTC [1] LOG:  listening on IPv6 address "::", port 5432
2025-06-18 11:38:41.567 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2025-06-18 11:38:41.587 UTC [45] LOG:  database system was shut down at 2025-06-18 11:38:15 UTC
2025-06-18 11:38:41.627 UTC [1] LOG:  database system is ready to accept connections

PostgreSQL Database directory appears to contain a database; Skipping initialization
2025-06-18 11:38:35.309 GMT [1] LOG:  skipping missing configuration file "/var/lib/postgresql/data/postgresql.override.conf"
2025-06-18 11:38:35.310 GMT [1] LOG:  skipping missing configuration file "/var/lib/postgresql/data/postgresql.override.conf"
2025-06-18 11:38:41.543 UTC [1] LOG:  starting PostgreSQL 14.17 (Debian 14.17-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
2025-06-18 11:38:41.544 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2025-06-18 11:38:41.545 UTC [1] LOG:  listening on IPv6 address "::", port 5432
2025-06-18 11:38:41.567 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2025-06-18 11:38:41.587 UTC [45] LOG:  database system was shut down at 2025-06-18 11:38:15 UTC
2025-06-18 11:38:41.627 UTC [1] LOG:  database system is ready to accept connections

PostgreSQL Database directory appears to contain a database; Skipping initialization
2025-06-18 11:38:35.309 GMT [1] LOG:  skipping missing configuration file "/var/lib/postgresql/data/postgresql.override.conf"
2025-06-18 11:38:35.310 GMT [1] LOG:  skipping missing configuration file "/var/lib/postgresql/data/postgresql.override.conf"
2025-06-18 11:38:41.543 UTC [1] LOG:  starting PostgreSQL 14.17 (Debian 14.17-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
2025-06-18 11:38:41.544 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2025-06-18 11:38:41.545 UTC [1] LOG:  listening on IPv6 address "::", port 5432
2025-06-18 11:38:41.567 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2025-06-18 11:38:41.587 UTC [45] LOG:  database system was shut down at 2025-06-18 11:38:15 UTC
2025-06-18 11:38:41.627 UTC [1] LOG:  database system is ready to accept connections

PostgreSQL Database directory appears to contain a database; Skipping initialization
2025-06-18 11:38:35.309 GMT [1] LOG:  skipping missing configuration file "/var/lib/postgresql/data/postgresql.override.conf"
2025-06-18 11:38:35.310 GMT [1] LOG:  skipping missing configuration file "/var/lib/postgresql/data/postgresql.override.conf"
2025-06-18 11:38:41.543 UTC [1] LOG:  starting PostgreSQL 14.17 (Debian 14.17-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
2025-06-18 11:38:41.544 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2025-06-18 11:38:41.545 UTC [1] LOG:  listening on IPv6 address "::", port 5432
2025-06-18 11:38:41.567 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2025-06-18 11:38:41.587 UTC [45] LOG:  database system was shut down at 2025-06-18 11:38:15 UTC
2025-06-18 11:38:41.627 UTC [1] LOG:  database system is ready to accept connections

Q

QuafleyOP•6/18/25, 11:39 AM

it seems it is working, thank god

Q

QuafleyOP•6/18/25, 11:39 AM

I think that copying the database over caused issues.

AAlex Tran You can probably reupload them

Q

QuafleyOP•6/18/25, 11:40 AM

The files do still seem to appear in my timeline though

QQuafley I think that copying the database over caused issues.

A

Alex Tran•6/18/25, 11:40 AM

Yep, should do back up/restore method when you want to move th database location

Q

QuafleyOP•6/18/25, 11:40 AM

yep now I know this, I didn't

QQuafley The files do still seem to appear in my timeline though

A

Alex Tran•6/18/25, 11:41 AM

If you can access/view/download them then the database backup was ran after the files were uploaded

A

Alex Tran•6/18/25, 11:41 AM

So you should be good

Q

QuafleyOP•6/18/25, 11:41 AM

I know 100% certain it was not

Q

QuafleyOP•6/18/25, 11:41 AM

I rant he backup at 4AM and uploaded the files at around 8AM

A

Alex Tran•6/18/25, 11:41 AM

Can you try to download a file? If it can download to your computer, it means the entry is already in the database

Q

QuafleyOP•6/18/25, 11:44 AM

Is there a way I can force my tablet to upload everthing again?

QQuafley Is there a way I can force my tablet to upload everthing again?

A

Alex Tran•6/18/25, 12:08 PM

You don’t need to force because it checks with the server if the assets on the device are on the server or not

AAlex Tran You don’t need to force because it checks with the server if the assets on the d...

Q

QuafleyOP•6/18/25, 1:26 PM

Thanks. Would you happen to know what the message about root database means? It pops up every time

Q

QuafleyOP•6/18/25, 1:27 PM

It is complaining about root database missing, but I don’t even know why it would complain as there is no such thing

Q

QuafleyOP•6/18/25, 1:27 PM

The only thing I did when I started out with Immich was name the user root instead of Postgres

A

Alex Tran•6/18/25, 1:37 PM

you might have mistakenly create a database name root

Q

QuafleyOP•6/18/25, 2:14 PM

How does one get rid of that? It’s weird that it is telling me that it cannot find it though. Perhaps I created an empty database

Q

QuafleyOP•6/18/25, 2:14 PM

I will have a look at it, any tips?

QQuafley I will have a look at it, any tips?

A

Alex Tran•6/18/25, 2:27 PM

Hmm exploring the database would the great first step to see if you actually have a database call root

Q

QuafleyOP•6/18/25, 2:37 PM

I do know my backups works, it just had to drop a few tables which I didn’t know was needed when pg dumping

A

Alex Tran•6/18/25, 2:39 PM

Do you know there is also a built-in automatic database dump mechanism as well?

Q

QuafleyOP•6/18/25, 2:51 PM

Yes I do!

AAlex Tran Do you know there is also a built-in automatic database dump mechanism as well?

Q

QuafleyOP•6/18/25, 2:51 PM

Is this normal behavior within immich_postgres:

2025-06-18 12:39:25.403 UTC [352] ERROR:  duplicate key value violates unique constraint "UQ_assets_owner_checksum"
2025-06-18 12:39:25.403 UTC [352] DETAIL:  Key ("ownerId", checksum)=(0eecf5ad-50a8-4a0d-9bfc-10d807df6191, \x0c1d9abfa236f90ccbf18a511a7faeae50dc8e42) already exists.
2025-06-18 12:39:25.403 UTC [352] STATEMENT:  insert into "assets" ("ownerId", "libraryId", "checksum", "originalPath", "deviceAssetId", "deviceId", "fileCreatedAt", "fileModifiedAt", "localDateTime", "type", "isFavorite", "duration", "visibility", "originalFileName") values ($1, $2, $3, $4, $5, $6, $7, $8, $9, $10, $11, $12, $13, $14) returning *

2025-06-18 12:39:25.403 UTC [352] ERROR:  duplicate key value violates unique constraint "UQ_assets_owner_checksum"
2025-06-18 12:39:25.403 UTC [352] DETAIL:  Key ("ownerId", checksum)=(0eecf5ad-50a8-4a0d-9bfc-10d807df6191, \x0c1d9abfa236f90ccbf18a511a7faeae50dc8e42) already exists.
2025-06-18 12:39:25.403 UTC [352] STATEMENT:  insert into "assets" ("ownerId", "libraryId", "checksum", "originalPath", "deviceAssetId", "deviceId", "fileCreatedAt", "fileModifiedAt", "localDateTime", "type", "isFavorite", "duration", "visibility", "originalFileName") values ($1, $2, $3, $4, $5, $6, $7, $8, $9, $10, $11, $12, $13, $14) returning *

2025-06-18 12:39:25.403 UTC [352] ERROR:  duplicate key value violates unique constraint "UQ_assets_owner_checksum"
2025-06-18 12:39:25.403 UTC [352] DETAIL:  Key ("ownerId", checksum)=(0eecf5ad-50a8-4a0d-9bfc-10d807df6191, \x0c1d9abfa236f90ccbf18a511a7faeae50dc8e42) already exists.
2025-06-18 12:39:25.403 UTC [352] STATEMENT:  insert into "assets" ("ownerId", "libraryId", "checksum", "originalPath", "deviceAssetId", "deviceId", "fileCreatedAt", "fileModifiedAt", "localDateTime", "type", "isFavorite", "duration", "visibility", "originalFileName") values ($1, $2, $3, $4, $5, $6, $7, $8, $9, $10, $11, $12, $13, $14) returning *

2025-06-18 12:39:25.403 UTC [352] ERROR:  duplicate key value violates unique constraint "UQ_assets_owner_checksum"
2025-06-18 12:39:25.403 UTC [352] DETAIL:  Key ("ownerId", checksum)=(0eecf5ad-50a8-4a0d-9bfc-10d807df6191, \x0c1d9abfa236f90ccbf18a511a7faeae50dc8e42) already exists.
2025-06-18 12:39:25.403 UTC [352] STATEMENT:  insert into "assets" ("ownerId", "libraryId", "checksum", "originalPath", "deviceAssetId", "deviceId", "fileCreatedAt", "fileModifiedAt", "localDateTime", "type", "isFavorite", "duration", "visibility", "originalFileName") values ($1, $2, $3, $4, $5, $6, $7, $8, $9, $10, $11, $12, $13, $14) returning *

Q

QuafleyOP•6/18/25, 2:52 PM

This is probably it spotting my uploads are already on the server right?

Q

QuafleyOP•6/18/25, 2:53 PM

Immich:

Q

QuafleyOP•6/18/25, 2:55 PM

This seems normal now

root@Hypnos:~# docker logs immich_postgres
Using SSD storage

PostgreSQL Database directory appears to contain a database; Skipping initialization

2025-06-18 14:54:15.155 GMT [1] LOG:  skipping missing configuration file "/var/lib/postgresql/data/postgresql.override.conf"
2025-06-18 14:54:15.157 GMT [1] LOG:  skipping missing configuration file "/var/lib/postgresql/data/postgresql.override.conf"
2025-06-18 14:54:19.896 UTC [1] LOG:  starting PostgreSQL 14.17 (Debian 14.17-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
2025-06-18 14:54:19.898 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2025-06-18 14:54:19.899 UTC [1] LOG:  listening on IPv6 address "::", port 5432
2025-06-18 14:54:19.908 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2025-06-18 14:54:19.931 UTC [42] LOG:  database system was shut down at 2025-06-18 14:53:36 UTC
2025-06-18 14:54:20.001 UTC [1] LOG:  database system is ready to accept connections

root@Hypnos:~# docker logs immich_postgres
Using SSD storage

PostgreSQL Database directory appears to contain a database; Skipping initialization

2025-06-18 14:54:15.155 GMT [1] LOG:  skipping missing configuration file "/var/lib/postgresql/data/postgresql.override.conf"
2025-06-18 14:54:15.157 GMT [1] LOG:  skipping missing configuration file "/var/lib/postgresql/data/postgresql.override.conf"
2025-06-18 14:54:19.896 UTC [1] LOG:  starting PostgreSQL 14.17 (Debian 14.17-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
2025-06-18 14:54:19.898 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2025-06-18 14:54:19.899 UTC [1] LOG:  listening on IPv6 address "::", port 5432
2025-06-18 14:54:19.908 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2025-06-18 14:54:19.931 UTC [42] LOG:  database system was shut down at 2025-06-18 14:53:36 UTC
2025-06-18 14:54:20.001 UTC [1] LOG:  database system is ready to accept connections

root@Hypnos:~# docker logs immich_postgres
Using SSD storage

PostgreSQL Database directory appears to contain a database; Skipping initialization

2025-06-18 14:54:15.155 GMT [1] LOG:  skipping missing configuration file "/var/lib/postgresql/data/postgresql.override.conf"
2025-06-18 14:54:15.157 GMT [1] LOG:  skipping missing configuration file "/var/lib/postgresql/data/postgresql.override.conf"
2025-06-18 14:54:19.896 UTC [1] LOG:  starting PostgreSQL 14.17 (Debian 14.17-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
2025-06-18 14:54:19.898 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2025-06-18 14:54:19.899 UTC [1] LOG:  listening on IPv6 address "::", port 5432
2025-06-18 14:54:19.908 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2025-06-18 14:54:19.931 UTC [42] LOG:  database system was shut down at 2025-06-18 14:53:36 UTC
2025-06-18 14:54:20.001 UTC [1] LOG:  database system is ready to accept connections

root@Hypnos:~# docker logs immich_postgres
Using SSD storage

PostgreSQL Database directory appears to contain a database; Skipping initialization

2025-06-18 14:54:15.155 GMT [1] LOG:  skipping missing configuration file "/var/lib/postgresql/data/postgresql.override.conf"
2025-06-18 14:54:15.157 GMT [1] LOG:  skipping missing configuration file "/var/lib/postgresql/data/postgresql.override.conf"
2025-06-18 14:54:19.896 UTC [1] LOG:  starting PostgreSQL 14.17 (Debian 14.17-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
2025-06-18 14:54:19.898 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2025-06-18 14:54:19.899 UTC [1] LOG:  listening on IPv6 address "::", port 5432
2025-06-18 14:54:19.908 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2025-06-18 14:54:19.931 UTC [42] LOG:  database system was shut down at 2025-06-18 14:53:36 UTC
2025-06-18 14:54:20.001 UTC [1] LOG:  database system is ready to accept connections

QQuafley This is probably it spotting my uploads are already on the server right?

A

Alex Tran•6/18/25, 2:55 PM

Correct

Q

QuafleyOP•6/18/25, 3:05 PM

Okay it's gone now. Apparently (because I so happen to have issues with 2 databases today) if you have a healthcheck setup like this:

test: ['CMD', 'pg_isready', '-U', 'root']

test: ['CMD', 'pg_isready', '-U', 'root']

test: ['CMD', 'pg_isready', '-U', 'root']

test: ['CMD', 'pg_isready', '-U', 'root'] << the way I named my default user. it will automatically search for the root database.

test: ['CMD', 'pg_isready', '-U', 'postgres', '-d', 'immich']

test: ['CMD', 'pg_isready', '-U', 'postgres', '-d', 'immich']

test: ['CMD', 'pg_isready', '-U', 'postgres', '-d', 'immich']

test: ['CMD', 'pg_isready', '-U', 'postgres', '-d', 'immich'] setting it like this would fix the issue.

Bit of an oddity really, do you recommend (whilst I'm at it now) to revert my database user back to default?

Q

QuafleyOP•6/18/25, 3:05 PM

root >> postgres

A

Alex Tran•6/18/25, 3:08 PM

up to you, if it works then maybe just leave it

Q

QuafleyOP•6/18/25, 3:10 PM

yeah, it works now so I'm happy. Thanks!

I

ImmichAPP•6/18/25, 3:10 PM

This thread has been closed. To re-open, use the button below.

Database refusing to start (out of nowhere).

References

Checklist

Information

Compose file

Similar Threads

Similar Threads

References

Checklist

Information

Compose file

Similar Threads