45 Replies
:wave: Hey @dipper998,
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. :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.Successfully submitted, a tag has been added to inform contributors. :white_check_mark:
I'm not sure how this happened, it was just kinda out of nowhere - immich_server randomly kept restarting a few days ago and yesterday it just wouldn't start at all.
It can't reach your postgres container
Start by compose down + up, if that does nothing, check your postgres logs in
DB_DATA_LOCATION/logI wonder... where did you get this compose file?
Looks pretty tame apart from switching out to PG16 and a pgadmin container?
yeah, but I believe first time should try the documented procedure then start making changes. imho
Apologies for the late reply - been at work
This isn't my first launch, I've had Immich up and running fine for over a year now
I'll just grab the postgres logs
I've also restarted the stack multiple times to no avail
here's the last two logs from /log
What are you hosting on @dipper998?
Custom little PC based on a HP Prodesk Mini
i7 9500t, 16GB RAM, 500GB SSD
No I mean what OS 😛
to be clear: I'm not using anything like unraid or truenas, just docker on Ubuntu
realised that just now 😅
can you
docker exec -it immich_postgres psql -U postgres ?I tried that, then with the db username in my .env
You need the -d immich for immichuser
I said -d immich :p also -U immichuser
docker exec -it immich_postgres psql -U immichuser -d immich
-U for user and -d for databaseah apologies i see what you mean now
yep I'm in now
I can type after the hashtag
alright so the database is there and the container stays up
just
exit now :p
next potential culprit: apparmor suddenly turning hostile
Not sure where the logs for apparmor are because I don't use it, but check out /var/log/apparmor probablyis that in the db container?
No on your host
I don't have an apparmor folder in /var/log on the host
sudo aa-status to check whether you have it at all :pAh it's in
/var/log/audit/audit.log
try grep -ni /var/log/audit/audit.log -e DENIED | tail for instanceI don't have a /var/log/audit folder
grep: /var/log/audit/audit.log: No such file or directoryuh, sudo it?
ah wait you're root nvm
I already
sudo -s at the beginningYou can try (temporarily) disabling it to rule it out as the culprit:
systemctl stop apparmor
Then compose down+upstill errors unfortunately
curious curious...
Not running any other containers are you?
I do have a bunch of other containers besides immich yes
I haven't created any new ones in the past few days though
docker ps --format 'table{{.Names}}\t{{.Ports}}' just to make sureCould you try shutting down the listmonk one to make sure it's not interfering?
(and compose updown left right etc )
yeah sure
oh my word that was it
Alright so we're halfway there now
Are you using a big compose or separate ones? I"m assuming separate but just making sure
halfway? I can access my instance now and there's no more error in the server logs anymore
Yeah but I imagine you'd like the use the listmonk thing
I can leave it for now don't worry it's not a big deal
thank you for your help
Immich has an env for specifying a database port, you could change it on our side or on the listmonk side if they support that
yeah I will do now that I know what the issue is