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

After long uptime, switching node results in: UNAVAILABLE: TCP Read failed #34

Open
janoside opened this issue Apr 17, 2019 · 0 comments
Labels
bug Something isn't working

Comments

@janoside
Copy link
Owner

Describe the bug
After long uptime, switching node results in: UNAVAILABLE: TCP Read failed

Environment (please complete the following information):

  • LND Version: 0.6
  • LND Admin Version: #39e2342

To Reproduce
Steps to reproduce the behavior:

  1. Launch app with multiple nodes configured
  2. Stay connected to single node for a "long time"
  3. Switch nodes
  4. See error

Screenshots or Log Output
https://pastebin.com/raw/cDMSjHcn

@janoside janoside added the bug Something isn't working label Apr 17, 2019
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

1 participant