Re-broadcast funding tx

[fixone]

one other issue that I've encountered is that for instance I have one peer like this

{
      "id": "02f21e5594a92b26f1517906600bc5cef1fe6f8c39620ebb48a11c55661f3786ce",
      "connected": true,
      "netaddr": [
        "69.15.179.58:10735"
      ],
      "channels": [
        {
          "state": "CHANNELD_AWAITING_LOCKIN",
          "owner": "lightning_channeld",
          "funding_txid": "8422f21be96e09d55c6e1dcfffb03012f66df9c4eecfa95e85190401abd1b68f",
          "msatoshi_to_us": 1000000000,
          "msatoshi_total": 1000000000,
          "dust_limit_satoshis": 546,
          "max_htlc_value_in_flight_msat": 18446744073709552000,
          "channel_reserve_satoshis": 0,
          "htlc_minimum_msat": 0,
          "to_self_delay": 6,
          "max_accepted_htlcs": 483
        }
      ]
    }

but the funding tx doesn't seem to have been sent. Is there a way to re-broadcast it?
BTW, maybe adding an automatic re-broadcast from time to time if the tx is not confirmed (much like bitcoind is doing) would make things easier

[cdecker]

@fixone Rusty just addressed something similar with PR #1084, that should better handle the broadcast of the transaction in the future. However, it won't really help with your current channel I think.

If you have the debug logs of lightningd while it was broadcasting it should have the hex encoded transaction in the logs. You can take that one and broadcast it through bitcoin-cli sendrawtransaction [hexblob] manually.

[fixone]

I've already tried this, but forgot to mention that (because in between the time this transaction was not sent and the 'sendrawtransaction' was issued, I suppose) some of the inputs got mixed up (probably have been spent?) I now get

btc sendrawtransaction 020000000001018fb6d1ab010419855ea9cfeec4f96df61230b0ffcf1d6e5cd5096ee91bf222840100000000ffffffff0240420f0000000000220020c2e1f613b56ab4e4d3045ffe3647c29ccaf95fa168f8a60ce0d61e64c1ad7ff59095710200000000160014b18ffcac55e241080caa19464453c3ffb114bfae0247304402201642e903dfae0d42790b826de52c0d7d120c8d43c48655a55a2b920e18504134022018916a12981d0189ad70f6975d1238ba904a126a00bbb2166bf611db79e243a601210262c2a4707d670f3a10c1a956707307290bc54fcad79e86a09a6a80d1c706968b00000000
error code: -25
error message:
Missing inputs

[cdecker]

Seems this is a child of a transaction that was not broadcast in the first place. Are there more sendrawtransactions that you can share? I think this may be the change from another channel funding that also got stuck.

If you're ok with failing this channel I'd suggest using dev-fail to fail it, and dev-rescan-outputs to sync your wallet's state with bitcoind again. I'm working on a fix for this, but it's taking longer than expected.

[fixone]

I only have two channels in CHANNELD_AWAITING_LOCKIN for which the TX was not broadcasted, inputs, but I would imagine that at least one of them has known inputs (and after broadcasting the funding tx, also the second), but they both fail

$ btc sendrawtransaction 020000000001018fb6d1ab010419855ea9cfeec4f96df61230b0ffcf1d6e5cd5096ee91bf222840100000000ffffffff0240420f0000000000220020c2e1f613b56ab4e4d3045ffe3647c29ccaf95fa168f8a60ce0d61e64c1ad7ff59095710200000000160014b18ffcac55e241080caa19464453c3ffb114bfae0247304402201642e903dfae0d42790b826de52c0d7d120c8d43c48655a55a2b920e18504134022018916a12981d0189ad70f6975d1238ba904a126a00bbb2166bf611db79e243a601210262c2a4707d670f3a10c1a956707307290bc54fcad79e86a09a6a80d1c706968b00000000
error code: -25
error message:
Missing inputs
$ btc sendrawtransaction 02000000000101b8493a71b192f78a84b7519c766562294d4b98ebbd55aa3445ef82d351fc272d0100000000ffffffff0240420f00000000002200200cd1804f48db0e589ee179dc5681596ff2677ab5435689d6421bba91f95f05e968d8800200000000160014afc3e6029e48754a173537a27f4dc8ac783aa9a60247304402202ae8af1c337d474afc6e560adf600f6e549b5c10fc28c8a7026d427a406bf24202202141984e3add6c71e04ffc1401a21f1801467040e2a99f84bb0edd6e18d62dfe012103cbf28137dd25af0e105c7098630d06bc6a91d181808148b6f9d7c7430f238ada00000000
error code: -25
error message:
Missing inputs

here's the full peer list

