Id is null after last update
Hello, I haven't changed anything in the configuration lately, but after the last update, my immich doesn't work at all.
The devices are backed up again and again, and after closing and opening the application, they do not detect the already uploaded images and back everything up again. Each new asset has all the data in the db OK, EXCEPT for the id, which is now null. My wife's entire mobile phone has been backed up several times this way, and today I deleted 28,000 records with null id. I already tried deleting the entire stack, deploying it again with a new pull, but still the same result. The only thing I changed is the storage migration format. first I chose one type and then the other, but I think this should not have any effect on the newly uploaded photos.
Has this happened to anyone else?
6 Replies
Can you share your set up? Docker compose file and .env?
Can you also share your template for storage?
.env:
Storage template;
{{y}}/{{MMMM}}/{{d}}/{{filename}}I don't see any problem in your setup. I am not sure why such error happen. Can you bring the stack down then up and try again?
the
ID of the asset is auto generated column so it should never be null
it is like during the write process into the database, some weird states with your postgresql container causes it to happenok, it's solved, I caused the problem. I played with the database and backed up the tables, I made a production assets table from the backup and it was missing indexes and references 😅 sorry