A user, smileBeda, reports that upgrading from 2.9.0.beta8 to a newer version via the admin interface caused their Discourse site to become unrecoverable, with no visible error messages. They had to restore from a backup. The community suggests checking logs (e.g., /var/discourse/shared/standalone/log/rails/production.log) and taking backups before updates. RGJ and Jagster emphasize the importance of backups and staging environments. JammyDodger and osioke ask for more details, including the app.yml file and plugin list, to diagnose the issue. pfaffman and Benjamin_D suggest using ./launcher rebuild app as a recovery step. merefield also requests clarification on the plugins in use.
We have simply clicked the admin upgrade button.
Did not expect this:
Oops
The software powering this discussion forum encountered an unexpected problem. We apologize for the inconvenience.
Detailed information about the error was logged, and an automatic notification generated. We'll take a look at it.
No further action is necessary. However, if the error condition persists, you can provide additional detail, including steps to reproduce the error, by posting a discussion topic in the site's feedback category.
Now, while this is a bit discouraging (what if this happens when the site has a couple thousand users?)… we have no users yet. Lucky. But we can’t get it back up running. There is no discernible error, any step to take to recover what went wrong… unless the ominous automatic notification generated. Who received that notification? What does it say? Why does a simple upgrade of the software send the site into oblivion? How can we fix that?
That is a real risk with every app, including Discourse. That’s why big guys are using a stage server and we smaller fishes are doing backups (site AND database) before every update, but at least before any upgrading.
Could you give us some more detail about your set up? For instance, what version you’re running, whether it’s a standard install, and if you have any plugins (official or third-party).
Normally upgrades go very smoothly, though taking a backup of a live site just beforehand is always prudent just in case.
It is a standard install from docker, however we run a couple plugins (but nothing unusual, really. No custom code so far)
At this point (without error log) I cannot really tell more, I guesss we’ve to bite the apple again and after a backup, run the update and if it fails again, submit the logs…
