#Can't recover database from dump on new host

1 messages · Page 1 of 1 (latest)

tulip plankBOT
#

:wave: Hey @keen viper,

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

#

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. :blue_square: 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.

edgy abyss
#

Hi, we would recommend to reach out to their team as we only support docker deployments

#

Did you come from windows or a different OS? sometimes that causes this \N error

keen viper
#

Always in proxmox. Before nested virtualisation with Docker in LXC, now a more cleaner way

edgy abyss
#

got it. yeah we don't recommend docker in LXC, and especially not the bare metal helper script

keen viper
#

I am a wondering, there is no clean way to just export and import this an easy way ...

edgy abyss
#

the easy way we recommend would be a VM running docker

keen viper
#

its proxmox-helper-scripts

#

you know them?

edgy abyss
#

yes, I know, but they have a pretty unusual deployment that we don't use/recommend

#

so issues should be asked of them

keen viper
#

I understand

edgy abyss
#

You can share the DB restore command you are trying but in general we don't know much about or support this method

keen viper
#

So you say for my setup an VM with Docker would be the best option?

#

Before I loose my last hair, I will give it a try