#Missing /var/lib/postgresql/
31 messages · Page 1 of 1 (latest)
:wave: Hey @sudden heath,
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
.
References
- Container Logs:
docker compose logsdocs - Container Status:
docker ps -adocs - 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...
- :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).
- :ballot_box_with_check: 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 -landdf -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.
Successfully submitted, a tag has been added to inform contributors. :white_check_mark:
We need the logs
how do i get a log file? i can only find live ones for the terminal
docker logs immich_postgres
its repeating
Using SSD storage
chmod: changing permissions of '/var/lib/postgresql/data': Permission denied
find: ‘/var/lib/postgresql/data’: Permission denied
chown: changing ownership of '/var/lib/postgresql/data': Permission denied
What filesystem are you using? And OS?
hdd which i have now changed. on Fedora Workstation
ext4
thats what i thought. know how to fix it?
Not sure, I don’t use fedora sorry
dang ok
in docker-compose.yml should it be default ssd or should it be hdd?
i believe i have hdd but it didnt seem to be the problem
For selinux add :Z to the mount paths in the yml
try addind :Z at the end of this line ${DB_DATA_LOCATION}:/var/lib/postgresql/data
i have tried that, but now it acts like its the first time and i have to setup admin
That means your database was stored elsewhere prior, which explains why you didn’t get this error
Please, can you tell how did you figured out? I have exactly same problem, now I need to locate old v2 postgres but I have no idea where to find it.
Here are my old env (v2) and yml and new one (v3). All works except I do not have data from previous version of Immich. Fedora Linux 43 (Workstation Edition) with Selinux. Please, help me locate and migrate old postgres to new version. Thanks.
you DB is in pgdata docker volume. just restore a backup on your new instance.
I found old pgdata and set DB_DATA_LOCATION in variables to /var/lib/docker/volumes/immich_pgdata/_data with - ${DB_DATA_LOCATION}:/var/lib/postgresql/data:Z in yml and it looks like everything is restored. Thanks!
the moment you do a cleanup your DB will be dead. don't mount the docker volume filesystem, use an external volume instead, or better, just point to an actual location managed by you
so I should copy DB to another location and then point in variable to it?
You can do it that way if you like to play around, otherwise I'd recommend doing a backup/restore cycle. It's fast and you can be sure the new location is clean.