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

lntop won't start #95

Open
caotic112 opened this issue Oct 10, 2022 · 8 comments
Open

lntop won't start #95

caotic112 opened this issue Oct 10, 2022 · 8 comments

Comments

@caotic112
Copy link

-Debian 11 , lntop v0.3.1

-After the recent lnd bug I can't start lntop anymore:

panic: send on closed channel

goroutine 23 [running]:
github.com/edouardparis/lntop/network/backend/lnd.Backend.SubscribeGraphEvents({0xc0000fc620?, {0x1208b10?, 0xc000097a90?}, 0xc0003441e0?}, {0x1207488, 0xc00033ed80}, 0x0?)
/home/lnd/lntop/network/backend/lnd/lnd.go:219 +0x27c
github.com/edouardparis/lntop/pubsub.(*PubSub).graphUpdates.func2()
/home/lnd/lntop/pubsub/pubsub.go:134 +0x4f
created by github.com/edouardparis/lntop/pubsub.(*PubSub).graphUpdates
/home/lnd/lntop/pubsub/pubsub.go:133 +0x158

-Somtimes it' just a black screen for a moment and then back to the shell with no output.

@edouardparis
Copy link
Owner

Thanks for reporting the issue, We will try to release a new binary with a fix ASAP

@caotic112
Copy link
Author

Not sure but I think that a pending channel during the bug is the cause.
The channel it's now up on my side but I can't get info about it:
[lncli] rpc error: code = Unknown desc = edge not found
The other side it's still offline I'm waiting to see if lntop fix itself when my peer comes back online.

@rkfg
Copy link
Contributor

rkfg commented Oct 11, 2022

It's probably this lnd issue then. Have you updated lnd to 0.15.2? There was another nasty bug recently so this update is required I think.

@caotic112
Copy link
Author

Yes I'm already on 0.15.2, I have done several restart but they dind't help.
I'm still waiting for the pending channel peer to come back up .

@rkfg
Copy link
Contributor

rkfg commented Oct 11, 2022

As a temporary measure you can comment out this line:

return err

(change it to // return err) and recompile lntop. If the problem is a missing policy it should help.

@caotic112
Copy link
Author

yes!!!it works again!

@rkfg
Copy link
Contributor

rkfg commented Oct 11, 2022

I think it should be patched, inability to query a single channel shouldn't be a show stopper. Just logging the error and continuing should be okay, at worst it'd be a stale channel showing outdated information.

@caotic112
Copy link
Author

thank you all for quick help

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