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

signer: next_commitment_number mismatch causing the signer to exit #349

Closed
roeierez opened this issue Jan 21, 2024 · 2 comments
Closed

signer: next_commitment_number mismatch causing the signer to exit #349

roeierez opened this issue Jan 21, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@roeierez
Copy link
Collaborator

roeierez commented Jan 21, 2024

I can't create invoice and I found this on the logs:

[BreezSdk] {WARNING} (2024-01-21T20:34:41.700656Z) : policy failed: policy-other get_current_holder_commitment_info: invalid next holder commitment number: 831 != 832
[BreezSdk] {SEVERE} (2024-01-21T20:34:41.700688Z) : FAILED PRECONDITION: policy failure: get_current_holder_commitment_info: invalid next holder commitment number: 831 != 832
[BreezSdk] {SEVERE} (2024-01-21T20:34:41.703995Z) : BACKTRACE:
@devrandom
Copy link
Collaborator

we've been working on addressing this - see https://gitlab.com/lightning-signer/validating-lightning-signer/-/issues/207 and ElementsProject/lightning#7010

@cdecker cdecker changed the title Signer crash? signer: next_commitment_number mismatch causing the signer to exit Jan 26, 2024
@ErikDeSmedt ErikDeSmedt added the bug Something isn't working label Jan 30, 2024
@cdecker
Copy link
Collaborator

cdecker commented Feb 29, 2024

This has been fixed by the recent CLN release. Closing this now as we deploy the new versions on the server.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants