<p>Generally your lightning node needs to scan blocks from <code>bitcoind</code> or <code>btcd</code>. It seems like due to the fact that your node was offline <code>lnd</code> did not catch up processing the blocks provided by your bitcoin node. So it seems like you just have to wait until lnd catches up. </p>

CC BY-SA 4.0
2019-02-18T11:18:20.467Z
Indeed... hope this helps someone else in the future, these panic modes are not healthy at all. Thanks again.
Lebowski
CC BY-SA 4.0
2019-02-17T10:58:21.200Z
2019-02-17T10:58:21.200Z
Rene Pickhardt
<p>Recently upgraded to the latest lnd version (following the stadicus guide) but once i restarted the client i keep getting this error when i check the logs: </p>

<p><em>[ERR] LNWL: Failed to process consensus server notification (name: <code>blockconnected</code>, detail: `failed to store sync information 00000000000000000024cca7ae0fea5ae75fd1405a44e7fac08a94c03b19bbe4: failed to fetch block hash for height 563348: block not found</em></p>

<p><a href="https://i.sstatic.net/gNDtJ.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/gNDtJ.png" alt="enter image description here"></a></p>

<p>I have all my channels inactive at the moment but the upgrade seemed to be worked as expected since </p>

<blockquote>
  <p>lncli getinfo</p>
</blockquote>

<p>prints the correct and latest version... Any ideas how to fix this issue?</p>

CC BY-SA 4.0
2019-02-17T00:48:27.047Z
is your btcd / bitcoind running?
Rene Pickhardt
CC BY-SA 4.0
2019-02-17T08:38:42.680Z
Yeh bitcoind was running smoothly, but i noticed this morning that it was all a matter of waiting around 1 hour for the client to synch properly... My panic mode and stubbornness yesterday didnt let me see the bigger picture.. This morning lnd is running as expected on the latest version and all my channels are open and active. Thanks as usual for your concern @RenePickhardt
Lebowski
CC BY-SA 4.0
2019-02-17T10:59:08.840Z
sure you'r welcome I just gave an answer to summarize and give some context. have you considered opening and lnd issue on their github?
Rene Pickhardt
<lightning-network><lightning-network-daemon><lightning-routing>
LND errors after upgraded to v0.5.2
Lebowski
# LND errors after upgraded to v0.5.2

(Asked by: username_0 on 2019-02-16)

Recently upgraded to the latest lnd version (following the stadicus guide) but once i restarted the client i keep getting this error when i check the logs:

*[ERR] LNWL: Failed to process consensus server notification (name: `blockconnected`, detail: `failed to store sync information 00000000000000000024cca7ae0fea5ae75fd1405a44e7fac08a94c03b19bbe4: failed to fetch block hash for height 563348: block not found*

[![enter image description here](https://i.sstatic.net/gNDtJ.png)](https://i.sstatic.net/gNDtJ.png)

I have all my channels inactive at the moment but the upgrade seemed to be worked as expected since

> lncli getinfo

prints the correct and latest version... Any ideas how to fix this issue?

**Tags:** lightning-network, lightning-network-daemon, lightning-routing

> **Comments:**
> **username_1**: is your btcd / bitcoind running?  
> **username_0**: Yeh bitcoind was running smoothly, but i noticed this morning that it was all a matter of waiting around 1 hour for the client to synch properly... My panic mode and stubbornness yesterday didnt let me see the bigger picture.. This morning lnd is running as expected on the latest version and all my channels are open and active. Thanks as usual for your concern @username_1  
> **username_1**: sure you'r welcome I just gave an answer to summarize and give some context. have you considered opening and lnd issue on their github?  

---

## 1 answers

### Answer by username_1 on 2019-02-17. Score: 1

Generally your lightning node needs to scan blocks from `bitcoind` or `btcd`. It seems like due to the fact that your node was offline `lnd` did not catch up processing the blocks provided by your bitcoin node. So it seems like you just have to wait until lnd catches up.

> **Comments:**
> **username_0**: Indeed... hope this helps someone else in the future, these panic modes are not healthy at all. Thanks again.  

---

