immich_server stuck in starting state after upgrading to latest version
[Nest] 17 - 01/09/2025, 2:05:55 PM ERROR [TypeOrmModule] Unable to connect to the database. Retrying (7)...
21 Replies
:wave: Hey @HelloIN,
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. :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.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
GNU nano 7.2 .env
UPLOAD_LOCATION=/mnt/share/server/pics/ IMMICH_VERSION=release DB_PASSWORD=** DB_HOSTNAME=immich_postgres DB_USERNAME=postgres DB_DATABASE_NAME=immich REDIS_HOSTNAME=immich_redis
UPLOAD_LOCATION=/mnt/share/server/pics/ IMMICH_VERSION=release DB_PASSWORD=** DB_HOSTNAME=immich_postgres DB_USERNAME=postgres DB_DATABASE_NAME=immich REDIS_HOSTNAME=immich_redis

Please post the logs of the postgres container too
"No space left on device"
Seems pretty clear to me @HelloIN
cleaned up space on my proxmox and re-deployed the immich server, still same issue
Please show me
df -hT
oot@prox:~# df -hT
Filesystem Type Size Used Avail Use% Mounted on
udev devtmpfs 7.8G 0 7.8G 0% /dev
tmpfs tmpfs 1.6G 1.2M 1.6G 1% /run
/dev/mapper/pve-root ext4 65G 6.1G 55G 10% /
tmpfs tmpfs 7.8G 43M 7.8G 1% /dev/shm
tmpfs tmpfs 5.0M 0 5.0M 0% /run/lock
/dev/sda2 vfat 1022M 348K 1022M 1% /boot/efi
/dev/fuse fuse 128M 20K 128M 1% /etc/pve
tmpfs tmpfs 1.6G 0 1.6G 0% /run/user/0
i have two vms in my proxmox, one truenas and other debian
i have created mnt storage on truenas and i point it to immich server hosted inside debian vm on docker
You need to
df -hT
inside the debian VMy@debian:~$ df -hT
Filesystem Type Size Used Avail Use% Mounted on
udev devtmpfs 7.8G 0 7.8G 0% /dev
tmpfs tmpfs 1.6G 1.5M 1.6G 1% /run
/dev/sda1 ext4 31G 30G 0 100% /
tmpfs tmpfs 7.9G 0 7.9G 0% /dev/shm
tmpfs tmpfs 5.0M 0 5.0M 0% /run/lock
//192.168.0.101/share cifs 7.2T 206G 7.0T 3% /mnt/share
tmpfs tmpfs 1.6G 52K 1.6G 1% /run/user/1000
sda1 is the issue
Your root partition is full
You’ll need to fix that
umm how to free up space, i only have some docker containers installed on this vm
Sorry this is beyond an immich issue
docker image prune
probably will free up some space there if you never did thatYou’ll have to research how to grow partitions on proxmox. It’s possible but not that straightforward
30G is pretty small for multiple docker containers tbh
wow
Total reclaimed space: 15.86GB
You should do that after every upgrade btw
(or provide enough space to start with)