Update from 1.2 -> latest not allowing immich to start anymore
Hi,
I recently updated from 1.12 (ish, can't remember the exact version) by just running the docker pull command to get latest release, however immich-server container failed to start. Upon looking at the docker instance it was failing due to TypeORM error and it said to follow this: https://docs.immich.app/errors/#typeorm-upgrade
I changed my version to 1.32.3 to handle the above error, but my whole VPS becomes unresponsive causing a need to force a hard reboot. I'm not sure where I can check logs to see what immich is trying to do that's causing this issue.
6 Replies
:wave: Hey @bulletsquid,
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. :blue_square: 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..env
Just tried again and ran a top command to see, and looks like kswap was using almost all the cpu. Not sure whats causing kswap to be used though by immich
Reverting back to 1.120 seems to make things happy. Would like to update to latest though.
You need to follow the breaking changes along the way
Your VPS probably cant handle the IOPS for the database upgrade
It seems to have happened again even with the original version. I will try following the breaking changes, but I feel like something else may be happening causing immich to hog all the resources.
kswapVM is choking on memory -> swapping. During start-up upon upgrade Immich will use more memory than usual, this is expected. It needs to load geolocation info, for example, or reindex data in the database.