Crash After Recent Update

Product Support

AI-generated summary

Hossein_Nazem reports a crash after updating Discourse via the dashboard following a successful Docker Manager update. Upon returning to the site, they encountered a generic error message stating “no further action is necessary.” David_Ghost suggests that without the specific error log from the update, troubleshooting is difficult, and recommends performing a manual update using ./launcher rebuild app from /var/discourse, referencing this guide. Firepup650 clarifies that the “no further action is necessary” message is typically meant to reassure non-staff users that the issue is temporary and being addressed automatically. The consensus implies that waiting may be appropriate, but if the problem persists, manual intervention or further diagnostics are advised.

1

Hi
I updated the docker manager successfully, then pressed the Discourse update button on the dashboard, and it started updating. I left my PC for minutes, and when I returned, I refreshed the page and got this error:

" 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."

It states “no further action is necessary.” Now I should wait or proceed with fixing the problem?
If I should wait, how long will it take?

2

Without knowing the error message when updating, it’s hard to know.

You better try is to do a manual update, by:

cd /var/discourse
./launcher rebuild app

3

That’s generally for non-staff users, to assure them that the issue is temporary.