Closed augustohalvarez closed 3 years ago
nisdas
commented
3 years ago @augustohalvarez You can try deleting your validator db either manually or with --clear-dbin your validator client. I am assuming the fact that you are running the same validator directory for both the testnet/mainnet might have caused issues here. Let me know if after that your validator is back up and running.
augustohalvarez
commented
3 years ago Thanks so much @nisdas, looks like it's working as expected since I'm seeing this in the logs now:
Feb 01 13:42:54 augusto-NUC8i5BEK prysm.sh[10632]: time="2021-02-01 13:42:54" level=info msg="Deposit processed, entering activation queue after finalization" index=88277 positionInActivationQueue=11227 prefix=validator pubKey=0x9075fe0036a4 status=DEPOSITED
Really appreciate the suggestion! Going to close the issue now.
🐞 Bug Report
Description
With Geth node and beacon chain fully synced and running, starting the validator process exits immediately after the log "Waiting for beacon chain start log from the ETH 1.0 deposit contract"
Has this worked before in a previous version?
Unclear. Same commands worked on Pyrmont testnet, though this is the first time running on mainnet ## 🔬 Minimal Reproductionsuccessfully imported validator_keys into the prysm wallet. The accounts list shows just one, and the pub key matches what I'm seeing in beaconcha.in (btw, validator is waiting to be activated) https://beaconcha.in/validator/9075fe0036a41dc6694e4ab0526b9e4fb8620e811135a07d2440f529c62d163c0758f0ae56e5711b1347d9f7367213b0#deposits
Geth was started as a systemd service:
The Geth javascript consle shows eth.syncing as
falseand the service seems to be running okay. Here's a snippet of the logs when restarting the service: eth1.logBeacon chain started as systemd service:
Appears to be fully synced and working as expected from looking at the logs. Here's a snippet of restarting the service: beacon-chain.log
Validator is also a systemd service:
All three services started the same way
systemctl start {service name}With both the Geth node and beacon chain synced and running, starting the validator gives the following output:🔥 Error
🌍 Your Environment
Operating System:
What version of Prysm are you running? (Which release)
Anything else relevant (validator index / public key)? Validator public key:
0x9075fe0036a41dc6694e4ab0526b9e4fb8620e811135a07d2440f529c62d163c0758f0ae56e5711b1347d9f7367213b0Also shown in link to beaconcha.in with some more info.Some things to note: I did encounter a bit of weirdness when transitioning off the Pyrmont testnet. I had everything running smoothly for a bit so I decided to perform a voluntary exit before starting mainnet. That was a success so I went ahead and created new validator keys with the deposit cli and imported into my prysm wallet. When running
validator accounts list --mainnet, it showed two accounts, the one I used for testnet and the newly imported account. I thought maybe I had left out the pyrmont flag when importing the key (still unsure), so I went ahead and deleted that account, leaving only the new mainnet one. Not sure if this did anything but thought I should mention.I have tried a full resync of the beacon chain by deleting the data directory and restarting the service but I'm still seeing the same error.
I have been running each service in separate tmux sessions but I've tried running them in separate terminal windows and still seeing the same error.
Please let me know if you need any more info. I realize this may be hard to reproduce so any help or further direction on how to debug would be immensely appreciated. Thanks for all the hard work and maintaining the discord channel, it's been incredibly helpful so far!