Skip to content

Commit 540a95a

Browse files
pscheitnaderman
andauthored
Update docs/self-hosted/troubleshooting.md
Co-authored-by: Nils Adermann <n.adermann@packagist.com>
1 parent 958d2e5 commit 540a95a

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

docs/self-hosted/troubleshooting.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -110,10 +110,10 @@ update the host IP and the NO_PROXY environment.
110110

111111
#### Replicated Management Console shows "Stopped" after upgrading to 1.12.4
112112

113-
You just upgraded to SelfHosted version 1.12.4 and now the Replicated Management Console
114-
only shows "Stopped" in the top left corner of the dashboard? In this SelfHosted update PostgreSQL is upgraded from 9.6 to 12. Depending on the size of your database, this will cause increased disk IO and might take a few minutes during which the application won't be available.
115-
The upgrade is done in the docker container `packagist-postgres-update` which should be first started then `stopped`. You can check the `Cluster` section: all containers should be started except the upgrade container should be stopped. The Replicated Management Console is just showing the wrong state.
116-
Pressing the button `Start now` on the dashboard would then show the correct state, but you can leave it as is.
113+
You just updated to Self-Hosted version 1.12.4 and now the Replicated Management Console
114+
only shows "Stopped" in the top left corner of the dashboard? As part of this this Self-Hosted update PostgreSQL is upgraded from 9.6 to 12. Depending on the size of your database, this will cause increased disk IO and might take a few minutes during which the application won't be available.
115+
The upgrade is done in the docker container `packagist-postgres-update` which only runs for the duration of the upgrade and then stops. You can check the `Cluster` section in the Replicated Management Console: all containers should be started except the upgrade container, which should be stopped. The Replicated Management Console is just showing the wrong state on the dashboard.
116+
Pressing the button `Start now` on the dashboard will correct the displayed application state, but you can also leave it as is.
117117

118118
#### Reset Replicated Management Console authentication
119119

0 commit comments

Comments
 (0)