{
  "peers": [
    {
      "id": "0231eee2441073c86d38f6085aedaf2bb7ad3d43af4c0e2669c1edd1a7d566ce31",
      "connected": true,
      "netaddr": [
        "[::ffff:77.251.249.36]:57468"
      ],
      "channels": [
        {
          "state": "CHANNELD_NORMAL",
          "owner": "lightning_channeld",
          "short_channel_id": "1284205:31:0",
          "funding_txid": "f43f941d5e42683a2ee2f6bcfb5de7457380db5fff2ea6f982c33de66a4d0536",
          "msatoshi_to_us": 1000000000,
          "msatoshi_total": 1000000000,
          "dust_limit_satoshis": 546,
          "max_htlc_value_in_flight_msat": 18446744073709552000,
          "channel_reserve_satoshis": 0,
          "htlc_minimum_msat": 0,
          "to_self_delay": 6,
          "max_accepted_htlcs": 483
        }
      ]
    },
    {
      "id": "03e103d5679dc41b96a0d11d8a9c359f9ee6f2eb3ba0e14e72d2b1918d03439d72",
      "connected": true,
      "netaddr": [
        "188.166.39.247:9735"
      ],
      "channels": [
        {
          "state": "CHANNELD_NORMAL",
          "owner": "lightning_channeld",
          "short_channel_id": "1284270:174:0",
          "funding_txid": "40cc700b1dd51f1eb5ed16f3fbc0de21807946b77ab0e4cca057b45bc379a281",
          "msatoshi_to_us": 1000000000,
          "msatoshi_total": 1000000000,
          "dust_limit_satoshis": 546,
          "max_htlc_value_in_flight_msat": 18446744073709552000,
          "channel_reserve_satoshis": 0,
          "htlc_minimum_msat": 0,
          "to_self_delay": 6,
          "max_accepted_htlcs": 483
        }
      ]
    },
    {
      "id": "033dd7f388fdbf33915c68b548883b899516a8ed7da14ae5eff03ad9f9ab1fe7ad",
      "connected": false,
      "channels": [
        {
          "state": "CHANNELD_NORMAL",
          "short_channel_id": "1284270:175:0",
          "funding_txid": "ec84b4163e6ccf0a0859fb57d441fcb9b99d4abb18dc28fd8d14413cb45a7351",
          "msatoshi_to_us": 991979118,
          "msatoshi_total": 1000000000,
          "dust_limit_satoshis": 546,
          "max_htlc_value_in_flight_msat": 18446744073709552000,
          "channel_reserve_satoshis": 0,
          "htlc_minimum_msat": 0,
          "to_self_delay": 6,
          "max_accepted_htlcs": 483
        }
      ]
    },
    {
      "id": "0316b3d2fac93a0638994b198ef19a548ad141874dc102c4b779feb3930bc46e20",
      "connected": true,
      "netaddr": [
        "142.4.213.42:9736"
      ],
      "channels": [
        {
          "state": "CHANNELD_NORMAL",
          "owner": "lightning_channeld",
          "short_channel_id": "1284270:176:0",
          "funding_txid": "e1dbd7017e58a2bab7599fe80793c748ab8441a6cbe3821724bbdfbd9e51b92c",
          "msatoshi_to_us": 899997800,
          "msatoshi_total": 1000000000,
          "dust_limit_satoshis": 546,
          "max_htlc_value_in_flight_msat": 18446744073709552000,
          "channel_reserve_satoshis": 0,
          "htlc_minimum_msat": 0,
          "to_self_delay": 6,
          "max_accepted_htlcs": 483
        }
      ]
    },
    {
      "id": "027e92b4fa1988ae5b0d44b87da80ab8875312fdae6631a8896851bc41857e66aa",
      "connected": true,
      "netaddr": [
        "133.18.23.0:9735"
      ],
      "channels": [
        {
          "state": "CHANNELD_NORMAL",
          "owner": "lightning_channeld",
          "short_channel_id": "1284270:177:0",
          "funding_txid": "c590a2cde116c74cd04facd2364ee6b8b9b667b92f56cc52bec5d1b5c724bb87",
          "msatoshi_to_us": 1000000000,
          "msatoshi_total": 1000000000,
          "dust_limit_satoshis": 546,
          "max_htlc_value_in_flight_msat": 18446744073709552000,
          "channel_reserve_satoshis": 0,
          "htlc_minimum_msat": 0,
          "to_self_delay": 6,
          "max_accepted_htlcs": 483
        }
      ]
    },
    {
      "id": "034fd1f523d694f340f2ee92971a04f837df3e910568222b889ad51b4b826ff361",
      "connected": false,
      "channels": [
        {
          "state": "CHANNELD_NORMAL",
          "short_channel_id": "1284356:186:0",
          "funding_txid": "96eba683e478c2f1b633f821ad66c067c38b5e0dbe91482aa0eb09752d690617",
          "msatoshi_to_us": 1000000000,
          "msatoshi_total": 1000000000,
          "dust_limit_satoshis": 546,
          "max_htlc_value_in_flight_msat": 18446744073709552000,
          "channel_reserve_satoshis": 0,
          "htlc_minimum_msat": 0,
          "to_self_delay": 6,
          "max_accepted_htlcs": 483
        }
      ]
    },
    {
      "id": "03c977ccfde5f30b43bcadd69dc1a1e8a29359824b8bddd44d9bf526a2b3f2bf37",
      "connected": true,
      "netaddr": [
        "54.86.199.43:9735"
      ],
      "channels": [
        {
          "state": "CHANNELD_AWAITING_LOCKIN",
          "owner": "lightning_channeld",
          "funding_txid": "2d27fc51d382ef4534aa55bdeb984b4d296265769c51b7848af792b1713a49b8",
          "msatoshi_to_us": 1000000000,
          "msatoshi_total": 1000000000,
          "dust_limit_satoshis": 546,
          "max_htlc_value_in_flight_msat": 18446744073709552000,
          "channel_reserve_satoshis": 0,
          "htlc_minimum_msat": 0,
          "to_self_delay": 6,
          "max_accepted_htlcs": 483
        }
      ]
    },
    {
      "id": "02f21e5594a92b26f1517906600bc5cef1fe6f8c39620ebb48a11c55661f3786ce",
      "connected": true,
      "netaddr": [
        "69.15.179.58:10735"
      ],
      "channels": [
        {
          "state": "CHANNELD_AWAITING_LOCKIN",
          "owner": "lightning_channeld",
          "funding_txid": "8422f21be96e09d55c6e1dcfffb03012f66df9c4eecfa95e85190401abd1b68f",
          "msatoshi_to_us": 1000000000,
          "msatoshi_total": 1000000000,
          "dust_limit_satoshis": 546,
          "max_htlc_value_in_flight_msat": 18446744073709552000,
          "channel_reserve_satoshis": 0,
          "htlc_minimum_msat": 0,
          "to_self_delay": 6,
          "max_accepted_htlcs": 483
        }
      ]
    },
    {
      "id": "03172377a939b21aadab64943ac82fc54a6600db48812dec9046c78abd78f5a0a2",
      "connected": true,
      "netaddr": [
        "88.99.209.230:9735"
      ],
      "channels": [
        {
          "state": "CHANNELD_AWAITING_LOCKIN",
          "owner": "lightning_channeld",
          "funding_txid": "8be2b4d62ec1caf616e803d9c44c707e8a5360ceca55ff574970154de1223424",
          "msatoshi_to_us": 1000000000,
          "msatoshi_total": 1000000000,
          "dust_limit_satoshis": 546,
          "max_htlc_value_in_flight_msat": 18446744073709552000,
          "channel_reserve_satoshis": 0,
          "htlc_minimum_msat": 0,
          "to_self_delay": 6,
          "max_accepted_htlcs": 483
        }
      ]
    },
    {
      "id": "0215b7a76fba355117f916473509719c5e9c3b57a0092f1395ceeea41f4b03c4f0",
      "connected": true,
      "netaddr": [
        "[::ffff:5.9.5.135]:5604"
      ],
      "channels": [
        {
          "state": "CHANNELD_NORMAL",
          "owner": "lightning_channeld",
          "short_channel_id": "1284585:53:1",
          "funding_txid": "5c17813733cea6ae42204f29d0c0e7cf6164c5d83c75958654018601929174d2",
          "msatoshi_to_us": 0,
          "msatoshi_total": 900000000,
          "dust_limit_satoshis": 546,
          "max_htlc_value_in_flight_msat": 18446744073709552000,
          "channel_reserve_satoshis": 0,
          "htlc_minimum_msat": 0,
          "to_self_delay": 6,
          "max_accepted_htlcs": 483
        }
      ]
    },
    {
      "state": "GOSSIPING",
      "id": "03c55a42cda1f6dce6e44dfdb279a73d319ce55f2d82c293ca6090504f0a127c91",
      "netaddr": [
        "[::ffff:174.149.126.134]:49252"
      ],
      "connected": true,
      "owner": "lightning_gossipd"
    }
  ]
}

