Lost and regained sync, not validating

I lost sync due to a power fluctuation. Now I’m back to sync but my validator still isn’t attesting. Is there something I image to do ?

Here is the error text from my validator log

Error: getaddrinfo ENOTFOUND goerli.dappnode.net goerli.dappnode.net:443
Error: Error: getaddrinfo ENOTFOUND goerli.dappnode.net goerli.dappnode.net:443
at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:56:26)
Error: Error: getaddrinfo ENOTFOUND goerli.dappnode.net goerli.dappnode.net:443
at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:56:26)
at t.XMLHttpRequest.event [as onreadystatechange] (/app/server/webpack:/node_modules/ethers/utils/web.js:85:23)
at t.XMLHttpRequest.dispatchEvent (/app/server/webpack:/node_modules/xmlhttprequest/lib/XMLHttpRequest.js:591:19)
at setState (/app/server/webpack:/node_modules/xmlhttprequest/lib/XMLHttpRequest.js:610:14)
at t.XMLHttpRequest.handleError (/app/server/webpack:/node_modules/xmlhttprequest/lib/XMLHttpRequest.js:532:5)
at ClientRequest.T (/app/server/webpack:/node_modules/xmlhttprequest/lib/XMLHttpRequest.js:459:14)
at ClientRequest.emit (events.js:198:13)
at TLSSocket.socketErrorListener (_http_client.js:401:9)
at TLSSocket.emit (events.js:198:13)
at emitErrorNT (internal/streams/destroy.js:91:8)
at emitErrorAndCloseNT (internal/streams/destroy.js:59:3)
at http://prysm-validator.public.dappnode/static/js/main.4a147952.chunk.js:1:1119
at u (http://prysm-validator.public.dappnode/static/js/2.ee0a35ef.chunk.js:2:274226)
at Generator._invoke (http://prysm-validator.public.dappnode/static/js/2.ee0a35ef.chunk.js:2:273979)
at Generator.forEach.e. [as next] (http://prysm-validator.public.dappnode/static/js/2.ee0a35ef.chunk.js:2:274583)
at r (http://prysm-validator.public.dappnode/static/js/2.ee0a35ef.chunk.js:2:5901)
at l (http://prysm-validator.public.dappnode/static/js/2.ee0a35ef.chunk.js:2:6104)

Looks like a temporary error trying to reach the Goerli RPC. Is it fixed now?

No. I’ve regained sync on my goerli node and geth node but the Onyx beacon chain node remains stuck at epoch 532 (or there about)

I tried restarting the onyx beacon node and validator but it’s still not syncing or attesting. That was last night, before it fell below 32 eth. Now, since that happened, I guess I can’t re-enter.

Have you checked that you have the last version of the package?

No, I didn’t realize there was a new one already or that it needed my attention to upgrade. I’ll have to check tonight since I can’t access it through the UFW from work.

I’m not using topaz, if that’s what you mean.

So, I saw that onyx indeed needed updated so that is done. I cleared the database of the beacon chain node and restarted it, as was suggested by someone elsewhere. It restarted sync but it seemed to get stuck at epoch 2. Its been like that. I checked it on etherscan, though, and it is attesting to slots. So apparently it is working but my validator dashboard is not updating with new info.

Looking at the validator log, I am seeing this over and over

time=“2020-06-19 10:18:00” level=error msg=“rpc error: code = Unavailable desc = Syncing to latest head, not ready to respond” prefix=validator
time=“2020-06-19 10:18:00” level=error msg=“Failed to update assignments” error=“rpc error: code = Unavailable desc = Syncing to latest head, not ready to respond” prefix=validator
time=“2020-06-19 10:18:12” level=error msg=“Could not report validator’s rewards/penalties” error=“rpc error: code = Unavailable desc = Syncing to latest head, not ready to respond” prefix=validator slot=37504
time=“2020-06-19 10:18:12” level=error msg=“rpc error: code = Unavailable desc = Syncing to latest head, not ready to respond” prefix=validator
time=“2020-06-19 10:18:12” level=error msg=“Failed to update assignments” error="rpc error: code = Unavailable desc =

I think I’ve solved this by backing up the validator, removing both beacon node and validator, reinstalling and allowing it to sync, then restoring the keys.