No Block Source Avaliable - Bitcoin-QT

[jackg]

I get an error on bitcoin core whenever I load it. It says: No Block Source Avaliable.

I have full connection to all 8 nodes at a pinging speed of less than 20ms for each node.

Any suggestions?

(NOTE: not sure if I have already posted this so please tell me if I have!)

[1715207580]

1715207580

[1715207580]

1715207580

[1715207580]

1715207580

[Jet Cash]

Have you got any activity on the network traffic graph?

[jackg]

Received 30 mb
Sent 3 mb

Yes, ther eis network traffic of this session. The session has only been online for about 1 or 2 hours.

I managed to verify another user's signed message of a bitcoin address but it cannot access the block sources.

[achow101]

Received 30 mb
Sent 3 mb

Yes, ther eis network traffic of this session. The session has only been online for about 1 or 2 hours.

I managed to verify another user's signed message of a bitcoin address but it cannot access the block sources.

Verifying signed messages does not require being online.

Try reindexing. Supposedly that has worked for people before to clear this problem. Can you also post your Debug log before reindexing?

[jackg]

Received 30 mb
Sent 3 mb

Yes, ther eis network traffic of this session. The session has only been online for about 1 or 2 hours.

I managed to verify another user's signed message of a bitcoin address but it cannot access the block sources.

Verifying signed messages does not require being online.

Try reindexing. Supposedly that has worked for people before to clear this problem. Can you also post your Debug log before reindexing?

What is reindexing? Deleting the blockchain? I have not done much downloading of that and am still 2 years and 53 weeks behind! I will check the debug log first. And post any relavent information here.

[Jet Cash]

Sounds as if you just need to wait. Go by the green bar, and not the catchup time. About half of the chain was created in the last year.

If you are in Somerset, England, I can give you a copy of the blockchain on a USB stick. 

[achow101]

What is reindexing? Deleting the blockchain? I have not done much downloading of that and am still 2 years and 53 weeks behind! I will check the debug log first. And post any relavent information here.

Depending on what OS you are using, you will need to change the start command to include the -reindex flag so that it will reindex the blockchain on start. All this does is deletes all of the databases and then rebuilds them with the downloaded blocks.

[jackg]

Sounds as if you just need to wait. Go by the green bar, and not the catchup time. About half of the chain was created in the last year.

If you are in Somerset, England, I can give you a copy of the blockchain on a USB stick. 

Do you know the command for cmd.
I am running a windows 7 home premium operating sysem.
Can you suggest the reindexing command?

I am loading back up bitcoin-qt, it will take a while.

[achow101]

Sounds as if you just need to wait. Go by the green bar, and not the catchup time. About half of the chain was created in the last year.

If you are in Somerset, England, I can give you a copy of the blockchain on a USB stick. 

Do you know the command for cmd.
I am running a windows 7 home premium operating sysem.
Can you suggest the reindexing command?

I am loading back up bitcoin-qt, it will take a while.

Close bitcoin core. Find the folder where Bitcoin Core is installed. Shift+Right Click and select the "Open a Command Window here" option. In the window that appears, type:

Code:

bitcoin-qt.exe -reindex

That will start Bitcoin core to reindex. After it is done, shutdown Bitcoin Core normally and then restart it. Hopefully it will works as it is supposed to.

[jackg]

I see many of these errors:

2015-11-10 21:37:32 ERROR: AcceptToMemoryPool: non-final

AND

2015-12-29 17:29:36 ERROR: AcceptToMemoryPool: nonstandard transaction: dust

[achow101]

I see many of these errors:

2015-11-10 21:37:32 ERROR: AcceptToMemoryPool: non-final

That is fine. It just means that a transaction is non-final (has sequence numbers for inputs that are not 0xffffffff) so it isn't considered standard and thus not accepted to the mempool. IIRC the exceptions are OP_CHECKLOCKTIMEVERIFY transactions and transactions with just nLockTime.

[jackg]

I see many of these errors:

2015-11-10 21:37:32 ERROR: AcceptToMemoryPool: non-final

