Closed kilrau closed 4 years ago
Also, if we end up implementing this, we should test create flows of all 3 networks and testnet+mainnet with full nodes too to make sure we didn't break anything there @raladev .
Tested, it works, but I prefer the way without additional restart of xud. It seems more correct for me, but is required a little bit more work:
What do you think about it @kilrau?
Not needed anymore.
It looks like https://github.com/ExchangeUnion/xud-docker/pull/469 did not fix lnd status stuck in
lnd-XTC is Unlocked
within xud in 100% of the cases. Sometimes, even after xud was restarted, lnd status got stuck inis Unlocked
. One more xud restart always brought it up healthy though. So this issue is about verifying that unlocking lnd before restarting xud let's xud come up healthy 100%.If this turns out to be the case, we'll add a verification path to the xud restart logic of https://github.com/ExchangeUnion/xud-docker/pull/469 where we detect if
xucli getinfo
returns lnd statusis Unlocked
after restart. If so, we'll automatically restart xud once more and prompt for password once more. This second password prompt will only occur if xud indeed has problems with lnd, which shouldn't happen for most users.