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

moneyd fails at startup with RippledError(entryNotFound) #427

Open
corak-ii opened this issue Apr 21, 2018 · 5 comments
Open

moneyd fails at startup with RippledError(entryNotFound) #427

corak-ii opened this issue Apr 21, 2018 · 5 comments

Comments

@corak-ii
Copy link

corak-ii commented Apr 21, 2018

Prior to this, I had a PayChan that didn't get cleaned up properly due to a recently fixed issue with 'moneyd cleanup'. It was removed via manually transmitted transaction.

A day later, I tried to run moneyd again, now it doesn't start properly:
Here's a paste from my shell. Machine is running Win10.
Just guessing here: is the code assuming the payment channel should already exist?
Anyway, it was not clear to me exactly what call from ilp-connector causes this error, or how to debug it.

moneyd start --admin-api-port 7769
88
88
88
88,dPYba,,adPYba, ,adPPYba, 8b,dPPYba, ,adPPYba, 8b d8 ,adPPYb,88
88P' "88" "8a a8" "8a 88P' "8a a8P_____88 8b d8' a8" Y88 88 88 88 8b d8 88 88 8PP""""""" 8b d8' 8b 88
88 88 88 "8a, ,a8" 88 88 "8b, ,aa 8b,d8' "8a, ,d88 88 88 88 "YbbdP"' 88 88 "Ybbd8"' Y88' "8bbdP"Y8
d8'
d8'
starting moneyd
2018-04-21T19:14:36.696Z connector:route-broadcaster info generated random routing secret.
2018-04-21T19:14:36.711Z connector:accounts info add account. accountId=parent
2018-04-21T19:14:36.711Z connector:accounts warn DEPRECATED: plugin accessed deprecated _log property. accountId=parent
2018-04-21T19:14:36.711Z connector:accounts info add account. accountId=local
2018-04-21T19:14:36.727Z connector:accounts warn DEPRECATED: plugin accessed deprecated _log property. accountId=local
2018-04-21T19:14:36.727Z connector:accounts warn DEPRECATED: plugin accessed deprecated _store property. accountId=local
2018-04-21T19:14:36.727Z connector:accounts warn DEPRECATED: plugin accessed deprecated _store property. accountId=local
2018-04-21T19:14:39.932Z connector:app error [RippledError(entryNotFound)]

@dappelt
Copy link

dappelt commented Apr 23, 2018

Thanks for the report.

I assume the error originates from ilp-plugin-xrp-asym-client. The plugin tries to load it's payment channel in function _connect(). If it fails an error like [RippledError(entryNotFound)] is thrown back to the connector.

Running moneyd with the following command should give us a better debug log: DEBUG=ilp* moneyd start --admin-api-port 7769. Can you run moneyd with this command and post the log?

@sharafian
Copy link

For now, you can force a new channel by setting a 'name' field in your moneyd config (More on that here: https://github.com/interledgerjs/moneyd-xrp#multiple-instances)

We're working on patching the root of the problem. Thanks for reporting all these issues!

@corak-ii
Copy link
Author

@dappelt : I ran it (SET DEBUG=ilp*, followed by moneyd start --admin-api-port 7769)

Here's the output:

starting moneyd
2018-04-23T23:01:24.075Z connector:route-broadcaster info generated random routing secret.
2018-04-23T23:01:24.091Z connector:accounts info add account. accountId=parent
2018-04-23T23:01:24.091Z connector:accounts warn DEPRECATED: plugin accessed deprecated _log property. accountId=parent
2018-04-23T23:01:24.091Z connector:accounts info add account. accountId=local
2018-04-23T23:01:24.091Z connector:accounts warn DEPRECATED: plugin accessed deprecated _log property. accountId=local
2018-04-23T23:01:24.091Z connector:accounts warn DEPRECATED: plugin accessed deprecated _store property. accountId=local
2018-04-23T23:01:24.091Z connector:accounts warn DEPRECATED: plugin accessed deprecated _store property. accountId=local
2018-04-23T23:01:24.106Z ilp-plugin-btp debug registering data handler
2018-04-23T23:01:24.106Z ilp-plugin-btp debug registering money handler
2018-04-23T23:01:24.106Z ilp-plugin-btp debug registering data handler
2018-04-23T23:01:24.106Z ilp-plugin-btp debug registering money handler
2018-04-23T23:01:24.818Z ilp-plugin-btp debug connected to server
2018-04-23T23:01:25.021Z ilp-plugin-btp debug processing btp packet {"type":1,"requestId":1692009281,"data":{"protocolData":[]}}
2018-04-23T23:01:25.036Z ilp-plugin-btp debug received BTP packet (TYPE_RESPONSE, RequestId: 1692009281): {"protocolData":[]}
2018-04-23T23:01:25.268Z ilp-plugin-btp debug processing btp packet {"type":1,"requestId":1005140841,"data":{"protocolData":[{"protocolName":"info","contentType":2,"data":{"type":"Buffer","data":[123,34,99,104,97,110,110,101,108,34,58,34,55,49,56,49,68,66,54,55,70,57,56,49,66,56,50,52,55,57,69,70,65,68,57,52,49,55,65,57,66,67,55,66,53,54,69,69,67,49,69,54,49,49,54,68,54,67,66,50,54,49,49,48,54,65,53,70,56,52,68,57,51,49,68,68,34,44,34,99,108,105,101,110,116,67,104,97,110,110,101,108,34,58,34,67,51,65,54,69,54,49,70,54,68,67,53,56,67,65,53,67,57,67,65,65,65,69,69,68,69,52,49,66,57,50,57,48,54,53,57,70,65,54,53,66,67,54,54,57,57,66,49,70,48,69,49,65,66,67,54,51,56,55,51,54,68,66,69,34,44,34,97,100,100,114,101,115,115,34,58,34,114,75,54,103,50,85,89,99,52,71,112,81,72,56,68,89,100,80,71,55,119,121,119,121,81,98,120,107,74,112,81,84,84,78,34,44,34,97,99,99,111,117,110,116,34,58,34,103,46,115,99,121,108,108,97,46,99,108,105,101,110,116,46,80,88,54,104,69,105,68,65,119,101,102,49,102,122,82,110,53,88,78,109,82,70,112,101,90,88,74,77,102,71,104,84,57,81,68,48,52,117,83,88,101,69,119,34,44,34,99,117,114,114,101,110,99,121,83,99,97,108,101,34,58,54,125]}}]}}
2018-04-23T23:01:25.268Z ilp-plugin-btp debug received BTP packet (TYPE_RESPONSE, RequestId: 1005140841): {"protocolData":[{"protocolName":"info","contentType":2,"data":{"type":"Buffer","data":[123,34,99,104,97,110,110,101,108,34,58,34,55,49,56,49,68,66,54,55,70,57,56,49,66,56,50,52,55,57,69,70,65,68,57,52,49,55,65,57,66,67,55,66,53,54,69,69,67,49,69,54,49,49,54,68,54,67,66,50,54,49,49,48,54,65,53,70,56,52,68,57,51,49,68,68,34,44,34,99,108,105,101,110,116,67,104,97,110,110,101,108,34,58,34,67,51,65,54,69,54,49,70,54,68,67,53,56,67,65,53,67,57,67,65,65,65,69,69,68,69,52,49,66,57,50,57,48,54,53,57,70,65,54,53,66,67,54,54,57,57,66,49,70,48,69,49,65,66,67,54,51,56,55,51,54,68,66,69,34,44,34,97,100,100,114,101,115,115,34,58,34,114,75,54,103,50,85,89,99,52,71,112,81,72,56,68,89,100,80,71,55,119,121,119,121,81,98,120,107,74,112,81,84,84,78,34,44,34,97,99,99,111,117,110,116,34,58,34,103,46,115,99,121,108,108,97,46,99,108,105,101,110,116,46,80,88,54,104,69,105,68,65,119,101,102,49,102,122,82,110,53,88,78,109,82,70,112,101,90,88,74,77,102,71,104,84,57,81,68,48,52,117,83,88,101,69,119,34,44,34,99,117,114,114,101,110,99,121,83,99,97,108,101,34,58,54,125]}}]}
2018-04-23T23:01:25.268Z ilp-plugin-xrp-asym-client debug got info: { channel: '7181DB67F981B82479EFAD9417A9BC7B56EEC1E6116D6CB261106A5F84D931DD',
  clientChannel: 'C3A6E61F6DC58CA5C9CAAAEEDE41B9290659FA65BC6699B1F0E1ABC638736DBE',
  address: 'rK6g2UYc4GpQH8DYdPG7wywyQbxkJpQTTN',
  account: 'g.scylla.client.PX6hEiDAwef1fzRn5XNmRFpeZXJMfGhT9QD04uSXeEw',
  currencyScale: 6 }
2018-04-23T23:01:27.247Z connector:app error [RippledError(entryNotFound)]

Followed by a loop of this:

2018-04-23T23:02:24.658Z ilp-ws-reconnect debug websocket disconnected with 1006; reconnect in 5000
2018-04-23T23:02:26.916Z ilp-xrp-channel-watcher debug checking 0 channels for expiry
2018-04-23T23:02:30.225Z ilp-plugin-btp debug connected to server
2018-04-23T23:02:30.413Z ilp-plugin-btp debug processing btp packet {"type":1,"requestId":2715890246,"data":{"protocolData":[]}}
2018-04-23T23:02:30.413Z ilp-plugin-btp debug received BTP packet (TYPE_RESPONSE, RequestId: 2715890246): {"protocolData":[]}
2018-04-23T23:03:26.917Z ilp-xrp-channel-watcher debug checking 0 channels for expiry

@corak-ii
Copy link
Author

Setting "name": "foo" in the JSON file and running it again indeed made it establish another payment channel.

moneyd info shows that it exists

@dappelt
Copy link

dappelt commented Apr 24, 2018

Thanks for the debug log. We are working on a fix.

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

3 participants