Microservices fail to run
Greetings, I'm trying to set up Immich as a docker compose on my server, In the next posts I will post the contents of my docker compose and env file.
Do you know how to solve?
Thanks in advance,
44 Replies
:wave: Hey @Xargon,
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.Container logs:
docker-compose-immich.yml
.env-immich
Probably the permissions on the photo folder aren't accepting of changes
This is a database issue, it can't reach postgres
So how can I solve or troubleshoot it?
I tried to enter in the immich container to check if they can see eachothers but there is no ping nor nc.
As you can see the docker compose is almost vanilla without big modifications so I wonder why is not reachable.
Check the database logs to start
you can install iputils-ping inside the container.
also, inspect the server container and verify the env is correctly set
also the server keep restarting, hard to troubleshoot
I tried to touch a file in with user (non root) and I can write in it, also I got space on the disk
Like it says, the logs are on disk
set entrypoint to sh and tty: true
Which one is useful? most are empty
And yes, env is correct
did you run update first ?
at least, the things that I defined are defined
ok, they seems to be rachable:
try this to check if the DB is working
but to me it looks something is miss configured on the server side
Yes, the query returned a schema
try setting the env
not sure if it will be useful tho, I don't know how much is logged on startup
Hmm not very useful, yeah:
can you go to the postgres folder and run
ls -a?
Should be in here DB_DATA_LOCATION=./postgresit should have something like this
then in the
log directory, you should see this
My /mnt folder is empty in me immich_server container
That isn't in the server container
Can you locate where the
docker-compose.yml file is at?
there should be a postgres folder there as wellAh ok sorry now I understood: I missed that there was a ./postgres mount point in the env, ok yes, I found the folder and I got data inside, 27 items @bo0tzz @Alex
Can you get the content of the two latest log?
previous:
I run docker with sudo (because old configs on my server, when I will migrate I will fix it) and the posgtres folder is now a+wrx
however not yet running
Looks good, I don’t see any error in the logs
immich_server is not producing logs
Could it be PUID and PGID issue
Or have you changed password of the database recently?
Well technically yes as it's a new deploy (first time) and I changed it, but probably postgres came up with the default password once
I don't care deleting all the data as I never reached the Immich screen yet
(just not the mounted picture folder)
I am leaning toward permission issue with group and user ID
can I add it to the env?
You have it in your env
By default we run the database as root
Ah yes
I try
YES!
I can see the webpage now, thanks a lot, was definitely that
Nice!
Thanks for your support, really 🙂
I thought we made changes so that the log was more useful
@bwees do you know if the correct changes to the database log is in the latest release?
it should have, unless our post install patching step isnt working on the release. I will look tomorrow morning and see. I think our check might be always returning false (and causing the script to not run). Should be able to remedy this by backing out of the server directory before installing the immich cli on the image build
It still ran on my machine after we fixed the POSIX issue but maybe somethign weird is happening in the build
Sounds good! Thanks Brandon
There is still a broken thing, I messaged in #dev about it, let me dig that back up
Yeah I know that when the patch gets applied successfully that it does fix this issue. I think our dockerfile and the check to see if we should run post install step is preventing that step from being run. I will make a pr today to change the way Immich cli gets installed
did you see the message I referenced? It seems like there's another case of a field missing, that isn't covered by the patch
ah i understand now, ok I will also look at that and add a check to safeguard if any of the fields are missing and if so, fall back to a normal throw
im getting this too on a truenas nfs mount
fresh install of only .env and docker_compose.yml, running sudo docker compose up spams this error...
just waiting somehow fixes it? idk