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

[Sparkswap] Error: 14 UNAVAILABLE: TCP Read failed #4

Closed
dmichael opened this issue May 16, 2019 · 4 comments
Closed

[Sparkswap] Error: 14 UNAVAILABLE: TCP Read failed #4

dmichael opened this issue May 16, 2019 · 4 comments
Labels
bug Something isn't working sparkswap

Comments

@dmichael
Copy link
Contributor

dmichael commented May 16, 2019

Description

When placing an order using the Sparkswap broker, user occasionally will get a TCP Read failed from the gRPC call to LND. This issue does not seem to arise from Sparkswap's stock install on x86.

Environment

  • Sparkswap Mini (ARM64)
  • BlackboxOS v0.1.30
  • Sparkswap Broker v0.6.2-beta
blackbox_sparkswap.1.srgiwkz3iwf7@sparkswap    | info: Request received: [OrderService:createBlockOrder] {"timestamp":"2019-05-16T14:20:16.861Z"}
blackbox_sparkswap.1.srgiwkz3iwf7@sparkswap    | info: Getting all block orders for market: BTC/LTC {"timestamp":"2019-05-16T14:20:16.869Z"}
blackbox_sparkswap.1.srgiwkz3iwf7@sparkswap    | info: Retrieving best priced from ASK up to 10000 {"timestamp":"2019-05-16T14:20:17.233Z"}
blackbox_sparkswap.1.srgiwkz3iwf7@sparkswap    | D0516 14:20:17.322003207      38 dns_resolver.cc:275]        Start resolving.
blackbox_sparkswap.1.srgiwkz3iwf7@sparkswap    | error: Error while handling request: [OrderService:createBlockOrder] {"timestamp":"2019-05-16T14:20:17.328Z"}
blackbox_sparkswap.1.srgiwkz3iwf7@sparkswap    | error: Error: 14 UNAVAILABLE: TCP Read failed
blackbox_sparkswap.1.srgiwkz3iwf7@sparkswap    |     at Object.exports.createStatusError (/home/app/node_modules/lnd-engine/node_modules/grpc/src/common.js:91:15)
blackbox_sparkswap.1.srgiwkz3iwf7@sparkswap    |     at Object.onReceiveStatus (/home/app/node_modules/lnd-engine/node_modules/grpc/src/client_interceptors.js:1204:28)
blackbox_sparkswap.1.srgiwkz3iwf7@sparkswap    |     at InterceptingListener._callNext (/home/app/node_modules/lnd-engine/node_modules/grpc/src/client_interceptors.js:568:42)
blackbox_sparkswap.1.srgiwkz3iwf7@sparkswap    |     at InterceptingListener.onReceiveStatus (/home/app/node_modules/lnd-engine/node_modules/grpc/src/client_interceptors.js:618:8)
blackbox_sparkswap.1.srgiwkz3iwf7@sparkswap    |     at callback (/home/app/node_modules/lnd-engine/node_modules/grpc/src/client_interceptors.js:845:24) {"timestamp":"2019-05-16T14:20:17.334Z"}
blackbox_sparkswap.1.srgiwkz3iwf7@sparkswap    | info: Request completed: [OrderService:createBlockOrder] {"timestamp":"2019-05-16T14:20:17.342Z"}
@dmichael dmichael added bug Something isn't working sparkswap labels May 16, 2019
@dmichael
Copy link
Contributor Author

Found similar issue grpc/grpc-node#692

@dmichael
Copy link
Contributor Author

Possible lead on a solution. Check to see if the gRPC connections are being explicitly closed as per dgraph-io/dgraph#2514

@dmichael
Copy link
Contributor Author

After a great deal of investigation, this issue is a Docker Swarm thing. The solution was to add deploy.endpoint_mode: dnsrr to the files. This solution has caused another quirk, which is that you can now not expose ports.

Summary: Docker Swarm should be considered dangerous and has been removed from the project.

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

No branches or pull requests

1 participant