I
Immich•4w ago
QuickishFM

database location missing after update

Hi folks, I recently updated my immich install as usual using docker compose pull, but first redownloaded the docker-compose and env files seeing as there were some breaking changes (it was a while since my last update). Now though it seems it doesn't launch 
~/immich$ docker compose up -d
WARN[0000] The "DB_DATA_LOCATION" variable is not set. Defaulting to a blank string. 
invalid spec: :/var/lib/postgresql/data: empty section between colons
~/immich$ docker compose up -d
WARN[0000] The "DB_DATA_LOCATION" variable is not set. Defaulting to a blank string. 
invalid spec: :/var/lib/postgresql/data: empty section between colons
So I set the DB_DATA_LOCATION to a folder on my PC, and running it again generated the folder but when I open Immich it's as if i'm a new user. How exactly do I connect it to the "old" database? I do take database backups on a schedule so nothing is terribly lost but I don't want to have to restore if I already have the existing database files somewhere that aren't being used. I'm thinking I didn't properly upgrade or something, and I'm not sure how to continue. Any help would be really appreciated. I'm using Arch Linux with docker compose.
4 Replies
Immich
Immich•4w ago
:wave: Hey @QuickishFM, 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. :blue_square: verified I'm on the latest release(note that mobile app releases may take some time). 2. :blue_square: read applicable release notes. 3. :blue_square: reviewed the FAQs for known issues. 4. :blue_square: reviewed Github for known issues. 5. :blue_square: tried accessing Immich via local ip (without a custom reverse proxy). 6. :blue_square: uploaded the relevant information (see below). 7. :blue_square: 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.
QuickishFM
QuickishFMOP•4w ago
Ok I saw some other folks posts and i dug into my backups. I think this caused it - the diff between new vs old. 
@@ -65,10 +61,9 @@ services:
       # Uncomment the DB_STORAGE_TYPE: 'HDD' var if your database isn't stored on SSDs
       DB_STORAGE_TYPE: 'HDD'
     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
-    shm_size: 128mb
+      - pgdata:/var/lib/postgresql/data
     restart: always
 
 volumes:
+  pgdata:
   model-cache:
@@ -65,10 +61,9 @@ services:
       # Uncomment the DB_STORAGE_TYPE: 'HDD' var if your database isn't stored on SSDs
       DB_STORAGE_TYPE: 'HDD'
     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
-    shm_size: 128mb
+      - pgdata:/var/lib/postgresql/data
     restart: always
 
 volumes:
+  pgdata:
   model-cache:
But if the "new" style is to use DB_DATA_LOCATION and not use pgdata volume, how am I supposed to fix that (or properly migrate to using this new scheme). Do I even need to..? I see at least 2 people fixed it after reverting the change but I'm hesitant to not follow the current example env and docker compose yml files. Was there a guide or post about this I missed? Edit: Reverted the change and my Immich is back to normal! Still not sure if I should leave this pgdata as it is though.
bo0tzz
bo0tzz•4w ago
You should read the release notes before you upgrade
Immich
Immich•4w ago

Did you find this page helpful?