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

Unknown command 'listpays' #3931

Closed
ghost opened this issue Aug 12, 2020 · 8 comments · Fixed by #3927
Closed

Unknown command 'listpays' #3931

ghost opened this issue Aug 12, 2020 · 8 comments · Fixed by #3927

Comments

@ghost
Copy link

ghost commented Aug 12, 2020

Issue and Steps to Reproduce

Sometimes (this happened a few times now) and maybe when interacting with spark-wallet, c-lightning loses listpays and responds:

{
   "code": -32601,
   "message": "Unknown command 'listpays'"
}

After a restart it knows about listpays again :-)

getinfo output

version: "v0.9.0-2-ge7d89cd"

@vincenzopalazzo
Copy link
Contributor

The plugin crashed for some reason, can you share your log?

@ghost
Copy link
Author

ghost commented Aug 12, 2020

Oh you are right but I restarted c-lightning again and the log is gone (output of lightningd). Stupid me! I will include it when it happens again.

@vincenzopalazzo
Copy link
Contributor

😄 Yep don't worry. I suggest (if you can) you to use the next release of lightningd (9.0.1) because include some refactoring inside the listpays, like #3915 but add also a little refactoring inside the format of the response more here #3888.

@ghost
Copy link
Author

ghost commented Aug 12, 2020

I will but only when spark-wallet is also up-to-date.

@ZmnSCPxj
Copy link
Contributor

ZmnSCPxj commented Aug 12, 2020

PR #3890 should also crash lightningd if any of the builtin plugins crash, which should help us debug, if you are willing to run on master and possibly have C-lightning crash outright.

@ghost
Copy link
Author

ghost commented Aug 12, 2020

I'm now on master and spark-wallet is still fine.

@cdecker
Copy link
Member

cdecker commented Aug 12, 2020

I'm pretty sure this is just another instance of #3915, which will be fixed by #3927 👍

@ghost
Copy link
Author

ghost commented Aug 12, 2020

Ok I close it for now

@ghost ghost closed this as completed Aug 12, 2020
This issue was closed.
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

Successfully merging a pull request may close this issue.

3 participants