Lightweight LN node (c-lightning + Spruned) Problems

[vv181]

I'm trying to follow this tutorial (https://bitcoin.stackexchange.com/questions/76849/c-lightning-lightweight-nodes-no-local-bitcoind) to set up an LN on my PC.

I could get the Spruned working, testing it on bitcoin-cli, and it works.

Code:

[➜  ~ bitcoin-cli getblockchaininfo
{
  "chain": "main",
  "warning": "spruned 0.0.8, emulating bitcoind v0.16",
  "blocks": 573648,
  "headers": 573648,
  "bestblockhash": "0000000000000000001364fc133de480d234b9ad7237581187f00792dae4f213",
  "difficulty": 0,
  "chainwork": "0000000000000000000000000000000000000000000000000000000000000000",
  "mediantime": 1556475871,
  "verificationprogress": 100,
  "pruned": false
}

However when i run

Code:

lightningd --log-level=debug --network=bitcoin \
           --bitcoin-rpcuser=rpcuser \
           --bitcoin-rpcpassword=rpcpassword

the lightnind exiting, and returns

Code:

bitcoin-cli -rpcuser=... -rpcpassword=... getblock 00000000000000000011f07bf95e39d064c016556e5aa8519efc8d5d42b0a299 false: bad block '(000080200d9d6b297fe99da8847e7586cfe39aad5f6275de1cd11a000000000000000000f82409279d4a6d05018ae69c85171d6e68b50ae59d0207987a5823bfde150ca992d2c55c114e2c177555aa18010000.......)'

lightningd log: https://ghostbin.com/paste/ervw9

I know there is a probably something wrong in the hash/block verification, that makes it returns 'false: bad block:'. But, I already make sure that both spruned and lightnin c conf is running on the mainnet.

EDIT: Closed since I got the workaround.

I just simply delete the spruned data folder and resync it again.

[nc50lc]

EDIT: Closed since I got the workaround.

I just simply delete the spruned data folder and resync it again.

Then consider to lock the thread and/or edit the title and add "[SOLVED]" at the beginning 

This might come in handy if someone got the same issue.
It will show in google search anyways.