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

Error subscribing to channel graph gRPC stream during sync process #2128

Closed
mrfelton opened this issue Apr 28, 2019 · 1 comment

Comments

2 participants
@mrfelton
Copy link
Member

commented Apr 28, 2019

Description

When creating a new wallet, or opening an existing one where some remaining sync is needed when opening the wallet, there is the following error in the logs:

zap:grpc [ERR]  CHANNELGRAPH ERROR: Error: router not started
    at Http2CallStream.call.on (call.js?4dae:52)
    at Http2CallStream.emit (events.js:187)
    at Http2CallStream.endCall (call-stream.js?85fb:58)
    at handlingTrailers (call-stream.js?85fb:147)
    at process._tickCallback (internal/process/next_tick.js:68) +19ms

The channel graph subscription doesn't get set up as a result.

This is a new problem after updating to the latest lnd.

In this commit some adjustments were made to delay the setting up of the subscriptions by 2 seconds after connecting to the api which resolves a similar problem when starting wallets that don't need to do any sync when opening.

The 2 second delay chosen there was completely arbitrary.

I'm not sure if there is a way to actually know when it is possible to connect to the stream.

Expected Behavior

Should not produce error and should set up subscription once lnd is ready to accept subscriptions.

Actual Behavior

Produces error and no active channel graph subscription

Possible Fix

  • Remove 2 second delay previously added.
  • If there is an error when trying to set up a subscription, set up a retry attempt on a backoff schedule.

Your Environment

  • Zap version: next
  • Operating System and version: all

@mrfelton mrfelton added this to the v0.5.0-beta milestone Apr 28, 2019

@korhaliv korhaliv self-assigned this Apr 29, 2019

korhaliv added a commit to korhaliv/zap-desktop that referenced this issue Apr 30, 2019

korhaliv added a commit to korhaliv/zap-desktop that referenced this issue Apr 30, 2019

korhaliv added a commit to korhaliv/zap-desktop that referenced this issue Apr 30, 2019

korhaliv added a commit to korhaliv/zap-desktop that referenced this issue Apr 30, 2019

korhaliv added a commit to korhaliv/zap-desktop that referenced this issue May 1, 2019

korhaliv added a commit to korhaliv/zap-desktop that referenced this issue May 1, 2019

korhaliv added a commit to korhaliv/zap-desktop that referenced this issue May 1, 2019

@mrfelton

This comment has been minimized.

Copy link
Member Author

commented May 1, 2019

closed via #2138

@mrfelton mrfelton closed this May 1, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.