deploy failing after installation of v0.15.10
Hi
After updating to 0.15.10, the application is not coming back up, I get the following error:
Solution:Jump to solution
That said I'm not completly sure how your setup works, but if your db migration is not run on every release then it will probably not work. Let me know if this helps or we can investigate further
13 Replies
Thank you for submitting a support request.
Depending on the volume of requests, our team should get in contact with you shortly.
⚠️ Please include the following details in your post or we may reject your request without further comment: - Log (See https://homarr.dev/docs/community/faq#how-do-i-open-the-console--log) - Operating system (Unraid, TrueNAS, Ubuntu, ...) - Exact Homarr version (eg. 0.15.0, not latest) - Configuration (eg. docker-compose, screenshot or similar. Use ``your-text`` to format) - Other relevant information (eg. your devices, your browser, ...)
❓ Frequently Asked Questions | Homarr documentation
Can I install Homarr on a Raspberry Pi?
Hi, what version did you upgrade from? What did you do to ugprade?
0.15.7--> 0.15.10
Please post your docker compose / run
I'm kinda not using docker, as Proxmox is my type one virtualizer.
Here the commands I run to update:
--> Backup .env file, config and DB
remove full application folder
download latest github release
Restart the service of homarr, this normally updates homarr just fine, but the latest v0.15.10 seems to not work with this method.
PS: the thing with nextauth exports came from here:
https://github.com/ajnart/homarr/issues/2125
GitHub
bug: Failing build static page generation · Issue #2125 · ajnart/ho...
Environment Docker Version 0.15.4 Describe the problem When I try to manually build this project, after updating I get the following error: To reproduce Install homarr via git build after a while a...
@Meierschlumpf can you look into this? Maybe migration is failing
Sure, so the thing is that we added something to the db in the version
0.15.10
. I suspect that is why it fails for you.Solution
That said I'm not completly sure how your setup works, but if your db migration is not run on every release then it will probably not work. Let me know if this helps or we can investigate further
So you think doing each upgrade e.g. 0.15.7-->0.15.8-->0.15.9-->0.15.10 with each a db migration?
Okay I'll test that.
No, directly should work but you need to check if the db migration was executed
i manually entered the yarn db:migrate command so yes
I just re-did the whole process from scratch using a backup from some days ago, the db corrupt seems the most logical thing, but it's working now 🙂
Thanks!