anyway I will dev-fail the channels and start again with them

[fixone]

However here's an interesting situation

2018-02-24T12:10:57.740Z lightning_gossipd(4673): Responder: Act 1
2018-02-24T12:10:57.740Z lightning_gossipd(4673): Responder: handshake failed act_one_responder2:931
2018-02-24T12:11:03.632Z lightningd(4665): Connected json input
2018-02-24T12:11:03.633Z lightningd(4665): 03172377a939b21aadab64943ac82fc54a6600db48812dec9046c78abd78f5a0a2 chan #30: Peer internal error CHANNELD_AWAITING_LOCKIN:
2018-02-24T12:11:03.633Z lightningd(4665):      03172377a939b21aadab64943ac82fc54a6600db48812dec9046c78abd78f5a0a2 chan #30: ... Failing due to dev-fail command
2018-02-24T12:11:03.633Z lightningd(4665): 03172377a939b21aadab64943ac82fc54a6600db48812dec9046c78abd78f5a0a2 chan #30: Peer permanent failure in CHANNELD_AWAITING_LOCKIN: Internal error
2018-02-24T12:11:03.633Z lightningd(4665): lightning_channeld-03172377a939b21aadab64943ac82fc54a6600db48812dec9046c78abd78f5a0a2 chan #30: Status closed, but not exited. Killing
2018-02-24T12:11:03.633Z lightningd(4665):       (tx 38226d9ec5c3d2909a7aa486313fc9773ef9952289361871a8b666a709d9b6b5)
2018-02-24T12:11:03.635Z lightningd(4665): sendrawtransaction: 02000000000101243422e14d15704957ff55cace60538a7e704cc4d903e816f6cac12ed6b4e28b00000000008bd46180018b410f0000000000220020f3be20
02308867d77061deedf8d7a67e253e5fa4a4b8db2a856ab989f110013b0400483045022100d097fd463c224d77f453deb407c7da46f37578927fb046b31e483ea37b63e14d0220323e00c2495346418eeccb171b7bc064dd387ebcfc42638
aff40410b24c92f910147304402207cb66fc96e5a6c2dafba767b282150d95682f493c1cfb9f8d5d0a2b65f0a029e02200d5a503c36f096e1057555e51743d673d69a6e784946f5d9c7edd1d3a5b9a57b014752210237060ab6fdd8d72897
8a2aebdeea9c4456a17ef5fb0c19ce82dd0eda595a7d802103bbba0788fe6ee47c463cd3ff2059e42ff9934f7f14fa2053fed60cea53f62ec152ae3ff26220
2018-02-24T12:11:03.636Z lightningd(4665):jcon fd 16: Success
2018-02-24T12:11:03.636Z lightning_gossipd(4673): Forgetting remote peer 03172377a939b21aadab64943ac82fc54a6600db48812dec9046c78abd78f5a0a2
2018-02-24T12:11:03.642Z lightningd(4665): sendrawtx exit 25, gave error code: -25?error message:?Missing inputs?
2018-02-24T12:11:04.351Z lightning_gossipd(4673): peer_in WIRE_PING
2018-02-24T12:11:04.351Z lightning_gossipd(4673): peer_out WIRE_PONG

[fixone]

And for the other one as well

2018-02-24T12:11:17.337Z lightningd(4665): Connected json input
2018-02-24T12:11:17.338Z lightningd(4665): 02f21e5594a92b26f1517906600bc5cef1fe6f8c39620ebb48a11c55661f3786ce chan #29: Peer internal error CHANNELD_AWAITING_LOCKIN:
2018-02-24T12:11:17.338Z lightningd(4665):      02f21e5594a92b26f1517906600bc5cef1fe6f8c39620ebb48a11c55661f3786ce chan #29: ... Failing due to dev-fail command
2018-02-24T12:11:17.338Z lightningd(4665): 02f21e5594a92b26f1517906600bc5cef1fe6f8c39620ebb48a11c55661f3786ce chan #29: Peer permanent failure in CHANNELD_AWAITING_LOCKIN: Internal error
2018-02-24T12:11:17.338Z lightningd(4665): lightning_channeld-02f21e5594a92b26f1517906600bc5cef1fe6f8c39620ebb48a11c55661f3786ce chan #29: Status closed, but not exited. Killing
2018-02-24T12:11:17.338Z lightningd(4665):       (tx 811e72ea414fb8dcbc910316b15b87e36d5081ff4e35e041a5edbbe8494a20f3)
2018-02-24T12:11:17.339Z lightningd(4665): sendrawtransaction: 020000000001018fb6d1ab010419855ea9cfeec4f96df61230b0ffcf1d6e5cd5096ee91bf2228400000000004ff6f680018b410f0000000000220020dcfe674861d414c16a7182bb2fe689d51ee9e4c7f15193e553e9a0caa2168065040047304402206ebd76ca4d4437e4871fe4cb2fc926da1521c9421f8e296880654e86db8de1c8022021a904283e4382e92cfd076e8bdc430b88b055818715f79fb5676b1c6edb7fdf0147304402207359562e73d964968cfedd90338063f8c918dffc7d73fa75827df10508ae654b0220638b1239de9d5afad00f0e7216a341c996d3b81b859107316fe6ac1bd7296aa3014752210225556eccf9d85d574406fd854a12a073bea50fb1173e18278cbae1edaa0da7bd2102bc8bab023a8d9e07c740ada8511ecbfafb401c44e07121e5da58773f99392b5a52ae1c2f9720
2018-02-24T12:11:17.339Z lightningd(4665):jcon fd 16: Success
2018-02-24T12:11:17.339Z lightning_gossipd(4673): Forgetting remote peer 02f21e5594a92b26f1517906600bc5cef1fe6f8c39620ebb48a11c55661f3786ce
2018-02-24T12:11:17.346Z lightningd(4665): sendrawtx exit 25, gave error code: -25?error message:?Missing inputs?

[fixone]

decoderawtransaction for

02000000000101243422e14d15704957ff55cace60538a7e704cc4d903e816f6cac12ed6b4e28b00000000008bd46180018b410f0000000000220020f3be2002308867d77061deedf8d7a67e253e5fa4a4b8db2a856ab989f110013b0400483045022100d097fd463c224d77f453deb407c7da46f37578927fb046b31e483ea37b63e14d0220323e00c2495346418eeccb171b7bc064dd387ebcfc42638aff40410b24c92f910147304402207cb66fc96e5a6c2dafba767b282150d95682f493c1cfb9f8d5d0a2b65f0a029e02200d5a503c36f096e1057555e51743d673d69a6e784946f5d9c7edd1d3a5b9a57b014752210237060ab6fdd8d728978a2aebdeea9c4456a17ef5fb0c19ce82dd0eda595a7d802103bbba0788fe6ee47c463cd3ff2059e42ff9934f7f14fa2053fed60cea53f62ec152ae3ff26220

shows

{
  "txid": "38226d9ec5c3d2909a7aa486313fc9773ef9952289361871a8b666a709d9b6b5",
  "hash": "39e8e1950214ef9741256b5ec06f817d226d0934fd26d46c9a1aa4ce3d356fad",
  "version": 2,
  "size": 315,
  "vsize": 150,
  "locktime": 543355455,
  "vin": [
    {
      "txid": "8be2b4d62ec1caf616e803d9c44c707e8a5360ceca55ff574970154de1223424",
      "vout": 0,
      "scriptSig": {
        "asm": "",
        "hex": ""
      },
      "txinwitness": [
        "",
        "3045022100d097fd463c224d77f453deb407c7da46f37578927fb046b31e483ea37b63e14d0220323e00c2495346418eeccb171b7bc064dd387ebcfc42638aff40410b24c92f9101",
        "304402207cb66fc96e5a6c2dafba767b282150d95682f493c1cfb9f8d5d0a2b65f0a029e02200d5a503c36f096e1057555e51743d673d69a6e784946f5d9c7edd1d3a5b9a57b01",
        "52210237060ab6fdd8d728978a2aebdeea9c4456a17ef5fb0c19ce82dd0eda595a7d802103bbba0788fe6ee47c463cd3ff2059e42ff9934f7f14fa2053fed60cea53f62ec152ae"
      ],
      "sequence": 2153895051
    }
  ],
  "vout": [
    {
      "value": 0.00999819,
      "n": 0,
      "scriptPubKey": {
        "asm": "0 f3be2002308867d77061deedf8d7a67e253e5fa4a4b8db2a856ab989f110013b",
        "hex": "0020f3be2002308867d77061deedf8d7a67e253e5fa4a4b8db2a856ab989f110013b",
        "type": "witness_v0_scripthash"
      }
    }
  ]
}

which doesn't seem right to me in txinwitness, is it?

[cdecker]

Looks ok to me, that's an empty push (indicating a segwit v0 script), 2 signatures and the push of the P2WSH script. That's a 2-of-2 multisig output that is being spent.

PS: the decode you show doesn't match the hex tx above 😉

[fixone]

yes, right, I forgot that it's supposed to be a multisig tx being spent, thus 2 signatures required.
as for decoderawtransaction, my client is "version": 150100, and that's what it gives me, here's a complete output

