I
Immich•3mo ago
Keedera

Hi all,

Update from 137.3 to 138.0, this time checking all the news and breaking changes before applying the update and all seems to be good to go to apply this update. So, after the update i'll get this error: home page ask me to start as a new user. I've often solved this error, changing docker-compose.yml a little bit (following instructions to do so from here and github users discussions) with portainer editor. Now, there are two different things i can see from my docker-compose and the new docker-compose, the first is this two lines after $DB_DATA_LOCATION line 
shm_size: 128mb
    restart: always
shm_size: 128mb
    restart: always
and the 2nd is the lines below that are present on my docker-compose.yml and not present to the new docker-compose.yml: 
'healthcheck:
      test: pg_isready --dbname='${DB_DATABASE_NAME}' --username='${DB_USERNAME}' || exit 1; Chksum="$$(psql --dbname='${DB_DATABASE_NAME}' --username='${DB_USERNAME}' --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, vchord.so", "-c", 'search_path="$$user", public, vectors', "-c", "logging_collector=on", "-c", "max_wal_size=2GB", "-c", "shared_buffers=512MB", "-c", "wal_compression=on"]
'healthcheck:
      test: pg_isready --dbname='${DB_DATABASE_NAME}' --username='${DB_USERNAME}' || exit 1; Chksum="$$(psql --dbname='${DB_DATABASE_NAME}' --username='${DB_USERNAME}' --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, vchord.so", "-c", 'search_path="$$user", public, vectors', "-c", "logging_collector=on", "-c", "max_wal_size=2GB", "-c", "shared_buffers=512MB", "-c", "wal_compression=on"]
so, i want to ask you guys if that lines matter on immich behaviour like i said above (it asks to create new user) and how to solve this time, any help is really appreciated. My docker compose can be found Here My .env is attached here. Host: Minis Forum Z83-F OS: ubuntu 22.04 Portainer: 2.27.9 LTS Immich: 138.0
No description
6 Replies
Immich
Immich•3mo ago
:wave: Hey @Keedera, 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 docs - Container Status: 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 Checklist I have... 1. :ballot_box_with_check: verified I'm on the latest release(note that mobile app releases may take some time). 2. :ballot_box_with_check: read applicable release notes. 3. :ballot_box_with_check: reviewed the FAQs for known issues. 4. :ballot_box_with_check: reviewed Github for known issues. 5. :ballot_box_with_check: tried accessing Immich via local ip (without a custom reverse proxy). 6. :ballot_box_with_check: uploaded the relevant information (see below). 7. :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 and 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 command, and re-open it later if needed. [Pull Request] chore: dockerfile layout changes (immich-app/immich#19673)
Keedera
KeederaOP•3mo ago
Immich_postgres 
Using SSD storage

PostgreSQL Database directory appears to contain a database; Skipping initialization

2025-07-27 00:45:39.601 UTC [1] LOG:  redirecting log output to logging collector process

2025-07-27 00:45:39.601 UTC [1] HINT:  Future log output will appear in directory "log".

Using SSD storage

PostgreSQL Database directory appears to contain a database; Skipping initialization

2025-08-03 15:39:11.247 UTC [1] LOG:  redirecting log output to logging collector process

2025-08-03 15:39:11.247 UTC [1] HINT:  Future log output will appear in directory "log".

2025-08-04 00:00:00.027 UTC [31] LOG:  could not open log file "log/postgresql-2025-08-04_000000.log": Input/output error

2025-08-04 00:00:00.027 UTC [31] LOG:  disabling automatic rotation (use SIGHUP to re-enable)

Using SSD storage

PostgreSQL Database directory appears to contain a database; Skipping initialization

2025-08-05 23:13:10.385 UTC [1] LOG:  redirecting log output to logging collector process

2025-08-05 23:13:10.385 UTC [1] HINT:  Future log output will appear in directory "log".

Using SSD storage

PostgreSQL Database directory appears to contain a database; Skipping initialization

2025-08-17 14:09:45.505 UTC [1] LOG:  redirecting log output to logging collector process

2025-08-17 14:09:45.505 UTC [1] HINT:  Future log output will appear in directory "log".
Using SSD storage

PostgreSQL Database directory appears to contain a database; Skipping initialization

2025-07-27 00:45:39.601 UTC [1] LOG:  redirecting log output to logging collector process

2025-07-27 00:45:39.601 UTC [1] HINT:  Future log output will appear in directory "log".

Using SSD storage

PostgreSQL Database directory appears to contain a database; Skipping initialization

2025-08-03 15:39:11.247 UTC [1] LOG:  redirecting log output to logging collector process

2025-08-03 15:39:11.247 UTC [1] HINT:  Future log output will appear in directory "log".

2025-08-04 00:00:00.027 UTC [31] LOG:  could not open log file "log/postgresql-2025-08-04_000000.log": Input/output error

2025-08-04 00:00:00.027 UTC [31] LOG:  disabling automatic rotation (use SIGHUP to re-enable)

Using SSD storage

PostgreSQL Database directory appears to contain a database; Skipping initialization

2025-08-05 23:13:10.385 UTC [1] LOG:  redirecting log output to logging collector process

2025-08-05 23:13:10.385 UTC [1] HINT:  Future log output will appear in directory "log".

Using SSD storage

PostgreSQL Database directory appears to contain a database; Skipping initialization

2025-08-17 14:09:45.505 UTC [1] LOG:  redirecting log output to logging collector process

2025-08-17 14:09:45.505 UTC [1] HINT:  Future log output will appear in directory "log".
Keedera
KeederaOP•3mo ago
Immich-machine-learning
[08/17/25 14:11:53] INFO     Starting gunicorn 23.0.0                           

[08/17/25 14:11:53] INFO     Listening at: http://[::]:3003 (8)                 

[08/17/25 14:11:53] INFO     Using worker: immich_ml.config.CustomUvicornWorker 

[08/17/25 14:11:53] INFO     Booting worker with pid: 9                         

[08/17/25 14:12:11] INFO     Started server process [9]                         

[08/17/25 14:12:11] INFO     Waiting for application startup.                   

[08/17/25 14:12:11] INFO     Created in-memory cache with unloading after 300s  

                             of inactivity.                                     

[08/17/25 14:12:11] INFO     Initialized request thread pool with 4 threads.    

[08/17/25 14:12:11] INFO     Application startup complete. 
[08/17/25 14:11:53] INFO     Starting gunicorn 23.0.0                           

[08/17/25 14:11:53] INFO     Listening at: http://[::]:3003 (8)                 

[08/17/25 14:11:53] INFO     Using worker: immich_ml.config.CustomUvicornWorker 

[08/17/25 14:11:53] INFO     Booting worker with pid: 9                         

[08/17/25 14:12:11] INFO     Started server process [9]                         

[08/17/25 14:12:11] INFO     Waiting for application startup.                   

[08/17/25 14:12:11] INFO     Created in-memory cache with unloading after 300s  

                             of inactivity.                                     

[08/17/25 14:12:11] INFO     Initialized request thread pool with 4 threads.    

[08/17/25 14:12:11] INFO     Application startup complete.

immich-redis.txt

Keedera
KeederaOP•3mo ago
Immich
Immich•3mo ago
Successfully submitted, a tag has been added to inform contributors. :white_check_mark:
Keedera
KeederaOP•3mo ago
steps i do when update: 
The only thing i do when upgrading images from portainer is:

    go to stacks
    select immich
    then click to immich-server (or pg,ml and so on)
    then click "recreate" and re-pull image
The only thing i do when upgrading images from portainer is:

    go to stacks
    select immich
    then click to immich-server (or pg,ml and so on)
    then click "recreate" and re-pull image
this works every time, not this one anyway. i've clicked submit on something that i've not read (maybe checklist)), thinking that was a simple confirm for send message, sorry. i close this because solved, a simple reboot do the things. Thank you all anyway.

Did you find this page helpful?