Problems after image upgrade
Hi all, as i wrote here https://github.com/immich-app/immich/pull/19673#issuecomment-3122892075 i do not know how to solve this problem due to the fact that i cannot connect to server container (error /bin/bash: start.sh: No such file or directory reported on logs).
After some reading on above link seems to be that move the file (start.sh) to the right position not only is not a solution, but it is impossible to do because i am unable to connect to server as i said before.
So i get a good suggestion from danieldietzler on github (i am LordRouter there) to came here hoping to find a way to solve without lose any data on my immich server.
On above link there is my docker-compose.yml and env file, do i repost it here?
The only thing Logs says is what i wrote above: error /bin/bash: start.sh: No such file or directory
(i've upgraded from 135)
Any help is appreciated,
Thanks to all
21 Replies
:wave: Hey @Keedera,
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
[Pull Request] chore: dockerfile layout changes (immich-app/immich#19673)
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 can't paste other container logs because discord gets them as .txt even if i put they here as
code ...That's not a problem, it'll still be formatted nicely :)
ok i try to do so, thanks
immich postgres (above)
immich machine learning (above)
immich server (above)
Please run the following:
Please share the output of these commands
immich runs on docker, managed it via portainer. Host machine is a Mini pc intel with ubuntu 22.04
i do all via portainer, anyway docker compose down output this
docker image prune -a
docker compose up -d
Idk with portainer but you need to bring down the stack and purge all the images to force re download
i do this every time i upgrade an image
you should do it again because its possible the first download got corrupted
Should I do this by updating the stack or one stack image at a time?
Personally when updating apps with portainer, I'll delete the containers, go to the images page and delete the (now) unused images, then go to the stack and just click deploy
Unless stated, I only delete the Immich-server and immich-machine-learning. I leave postgres and redis alone unless a change is explicitly needed per the release notes
for me the working and simpliest way is to go into container and click "recreate" button with flag re-deploy image
for every images that needs upgrade
this time anyway the stange thing is that there is a file missing (start.sh)
upgrading to 135 was to add this flag
shared_preload_libraries=vectors.so, vchord.so on command section of docker compose...
after that i learned to read breaking changes BEFORE upgrade, thing that i do this time and reading them it seemed like it should work right away but it's not true.Pretty sure with 135 update a breaking change was to remove the database healthcheck and command, wasn't it?
yes, it is
*133
Maybe. I only noticed after a couple of version updates because it made me repeat the installation as the first user (which I obviously never did, preferring to solve the problem). Once I understood, I had no more problems.
until today....
which is the correct pull command for the latest (136) immich-server image? I ask this because the actual image is v1.135.3 even trying to repull from portainer
if using portainer still I would just update the stack: Delete container (server, machine-learning) and images, double check the compose matches similarly to the official one, sparing any specific volume mounts you've set up, then deploy again.
You could also test before that that your database is functioning correctly by going through the backup step in https://immich.app/docs/administration/backup-and-restore/
OMG! Now it works! I've done the same things today 2 times and getting errors. Now it works....!!!
Thanks for ur support @CJPeckover
Happy to help!
make sure you've got accessible backups (db, pictures) just in case 🙂