#Error failed to find parent tuple after upgrade V1.106.4

1 messages · Page 1 of 1 (latest)

wicked wyvern
#

After an upgrade from 1.105.1 to 1.106.4, immich server can't start and display an error in attached file

Starting microservices worker
[Nest] 7 - 06/23/2024, 8:09:24 PM LOG [Microservices:EventRepository] Initialized websocket server
Migration "CreateAssetDuplicateColumns1711989989911" failed, error: failed to find parent tuple for heap-only tuple at (4884,8) in table "assets"
...
microservices worker exited with code 1

Environnement :
Docker compose with portainer (adapted without microservice)
Config on attached file.
If I revert back to V1.105.1 and restore my previous docker compose file, it's work again.

What does this error mean and How I can solve it?
Thanks guys
Regards

lapis lanceBOT
#

:wave: Hey @wicked wyvern,

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

lapis lanceBOT
thick idol
#

That's concerning, it indicates some corruption in your database that I don't think has an easy solution

#

But note that this means effectively deleting assets from the database

#

So then after you'll need to figure out which ones those are and reupload them

wicked wyvern
#

Why is-it working un V1.105.1 and not in V1.106.4 ???

thick idol
#

The corruption is there in both, when 106 starts up it tries to run a migration that encounters the corruption/makes it visible

wicked wyvern
#

Strange,
Is there a way to reconstruct database without losing all person and face recognition?
Thks

thick idol
#

You can try what I linked above which if it goes well will keep most of your database intact (but no telling how much until you get going)