# Cannot rebuild following site failure: "postgres already running"

**URL:** <https://meta.discourse.org/t/cannot-rebuild-following-site-failure-postgres-already-running/24102>\
**Category:** Self-hosting\
**Created:** [16.Январь.2015 22:06:26 UTC](https://meta.discourse.org/t/cannot-rebuild-following-site-failure-postgres-already-running/24102 "2015-01-16T22:06:26Z")\
**Posts on this page:** 1\
**Showing post:** 15

<div class="post-metadata">

**Author:** ![oblio](https://avatars.discourse-cdn.com/v4/letter/o/c4cdca/32.png) [@oblio](https://meta.discourse.org/u/oblio)\
**Post date:** [17.Сентябрь.2015 12:26:41 UTC](https://meta.discourse.org/t/cannot-rebuild-following-site-failure-postgres-already-running/24102/15 "2015-09-17T12:26:41Z")

</div>

I found the root case. I had renamed the container “standalone” but apparently something went wrong and even though Discourse worked, some bits and pieces were still looking for “app”.

After a docker restart and OS restart the forum was running, as “app”, even though the container was “standalone.yml”.

I have no idea how this could have happened, isn’t the container name just the yml file name?

Can I force the execution of the performance report or do I have to wait for cron to trigger it?

---

_[View the full topic](https://meta.discourse.org/t/cannot-rebuild-following-site-failure-postgres-already-running/24102)._