Inconsistency between XUD status and synced status printed by getinfo call

peartobear commented 4 years ago

XUD status shows ready even though the env is out of sync

Screenshot 2020-08-26 at 2 39 10 PM

kilrau commented 4 years ago

Thanks for reporting this. But it looks like you are running a very outdated xud-docker version there, this is how it should look like

testnet > status
┌───────────┬────────────────────────────────────────────────┐
│ SERVICE   │ STATUS                                         │
├───────────┼────────────────────────────────────────────────┤
│ bitcoind  │ Ready (light mode)                             │
├───────────┼────────────────────────────────────────────────┤
│ litecoind │ Ready (light mode)                             │
├───────────┼────────────────────────────────────────────────┤
│ geth      │ Ready (light mode)                             │
├───────────┼────────────────────────────────────────────────┤
│ lndbtc    │ Syncing                                        │
├───────────┼────────────────────────────────────────────────┤
│ lndltc    │ Ready                                          │
├───────────┼────────────────────────────────────────────────┤

Didn't you get an update prompt?

peartobear commented 4 years ago

I did get it but I'm stuck in "Failed to wait for LNDBTC to be ready" so the env is not booting up anymore. It's a bad Tor circuit issue

kilrau commented 4 years ago

So it sounds like https://github.com/ExchangeUnion/xud-docker/issues/599 is your actual issue. If so, the only way please try to manually restart lnd via docker restart and watch lnd logs if that solves it. We should find an automated way to resolve this tor issue.

Once you manage to bring up your environment again, I bet above issue is solved through the upgrade. But let's see about that.

ExchangeUnion / xud-docker

Inconsistency between XUD status and synced status printed by getinfo call #690