<p>are you running bitcoin testnet3?</p>

<p>put these lines to your conf file, shutdown and restart syncing again </p>

<pre><code>addnode=104.237.131.138
addnode=151.80.205.132
addnode=192.155.82.123
addnode=74.220.255.190
addnode=80.100.203.151
</code></pre>

CC BY-SA 3.0
2018-04-09T07:33:16.043Z
Thanks @amaclin Now syncing is done, but pruning is taking long time.$ bitcoin-cli getblockchaininfo
error code: -28
error message:
Pruning blockstore...
User97693321
CC BY-SA 3.0
2018-04-09T08:03:33.190Z
I have never used pruning. Testnet spends ~13 Gb on disk - it is OK for me. AFAIK, you could prune blockchain while downloading it, not after syncing
amaclin
CC BY-SA 3.0
2018-04-08T06:28:29.517Z
2018-04-08T06:28:29.517Z
amaclin
<p>My config file is similar to this:</p>

<pre><code>testnet=1
blocksonly=1
rpcport=5000
server=1
listen=0
prune=1000  
dbcache=16000 
rpcallowip=0.0.0.0/0
rpcuser=someuser
rpcpassword=somepass
</code></pre>

<p>I have started the node sync in testnet mode and I tried to check the status by using the command </p>

<pre><code>$ tail -f testnet3/debug.log

Ouput: 2018-04-08 04:09:51 Potential stale tip detected, will try using extra outbound peer (last tip update: 46620 seconds ago)
2018-04-08 04:20:21 Potential stale tip detected, will try using extra outbound peer (last tip update: 47250 seconds ago)
2018-04-08 04:30:51 Potential stale tip detected, will try using extra outbound peer (last tip update: 47880 seconds ago)
2018-04-08 04:41:21 Potential stale tip detected, will try using extra outbound peer (last tip update: 48510 seconds ago)
2018-04-08 04:51:51 Potential stale tip detected, will try using extra outbound peer (last tip update: 49140 seconds ago)
2018-04-08 05:02:21 Potential stale tip detected, will try using extra outbound peer (last tip update: 49770 seconds ago)
2018-04-08 05:12:51 Potential stale tip detected, will try using extra outbound peer (last tip update: 50400 seconds ago)
2018-04-08 05:23:21 Potential stale tip detected, will try using extra outbound peer (last tip update: 51030 seconds ago)
2018-04-08 05:33:51 Potential stale tip detected, will try using extra outbound peer (last tip update: 51660 seconds ago)
2018-04-08 05:44:21 Potential stale tip detected, will try using extra outbound peer (last tip update: 52290 seconds ago)
</code></pre>

<p>...and keep on getting the same </p>

<p>Again I tried this command to see the peers info </p>

<pre><code>$ bitcoin-cli getpeerinfo
output:
[
]
</code></pre>

<p>It means there are no peers, so I want to know what is wrong. </p>

<p>The syncing is happening from more than 13 hours, but still headers and blocks are 0 only.</p>

<pre><code>$ bitcoin-cli getblockchaininfo
{
  "chain": "test",
  "blocks": 0,
  "headers": 0,
  "bestblockhash": "000000000xxxxxxxxxx",
  "difficulty": 1,
  "mediantime": 1296688602,
  "verificationprogress": 5.667000646249453e-08,
  "initialblockdownload": true,
  "chainwork": "0000000000000000000000000000000000000000000000000000000100010001",
.......
</code></pre>

CC BY-SA 3.0
2018-04-08T07:23:34.527Z
You aren't connected to the testnet network (as evidenced by having no peers), of course you aren't syncing! Can you post more of your debug.log, preferably parts where it says something about connecting to peers? If you can post all of it, that would be better.
Ava Chow
<bitcoin-core><bitcoind><testnet>
testnet3 node sync process is very slow
User97693321
# testnet3 node sync process is very slow

(Asked by: username_0 on 2018-04-08)

My config file is similar to this:
testnet=1
blocksonly=1
rpcport=5000
server=1
listen=0
prune=1000  
dbcache=16000 
rpcallowip=0.0.0.0/0
rpcuser=someuser
rpcpassword=somepass

I have started the node sync in testnet mode and I tried to check the status by using the command 
$ tail -f testnet3/debug.log

Ouput: 2018-04-08 04:09:51 Potential stale tip detected, will try using extra outbound peer (last tip update: 46620 seconds ago)
2018-04-08 04:20:21 Potential stale tip detected, will try using extra outbound peer (last tip update: 47250 seconds ago)
2018-04-08 04:30:51 Potential stale tip detected, will try using extra outbound peer (last tip update: 47880 seconds ago)
2018-04-08 04:41:21 Potential stale tip detected, will try using extra outbound peer (last tip update: 48510 seconds ago)
2018-04-08 04:51:51 Potential stale tip detected, will try using extra outbound peer (last tip update: 49140 seconds ago)
2018-04-08 05:02:21 Potential stale tip detected, will try using extra outbound peer (last tip update: 49770 seconds ago)
2018-04-08 05:12:51 Potential stale tip detected, will try using extra outbound peer (last tip update: 50400 seconds ago)
2018-04-08 05:23:21 Potential stale tip detected, will try using extra outbound peer (last tip update: 51030 seconds ago)
2018-04-08 05:33:51 Potential stale tip detected, will try using extra outbound peer (last tip update: 51660 seconds ago)
2018-04-08 05:44:21 Potential stale tip detected, will try using extra outbound peer (last tip update: 52290 seconds ago)

...and keep on getting the same 
Again I tried this command to see the peers info 
$ bitcoin-cli getpeerinfo
output:
[
]

It means there are no peers, so I want to know what is wrong. 
The syncing is happening from more than 13 hours, but still headers and blocks are 0 only.
$ bitcoin-cli getblockchaininfo
{
  "chain": "test",
  "blocks": 0,
  "headers": 0,
  "bestblockhash": "000000000xxxxxxxxxx",
  "difficulty": 1,
  "mediantime": 1296688602,
  "verificationprogress": 5.667000646249453e-08,
  "initialblockdownload": true,
  "chainwork": "0000000000000000000000000000000000000000000000000000000100010001",
.......

**Tags:** bitcoin-core, bitcoind, testnet

> **Comments:**
> **username_1**: You aren't connected to the testnet network (as evidenced by having no peers), of course you aren't syncing! Can you post more of your debug.log, preferably parts where it says something about connecting to peers? If you can post all of it, that would be better.  

---

## 1 answers

### Answer by username_2 on 2018-04-08. Score: 1 | Accepted answer

are you running bitcoin testnet3?
put these lines to your conf file, shutdown and restart syncing again 
addnode=104.237.131.138
addnode=151.80.205.132
addnode=192.155.82.123
addnode=74.220.255.190
addnode=80.100.203.151

> **Comments:**
> **username_0**: Thanks @username_2 Now syncing is done, but pruning is taking long time.$ bitcoin-cli getblockchaininfo error code: -28 error message: Pruning blockstore...  
> **username_2**: I have never used pruning. Testnet spends ~13 Gb on disk - it is OK for me. AFAIK, you could prune blockchain while downloading it, not after syncing  

---

