One solution is to aquire bootstrap.dat via the Torrent network. That will help,
-snip-
-snip-
Use electrum or the Blockchain torrent
What with the necroposting? Borred?
Can confirm
Topic: Stuck on the frustratingly slow bitcoin network.. (Read 1695 times)
What with the necroposting? Borred?
Can confirm
One solution is to aquire bootstrap.dat via the Torrent network. That will help,
-snip-
-snip-
Use electrum or the Blockchain torrent
What with the necroposting? Borred?
One solution is to aquire bootstrap.dat via the Torrent network. That will help,
-snip-
-snip-
Use electrum or the Blockchain torrent
What with the necroposting? Borred?
Use electrum or the Blockchain torrent
try my node 104.45.145.179 (hosted on microsoft azure, 100Mb/s connection)
Thanks
Code:
: bitcoind -connect=104.45.145.179 -daemon
: tail -f debug.log
2014-11-29 17:32:05 receive version message: /Satoshi:0.9.3/: version 70002, blocks=332162, us=0.0.0.0:32795, them=104.45.145.179:8333, peer=104.45.145.179:8333
2014-11-29 17:32:05 Added time data, samples 2, offset -1 (+0 minutes)
2014-11-29 17:35:35 ProcessBlock: ORPHAN BLOCK 0, prev=000000000000000005d8f98093bfcd77fe473cc195ca4bc3ece2a77291fdf7ac
2014-11-29 17:36:09 ProcessBlock: ORPHAN BLOCK 1, prev=0000000000000000131bd22a1e2b53594c5589af93d9ebe34d4027777b1131c8
: tail -f debug.log
2014-11-29 17:32:05 receive version message: /Satoshi:0.9.3/: version 70002, blocks=332162, us=0.0.0.0:32795, them=104.45.145.179:8333, peer=104.45.145.179:8333
2014-11-29 17:32:05 Added time data, samples 2, offset -1 (+0 minutes)
2014-11-29 17:35:35 ProcessBlock: ORPHAN BLOCK 0, prev=000000000000000005d8f98093bfcd77fe473cc195ca4bc3ece2a77291fdf7ac
2014-11-29 17:36:09 ProcessBlock: ORPHAN BLOCK 1, prev=0000000000000000131bd22a1e2b53594c5589af93d9ebe34d4027777b1131c8
Then nothing.
Second try with bitcoin-qt, because I saw bitcoind did not open any ports (UPnP).
Code:
2014-11-29 17:46:59 receive version message: /Satoshi:0.9.3/: version 70002, blocks=332165, us=0.0.0.0:32805, them=104.45.145.179:8333, peer=104.45.145.179:8333
2014-11-29 17:46:59 Added time data, samples 2, offset -1 (+0 minutes)
2014-11-29 17:47:01 UPnP Port Mapping successful.
2014-11-29 17:46:59 Added time data, samples 2, offset -1 (+0 minutes)
2014-11-29 17:47:01 UPnP Port Mapping successful.
And stuck again.
Maybe it's my provider. But I fail to see how we then can handshake and orphaned blocks do get here.
So.. I installed a fresh new VPS with a huge pipe and scp'ed my initial setup and binaries.
I connected again to eldinhadzic.org (1000 Mb/s) which has been really whooshing blocks last night, and still nothing. Not blocking by IP it seems. Maybe it's my BTC address then..
Now my node is sync'ing with the network ok. I just hope this will be done before I reach my retirement age..
This, friends of BTC, is going nowhere fast.
Seems I'm done here. Not much help nor support. I will go now. Any mention of me in forums or press will be bogus. It has been one heck of a ride.. Gained some, lost everything again. But it has been fun by all means.
Hmm.. They even 'jacked my old nick.
Shrike.
PS. My IP here has been obfuscated by the system of an old friend. Don't bother him, hm?
try my node 191.236.50.217 (hosted on microsoft azure, 100Mb/s connection)
Problem: Blocks are not loading or loading very slow, so filling the blockchain database takes forever.
One solution is to aquire bootstrap.dat via the Torrent network. That will help, but 22+ GB will take hours.
- The current bootstrap.dat contains 317000 blocks.
The bootstrap.dat needs to be placed in the directory containing bitcoin.conf and wallet.dat. Better make a clean start and just delete everything else in that directory.
After starting either bitcoind or bitcoin-qt, the blocks from bootstrap.dat file will be loaded in the newly created blochain database structure.
- This can take a while.
After loading all blocks from bootstrap.dat, the file is renamed bootstrap.dat.old.
- Better not delete this file right away when you have enough space left on your disc(s), because you never know if/when you're going to need it again.
Another solution is to connect to very fast nodes on the bitcoin network with the "-connect=" directive. But you'd have to start bitcoind for that using the command line interface.
- Here's the latest list:
My problem: Did all that, but..
After downloading and importing bootstrap.dat and then conncting to the fast nodes, my database crashed a few times because I failed to see the problem was the canned version of bitcoind I used on Ubuntu 14.04. After I compiled bitcoind and bitcoin-qt from source myself the problem seemed to be over. But now I am stuck again because the fast nodes seemed to have locked out my IP for pulling too much data, or because of a "misbehaving node status" because I pulled the same blocks a few times. I don't know.
The only thing I do know is that I am stuck again on a frustratingly slow bitcoin network.
Then of course I thought that perhaps "misbehaving" node IP's were propagated over the network leaving my IP address essentially stranded for ever. Like I said, I don't know. But blocks are not loading.
One solution is to aquire bootstrap.dat via the Torrent network. That will help, but 22+ GB will take hours.
- The current bootstrap.dat contains 317000 blocks.
The bootstrap.dat needs to be placed in the directory containing bitcoin.conf and wallet.dat. Better make a clean start and just delete everything else in that directory.
After starting either bitcoind or bitcoin-qt, the blocks from bootstrap.dat file will be loaded in the newly created blochain database structure.
- This can take a while.
After loading all blocks from bootstrap.dat, the file is renamed bootstrap.dat.old.
- Better not delete this file right away when you have enough space left on your disc(s), because you never know if/when you're going to need it again.
Another solution is to connect to very fast nodes on the bitcoin network with the "-connect=
- Here's the latest list:
Code:
last updated 2014.11.25
-------------------------------------------------------------------------------------------------
IP - location - owner[1] - speed - info/stats page[2] - testnet
-------------------------------------------------------------------------------------------------
eldinhadzic.org[4] - LA, USA - eldinhadz - 1000 mbit/s - no - no
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
[4] IP is 173.236.158.177
-------------------------------------------------------------------------------------------------
IP - location - owner[1] - speed - info/stats page[2] - testnet
-------------------------------------------------------------------------------------------------
eldinhadzic.org[4] - LA, USA - eldinhadz - 1000 mbit/s - no - no
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
[4] IP is 173.236.158.177
My problem: Did all that, but..
After downloading and importing bootstrap.dat and then conncting to the fast nodes, my database crashed a few times because I failed to see the problem was the canned version of bitcoind I used on Ubuntu 14.04. After I compiled bitcoind and bitcoin-qt from source myself the problem seemed to be over. But now I am stuck again because the fast nodes seemed to have locked out my IP for pulling too much data, or because of a "misbehaving node status" because I pulled the same blocks a few times. I don't know.
The only thing I do know is that I am stuck again on a frustratingly slow bitcoin network.
Then of course I thought that perhaps "misbehaving" node IP's were propagated over the network leaving my IP address essentially stranded for ever. Like I said, I don't know. But blocks are not loading.
Jump to: