Hmm. Yes from that it does appear that I’m connecting to an up to date server.
What about the xrpServer? Could that be the source of the problem?
From the console output, it’s not clear to me which connection is generating the exception:
starting moneyd
2019-03-25T16:37:23.937Z connector:route-broadcaster info generated random routing secret.
2019-03-25T16:37:23.944Z connector:accounts info add account. accountId=parent
2019-03-25T16:37:23.947Z connector:accounts info add account. accountId=local
2019-03-25T16:37:23.995Z connector:admin-api info listen called
2019-03-25T16:37:23.998Z connector:balance-middleware info initializing balance for account. accountId=parent minimumBalance=-Infinity maximumBalance=20000000
2019-03-25T16:37:23.999Z connector:balance-middleware info initializing balance for account. accountId=local minimumBalance=-Infinity maximumBalance=Infinity
2019-03-25T16:37:26.718Z connector:/home/vagrant/.nvm/versions/node/v8.15.1/lib/node_modules/moneyd-uplink-xrp/node_modules/ilp-plugin-xrp-asym-client/index.js[parent] info creating outgoing channel. from=rMNCEssSjFZkgaAp95AfKnXgMiVpncZLfA to=rJEi339p24K7SozLDyfsvrn14J1qLg4Z6A amount=10
2019-03-25T16:37:31.635Z connector:/home/vagrant/.nvm/versions/node/v8.15.1/lib/node_modules/moneyd-uplink-xrp/node_modules/ilp-plugin-xrp-asym-client/index.js[parent] info transaction complete
2019-03-25T16:37:40.605Z connector:app error Error: {"code":"F00","name":"NotAcceptedError","triggeredAt":"2019-03-25T16:37:40.875Z","data":"Cannot read property 'Account' of undefined","protocolData":[]}
at Plugin.callback (/home/vagrant/.nvm/versions/node/v8.15.1/lib/node_modules/moneyd-uplink-xrp/node_modules/ilp-plugin-btp/src/index.ts:666:20)
at Plugin.listener (/home/vagrant/.nvm/versions/node/v8.15.1/lib/node_modules/moneyd-uplink-xrp/node_modules/eventemitter2/lib/eventemitter2.js:290:17)
at Plugin.EventEmitter.emit (/home/vagrant/.nvm/versions/node/v8.15.1/lib/node_modules/moneyd-uplink-xrp/node_modules/eventemitter2/lib/eventemitter2.js:357:19)
at Plugin._handleIncomingBtpPacket (/home/vagrant/.nvm/versions/node/v8.15.1/lib/node_modules/moneyd-uplink-xrp/node_modules/ilp-plugin-btp/src/index.ts:711:14)
at Plugin._handleIncomingWsMessage (/home/vagrant/.nvm/versions/node/v8.15.1/lib/node_modules/moneyd-uplink-xrp/node_modules/ilp-plugin-btp/src/index.ts:528:18)
at WebSocketReconnector.EventEmitter.emit (/home/vagrant/.nvm/versions/node/v8.15.1/lib/node_modules/moneyd-uplink-xrp/node_modules/eventemitter2/lib/eventemitter2.js:354:19)
at WebSocket._instance.on (/home/vagrant/.nvm/versions/node/v8.15.1/lib/node_modules/moneyd-uplink-xrp/node_modules/ilp-plugin-btp/src/ws-reconnect.ts:120:70)
at emitOne (events.js:116:13)
at WebSocket.emit (events.js:211:7)
at Receiver.receiverOnMessage (/home/vagrant/.nvm/versions/node/v8.15.1/lib/node_modules/moneyd-uplink-xrp/node_modules/ilp-plugin-btp/node_modules/ws/lib/websocket.js:792:20)
Is that coming from the ILSP server or the XRP server?
I got this error sometime in February. It got resolved after 2 weeks - I didn’t do anything. However the old connectors were running like a charm (and they run now, as well) I’m just not able to create new instances on new machines. I would suggest work on your running configurations (if you have any) and wait for this to be resolved.
@DanCarroll and @Kate_Sills — Yesterday I was able to get past the error by changing the server key in .moneyd.test.json from strata-ilsp.com to testnet.ilpnetwork.dev.
I still have not been able to send funds to anyone other than myself, however. So there is another piece I’m still missing somewhere.
Looks like the issue has been fixed for strata-ilsp.com/testnet/xrp.
I have the same moneyd configuration as @christophersanborn and tried to get around the F00 NotAcceptedError in the last weeks. Today, I tried it again and the error was gone
However, while the sender (ilp-spsp) and receiver (ilp-spsp-server) report a successful transaction, the debug logs show some errors:
ilp-protocol-stream:Server:Connection handling reject: {"code":"F02","triggeredBy":"test.strata.xrpClients.MhH3tPqeEU962O4E6N8yp61ePgxVGtV3rtIhOYGmlY0","message":"failed to send packet: No clients connected for account 1Wn29sRYAy4WQMDWdKxl-83FzdbZEvJ95CPPUTsuSD4","data":{"type":"Buffer","data":[]}} +0ms
ilp-protocol-stream:Server:Connection unexpected error. code: F02, message: failed to send packet: No clients connected for account 1Wn29sRYAy4WQMDWdKxl-83FzdbZEvJ95CPPUTsuSD4, data: +0ms
ilp-protocol-stream:Server:Connection destroying connection with error: Error: Unexpected error while sending packet. Code: F02, message: failed to send packet: No clients connected for account 1Wn29sRYAy4WQMDWdKxl-83FzdbZEvJ95CPPUTsuSD4
at Connection.<anonymous> (/usr/lib/node_modules/ilp-spsp-server/node_modules/ilp-protocol-stream/src/connection.ts:1155:13)
at Generator.next (<anonymous>)
at /usr/lib/node_modules/ilp-spsp-server/node_modules/ilp-protocol-stream/src/connection.js:7:71
at new Promise (<anonymous>)
at __awaiter (/usr/lib/node_modules/ilp-spsp-server/node_modules/ilp-protocol-stream/src/connection.js:3:12)
at Connection.handleConnectorError (/usr/lib/node_modules/ilp-spsp-server/node_modules/ilp-protocol-stream/src/connection.js:778:16)
at Connection.<anonymous> (/usr/lib/node_modules/ilp-spsp-server/node_modules/ilp-protocol-stream/src/connection.ts:1059:21)
at Generator.next (<anonymous>)
at fulfilled (/usr/lib/node_modules/ilp-spsp-server/node_modules/ilp-protocol-stream/src/connection.js:4:58)
at process._tickCallback (internal/process/next_tick.js:68:7) +0ms
ilp-protocol-stream:Server:Connection error in error handler: Error: Unexpected error while sending packet. Code: F02, message: failed to send packet: No clients connected for account 1Wn29sRYAy4WQMDWdKxl-83FzdbZEvJ95CPPUTsuSD4
at Connection.<anonymous> (/usr/lib/node_modules/ilp-spsp-server/node_modules/ilp-protocol-stream/src/connection.ts:1155:13)
at Generator.next (<anonymous>)
at /usr/lib/node_modules/ilp-spsp-server/node_modules/ilp-protocol-stream/src/connection.js:7:71
at new Promise (<anonymous>)
at __awaiter (/usr/lib/node_modules/ilp-spsp-server/node_modules/ilp-protocol-stream/src/connection.js:3:12)
at Connection.handleConnectorError (/usr/lib/node_modules/ilp-spsp-server/node_modules/ilp-protocol-stream/src/connection.js:778:16)
at Connection.<anonymous> (/usr/lib/node_modules/ilp-spsp-server/node_modules/ilp-protocol-stream/src/connection.ts:1059:21)
at Generator.next (<anonymous>)
at fulfilled (/usr/lib/node_modules/ilp-spsp-server/node_modules/ilp-protocol-stream/src/connection.js:4:58)
at process._tickCallback (internal/process/next_tick.js:68:7) +2ms
ilp-protocol-stream:Server:Stream:1 destroying stream because of error: null +561ms
Not sure if there has been any progress on this - I am also getting errors when attempting to connect to the testnet as a client. Below is what my moneyd log looks like. Testing spsp and ilp-curl hang up and do not finish executing.
starting moneyd
2019-04-11T16:16:36.912Z connector:route-broadcaster info generated random routing secret.
2019-04-11T16:16:36.995Z connector:accounts info add account. accountId=parent
2019-04-11T16:16:37.685Z connector:accounts info add account. accountId=local
2019-04-11T16:16:38.160Z connector:admin-api info listen called
2019-04-11T16:16:38.170Z connector:balance-middleware info initializing balance for account. accountId=parent minimumBalance=-Infinity maximumBalance=20000000
2019-04-11T16:16:38.172Z connector:balance-middleware info initializing balance for account. accountId=local minimumBalance=-Infinity maximumBalance=Infinity
2019-04-11T16:16:39.493Z connector:/Users/Nikhil/.nvm/versions/node/v9.3.0/lib/node_modules/moneyd-uplink-xrp/node_modules/ilp-plugin-xrp-asym-client/index.js[parent] info creating outgoing channel. from=rMBR8W3Lgh2DuwLV1X1L92b3e8SEsZmNbT to=rJEi339p24K7SozLDyfsvrn14J1qLg4Z6A amount=10
2019-04-11T16:16:39.695Z connector:app error [RippledError(actNotFound)]
@bioround I’ve made some progress and got past the F02 - No clients connected for account error. I had to upgrade ilp-plugin-mini-accounts from 3.5.1 (specified in the package.json of moneyd) to the latest version 4.0.5. However, I am still not able to do complete transactions due to invalid claim signatures (ilp-plugin-xrp-asym-client#39). Could you run your moneyd/ilp-spsp/ilp-curl with DEBUG=* to get more verbose logging output?
@bioround I am not sure but it looks like the moneyd-uplink-xrp cannot validate your account. How did you create your wallet and how’s your .moneyd.test.json configured?
Thanks for your help. I think there must have been an issue with how moneyd configured my testnet address. I just went to the ripple testnet faucet and created a new testnet account for myself, so now it’s working.
I am using strata-ilsp.com/testnet/xrp but am still struggling to send money from one moneyd to another. It is hard to reproduce the errors, but these are the ones that appear the most:
Error processing BTP packet of type 7: Error: Invalid claim signature for: 1 (ilp-plugin-xrp-asym-client#39 ) — after this, both sides get out of sync and all subsequent transfers fail.
F02 - failed to send packet: No clients connected for account — on both sides, sender and receiver.
Error: Unable to establish connection, no packets meeting the minimum exchange precision of 3 digits made it through the path. — this happens occasionally on the sender’s side.
Today, I want to setup my own testnet connector and do some debugging there. Any ideas on how to get around these issues are very welcome
@martinlowinski@austin_king I believe that invalid claim error (and possibly the stream error) are due to this issue in ilp-plugin-xrp-asym-server. Merging that PR and updating the plugin should resolve the issue.
