# Can we avoid updates that force me to debug on the command line please?
**URL:** https://meta.discourse.org/t/can-we-avoid-updates-that-force-me-to-debug-on-the-command-line-please/379995
**Category:** Support
**Created:** [August 23, 2025, 10:14am UTC](https://meta.discourse.org/t/can-we-avoid-updates-that-force-me-to-debug-on-the-command-line-please/379995 "2025-08-23T10:14:48Z")
**Posts on this page:** 11
**Page:** 1
### Author:  [@Benjol](https://meta.discourse.org/u/Benjol)
#### Post date: [August 23, 2025, 10:14am UTC](https://meta.discourse.org/t/can-we-avoid-updates-that-force-me-to-debug-on-the-command-line-please/379995/1 "2025-08-23T10:14:48Z")
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.
(Last time):
> [@Is it by design that updates via web UI can provoke breaking changes?](https://meta.discourse.org/t/is-it-by-design-that-updates-via-web-ui-can-provoke-breaking-changes/345426):
>
> I just tried upgrading via the web UI. The first part went ok, but the second step (update Discourse version) got part way through, then said there was an error, and the forum no longer works at all (just the āOopsā page). Logging into ssh (to manually run ./launcher rebuild app), I get ERROR: Docker version 18.06.3-ce not supported, please upgrade to at least 20.10.0, or recommended 24.0.7 Putting aside the possible solutions to that problem (which are beyond my level of comfort/competence),ā¦
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [August 23, 2025, 11:31pm UTC](https://meta.discourse.org/t/can-we-avoid-updates-that-force-me-to-debug-on-the-command-line-please/379995/2 "2025-08-23T23:31:51Z")
> [@Is it by design that updates via web UI can provoke breaking changes?](https://meta.discourse.org/t/is-it-by-design-that-updates-via-web-ui-can-provoke-breaking-changes/345426/1):
>
> manually
It should have printed a warning about exactly that. You could then restart the container with
./launcher start app
And then figured out your next steps more leisurely.
You may still be able to start the container.
But to answer the question in the title, not really. This was a big change and there were notifications here about it. Periodically things need upgrading that are external to the stuff that is just the discourse source code that can be upgraded in the ux.
---
### Author:  [@Benjol](https://meta.discourse.org/u/Benjol)
#### Post date: [August 24, 2025, 7:43am UTC](https://meta.discourse.org/t/can-we-avoid-updates-that-force-me-to-debug-on-the-command-line-please/379995/3 "2025-08-24T07:43:25Z")
Youāre right, of course.
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 š
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [August 24, 2025, 3:22pm UTC](https://meta.discourse.org/t/can-we-avoid-updates-that-force-me-to-debug-on-the-command-line-please/379995/4 "2025-08-24T15:22:43Z")
> [@Benjol](#):
>
> Itās just that I wasnāt expecting the first rebuild to fail, so that caught me off guard
Yup. That was a bit of bad luck. This is the most disruptive upgrade thatās happened in ten years.
> [@Benjol](#):
>
> because it was in the wall of log text, I lacked confidence that I would find whatever the problem was.
Yes. It is a huge wall of text. Iāve been looking at it for almost a decade and itās still hard to know just what to look at.
> [@Benjol](#):
>
> I guess this is what happens when one is a part-part time webmaster
Iām afraid so!
When you use āthe aiā use [Ask.discourse.com](http://Ask.discourse.com)
---
### Author:  [@Kartoon](https://meta.discourse.org/u/Kartoon)
#### Post date: [August 24, 2025, 10:10pm UTC](https://meta.discourse.org/t/can-we-avoid-updates-that-force-me-to-debug-on-the-command-line-please/379995/5 "2025-08-24T22:10:30Z")
How would a warning someplace else be better than a warning there when both would do the exact same thing and neither have a negative effect outside of reading? The log is always the first place you should look if thereās an errorā¦
---
### Author:  [@RGJ](https://meta.discourse.org/u/RGJ)
#### Post date: [August 24, 2025, 10:29pm UTC](https://meta.discourse.org/t/can-we-avoid-updates-that-force-me-to-debug-on-the-command-line-please/379995/6 "2025-08-24T22:29:55Z")
> [@Benjol](#):
>
> at least have a warning like āget ready, this one is going to hurtā
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.
---
### Author:  [@Benjol](https://meta.discourse.org/u/Benjol)
#### Post date: [August 25, 2025, 11:59am UTC](https://meta.discourse.org/t/can-we-avoid-updates-that-force-me-to-debug-on-the-command-line-please/379995/7 "2025-08-25T11:59:16Z")
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 ā¹
---
### Author:  [@tobiaseigen](https://meta.discourse.org/u/tobiaseigen)
#### Post date: [September 22, 2025, 11:45pm UTC](https://meta.discourse.org/t/can-we-avoid-updates-that-force-me-to-debug-on-the-command-line-please/379995/8 "2025-09-22T23:45:43Z")
> [@Benjol](#):
>
> 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.
Sorry this was a rough experience for you! š¤
> [@pfaffman](#):
>
> Yup. That was a bit of bad luck. This is the most disruptive upgrade thatās happened in ten years.
Not a lot of consolation in your case, but true. It is rare for an update to require intervention at the command line.
> [@Benjol](#):
>
> Also, my backup is broken again since the update, back to the grindstone for me ā¹
Hope you were able to resolve this issue! You need to have backups if you are self-hosting, because you never know what might happen.
---
### Author:  [@Benjol](https://meta.discourse.org/u/Benjol)
#### Post date: [September 23, 2025, 5:40am UTC](https://meta.discourse.org/t/can-we-avoid-updates-that-force-me-to-debug-on-the-command-line-please/379995/9 "2025-09-23T05:40:41Z")
I knuckled down and tackled this on Saturday, with the help of ask.discourse this time.
I discovered that we had a non-standard volumes set up, with uploads and backups on a secondary disk. Which would not have been a problem, but when we grew the data disk from 20GB to 30GB, we omitted to inform the file system!
With that fixed, Iāve now got breathing space for a few more years.
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [September 23, 2025, 10:34am UTC](https://meta.discourse.org/t/can-we-avoid-updates-that-force-me-to-debug-on-the-command-line-please/379995/10 "2025-09-23T10:34:25Z")
> [@Benjol](#):
>
> when we grew the data disk from 20GB to 30GB, we omitted to inform the file system!
Ah! Thatās a tough one! And an advanced setup to be sure.
Glad you got it sorted.
---
### Author:  [@tobiaseigen](https://meta.discourse.org/u/tobiaseigen)
#### Post date: [September 29, 2025, 3:01pm UTC](https://meta.discourse.org/t/can-we-avoid-updates-that-force-me-to-debug-on-the-command-line-please/379995/11 "2025-09-29T15:01:02Z")
This topic was automatically closed after 6 days. New replies are no longer allowed.