lnd: SRVR: unable to start server: edge not found
Background
Issue is somewhat similar to what is there: https://github.com/lightningnetwork/lnd/issues/1938
I upgraded my node to the last version of LND. The node had been shutdown for about a month and caught up using the new version. It worked fine for about 12 hours, I could even send 2 payments, after that it just crashed (logs stopped for 1min and the node restarted after that).
...
2019-04-28 19:44:15.147 [DBG] CNCT: ChannelArbitrator(dd86576ac02a0a361d2e9086bb23cf8d139fccfd2bd82fb76f1cd947d4da5c0a:0): new block (height=573650) examining active HTLC's
2019-04-28 19:44:15.149 [DBG] CNCT: ChannelArbitrator(dd86576ac02a0a361d2e9086bb23cf8d139fccfd2bd82fb76f1cd947d4da5c0a:0): checking chain actions at height=573650
2019-04-28 19:44:15.156 [DBG] CNCT: ChannelArbitrator(2c056f7d16ba3802b348b8d2904d70ca8f4318bab3d50fa6dc2f3ac2f82ba3e1:0): new block (height=573650) examining active HTLC's
2019-04-28 19:44:15.156 [DBG] CNCT: ChannelArbitrator(2c056f7d16ba3802b348b8d2904d70ca8f4318bab3d50fa6dc2f3ac2f82ba3e1:0): checking chain actions at height=573650
2019-04-28 19:44:15.156 [DBG] CNCT: Starting ChannelArbitrator(5beab5e5b7d36e9eaff3d574f733460d89d147e1bed1bb1388740b02ffe539e5:0), htlc_set=(contractcourt.htlcSet) {
incomingHTLCs: (map[uint64]channeldb.HTLC) {
},
outgoingHTLCs: (map[uint64]channeldb.HTLC) {
}
}
2019-04-28 19:44:15.156 [INF] CNCT: ChannelArbitrator(5beab5e5b7d36e9eaff3d574f733460d89d147e1bed1bb1388740b02ffe539e5:0): starting state=StateDefault
2019-04-28 19:44:15.156 [DBG] CNCT: ChannelArbitrator(2c056f7d16ba3802b348b8d2904d70ca8f4318bab3d50fa6dc2f3ac2f82ba3e1:0): new block (height=573650) examining active HTLC's
2019-04-28 19:44:15.157 [DBG] CNCT: ChannelArbitrator(2c056f7d16ba3802b348b8d2904d70ca8f4318bab3d50fa6dc2f3ac2f82ba3e1:0): checking chain actions at height=573650
2019-04-28 19:44:15.164 [DBG] CNCT: ChannelArbitrator(5beab5e5b7d36e9eaff3d574f733460d89d147e1bed1bb1388740b02ffe539e5:0): new block (height=573650) examining active HTLC's
2019-04-28 19:44:15.164 [DBG] CNCT: ChannelArbitrator(5beab5e5b7d36e9eaff3d574f733460d89d147e1bed1bb1388740b02ffe539e5:0): checking chain actions at height=573650
2019-04-28 19:44:15.164 [DBG] CNCT: ChannelArbitrator(5beab5e5b7d36e9eaff3d574f733460d89d147e1bed1bb1388740b02ffe539e5:0): new block (height=573650) examining active HTLC's
2019-04-28 19:44:15.167 [DBG] CNCT: ChannelArbitrator(5beab5e5b7d36e9eaff3d574f733460d89d147e1bed1bb1388740b02ffe539e5:0): checking chain actions at height=573650
2019-04-28 19:44:15.259 [INF] DISC: Authenticated Gossiper is starting
2019-04-28 19:44:15.259 [INF] BRAR: Starting contract observer, watching for breaches.
2019-04-28 19:44:15.259 [INF] NTFN: New block epoch subscription
2019-04-28 19:44:15.266 [INF] CRTR: FilteredChainView starting
2019-04-28 19:44:19.566 [ERR] SRVR: unable to start server: edge not found
2019-04-28 19:44:19.566 [INF] RPCS: Stopping RPC Server
2019-04-28 19:44:19.571 [INF] LTND: Shutdown complete
Your environment
LND v0.6 bitcoind v0.17.1 Raspbian 9.4 I’m using a Raspberry, everything is stored on a hard drive
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 69 (21 by maintainers)
@fluidvoice how often does the Raspiblitz setup call
GetInfo? We’ve found a potential deadlock when pollingGetInfothat could cause the daemon to not shut down cleanly, which would explain why users are experiencing this database issue.@wpaulino @halseth we have about seven Pi nodes now experiencing this “edge not found” error: https://github.com/rootzoll/raspiblitz/issues/562#issuecomment-493715389
@fluidvoice Yes, I use Raspiblitz and yes I use Tor on my node. Currently, I have disabled Tor and the error persists.
Copy the diff into a file named
patch.txtand rungit apply patch.txt. Recompile, runlnd, and post the new error output.@fluidvoice TOR should have nothing to do with this error, it looks like the database state is non-consistent.