immich-server:v2 keeps restarting.
Went to the github, got the docker-compose.yml and the example.env files(renamed for just .env), upgraded as instructions on immich website after not finding any breaking changes on change log. Now immich-server:v2 just keeps restarting and its never up.
36 Replies
:wave: Hey @rafael_ms,
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.the logs, compose file and envelople used
i made a small mistake of overlooking the HDD line on the first try, but then i fixed it and upgraded
Its a Ryzen 4600G running on a 2TB HDD
Docker PS:
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
b81a2bfc4e29 ghcr.io/immich-app/postgres:14-vectorchord0.4.3-pgvectors0.2.0 "/usr/local/bin/immi…" 15 minutes ago Up 14 minutes (healthy) 5432/tcp immich_postgres
0f2531247d58 ghcr.io/immich-app/immich-server:v2 "tini -- /bin/bash -…" 23 minutes ago Restarting (1) 37 seconds ago immich_server
3bda5a950bbb ghcr.io/immich-app/immich-machine-learning:v2 "tini -- python -m i…" 23 minutes ago Up 23 minutes (healthy) immich_machine_learning
ab6c5633bb8f valkey/valkey:8 "docker-entrypoint.s…" 23 minutes ago Up 23 minutes (healthy) 6379/tcp immich_redis
fdisk -l:
Disk /dev/sda: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: WDC WD20EZAZ-00L
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: A0E7CA68-A4AC-4095-A836-9BEEDD41BAAB
Device Start End Sectors Size Type
/dev/sda1 2048 2203647 2201600 1G EFI System
/dev/sda2 2203648 3907026943 3904823296 1.8T Linux filesystem
The issue is there in the logs. Something changed in your connection to postgres and the password is wrong. You will need to either figure out what happened or update the postgres password and the matching password in your env
i have kept ye old files from 2.1.0 upgrade
will it help?
Did you change anything in your env at all?
no, i downloaded the example.env, renamed it to .env and did the compose pull and up
I mean that would do it. You need your old password for postgres you originally setup
huh, I see
do i set it in ,env or compose file?
shuhbacca is saying you deleted your old password and unless you have a backup for it, you're pretty much boned
UUUUUU
i have it
i have the old env files and i know the password!
Okay so change the DB_PASSWORD back to the old one
should i change in the new env file and run upgrade again
will try now
And please don't ever re-download the env file
just a sec
That is very much not how to upgrade
this is a sigh of relief
Did you read anywhere that you had to do this?
The example.env is only for fresh installs
had no idea, thought better to do it due to the change to "=v2"
No what you did amounts to a full settings reset
It's a good thing you kept the old files
so, its better to just put the old .env file back in place?
Only the
docker-compose.yml should be changed, and even that should be done carefully not just blind copy/paste
No, unless you have other changes in there?the old .env is "immich_version=lastest" and the new is "immich_version=v2"
This is why i though i needed the new one
You can change that one line
ok...
In any case, don't change anything in either file unless you understand what it does
You're always welcome to come and ask
so, now i use the .env i sent here(the new one), put in the old database passwork and upgrade again.
is that a valid course of action?
i'm thankful
Yes just setting back the old password should fix it
docker compose up -dok no need to pull this time then?
i'll just double check the file
No the images are already downloaded
pull = download to docker image library
compose up = create the containers with the config
or apply the new config, if already created
great!
its running again
Thank you guys, worked like a charm.
should i close this topic now?
Unless you have other questions
it's simply /close
It was the first time i downloaded a new docker-compose too 😆 always changed by hand before, will keep doing that.
This thread has been closed. To re-open, use the button below.