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

xucli unlock / lncli unlock shows lnd unlocked when it actually didn't #1346

Closed
kilrau opened this issue Dec 4, 2019 · 2 comments
Closed

xucli unlock / lncli unlock shows lnd unlocked when it actually didn't #1346

kilrau opened this issue Dec 4, 2019 · 2 comments
Assignees
Labels

Comments

@kilrau
Copy link
Contributor

@kilrau kilrau commented Dec 4, 2019

Off-shoot from #1319 (comment):

Problem: lnd returning it successfully unlocked, when it didn't
Solution: call getinfo after unlock to verify unlock actually worked.

Details & how to reproduce: #1319 (comment)

@kilrau kilrau added bug P1 labels Dec 4, 2019
@kilrau kilrau added this to To do in 1.0.0-beta.1 via automation Dec 4, 2019
@kilrau

This comment has been minimized.

Copy link
Contributor Author

@kilrau kilrau commented Jan 15, 2020

Still seeing this occassionally with xud-docker setup. Mostly fixed by restarting lnd.

@kilrau

This comment has been minimized.

Copy link
Contributor Author

@kilrau kilrau commented Jan 15, 2020

Duplicate (ExchangeUnion/xud-docker#195). Closing here.

@kilrau kilrau closed this Jan 15, 2020
1.0.0-beta.1 automation moved this from To do to Done Jan 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
1.0.0-beta.1
  
Done
2 participants
You can’t perform that action at this time.