That is fine. It just means that a transaction is non-final (has sequence numbers for inputs that are not 0xffffffff) so it isn't considered standard and thus not accepted to the mempool. IIRC the exceptions are OP_CHECKLOCKTIMEVERIFY transactions and transactions with just nLockTime.

How does that happen if I actually haven't made ANY transactions in hat wallet?

[achow101]

I see many of these errors:

2015-11-10 21:37:32 ERROR: AcceptToMemoryPool: non-final

That is fine. It just means that a transaction is non-final (has sequence numbers for inputs that are not 0xffffffff) so it isn't considered standard and thus not accepted to the mempool. IIRC the exceptions are OP_CHECKLOCKTIMEVERIFY transactions and transactions with just nLockTime.

How does that happen if I actually haven't made ANY transactions in hat wallet?

It is part of how Bitcoin relays transactions across the network. Someone made a transaction, and it gets relayed through its peers and through their peers and so on and so forth until every single node has that transaction. Since Bitcoin Core is a full node, it must verify and store the transactions that it receives, and if the transaction doesn't verify or is nonstandard, then it rejects it and doesn't relay or store it. The message is just telling you that it received a transaction and didn't store it because it failed one of the checks.

[cr1776]

I see many of these errors:

2015-11-10 21:37:32 ERROR: AcceptToMemoryPool: non-final

That is fine. It just means that a transaction is non-final (has sequence numbers for inputs that are not 0xffffffff) so it isn't considered standard and thus not accepted to the mempool. IIRC the exceptions are OP_CHECKLOCKTIMEVERIFY transactions and transactions with just nLockTime.

How does that happen if I actually haven't made ANY transactions in hat wallet?

Bitcoin core is part of the bitcoin network so it is accepting and relaying transactions to other nodes whenever it is open.  Some, like the ones above, were non-standard and that is being reported.

[jackg]

This is the data from this session.

2015-12-29 17:25:14 receive version message: /Satoshi:0.11.1/: version 70002, blocks=390827, us=xx.xx.xxx.xxx:51484, peer=8
2015-12-29 17:25:14 Added time data, samples 9, offset -15 (+0 minutes)
2015-12-29 17:25:14 nTimeOffset = -12  (+0 minutes)
2015-12-29 17:25:15 ERROR: AcceptToMemoryPool: nonstandard transaction: dust
2015-12-29 17:29:36 ERROR: AcceptToMemoryPool: nonstandard transaction: dust

xx.xx.xxx.xxx Is my external IP address.

[achow101]

This is the data from this session.

2015-12-29 17:25:14 receive version message: /Satoshi:0.11.1/: version 70002, blocks=390827, us=xx.xx.xxx.xxx:51484, peer=8
2015-12-29 17:25:14 Added time data, samples 9, offset -15 (+0 minutes)
2015-12-29 17:25:14 nTimeOffset = -12  (+0 minutes)
2015-12-29 17:25:15 ERROR: AcceptToMemoryPool: nonstandard transaction: dust
2015-12-29 17:29:36 ERROR: AcceptToMemoryPool: nonstandard transaction: dust

xx.xx.xxx.xxx Is my external IP address.

Nothing abnormal there. The dust warning is just telling you that a transaction has a dust output, and dust outputs make a transaction nonstandard so they aren't accepted to the mempool.

Have you tried reindexing yet? Do you still have the "No block source available" error?

[jackg]

This is the data from this session.

2015-12-29 17:25:14 receive version message: /Satoshi:0.11.1/: version 70002, blocks=390827, us=xx.xx.xxx.xxx:51484, peer=8
2015-12-29 17:25:14 Added time data, samples 9, offset -15 (+0 minutes)
2015-12-29 17:25:14 nTimeOffset = -12  (+0 minutes)
2015-12-29 17:25:15 ERROR: AcceptToMemoryPool: nonstandard transaction: dust
2015-12-29 17:29:36 ERROR: AcceptToMemoryPool: nonstandard transaction: dust

xx.xx.xxx.xxx Is my external IP address.

Nothing abnormal there. The dust warning is just telling you that a transaction has a dust output, and dust outputs make a transaction nonstandard so they aren't accepted to the mempool.

Have you tried reindexing yet? Do you still have the "No block source available" error?

I will re index now.

I will go to cmd, go to the D:\Bitcoin and type in bitcoin-qt.exe -reindex.
I assume this is correct.

[jackg]

Reindexing blocks on disk!

It is now running OK, I think.

I will post here if I get any problems.

Thanks for the help.

[jackg]

It is working fine now. Thank you for your support and suggestions.

I have updated its priority on taskmgr.exe to high.

[shorena]

It is working fine now. Thank you for your support and suggestions.

I have updated its priority on taskmgr.exe to high.

There is no need to do that. It will - if anything - only make other things slower.

[jackg]

It is working fine now. Thank you for your support and suggestions.

I have updated its priority on taskmgr.exe to high.

There is no need to do that. It will - if anything - only make other things slower.

Yes Shorena, I changed it back a few minutes after I did it. My fan got too warm. Also, it slowed down the display of my computer and since then, Norton Internet Security has flagged up an error saying it is using high sis usage. However, I assume this is normal!

[shorena]

It is working fine now. Thank you for your support and suggestions.

I have updated its priority on taskmgr.exe to high.

There is no need to do that. It will - if anything - only make other things slower.

Yes Shorena, I changed it back a few minutes after I did it. My fan got too warm. Also, it slowed down the display of my computer and since then, Norton Internet Security has flagged up an error saying it is using high sis usage. However, I assume this is normal!

High CPU usage durring sync is normal. If your system overheats because of that you might want to look into that though. If its an older system it might be just dust clogging the air circulation.

[jackg]

It is working fine now. Thank you for your support and suggestions.

I have updated its priority on taskmgr.exe to high.

There is no need to do that. It will - if anything - only make other things slower.

Yes Shorena, I changed it back a few minutes after I did it. My fan got too warm. Also, it slowed down the display of my computer and since then, Norton Internet Security has flagged up an error saying it is using high sis usage. However, I assume this is normal!

High CPU usage durring sync is normal. If your system overheats because of that you might want to look into that though. If its an older system it might be just dust clogging the air circulation.

It is fine. I would expect this from a computer that is around 6 years old.

It has been underclocked for its entire use, so that keeps its CPU very well.

When new, it was at 2.3GHz dual core - 4.6GHz! As soon as I changed the priority it stopped overheatng.

I would also expect for it to go at least 50 megabytes per hour. I think that tht is a reasonable assumption for it.

[shorena]

It is working fine now. Thank you for your support and suggestions.

I have updated its priority on taskmgr.exe to high.

There is no need to do that. It will - if anything - only make other things slower.

Yes Shorena, I changed it back a few minutes after I did it. My fan got too warm. Also, it slowed down the display of my computer and since then, Norton Internet Security has flagged up an error saying it is using high sis usage. However, I assume this is normal!

High CPU usage durring sync is normal. If your system overheats because of that you might want to look into that though. If its an older system it might be just dust clogging the air circulation.

It is fine. I would expect this from a computer that is around 6 years old.

It has been underclocked for its entire use, so that keeps its CPU very well.

When new, it was at 2.3GHz dual core - 4.6GHz! As soon as I changed the priority it stopped overheatng.

I would also expect for it to go at least 50 megabytes per hour. I think that tht is a reasonable assumption for it.

Considering that the blockchain (blocks folder only) currently uses 57.4GB I hope you can do more than 50 MB per hour or it would take you > 40 days to fully sync.

[jackg]

~snipped~

Considering that the blockchain (blocks folder only) currently uses 57.4GB I hope you can do more than 50 MB per hour or it would take you > 40 days to fully sync.

I have run it for about 6 hours flat! The blocks folder (on its own) is:
13.4 GB (14,399,550,285 bytes)

and contains 223 files and 1 folder!

[shorena]

~snipped~

Considering that the blockchain (blocks folder only) currently uses 57.4GB I hope you can do more than 50 MB per hour or it would take you > 40 days to fully sync.

I have run it for about 6 hours flat! The blocks folder (on its own) is:
13.4 GB (14,399,550,285 bytes)

and contains 223 files and 1 folder!

2GB per hour sounds better. It will slow down a bit for the last year, but it should not take longer than 2-3 days total.