Immich_server always restarting
My setup (Ubuntu 24 on MacMini 2014) keeps failing on Immich startup - gets a error;
severity_local: 'ERROR',
severity: 'ERROR',
code: 'XX000',
file: 'multixact.c',
line: '1305',
routine: 'GetMultiXactIdMembers'
Then: api worker exited with code 1
Followed by restart.
20 Replies
:wave: Hey @rustang46,
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.I've tried the approach of changing the port number from 2283 to 224 in the yml file, same result.
here is an example of the sudo lsof querry:
Each attempt of the server to restart increments up both PID's.
I also turned off the IPv6 in the system settings.
But still see both Types of processes - not sure if this is the problem or not.
I get errors in trying to shut down the Docker containers - permission errors.
Completely stuck - no idea on what is going on here, or how to clear error.
I am a newbie, and trying to figure this out without experience has been frustrating.
Appreciate detailed advice on how to resolve.
From server lots: Failure
Failed starting container: failed to set up container networking: driver failed programming external connectivity on endpoint immich_server (b72b2a303befef5e7a33d15072f678e916ec9ba996e7bceee58ed50266b00f39): failed to bind host port for 0.0.0.0:2283:172.18.0.4:2283/tcp: address already in use Looks like it is still looking for port 2283 even though I set up yml file for 2284. restarting system to see if that fixes the issue. Restart did not help. sure looks like somewhere I have another immich container running, but no idea where to look.
Failed starting container: failed to set up container networking: driver failed programming external connectivity on endpoint immich_server (b72b2a303befef5e7a33d15072f678e916ec9ba996e7bceee58ed50266b00f39): failed to bind host port for 0.0.0.0:2283:172.18.0.4:2283/tcp: address already in use Looks like it is still looking for port 2283 even though I set up yml file for 2284. restarting system to see if that fixes the issue. Restart did not help. sure looks like somewhere I have another immich container running, but no idea where to look.
getting errors on postgres database as well:
just a sample of the errors.
Your database is corrupted
You'll want to restore a backup
I have no backup - just getting started and had very few images included.
What is best way to do a clean install?
apparently I don't have correct permissions...
even using sudo docker compose down -v does not allow me to remove Immich.
Further in the help menu, I did a database integrity check. It passed checksums and corruption checks, but failed the check for structure errors.
I think we already determined the DB is corrupted, and you need to start over
If you don’t have backups
what is most efficient way to remove existing DB and do a clean install? Especially since I dont' seem to know how to remove the corrupted database.
You would delete the contents of the database folder, which is specified in your .env file
The link I sent explains all this
boOtzz - thanks - I see this now. But I still have no permissions to do a docker compose down or through portainer to stop / remove volumes.
How do I get permissions to do this?