You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think peerdb tries to connect to flow_api before flow_api is ready. This causes peerdb not to start. Have seen this mostly happen when we first time docker compose up. Restarting the docker compose up command fixes the issue most of the times.
peerdb-stack-peerdb-1 | 2023-06-12T17:17:21.339614Z INFO Migration Applied - Name: peer_connections, Version: 2
peerdb-stack-peerdb-1 | 2023-06-12T17:17:21.339617Z INFO Migration Applied - Name: add_workflow_id_to_flows, Version: 3
peerdb-stack-peerdb-1 | 2023-06-12T17:17:21.340716Z INFO Listening on 0.0.0.0:9900
peerdb-stack-peerdb-1 | Error: failed to send health check request
peerdb-stack-peerdb-1 |
peerdb-stack-peerdb-1 | Caused by:
peerdb-stack-peerdb-1 | 0: error sending request for url (http://flow_api:8112/health): error trying to connect: dns error: failed to lookup address information: Name or service not known
peerdb-stack-peerdb-1 | 1: error trying to connect: dns error: failed to lookup address information: Name or service not known
peerdb-stack-peerdb-1 | 2: dns error: failed to lookup address information: Name or service not known
peerdb-stack-peerdb-1 | 3: failed to lookup address information: Name or service not known
peerdb-stack-peerdb-1 exited with code 1```
The text was updated successfully, but these errors were encountered:
I think peerdb tries to connect to flow_api before flow_api is ready. This causes peerdb not to start. Have seen this mostly happen when we first time docker compose up. Restarting the docker compose up command fixes the issue most of the times.
The text was updated successfully, but these errors were encountered: