Error: "No connection to first peer found"

[microlancer]

Issue and Steps to Reproduce

I closed a bunch of channels, upgraded my node to latest master (v0.6.3rc1-151-gd413fc7) and created a whole new set of channels. I should have plenty of outbound liquidity. But I can't send any funds.

When I attempt any payment, I get this error:

$ lc -k pay bolt11=lnbc13950n1pw97s46rzjqvxr7xwhgt9zjjj4cqphdvan2hpujrtpc6mt8925m0r6cxd3g8q57zy9pcqqs9qqqqqqqqlgqqqqq2qqjqrzjqwryaup9lh50kkranzgcdnn2fgvx390wgj5jd07rwr3vxeje0glc7zrwwyqq82qqqqqqqqlgqqqqqeqqjqrzjqwryaup9lh50kkranzgcdnn2fgvx390wgj5jd07rwr3vxeje0glc7zz75qqqr9qqqqqqqqlgqqqqqeqqjqfppqpx2yxaeda6lqs6ws43a0hxzu9p5a6k39dqqxqy9gcqpp5zfr7j6t5n8tf7rasn86pzc45gwyxf4836e378pwn3majgxrvc36ssp6dyvy56m0flcjj8dp4j0py547jsmpyarsjergscazq0dkvk5e9fepgm229cycv2ye4qazuvvw2e4kjhlpv3uthqnu7prgph8pe7egpcp50v8 retry_for=30
{ "code" : 204, "message" : "No connection to first peer found", "data" :
{
  "erring_index": 0,
  "failcode": 16394,
  "failcodename": "WIRE_UNKNOWN_NEXT_PEER",
  "erring_node": "038df0bd2fad1bfe42d177f18ea5e33543e2b855ef369d06bd94b81d2c87187c82",
  "erring_channel": "556292x777x1",
  "erring_direction": 1
} }

getinfo output

$ lc getinfo
{
  "id": "038df0bd2fad1bfe42d177f18ea5e33543e2b855ef369d06bd94b81d2c87187c82",
  "alias": "ghostofsatoshi",
  "color": "038df0",
  "num_peers": 30,
  "num_pending_channels": 13,
  "num_active_channels": 16,
  "num_inactive_channels": 3,
  "address": [
    {
      "type": "ipv4",
      "address": "178.238.237.16",
      "port": 9735
    }
  ],
  "binding": [
    {
      "type": "ipv4",
      "address": "0.0.0.0",
      "port": 9735
    }
  ],
  "version": "v0.6.3rc1-151-gd413fc7",
  "blockheight": 562354,
  "network": "bitcoin",
  "msatoshi_fees_collected": 157646
}

[cdecker]

It seems that getroute (called internally by pay) returned a route that included 556292x777x1 as a hop. The peer however seems to be offline which is why your node (038df0bd2fad1bfe42d177f18ea5e33543e2b855ef369d06bd94b81d2c87187c82) reported a failure to route through that channel. Either that channel is in the only available route, or it might be your direct peer (in which case using the direct channel is preferred).

[microlancer]

I restarted lightningd and the issue went away. I also don't see 556292x777x1 anymore. So I'm not sure which peer that was.

[microlancer]

Actually, I found this under listchannels:

    {
      "source": "0317d6b11e81729192aab651174991a32e566786a7abb45b88898ed27e218a15e6",
      "destination": "038df0bd2fad1bfe42d177f18ea5e33543e2b855ef369d06bd94b81d2c87187c82",
      "short_channel_id": "556292x777x1",
      "public": true,
      "satoshis": 700000,
      "message_flags": 1,
      "channel_flags": 2,
      "flags": 258,
      "active": false,
      "last_update": 1549653368,
      "base_fee_millisatoshi": 0,
      "fee_per_millionth": 1,
      "delay": 144
    },
    {
      "source": "038df0bd2fad1bfe42d177f18ea5e33543e2b855ef369d06bd94b81d2c87187c82",
      "destination": "0317d6b11e81729192aab651174991a32e566786a7abb45b88898ed27e218a15e6",
      "short_channel_id": "556292x777x1",
      "public": true,
      "satoshis": 700000,
      "message_flags": 1,
      "channel_flags": 1,
      "flags": 257,
      "active": false,
      "last_update": 1549469940,
      "base_fee_millisatoshi": 1000,
      "fee_per_millionth": 10,
      "delay": 14
    },

[microlancer]

The node 0317d6b11e81729192aab651174991a32e566786a7abb45b88898ed27e218a15e6 does not look to be a direct peer, as it's not shown under listpeers. Could the node have gone offline during the middle of payment? It's strange that even new invoices being paid to different destinations were also getting the exact same error.

[cdecker]

That's interesting, it seems to be picking up your old channels. The output is spent though (according to this) so your node should be removing that edge from its view of the network, but it somehow isn't. Have you started lightningd with some special setting for --rescan? Maybe it's skipping some blocks, or hasn't caught up with the blockchain head yet. The close happened 440 blocks ago.