# Discourse AI causing rebuild to fail

**URL:** <https://meta.discourse.org/t/discourse-ai-causing-rebuild-to-fail/328232>\
**Category:** Product Support\
**Tags:** ai\
**Created:** [September 26, 2024, 2:10pm UTC](https://meta.discourse.org/t/discourse-ai-causing-rebuild-to-fail/328232 "2024-09-26T14:10:55Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)\
**Post date:** [September 26, 2024, 7:36pm UTC](https://meta.discourse.org/t/discourse-ai-causing-rebuild-to-fail/328232/6 "2024-09-26T19:36:03Z")

</div>

Well, I’m about as command-line as they come, and the nice thing about the dashboard is that it runs an ansible script that does a whole bunch of stuff that people are likely to forget like doing a cleanup when disk gets tight, noticing that it’s time for a postgres upgrade (or in this case to just do a simple rebuild as opposed to a full version rebuild which takes a couple of rebuilds). It even shuts down the web container, rebuilds data, then starts up the web container before it goes on to doing the bootstrap.

Oh! And it knows about some plugins that are deprecated or moved to core, and removes those automatically.

But if you really like doing extra work and just mindlessly staring and computers do things (like I do), you can log in at the command line while it’s doing the upgrade and do a

```
docker logs -f container-name

```

to watch it do the bootstrap. If you tab twice for the container name, you’ll see the silly random name that docker assigns.

Cheers

---

_[View the full topic](https://meta.discourse.org/t/discourse-ai-causing-rebuild-to-fail/328232)._