Files
lightning/daemon
Rusty Russell df4df8679d chaintopology: only report active chaintip.
getchaintips returns tips even if we don't have the body for them, so
we need to look for the active tip, not just the first (most-work) one.

Here's what happens in the log:

	+2849.963414597 lightningd(26779):BROKEN: bitcoin-cli getblock 0000000000000000018626ff7160bdf38a602e6650bd04ec258759ea578b106d false exited 91: 'error code: -32603
	error message:
	Can't read block from disk
	'

And here's an example problematic getchaintips output:

[
  {
    "height": 419635,
    "hash": "0000000000000000000fd32d87fce19efb7ccd07aa4ddaf1b94b9a219deec0f9",
    "branchlen": 1,
    "status": "headers-only"
  }, 
  {
    "height": 419634,
    "hash": "000000000000000002988d6512719697147cf252b2f64d247cf229266615d2bb",
    "branchlen": 0,
    "status": "active"
  }, 
  {
    "height": 416372,
    "hash": "0000000000000000004d0a54341c992ae174a91c8dd3981a9f2b3d3f6221ba59",
    "branchlen": 1,
    "status": "valid-headers"
  }, 
  {
    "height": 416231,
    "hash": "0000000000000000044d0d2c25f33cb48931540366149cde3fb0154f55b58c76",
    "branchlen": 1,
    "status": "headers-only"
  }
]

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2016-07-07 13:36:39 +09:30
..
2016-01-22 06:41:47 +10:30
2016-07-01 12:00:17 +09:30
2016-01-22 06:45:28 +10:30
2016-05-26 15:25:24 +09:30
2016-01-22 06:41:49 +10:30
2016-05-26 15:25:24 +09:30
2016-05-26 15:25:24 +09:30
2016-07-01 12:00:17 +09:30
2016-07-01 12:00:17 +09:30
2016-07-01 12:00:17 +09:30
2016-07-01 12:00:17 +09:30
2016-01-22 06:41:48 +10:30
2016-01-22 06:41:48 +10:30
2016-05-10 06:28:17 +09:30
2016-05-10 06:28:17 +09:30
2016-07-01 12:00:17 +09:30
2016-07-01 12:00:17 +09:30
2016-07-01 11:59:15 +09:30
2016-07-01 11:59:15 +09:30
2016-07-01 12:00:17 +09:30
2016-07-01 12:00:17 +09:30
2016-07-01 12:00:17 +09:30
2016-07-01 12:00:17 +09:30
2016-07-01 12:00:17 +09:30
2016-05-10 06:26:09 +09:30
2016-05-10 06:26:09 +09:30