Closed stefa2k closed 3 years ago
Will this be fixed by genesis?
Yes, it is currently under test with a few other changes that should be released in the next day or so.
I pulled in the latest changes but getting a different error now. Is this user error config or vouch bug?
{"level":"warn","service":"controller","impl":"standard","error":"failed to obtain attester duties: failed to request attester duties: GET failed with status 405: {\"code\":405,\"message\":\"METHOD_NOT_ALLOWED\",\"stacktraces\":[]}","time":"2020-11-27T18:43:19Z","message":"Failed to subscribe to beacon committees"} {"level":"error","service":"controller","impl":"standard","error":"failed to request proposer duties: GET failed with status 503: {\"code\":503,\"message\":\"SERVICE_UNAVAILABLE: beacon node is syncing: head slot is 63104, current slot is 66848\",\"stacktraces\":[]}","time":"2020-11-27T18:49:43Z","message":"Failed to obtain proposer duties"} {"level":"error","service":"controller","impl":"standard","error":"failed to request attester duties: GET failed with status 405: {\"code\":405,\"message\":\"METHOD_NOT_ALLOWED\",\"stacktraces\":[]}","time":"2020-11-27T18:49:43Z","message":"Failed to obtain attester duties"} {"level":"warn","service":"controller","impl":"standard","error":"failed to obtain attester duties: failed to request attester duties: GET failed with status 405: {\"code\":405,\"message\":\"METHOD_NOT_ALLOWED\",\"stacktraces\":[]}","time":"2020-11-27T18:49:43Z","message":"Failed to subscribe to beacon committees"}
The key line there is most likely:
{"level":"error","service":"controller","impl":"standard","error":"failed to request proposer duties: GET failed with status 503: {"code":503,"message":"SERVICE_UNAVAILABLE: beacon node is syncing: head slot is 63104, current slot is 66848","stacktraces":[]}","time":"2020-11-27T18:49:43Z","message":"Failed to obtain proposer duties"}
I suspect that the other errors are due to the fact that the node is syncing. Can you check again once the node is synced?
You are correct. All letting all nodes sync up, my issue is resolved.
This issue was fixed with vouch 1.0.0
Errors:
Workaround: Settings on prysm beacons: