mirror of
https://github.com/bigchaindb/bigchaindb.git
synced 2024-10-13 13:34:05 +00:00
Elaborate on 502 gateway error
This commit is contained in:
parent
df2bd10430
commit
cba933a592
@ -29,9 +29,16 @@ TODO: paste the error message the next time this error happens!
|
|||||||
------------------------------------------
|
------------------------------------------
|
||||||
|
|
||||||
It means that NGINX could not find the appropriate backed to forward the
|
It means that NGINX could not find the appropriate backed to forward the
|
||||||
requests to. This typically happens when MongoDB goes down (as described above)
|
requests to. This typically happens when:
|
||||||
and BigchainDB, after trying for ``BIGCHAINDB_DATABASE_MAXTRIES`` times, gives
|
|
||||||
up. The Kubernetes BigchainDB Deployment then restarts the BigchainDB pod.
|
#. MongoDB goes down (as described above) and BigchainDB, after trying for
|
||||||
|
``BIGCHAINDB_DATABASE_MAXTRIES`` times, gives up. The Kubernetes BigchainDB
|
||||||
|
Deployment then restarts the BigchainDB pod.
|
||||||
|
|
||||||
|
#. BigchainDB crashes for some reason. We have seen this happen when updating
|
||||||
|
BigchainDB from one version to the next. This usually means the older
|
||||||
|
connections to the service gets disconnected; retrying the request one more
|
||||||
|
time, forwards the connection to the new instance and succeed.
|
||||||
|
|
||||||
|
|
||||||
3. Service Unreachable
|
3. Service Unreachable
|
||||||
|
Loading…
x
Reference in New Issue
Block a user