-
Notifications
You must be signed in to change notification settings - Fork 26
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
bug: registry service not starting #552
Comments
Hey could you share the logs from the |
I needed to run the log command many times to get something meaningful. ➜ manifestjs git:(starship) ✗ kubectl logs -f registry-f997744df-n7wlz --all-containers=true
Error from server (BadRequest): container "registry" in pod "registry-f997744df-n7wlz" is waiting to start: PodInitializing
➜ manifestjs git:(starship) ✗ kubectl logs -f registry-f997744df-n7wlz --all-containers=true
Genesis validator does not seem to be ready for: manifest-ledger-beta. Waiting for it to start...
Checking: http://manifest-ledger-beta-genesis.default.svc.cluster.local:8081/node_id
Genesis validator does not seem to be ready for: manifest-ledger-beta. Waiting for it to start...
Checking: http://manifest-ledger-beta-genesis.default.svc.cluster.local:8081/node_id
Genesis validator does not seem to be ready for: manifest-ledger-beta. Waiting for it to start...
Error from server (BadRequest): container "registry" in pod "registry-f997744df-n7wlz" is waiting to start: PodInitializing
➜ manifestjs git:(starship) ✗ kubectl logs -f registry-f997744df-n7wlz --all-containers=true
Genesis validator does not seem to be ready for: manifest-ledger-beta. Waiting for it to start...
Checking: http://manifest-ledger-beta-genesis.default.svc.cluster.local:8081/node_id
Genesis validator does not seem to be ready for: manifest-ledger-beta. Waiting for it to start...
Checking: http://manifest-ledger-beta-genesis.default.svc.cluster.local:8081/node_id
Genesis validator does not seem to be ready for: manifest-ledger-beta. Waiting for it to start...
Checking: http://manifest-ledger-beta-genesis.default.svc.cluster.local:8081/node_id
Genesis validator does not seem to be ready for: manifest-ledger-beta. Waiting for it to start...
Checking: http://manifest-ledger-beta-genesis.default.svc.cluster.local:8081/node_id
Genesis validator does not seem to be ready for: manifest-ledger-beta. Waiting for it to start...
Checking: http://manifest-ledger-beta-genesis.default.svc.cluster.local:8081/node_id
Error from server (BadRequest): container "registry" in pod "registry-f997744df-n7wlz" is waiting to start: PodInitializing
➜ manifestjs git:(starship) ✗ kubectl logs -f registry-f997744df-n7wlz --all-containers=true
Error from server (BadRequest): container "registry" in pod "registry-f997744df-n7wlz" is waiting to start: PodInitializing
➜ manifestjs git:(starship) ✗ kubectl logs -f registry-f997744df-n7wlz --all-containers=true
Error from server (BadRequest): container "registry" in pod "registry-f997744df-n7wlz" is waiting to start: PodInitializing
|
This is weird. let me try it on my end as well. It seems that the custom chain is not been able to be waited for. Could you also try this command once. kubect exec -it manifest-ledger-beta-genesis-0 -- /bin/bash
# in the command run curl command
curl http://0.0.0.0:8081/node_id |
✗ kubectl exec -it manifest-ledger-beta-genesis-0 -- /bin/bash
Defaulted container "validator" out of: validator, exposer, faucet, init-genesis (init), init-config (init)
manifest-ledger-beta-genesis-0:/opt# curl http://0.0.0.0:8081/node_id
{"node_id":"b11dc39fbf0d04583295e12f463696291bc30802"} |
Hmm this looks correct. Not sure what is the issue now. Could be a DNS issue with Kind. Let me run it with docker-desktop. |
Ok i think i was able to re-create the issue. I will have to dig a little into this. Let me have a look and get back to you about the same. |
Could you try with docker-desktop instead for the backend? My prediction is that the |
I was able to make it work with This issue looks related to |
Prefect. Let me make sure we remove |
The registry service fails to start with
Configuration is
# kubectl get pods NAME READY STATUS RESTARTS AGE cosmos-2-genesis-0 3/3 Running 0 5m45s manifest-ledger-beta-genesis-0 3/3 Running 0 5m45s registry-f997744df-p524s 0/1 Init:0/1 0 5m45s
# helm list NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION starship-manifestjs default 1 2024-09-05 09:47:04.036022695 -0400 EDT deployed devnet-0.2.12 0.1.1
Backend is
kind
.The text was updated successfully, but these errors were encountered: