#Unable to run after update to 1.136.0

1 messages · Page 1 of 1 (latest)

fringe rose
#

Hi all, I have a problem to run immich after upgrading to 1.136.0. The server is keep restarting. See attached log.
Docker-compose is quiet standard one. Attaching also.
Database is not corrupted. Tested on 1.135.3:
`DB_URL=postgres://postgres:26789094@immich_postgres:5432/immich npm run migrations:generate

[email protected] migrations:generate
node ./dist/bin/migrations.js generate

No changes detected`

And this issue is probably same as https://github.com/immich-app/immich/discussions/20896

I am running on RPI4 with 8GB RAM.

Can anybody help, please?

📎 log.txt 📎 docker-compose.yml
real epochBOT
#

:wave: Hey @fringe rose,

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

#

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.

real epochBOT
real epochBOT
radiant timber
real epochBOT
radiant timber
#

@fringe rose Thanks for the outputs you posted on github!
As I spotted some specific configuration in your docker compose, I decided to discuss it here quickly / more interactively.

  1. Yesterday I overlooked the anonymous volume definition in your docker compose for Postgres:
database:
  volumes:
    - /var/lib/postgresql/data

vs Immich default

# option (a) default
database:
  volumes:
    - ${DB_DATA_LOCATION}:/var/lib/postgresql/data

# option (b) replacing the var with its value from .env
database:
  volumes:
    - ./postgres:/var/lib/postgresql/data
  1. Having anonymous volume (without lefthand part before the colon) means that each time after "docker compose down + up" there will be new empty volume created for Postgres. Old volumes are not deleted, but they are not in use too, just lingering in your file system (can be removed with docker system prune).

2.1. Quick experiment/demo: at first the volume was f5d0ec..., then I run down + up, then it becomes 52d1ec...

docker inspect --format '{{ json .Mounts }}' immich_postgres
[{"Type":"volume","Name":"f5d0ec...","Source":"/var/lib/docker/volumes/f5d0ec.../_data","Destination":"/var/lib/postgresql/data",...}]

dcompose down && dcompose up -d

docker inspect --format '{{ json .Mounts }}' immich_postgres
[{"Type":"volume","Name":"52d1ec...","Source":"/var/lib/docker/volumes/52d1ec.../_data","Destination":"/var/lib/postgresql/data",...}]
  1. Accidental destroy may happen upon running "compose down + up" (as I adviced, sorry). Also it will happen after possible change of Postgres image in the future.
    To avoid that I suggest to change the volume definition: follow Immich example, use either option (a) or option (b).
radiant timber
#

Another question: do you have by any chance DB_SKIP_MIGRATIONS defined in .env? Could you post your .env?

radiant timber