<p>I sorted it out in kind of hacky way. I watched the behavior of Bitcoin-qt during multiple sync attempts I did. The moment it used to come at 24 hrs mark, it used to get stuck there for few minutes. My guess was, it may be in some code path which will cause it to exit after some time. So I decided to perform some operation just as a hunch. And it helped.</p>
<p>Here is what I did - I launched the bitcoin-qt and it started to sync. When it reached 24 hours mark, I waited for a minute or so and then I created a blank wallet using the UI. It did the magic, this time sync moved beyond 24 hours and synced the whole way through. Bitcoin node is now up again and running successfully.</p>

CC BY-SA 4.0
2022-09-27T08:54:03.233Z
2022-09-27T08:54:03.233Z
Noncentralised
<p>I shutdown bitcoin-qt (version: 23.0) around two weeks back. Now when I relaunch it, it syncs blocks until 24 hours and then silently exits. debug.log file contains the following as last line -</p>
<p>2022-09-26T13:28:01Z Leaving InitialBlockDownload (latching to false)</p>
<p>I removed all the wallets to see if that is causing any issue, but that was in vain. Any help will be appreciated.</p>
<p>Best.</p>

CC BY-SA 4.0
2022-09-26T13:59:02.020Z
Hi, is there anything uncommon in how you set up your node? Are you running your node with some uncommon startup options or config? Is it running in pruning mode? It would help if you could tell us a bit more.
Murch
CC BY-SA 4.0
2022-09-26T14:08:23.343Z
Nothing specific. I have been running nodes for more than a year now, never faced this issue. Only thing uncommon would be Tor onion, though I don't think that is uncommon.
Noncentralised
CC BY-SA 4.0
2022-09-26T14:20:56.913Z
I tried to run bitcoind as well, but that also exited after syncing until 24 hours.
Noncentralised
CC BY-SA 4.0
2022-09-26T14:43:28.440Z
Here is the content of bicoin.conf

daemon=1
txindex=1
server=1
listen=1

proxy=127.0.0.1:9050
bind=127.0.0.1

onlynet=onion

walletbroadcast=0
Noncentralised
<synchronization><full-node>
Bitcoin-qt exits silently after syncing blocks until before 24 hours
Noncentralised
# Bitcoin-qt exits silently after syncing blocks until before 24 hours

(Asked by: username_0 on 2022-09-26)

I shutdown bitcoin-qt (version: 23.0) around two weeks back. Now when I relaunch it, it syncs blocks until 24 hours and then silently exits. debug.log file contains the following as last line -

2022-09-26T13:28:01Z Leaving InitialBlockDownload (latching to false)

I removed all the wallets to see if that is causing any issue, but that was in vain. Any help will be appreciated.

Best.

**Tags:** synchronization, full-node

> **Comments:**
> **username_1**: Hi, is there anything uncommon in how you set up your node? Are you running your node with some uncommon startup options or config? Is it running in pruning mode? It would help if you could tell us a bit more.  
> **username_0**: Nothing specific. I have been running nodes for more than a year now, never faced this issue. Only thing uncommon would be Tor onion, though I don't think that is uncommon.  
> **username_0**: I tried to run bitcoind as well, but that also exited after syncing until 24 hours.  
> **username_0**: Here is the content of bicoin.conf  daemon=1 txindex=1 server=1 listen=1  proxy=127.0.0.1:9050 bind=127.0.0.1  onlynet=onion  walletbroadcast=0  

---

## 1 answers

### Answer by username_0 on 2022-09-27. Score: 1

I sorted it out in kind of hacky way. I watched the behavior of Bitcoin-qt during multiple sync attempts I did. The moment it used to come at 24 hrs mark, it used to get stuck there for few minutes. My guess was, it may be in some code path which will cause it to exit after some time. So I decided to perform some operation just as a hunch. And it helped.

Here is what I did - I launched the bitcoin-qt and it started to sync. When it reached 24 hours mark, I waited for a minute or so and then I created a blank wallet using the UI. It did the magic, this time sync moved beyond 24 hours and synced the whole way through. Bitcoin node is now up again and running successfully.


---

