Sorry, little from a non-expert, but once again, I start off innocently clicking on the ‘update’ in the UI, then get booted to ‘go do a rebuild from the command line’, and then that fails and I’m pasting bash output into AI for it to tell me what’s wrong.
“The error indicates that the Discourse update failed because the discourse-data-explorer plugin is now bundled with Discourse core and should not be included as a separate plugin in your app.yml configuration file.”
I know that it’s not always possible, but it would be nice to at least have a warning like “get ready, this one is going to hurt”. It could prolong my life expectancy.
It’s just that I wasn’t expecting the first rebuild to fail, so that caught me off guard.
The message was there, but I because it was in the wall of log text, I lacked confidence that I would find whatever the problem was. For all I knew it was going to be some obscure exception buried in a call stack. Once AI told me, I saw it was right there near the bottom.
I guess this is what happens when one is a part-part time webmaster
Hoe zou een waarschuwing ergens anders beter zijn dan een waarschuwing daar, terwijl beide precies hetzelfde doen en geen negatief effect hebben buiten het lezen? Het logboek is altijd de eerste plaats waar je moet kijken als er een fout is…
The complexity of an update does not depend on the specific update but more on the version your forum is at before the update, and the versions of Postgres, Redis and all the plugins you have.
So it’s basically impossible to tell whether the update is going to “hurt”.
I’ve done updates from 1.8 to 3.5 without issues, and updates from 3.2.1 to 3.2.2 that cost me hours to fix.
I guess one thing that might help, is if this is an ‘expected’ problem (as in, not something buried in a call stack), to surround it with ---- in the log output. That would make it easier to find.
Also, my backup is broken again since the update, back to the grindstone for me
Ik heb me er zaterdag op geconcentreerd en dit aangepakt, dit keer met behulp van ask.discourse.
Ik ontdekte dat we een niet-standaard volumes hadden ingesteld, met uploads en back-ups op een secundaire schijf. Wat geen probleem zou zijn geweest, maar toen we de datadisk van 20 GB naar 30 GB vergrootten, vergaten we het bestandssysteem te informeren!
Nu dat is opgelost, heb ik weer wat ademruimte voor een paar jaar.
from a non-expert, but once again, I start off innocently clicking on the ‘update’ in the UI, then get booted to ‘go do a rebuild from the command line’, and then that fails and I’m pasting bash output into AI for it to tell me what’s wrong.
