No block source available. With active connections.

[scenkner]

My Bitcoin Core was showing "no block source available..." This is a new problem, I have not changed firewall or router configs since it was working last. I am showing 17 connections, 9 in and 8 out. I have been stuck at 3 weeks behind for over 24 hours now. I am at block number 371276. Please help, I foolishly sent money to one of my addresses assuming that it was catching up.

I am using Bitcoin Core v.0.11.0.0 and am running on linux.
My debug.log is repeating the message "ERROR: AcceptToMemoryPool: non-final"

I am now in the process of reindexing and it is progressing.
(This is an xpost from reddit/r/bitcoin.)

Thanks.

[1714660463]

1714660463

[1714660463]

1714660463

[1714660463]

1714660463

[pedrog]

Find a recent IP list of nodes and try this:

launch with bitcoin-qt -connect=IP

from terminal. A single IP. You will have a single connection, but since you can only sync with one anyway it does not matter. Launch regularly when done sycning.

Code:

last updated 2014.10.10
-------------------------------------------------------------------------------------------------
IP               - location             - owner[1]-  speed      - info/stats page[2] - testnet
-------------------------------------------------------------------------------------------------
84.200.34.113    - Freinsheim, DE, EU   - Newar   - 1000 mbit/s - yes                - no
185.45.192.129   - Amsterdam, NL, EU    - anon    - 1000 mbit/s - /node.php[3]       - yes
213.165.91.169   - Germany, EU          - shorena -  100 mbit/s - yes                - no
50.7.68.180      - New York, USA        - Newar   -  100 mbit/s - yes                - no
5.9.24.81        - Germany, EU          - zvs     -  unknown    - no                 - no
178.79.173.71    - United Kingdom, EU   - zvs     -  unknown    - no                 - no
107.155.104.194  - Dalls, USA           - zvs     -  unknown    - no                 - no
106.185.32.195   - Japan, Asia          - zvs     -  unknown    - no                 - no
94.242.57.173    - Russia, Asia         - zvs     -  unknown    - no                 - no
-------------------------------------------------------------------------------------------------
[1] refers to a bitcointalk.org username or anon if requested
[2] same IP, port 80 or path/port given
[3] work in progress

[1] https://bitcointalk.org/index.php?topic=145386.0

[Newar]

Find a recent IP list of nodes and try this:

launch with bitcoin-qt -connect=IP

from terminal. A single IP. You will have a single connection, but since you can only sync with one anyway it does not matter. Launch regularly when done sycning.
[...]

IIRC, this procedure is not necessary any more with Bitcoin Core >0.10.0, as it gets data from multiple peers now.

Code:

last updated 2014.10.10
-------------------------------------------------------------------------------------------------
IP               - location             - owner[1]-  speed      - info/stats page[2] - testnet
-------------------------------------------------------------------------------------------------
84.200.34.113    - Freinsheim, DE, EU   - Newar   - 1000 mbit/s - yes                - no
185.45.192.129   - Amsterdam, NL, EU    - anon    - 1000 mbit/s - /node.php[3]       - yes
213.165.91.169   - Germany, EU          - shorena -  100 mbit/s - yes                - no
50.7.68.180      - New York, USA        - Newar   -  100 mbit/s - yes                - no
5.9.24.81        - Germany, EU          - zvs     -  unknown    - no                 - no
178.79.173.71    - United Kingdom, EU   - zvs     -  unknown    - no                 - no
107.155.104.194  - Dalls, USA           - zvs     -  unknown    - no                 - no
106.185.32.195   - Japan, Asia          - zvs     -  unknown    - no                 - no
94.242.57.173    - Russia, Asia         - zvs     -  unknown    - no                 - no
-------------------------------------------------------------------------------------------------
[1] refers to a bitcointalk.org username or anon if requested
[2] same IP, port 80 or path/port given
[3] work in progress

Regarding that list... I had to close those two (not impressed with VertVPS and Hetzner customer service / support at all).
 
Also, AFAIK, zvs closed his nodes on that list too.

[pedrog]

Oh, right, two of those were yours.

How about deleting peers.dat forcing bitcoin-qt to generate a new list?

[Newar]

[...] How about deleting peers.dat forcing bitcoin-qt to generate a new list?

That also works (let the software shut down properly before deleting), although there is a slim chance that all the "fresh" ones you receive are duds. It's better to addnode= at least one known good node. Some other lists with nodes you can consider to try:
https://en.bitcoin.it/wiki/Fallback_Nodes
http://nodes.bitcoin.st/
https://getaddr.bitnodes.io/nodes/leaderboard/

[pha2G]

My bitcoin core wallet its not working and I have being sending Bitcoins withot receiveing them, its says something like this "No block source Available and 4 years and 6 weeks behind". I am in South Africa Please help Soonest.

Kind Regards

[ranochigo]

Error: AcceptToMemoryPool isn't an serious error and should be ignored by the user as it is a standard behaviour of the client. However, since it is actively receiving transactions from peer, your peers would likely have no problem sending the blocks to you. Try to reindex the blockchain, I believe its an error on your side.

My bitcoin core wallet its not working and I have being sending Bitcoins withot receiveing them, its says something like this "No block source Available and 4 years and 6 weeks behind". I am in South Africa Please help Soonest.

Kind Regards

Do you have any active connections to the network, if not try to import nodes using

Code:

addnode [IP OF NODE] add

, replacing IP OF NODE to the nodes listed above by going to the HELP>DEBUG WINDOW>CONSOLE. If you have connections to the network, go to network traffic and ensure that there is a good amount of traffic.