$ btc getinfo
{
  "deprecation-warning": "WARNING: getinfo is deprecated and will be fully removed in 0.16. Projects should transition to using getblockchaininfo, getnetworkinfo, and getwalletinfo before upgrading to 0.16",
  "version": 150100,
  "protocolversion": 70015,
  "walletversion": 139900,
  "balance": 0.00000000,
  "blocks": 1286058,
  "timeoffset": 0,
  "connections": 21,
  "proxy": "",
  "difficulty": 1549169.053332807,
  "testnet": true,
  "keypoololdest": 1516528622,
  "keypoolsize": 2000,
  "paytxfee": 0.00000000,
  "relayfee": 0.00001000,
  "errors": "Warning: unknown new rules activated (versionbit 28)"
}
$ btc decoderawtransaction 02000000000101243422e14d15704957ff55cace60538a7e704cc4d903e816f6cac12ed6b4e28b00000000008bd46180018b410f0000000000220020f3be2002308867d77061deedf8d7a67e253e5fa4a4b8db2a856ab989f110013b0400483045022100d097fd463c224d77f453deb407c7da46f37578927fb046b31e483ea37b63e14d0220323e00c2495346418eeccb171b7bc064dd387ebcfc42638aff40410b24c92f910147304402207cb66fc96e5a6c2dafba767b282150d95682f493c1cfb9f8d5d0a2b65f0a029e02200d5a503c36f096e1057555e51743d673d69a6e784946f5d9c7edd1d3a5b9a57b014752210237060ab6fdd8d728978a2aebdeea9c4456a17ef5fb0c19ce82dd0eda595a7d802103bbba0788fe6ee47c463cd3ff2059e42ff9934f7f14fa2053fed60cea53f62ec152ae3ff26220
{
  "txid": "38226d9ec5c3d2909a7aa486313fc9773ef9952289361871a8b666a709d9b6b5",
  "hash": "39e8e1950214ef9741256b5ec06f817d226d0934fd26d46c9a1aa4ce3d356fad",
  "version": 2,
  "size": 315,
  "vsize": 150,
  "locktime": 543355455,
  "vin": [
    {
      "txid": "8be2b4d62ec1caf616e803d9c44c707e8a5360ceca55ff574970154de1223424",
      "vout": 0,
      "scriptSig": {
        "asm": "",
        "hex": ""
      },
      "txinwitness": [
        "",
        "3045022100d097fd463c224d77f453deb407c7da46f37578927fb046b31e483ea37b63e14d0220323e00c2495346418eeccb171b7bc064dd387ebcfc42638aff40410b24c92f9101",
        "304402207cb66fc96e5a6c2dafba767b282150d95682f493c1cfb9f8d5d0a2b65f0a029e02200d5a503c36f096e1057555e51743d673d69a6e784946f5d9c7edd1d3a5b9a57b01",
        "52210237060ab6fdd8d728978a2aebdeea9c4456a17ef5fb0c19ce82dd0eda595a7d802103bbba0788fe6ee47c463cd3ff2059e42ff9934f7f14fa2053fed60cea53f62ec152ae"
      ],
      "sequence": 2153895051
    }
  ],
  "vout": [
    {
      "value": 0.00999819,
      "n": 0,
      "scriptPubKey": {
        "asm": "0 f3be2002308867d77061deedf8d7a67e253e5fa4a4b8db2a856ab989f110013b",
        "hex": "0020f3be2002308867d77061deedf8d7a67e253e5fa4a4b8db2a856ab989f110013b",
        "type": "witness_v0_scripthash"
      }
    }
  ]
}

Oh, and remeber that I have two channels in this situation, so there are two rawtx (the other one is also somewhere in this thread) i.e.

{
  "txid": "811e72ea414fb8dcbc910316b15b87e36d5081ff4e35e041a5edbbe8494a20f3",
  "hash": "85723e3a3c28e5c6e2fa1a3ca3c331a301179a3b6d387b10884d9c023d5f9419",
  "version": 2,
  "size": 314,
  "vsize": 149,
  "locktime": 546778908,
  "vin": [
    {
      "txid": "8422f21be96e09d55c6e1dcfffb03012f66df9c4eecfa95e85190401abd1b68f",
      "vout": 0,
      "scriptSig": {
        "asm": "",
        "hex": ""
      },
      "txinwitness": [
        "",
        "304402206ebd76ca4d4437e4871fe4cb2fc926da1521c9421f8e296880654e86db8de1c8022021a904283e4382e92cfd076e8bdc430b88b055818715f79fb5676b1c6edb7fdf01",
        "304402207359562e73d964968cfedd90338063f8c918dffc7d73fa75827df10508ae654b0220638b1239de9d5afad00f0e7216a341c996d3b81b859107316fe6ac1bd7296aa301",
        "52210225556eccf9d85d574406fd854a12a073bea50fb1173e18278cbae1edaa0da7bd2102bc8bab023a8d9e07c740ada8511ecbfafb401c44e07121e5da58773f99392b5a52ae"
      ],
      "sequence": 2163668559
    }
  ],
  "vout": [
    {
      "value": 0.00999819,
      "n": 0,
      "scriptPubKey": {
        "asm": "0 dcfe674861d414c16a7182bb2fe689d51ee9e4c7f15193e553e9a0caa2168065",
        "hex": "0020dcfe674861d414c16a7182bb2fe689d51ee9e4c7f15193e553e9a0caa2168065",
        "type": "witness_v0_scripthash"
      }
    }
  ]
}

[fixone]

Okay I did some log-digging by going upstream on each transaction being spent (raw transactions at the end). The summary is this
8422f21be96e09d55c6e1dcfffb03012f66df9c4eecfa95e85190401abd1b68f spends 2d27fc51d382ef4534aa55bdeb984b4d296265769c51b7848af792b1713a49b8
2d27fc51d382ef4534aa55bdeb984b4d296265769c51b7848af792b1713a49b8 spends 96eba683e478c2f1b633f821ad66c067c38b5e0dbe91482aa0eb09752d690617 (output 1)
9cf727bc8589a9810d2501df350b66aa49fe28f84a522069250510fe0e7fb467 spends 96eba683e478c2f1b633f821ad66c067c38b5e0dbe91482aa0eb09752d690617 (output 1)

So two of those transactions 9cf727bc8589a9810d2501df350b66aa49fe28f84a522069250510fe0e7fb467 (broadcasted) and 2d27fc51d382ef4534aa55bdeb984b4d296265769c51b7848af792b1713a49b8 (not broadcasted) spend the same output, thus I've looked for relevant info about those in the log, here's what I got

2018-02-22T18:27:19.859Z lightningd(32119): Owning output 1 42998592 (SEGWIT) txid 2d27fc51d382ef4534aa55bdeb984b4d296265769c51b7848af792b1713a49b8
2018-02-22T18:27:19.859Z lightningd(32119):      (tx 2d27fc51d382ef4534aa55bdeb984b4d296265769c51b7848af792b1713a49b8)
2018-02-22T18:27:19.859Z lightningd(32119): sendrawtransaction: 020000000001011706692d7509eba02a4891be0d5e8bc367c066ad21f833b6f1c278e483a6eb960100000000ffffffff0240420f0000000000220020deffcaed043020e7a9b2164102cc39259e58bdc4454389bee1b6f05de4cf8de4401b900200000000160014b739aac5c1a86c35d53836da6b6acbba776a3cf102483045022100bb3aa46662d012035432527e1571b0f7f31201372faeea70864928394563e96702206484f34845ef956e9ef7816666d3d27d952af520a41af8a4ee3ef0feb96e40aa0121039f6c70bd24d26a11fa17b7146e8a20e2cdc5646fb79caa654fb8934ccb6c5a6600000000
2018-02-22T18:27:19.860Z lightningd(32119): Client: Received message 9 from client
2018-02-22T18:27:19.891Z lightningd(32119): lightning_channeld-03c977ccfde5f30b43bcadd69dc1a1e8a29359824b8bddd44d9bf526a2b3f2bf37 chan #25: pid 17518, msgfd 31
2018-02-22T18:27:19.891Z lightningd(32119): 03c977ccfde5f30b43bcadd69dc1a1e8a29359824b8bddd44d9bf526a2b3f2bf37 chan #25: Waiting for funding confirmations
2018-02-22T18:27:19.891Z lightningd(32119): 03c977ccfde5f30b43bcadd69dc1a1e8a29359824b8bddd44d9bf526a2b3f2bf37 chan #25: Ignoring fee limits!
2018-02-22T18:27:19.892Z lightningd(32119):jcon fd 16: Success
2018-02-22T18:27:19.900Z lightningd(32119): sendrawtx exit 26, gave error code: -26?error message:?66: min relay fee not met?
2018-02-22T18:27:19.900Z lightningd(32119): 03c977ccfde5f30b43bcadd69dc1a1e8a29359824b8bddd44d9bf526a2b3f2bf37 chan #25: Peer internal error CHANNELD_AWAITING_LOCKIN:
2018-02-22T18:27:19.900Z lightningd(32119):     03c977ccfde5f30b43bcadd69dc1a1e8a29359824b8bddd44d9bf526a2b3f2bf37 chan #25: ... Funding broadcast exited with 26: error code: -26?error message:?66: min relay fee not met?
2018-02-22T18:27:19.901Z lightningd(32119): 03c977ccfde5f30b43bcadd69dc1a1e8a29359824b8bddd44d9bf526a2b3f2bf37 chan #25: Peer permanent failure in CHANNELD_AWAITING_LOCKIN: Internal error
2018-02-22T18:27:19.901Z lightningd(32119): lightning_channeld-03c977ccfde5f30b43bcadd69dc1a1e8a29359824b8bddd44d9bf526a2b3f2bf37 chan #25: Status closed, but not exited. Killing
2018-02-22T18:27:19.901Z lightningd(32119):      (tx 8c3e0e99490a38e04d18711464a6893383c6f068dde6a3e56f21dd9f50a30218)
2018-02-22T18:27:19.902Z lightningd(32119): sendrawtransaction: 02000000000101b8493a71b192f78a84b7519c766562294d4b98ebbd55aa3445ef82d351fc272d0000000000e9137b80018c410f0000000000220020ed43acec5388691e6ee8953ea5abfe60afc198482628cc325aa8efcc956053180400483045022100e30e5f1066cbd9c9b3fc189508490bc320af7043c4afa9af75db14523afae040022055d7c44e1c09d1fbb784a01a138b135f5160ac5c30f8e589ab2fe96d62a691c401483045022100ce2565cd360d57d04119b731b0cb3e2ffb593061c2ee5fb7f8f30514f0f275e202205a05daae1e784e922fc0f6e40919d09a1e68f6f8d40a3ce9f57abf340cffbc240147522102408017bfdd005084347b0f74c3fec5f591cd35d75c35b18f7a3bcea29c504ad02103c5e30dc12f1bbdcb45036c215adfd6f92bd33397c0fb5bf2a7ff53bb316d4ddc52ae56038220
2018-02-22T18:27:19.904Z lightningd(32119): Connected json input
2018-02-22T18:27:19.904Z lightning_gossipd(32127): Forgetting remote peer 03c977ccfde5f30b43bcadd69dc1a1e8a29359824b8bddd44d9bf526a2b3f2bf37


2018-02-25T07:07:09.887Z lightningd(15727): Owning output 1 42998267 (SEGWIT) txid 9cf727bc8589a9810d2501df350b66aa49fe28f84a522069250510fe0e7fb467
2018-02-25T07:07:09.887Z lightningd(15727):      (tx 9cf727bc8589a9810d2501df350b66aa49fe28f84a522069250510fe0e7fb467)
2018-02-25T07:07:09.887Z lightningd(15727): sendrawtransaction: 020000000001011706692d7509eba02a4891be0d5e8bc367c066ad21f833b6f1c278e483a6eb960100000000ffffffff0240420f0000000000220020325539f3f391d5774b99c5a6b0dba4a33dfec1057ca4ac034f47f1d646828c34fb199002000000001600140f2ef1b5951167e524c669931846c9ccf62b27c2024730440220046e129309bab0243e2868619890d65fc2ee1dc34efd11022999b66aa759e25202206654d92aa4a5d4fc74919aeee3c2aaa5e8dd134e9708207343483bb837ad1a460121039f6c70bd24d26a11fa17b7146e8a20e2cdc5646fb79caa654fb8934ccb6c5a6600000000
2018-02-25T07:07:09.888Z lightningd(15727): Client: Received message 9 from client
2018-02-25T07:07:09.898Z lightningd(15727): lightning_channeld-028fd42a3eb383bfb803e49f393fb11786108d879fcd46cdfa5ee283e3b896077b chan #32: pid 2739, msgfd 28
2018-02-25T07:07:09.898Z lightningd(15727): 028fd42a3eb383bfb803e49f393fb11786108d879fcd46cdfa5ee283e3b896077b chan #32: Waiting for funding confirmations
2018-02-25T07:07:09.898Z lightningd(15727): 028fd42a3eb383bfb803e49f393fb11786108d879fcd46cdfa5ee283e3b896077b chan #32: Ignoring fee limits!
2018-02-25T07:07:09.898Z lightningd(15727):jcon fd 16: Success
2018-02-25T07:07:09.902Z lightningd(15727): sendrawtx exit 0, gave 9cf727bc8589a9810d2501df350b66aa49fe28f84a522069250510fe0e7fb467?

The thing that I don't understand (and is not a consistent behavior) is this: if lightningd accepted that the transaction failed (and thus re-used the output in a different funding) why does it expect that the original funding transaction (that failed to be broadcasted) will be confirmed?

raw transactions

02000000000101b8493a71b192f78a84b7519c766562294d4b98ebbd55aa3445ef82d351fc272d0100000000ffffffff0240420f00000000002200200cd1804f48db0e589ee179dc5681596ff2677ab5435689d6421bba91f95f05e968d8800200000000160014afc3e6029e48754a173537a27f4dc8ac783aa9a60247304402202ae8af1c337d474afc6e560adf600f6e549b5c10fc28c8a7026d427a406bf24202202141984e3add6c71e04ffc1401a21f1801467040e2a99f84bb0edd6e18d62dfe012103cbf28137dd25af0e105c7098630d06bc6a91d181808148b6f9d7c7430f238ada00000000

020000000001018fb6d1ab010419855ea9cfeec4f96df61230b0ffcf1d6e5cd5096ee91bf222840100000000ffffffff0240420f0000000000220020c2e1f613b56ab4e4d3045ffe3647c29ccaf95fa168f8a60ce0d61e64c1ad7ff59095710200000000160014b18ffcac55e241080caa19464453c3ffb114bfae0247304402201642e903dfae0d42790b826de52c0d7d120c8d43c48655a55a2b920e18504134022018916a12981d0189ad70f6975d1238ba904a126a00bbb2166bf611db79e243a601210262c2a4707d670f3a10c1a956707307290bc54fcad79e86a09a6a80d1c706968b00000000


020000000001011706692d7509eba02a4891be0d5e8bc367c066ad21f833b6f1c278e483a6eb960100000000ffffffff0240420f0000000000220020deffcaed043020e7a9b2164102cc39259e58bdc4454389bee1b6f05de4cf8de4401b900200000000160014b739aac5c1a86c35d53836da6b6acbba776a3cf102483045022100bb3aa46662d012035432527e1571b0f7f31201372faeea70864928394563e96702206484f34845ef956e9ef7816666d3d27d952af520a41af8a4ee3ef0feb96e40aa0121039f6c70bd24d26a11fa17b7146e8a20e2cdc5646fb79caa654fb8934ccb6c5a6600000000

[cdecker]

Did you at any point run dev-rescan-outputs? That's the only way outputs are currently being marked as unspent after they have been marked as spent.

[fixone]

I did, just can't remember when - likely it was around the time when I opened this issue & probably after I run dev-fail. Regardless of how it got in this situation, shouldn't lightningd close/remove or otherwise get rid of the channel in CHANNELD_AWAITING_LOCKIN as it's clear it won't ever lock?