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
stop_local_testnet.sh and clean.sh fail to properly stop all geth instances. Causing the port to remain busy after restarting the local testnet, which prevents new testnets to run until all geth processes are killed manually.
Version
Branch: unstable
Version: v5.0.0-f93844e
Present Behaviour
Go to scripts/local_testnet/ and run ./start_local_testnet.sh genesis.json
Wait for the script to finish and run tail -f ~/.lighthouse/local-testnet/testnet/geth_1.log
After a small wait, the testnet will start advancing:
Re-start the testnet by running ./start_local_testnet.sh genesis.json again. (stop_local_testnet.sh and clean.sh) are part of this script.
Wait for the script to finish and run tail -f ~/.lighthouse/local-testnet/testnet/geth_1.log
The geth instances will fail to start because their ports will be busy:
Run ./stop_local_testnet.sh && ./clean.sh
Run htop and search for geth. A bunch of geth processes will still be running:
Kill the geth processes manually.
Run ./start_local_testnet.sh genesis.json again. Now the testnet will start with no issues:
Expected Behaviour
In step 4 a new testnet should be started with no issues. Also, ./stop_local_testnet.sh && ./clean.sh should kill all geth processes.
The text was updated successfully, but these errors were encountered:
In Step 4, when you restart the testnet, you will need to stop the testnet properly: ./stop_local_testnet.sh and then run ./start_local_testnet.sh genesis.json. Otherwise it is like you are trying to start another instance of testnet (geth and lighthouse which are already running) , it will fail as the error you show in Step 6.
If you run ./stop_local_testnet.sh, all processes would be stopped properly. This can then be followed by a ./start_local_testnet.sh genesis.json.
Edit: let me look further as the ./start_local_testnet.sh genesis.json contains the stopping as well. I will get back later
Update: This is due to the change in geth.sh in #5137 that modifies the script to enable logging for geth. This may not be necessary as we already save the logs for geth in ./start_local_testnet.sh genesis.json . The logs are in ~/.lighthouse/local-testnet/testnet/geth_1.log (and geth_2 etc)
Description
stop_local_testnet.sh
andclean.sh
fail to properly stop all geth instances. Causing the port to remain busy after restarting the local testnet, which prevents new testnets to run until all geth processes are killed manually.Version
Branch:
unstable
Version:
v5.0.0-f93844e
Present Behaviour
scripts/local_testnet/
and run./start_local_testnet.sh genesis.json
tail -f ~/.lighthouse/local-testnet/testnet/geth_1.log
./start_local_testnet.sh genesis.json
again. (stop_local_testnet.sh
andclean.sh
) are part of this script.tail -f ~/.lighthouse/local-testnet/testnet/geth_1.log
./stop_local_testnet.sh && ./clean.sh
htop
and search forgeth
. A bunch of geth processes will still be running:./start_local_testnet.sh genesis.json
again. Now the testnet will start with no issues:Expected Behaviour
In step 4 a new testnet should be started with no issues. Also,
./stop_local_testnet.sh && ./clean.sh
should kill all geth processes.The text was updated successfully, but these errors were encountered: