#Error Updating to 1.106.1

1 messages · Page 1 of 1 (latest)

burnt canopy
#

I'm trying to update to 1.106.1 from 1.105.1

I updated the compose file and tried to 'update stack' and I am getting this error.

WARN[0000] The "DB_DATA_LOCATION" variable is not set. Defaulting to a blank string.
invalid spec: :/var/lib/postgresql/data: empty section between colons
WARN[0000] The "DB_DATA_LOCATION" variable is not set. Defaulting to a blank string.
invalid spec: :/var/lib/postgresql/data: empty section between colons

dense mapleBOT
#

:wave: Hey @burnt canopy,

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. :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. :ballot_box_with_check: I have uploaded the relevant logs, docker compose, and .env files using the buttons below or the /upload command.
  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.

forest spindle
#

If you were using a docker volume before, you should stick with that. You updated your compose and removed the docker volume, essential voiding your database

burnt canopy
#

Ok, so how do I fix it. Its on an Unraid server. I edited the compose file and removed the lines under breaking changes. then I tried to update the stack. Then it gave me this error. How do I get back to where I was?

#

I am sorry for my lack of knowledge on the subject.

forest spindle
#

You can try reverting your postgres section back to how it was before. And hopefully the postgres volume wasn't dropped and is still available

image.png image.png
burnt canopy
#

ok. I will see what I have in backups

forest spindle
#

If that doesn't work hopefully you have postgres backups that you can try and restore in a new db instance

burnt canopy
#

I do have a postgres backup.

forest spindle
#

Then yeah I would say first try and revert to using the docker volume you had before. If that fails, then you can move to using the new file system db volume and try and restore a backup into it.

burnt canopy
#

Ok. I may be a bit confused here. Do I just change my compose file back to what it was before I changed it for the latest release? Then update the statck?

dense mapleBOT
burnt canopy
#

That was my previous one before trying to update.

#

I guess the DB is all still there because I can start the containers and all my images show up.

#

And thanks for your help schuhbacca

#

I used that compose when I updated to 1.105.1 and it worked. Thats the version I am on.

idle ridge
burnt canopy
#

I believe that is what I tried first. I will try again. Standby

#

Now to be clear. I am in unraid. In the Compose section I can click "update stack" then "compose up"

#

that will do the 'docker compose pull' and 'docker compose up' ?

#

I click on update stack and get the same error

idle ridge
#

can you post the content of your .env?

dense mapleBOT
burnt canopy
#

I don't ever remember if I changed those passwords or not...

idle ridge
#

You don't have DB_DATA_LOCATION set in your .env file

#

so your setup was most likely didn't use it before

burnt canopy
#

Oh.. ok. So my database is working. How would I go about getting my old database location so I can set that?

idle ridge
burnt canopy
#

Everything should be default as I haven't changed much

idle ridge
burnt canopy
#

ok

idle ridge
#

try to put those back

#

and see if it works for you

burnt canopy
#

ok thats pulling.. Thanks Alex. Was this part of some other breaking change that I didn't do in the past or something along those lines?

idle ridge
#

this was in 1.102