Immich v1.123.0 stuck initializing
Hello!
I just upgraded immich to the newest version but it doesn't seem to be working.
I review the docker-compose file and start it. All images seem to be starting normally but immich server. All I see is the following in the logs all over again:
Initializing Immich v1.123.0
Detected CPU Cores: 16
Initializing Immich v1.123.0
Detected CPU Cores: 16
Initializing Immich v1.123.0
Detected CPU Cores: 16
Initializing Immich v1.123.0
Detected CPU Cores: 16
...
20 Replies
:wave: Hey @stardust,
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_01GY0DAKGXDEHE263BCAYEGFJAChecklist
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.GitHub
immich-app immich · Discussions
Explore the GitHub Discussions forum for immich-app immich. Discuss code, ask questions & collaborate with the developer community.
FAQ | Immich
User
GitHub
Issues · immich-app/immich
High performance self-hosted photo and video management solution. - Issues · immich-app/immich
Successfully submitted, a tag has been added to inform contributors. :white_check_mark:
Please post the info the bot asked for
I'm using a stack in Portainer, so I'll try to find another way.
Let me know if you need further details
Can you get the actual database logs from the postgres log folder?
Here's the last log I could find
Can you set
IMMICH_LOG_LEVEL=verbose and recreate the container?Sure, will do
Not much difference I'm afraid
Any memory limits?
I haven't set any. It's running in a VM with 8GB of RAM. I don't see any issue with the space either.
Never had problems with memory before.
It’s a VM not a LXC? What’s the host and guest os? Looks like Ubuntu in the guest
Ubuntu server in TrueNAS.
What version did you upgrade from?
From 1.122.2
Please do docker compose down; docker image prune -a
Likely the image got corrupted on download
That was it! Thanks for your help.
Might want to keep an eye out for why that happened if you notice other corruption