Skip to content
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

incorrect offset should provide clearer indications #109

Open
RaekwonIII opened this issue Aug 30, 2024 · 2 comments
Open

incorrect offset should provide clearer indications #109

RaekwonIII opened this issue Aug 30, 2024 · 2 comments

Comments

@RaekwonIII
Copy link
Collaborator

By now it has become clear that this message:

2024-08-30T08:28:56.951050Z    DEBUG    logger is ready    {"level": "debug", "encoder": "json", "format": "capitalColor", "file_options": null}
2024-08-30T08:28:56.954317Z    INFO    dkg-initiator    🪛 Initiator`s    {"Version": "v2.1.0"}
2024-08-30T08:28:58.047233Z    DEBUG    dkg-initiator    operator responded    {"IP": "https://lido-ssv.sre.ideasoft.io/", "method": "health_check", "status": 400}
2024-08-30T08:28:58.048343Z    ERROR    dkg-initiator    😥 Operator not healthy:     {"error": "incorrect offset", "IP": "https://lido-ssv.sre.ideasoft.io:443"}

generally indicates that the node is running a different version from the one performing the ping (or ceremony). But the error message should be clearer.

Instead of incorrect offset, it could say incorrect offset: likely due to version mismatch, or, even better incorrect offset: expected version v2.1.0, found <node version...

People keep opening tickets and asking questions about this, even if we add it to the Troubleshooting page, not everyone takes time to read it...

@pavelkrolevets
Copy link
Contributor

pavelkrolevets commented Sep 19, 2024

Fixed at PR

  • for ping unfortunately we cant unfortunately get a version from messages coming from operator from old versions v0.0.1, v1.0.1
  • added messages probably of old version, please upgrade

@pavelkrolevets
Copy link
Contributor

pavelkrolevets commented Oct 30, 2024

Now error looks like this, if try to init with old version operators:

initiator-1 | 2024-10-30T14:46:18.821331Z FATAL dkg-initiator 😥 Failed to initiate DKG ceremony: {"error": "some new operators returned errors, cant continue: error: operator ID: 1, operator 1 failed with: probably of old version, please upgrade invalid ssz encoding. first variable element offset indexes into fixed value data, operator probably of old version 1.*.*, please upgrade\nerror: operator ID: 2, operator 2 failed with: probably of old version, please upgrade invalid ssz encoding. first variable element offset indexes into fixed value data, operator probably of old version 1.*.*, please upgrade\nerror: operator ID: 3, operator 3 failed with: probably of old version, please upgrade invalid ssz encoding. first variable element offset indexes into fixed value data, operator probably of old version 1.*.*, please upgrade\nerror: operator ID: 4, operator 4 failed with: probably of old version, please upgrade invalid ssz encoding. first variable element offset indexes into fixed value data, operator probably of old version 1.*.*, please upgrade"}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants