-
Notifications
You must be signed in to change notification settings - Fork 97
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
error running app: unable to create Temporal client: failed reaching server: context deadline exceeded #2352
Comments
Can you re run docker compose? I have seen this on resource constrained systems sometimes where temporal slows down a bit. Also can you check temporal logs? That should also clear things up a bit |
@iamKunalGupta I tried re-running it many times. Same error always. Nothing suspicious in the temporal logs. This is Docker Compose output:
|
And temporal logs looks ok, no errors:
|
This is very weird tbh, I cleaned my old containers and cloned and re-ran, seems to be working fine for me. Once temporal is up (and the rest of the containers are failing), can you try running the left over containers one by one? |
I have generally seen this happen only when developing flow-* locally and using temporal via the container, a re-run of the build usually, does it for me |
I tried that as well. Tried to run temporal, wait for a while (5-10 minutes), and later run the rest of them. |
If you are available for a few mins, maybe we can sit down and take a look at it? You can join the community slack and message and we can schedule a call https://slack.peerdb.io/ |
Hi!
I'm following Quick Start documentation trying to start PeerDB and getting the error right after that.
git clone --recursive https://github.com/PeerDB-io/peerdb.git cd peerdb ./run-peerdb.sh
After running
./run-peerdb.sh
I can see the error fromflow_api
,flow-worker
andflow-snapshot-worker
containers with such message:All three of them exiting on start with similar messages:
It looks like there is something wrong with the Temporal connection configuration.
The text was updated successfully, but these errors were encountered: