-
Notifications
You must be signed in to change notification settings - Fork 797
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
Local testnet with one beacon node #2094
Comments
Hey there, |
Just checked the testnet scripts with a single testnet node and it failed for me too. A temporary workaround here would be to start with 2 beacon nodes(along with the bootnode) and connect the vc to just one of them. |
An example of how to make this work can be seen in the I'm not sure if/when that will get merged to |
Based on recent testing by @chong-he single-node networks are working, but require the use of the flag
I think we could make single-node networks work a bit more smoothly by not logging these warnings when they are irrelevant (in the I think there's also a case for deprecating |
Description
After following instruction from scripts/local_testnet block is not initialized with one beacon node
Version
branch
unstable
(Lighthouse/v1.0.4-c1e27f4+)Present Behaviour
running one beacon node and validator in validator got an error
SERVICE_UNAVAILABLE: beacon node is syncing: sync is stalled
Beacon Node log
Validator log
Expected Behaviour
able to run testnet beacon node and validator without getting stalled sync (like when 2 beacon nodes are started)
The text was updated successfully, but these errors were encountered: