Closed profucius closed 2 weeks ago
GSKang94
commented
2 weeks ago Hey @profucius
I faced same issue this morning after latest Riven update
Try dropping database with
docker exec -it DMB sh -c "PGPASSWORD=postgres psql -U DMB -d postgres -c 'DROP DATABASE riven;'"
and then restart docker container
profucius
commented
2 weeks ago Try dropping database with
docker exec -it DMB sh -c "PGPASSWORD=postgres psql -U DMB -d postgres -c 'DROP DATABASE riven;'"and then restart docker container
That worked, thanks! Is there any way of knowing or predicting these kinds of issues? Or are we destined to just continue expecting things to break, reporting them here, and someone like yourself happening to know what to do about it. I always feel helpless against the constant shifting of tectonic plates within Riven especially, since it always updates itself even when I wanted to prevent that from happening.
I-am-PUID-0
commented
2 weeks ago The root cause was an update to the Riven Backend that required a database reset.
Riven is very much still beta, so breaking changes are to be expected. I try to limit breaking changes to DMB, but some are necessitated by Riven changes.
If you want to lock the Riven Backend and Fronted versions, you can use RIVEN_BACKEND_VERSION= & RIVEN_FRONTEND_VERSION= respectively.
I recommend following the Riven & DMB Discord Servers so you can stay apprised of changes sooner.
I-am-PUID-0
commented
2 weeks ago It looks like you may also have RIVEN_BACKEND_BRANCH=main & RIVEN_FRONTEND_BRANCH=main set; remove them, as Riven uses the main branches as dev.
profucius
commented
2 weeks ago I know it's usually not DMB but Riven instead; My beef with them is that they don't make a callout mention of breaking changes in their github releases. Maybe they mention it casually as a line item that someone in-the-know might recognize. But not everyone has the ability to constantly keep up with discord updates across hundreds of softwares. I've mentioned this to them in their discord, and it seems to have fallen on deaf ears. I'm just venting. Thanks for the help. And I'll make that change in my yaml.
I-am-PUID-0
commented
2 weeks ago No worries — I totally get it! They use semantic versioning but don't use the first digit — e.g., 1.0.0 to 2.0.0 — to highlight breaking changes. This keeps me on my toes as well.
Describe the bug
After my nightly backup stopped and restarted the stacks, Riven no longer works. It appears the backend updated itself, and I am getting the below errors. I have also forced my stack to update DMB to the latest 5.4.3 today, same issue.
The Riven frontend eventually starts, but because the backend does not, nothing works.
The error that I noticed might be of note is this line:
Log