Creating and restoring database fails #900
Replies: 4 comments 5 replies
-
Hi Felix, this seems like a question for Martin (@mzur). Unfortunately, our holidays all start tomorrow. I'm not sure if Martin will be able to assist you during his holiday. That's why it will take some time before you get an answer. Sry. Best |
Beta Was this translation helpful? Give feedback.
-
I'm back on August 19. If you need support earlier, please write me an email. |
Beta Was this translation helpful? Give feedback.
-
Hi Daniel and Martin, Thanks for your answer! Let's come back to this after you are back from holiday Martin :). Do not want to disturb you! Best, |
Beta Was this translation helpful? Give feedback.
-
So there are three issues here:
|
Beta Was this translation helpful? Give feedback.
-
Hello,
Would appreciate some help here :)
We have a Biigle instance running with some users and projects and use a s3 user-disk as a source of the video/image data.
I tried to follow https://biigle-admin-documentation.readthedocs.io/maintenance/
to create a database dump and restore it on a new instance.
I set up the new instance (with the same APP_KEY as the one I created the dump of), cleared the database using "./artisan db:wipe" and then restored using "cat biigle_db.sql | docker exec -i $(docker compose ps -q database) \ psql -U biigle biigle". As far as I can tell the restore runs as expected and no errors are printed.
Now the instance has all the projects/volumes available and I can log in with my old user name/password. However the projects/volumes are missing template images and when I open videos/images I get:
Also when trying to look into the s3 user-disk (under storage) I get:
The server logs show those errors:
I'm not sure how to fix this. Am I doing something wrong?
Thanks!
Felix
Beta Was this translation helpful? Give feedback.
All reactions