Switching from "release" to "main" version
Hi everyone.
Last night I asked Google Gemini (Big mistake, now I know!) for help to resolve an apparent incompatibility with the rocm driver on my immich_machine_learning server. Among other things, the Al had me try the "main" development version instead of the classic "release" version, which I've always used with great satisfaction. The room incompatibility persisted (but I'm getting over it), but when I tried to revert to the "release" version, the immich_server container kept restarting, and the log reported:
Gemini, after having me unsuccessfully search for the DB log entry, said that switching to main probably changed the DB table names: leaving the version on "main" restarts the container without any problems. Is there a way to restore proper "release" functionality? I don't really like the idea of having a "development" version on the server. Unfortunately, I also just realized that the script that performs my daily media and DB dump backups had an error and was generating a 0 KB SQL file, and the only valid backup is now seven months old... damn me!
My Immich instance runs on Docker in a Debian 12 VM on Proxmox.
Any ideas without having to reset the DB (or stay in "main")? Thanks in advance...
4 Replies
:wave: Hey @tgalex75#2020,
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.Didn't you ask this before already?
Not here in Discord. A Reddit user suggested I ask here for help.
Without backups, we would recommend to wait for 2.3.0
You probably could manually un migrate, but I doubt anyone here will help with that, pretty risky