#No thumbnail generation after upgrading from 1.106.4 to 1.111.0

1 messages · Page 1 of 1 (latest)

somber seal
#

I was busy with work for a while and let my server and phone app versions get out of sync. I got that fixed, and now I am having issues with thumbnail generation. If I try to manually start a thumbnail generation job, I have to click on the button a random number of times (sometimes up to 20) to get it to start. Once it starts, it generates perhaps 8-20 thumbnails then just stops with no log errors I can discern as having caused the termination. Really perplexing. This is browser agnostic and the files themselves are not corrupt since I can download them and view them fine. All JPGs from a Pixel 7 Pro. My Docker Compose file is basically identical to the posted file minus some additions for my Traefik setup.

eternal boughBOT
#

:wave: Hey @somber seal,

Thanks for reaching out to us. Please follow the recommended actions below; this will help us be more effective in our support effort and leave more time for building Immich immich.

References

Checklist

  1. :blue_square: I have verified I'm on the latest release(note that mobile app releases may take some time).
  2. :blue_square: I have read applicable release notes.
  3. :blue_square: I have reviewed the FAQs for known issues.
  4. :blue_square: I have reviewed Github for known issues.
  5. :blue_square: I have tried accessing Immich via local ip (without a custom reverse proxy).
  6. :blue_square: I have uploaded the relevant logs, docker compose, and .env files, making sure to use code formatting.
  7. :blue_square: I have 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)

If this ticket can be closed you can use the /close command, and re-open it later if needed.

torn cloak
#

Please post your full compose and env

#

Saying it is “same as posted” isn’t enough

#

Also post the immich_server logs

somber seal
#

I'm working it 🙂 It just takes a second.

#

This is a bit embarassing. Discord won't let me dump the .yml and .env files in here directly. Is there a recommended way to get them attached? Do I need to self-host somewhere and post a link?

torn cloak
#

You can just post the text no?

#

Use a code block

somber seal
#

I guess the default compose file is too long for the 2000 character limit... let me see if I can self host this stuff.

#

ENV file ` # You can find documentation for all the supported env variables at https://immich.app/docs/install/environment-variables

The location where your uploaded files are stored

UPLOAD_LOCATION=/home/norad/noradshare/Photos/Immich

The Immich version to use. You can pin this to a specific version like "v1.71.0"

IMMICH_VERSION=release

Connection secret for postgres. You should change it to a random password

DB_PASSWORD=postgres

The values below this line do not need to be changed

###################################################################################
DB_HOSTNAME=immich_postgres
DB_USERNAME=postgres
DB_DATABASE_NAME=immich
DB_DATA_LOCATION=/home/norad/noradsahre/Photos/Immich/.postgres `

torn cloak
#

Ok so you still have a pgdata volume defined, what is that from? Did you migrate your DB to DB_DATA_LOCATION?

#

Also your .Postgres is a subfolder of UPLOAD_LOCATION, I don’t think that’s good

somber seal
#

I think the pgdata volume is probably something I didn't catch when updating the compose file at some point. I've been dabbling with Immich for about a year and just tweaking the same compose. As for the reason I located the .Postgres subfolder there is b/c that whole folder is on a logical volume on a Raid-1 device for backup. I can move it if you think that's causing an issue. Uploading log here in a second.

#

Log file. I stopped the container, brought it back up and tried to get it to re-generate thumbnails. It did about 10 or so then just stopped.

torn cloak
#

I doubt that’s the cause of this is issue, but pretty unusual

somber seal
#

I'm a freaking idiot, I think I figured it out

#

No idea how this happened, but there was a zombie docker process running the old microservices container that had been up for 2 months. So even though I was starting and stopping via the compose file, with that service removed nothing was telling docker to kill it. I just manually killed the process and it seems to be working. Chugging along generating all thumbnails. No clue how that happened, unless I edited the compose file then did a pull and restart without stopping. facepalm

#

I'm going to wait and let it regenerate all thumbnails and, if successful, I'll close this.

somber seal
#

That fixed it. Hope somebody else sees this if they did the same stupid thing. 🙈

somber seal
#

So re-opening this again. Its started again, and I don't know why. No changes to config.

#

It is very intermitant. Example coming