 Show Posts
|
|
Pages: [1]
|
try my node 104.45.145.179 (hosted on microsoft azure, 100Mb/s connection)
Thanks  : 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
Then nothing. Second try with bitcoin-qt, because I saw bitcoind did not open any ports (UPnP). 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.
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? |
|
|
|
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=<IP>" directive. But you'd have to start bitcoind for that using the command line interface. - Here's the latest list: 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 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. |
|
|
|
Please! keep the dramaqueen out. I am not even sure I understand your problem - the technical one, I dont give a fuck about how long you mined, your "status" or what you need your coins for - and frankly, I dont care to read through the wall of drama to figure out. The last few posts derailed this thread and if you need further help with bitcoin core I suggest you start a thread in the tech support section and keep it technical.
You are right. I just cracked up because I saw stuff getting lost. Sorry 'bout the drama. Problem is: 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. 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. |
|
|
|
Activity != posts. I would love to hide these stats next to my posts by the way.
I judged you based on what and how you posted here. Also your forum title as of writing this actually IS "Newbie". Enjoy your amazing ubuntu machine, Linux skills and fantastical amount of BTC that you mined far earlier than me.
Hm.. This is the real newbie answer. Biased because of entrance time, and board status.. I mine Bitcoins yes, for years now. Yes, I CPU mined them also. No, I did not buy a pizza back then. But whatever amount, there was very little converted to fiat. So I ain't no fat cat like some, right? And yeah, some of my systems run Linux, some don't. How I stepped in? Well, I didn't expect a closed community like some of the newsgroups, and I certainly did not expect a post score based status thing. Some seem to need that. Like with reference codes in their .sig.. I didn't see that either. So I simply asked stuff I didn't know, right? I don't even know whether there is a propagation system for bad nodes. Should be if not Even though it leaves me dead now. Ah, f*ck this. |
|
|
|
Activity != posts. I would love to hide these stats next to my posts by the way.
I judged you based on what and how you posted here. Also your forum title as of writing this actually IS "Newbie". Enjoy your amazing ubuntu machine, Linux skills and fantastical amount of BTC that you mined far earlier than me.
Hm.. This is the real newbie answer. Biased because of entrance time, and board status.. I mine Bitcoins yes, for years now. Yes, I CPU mined them also. No, I did not buy a pizza back then. But whatever amount, there was very little converted to fiat. So I ain't no fat cat like some, right? And yeah, some of my systems run Linux, some don't. How I stepped in? Well, I didn't expect a closed community like some of the newsgroups, and I certainly did not expect a post score based status thing. Some seem to need that. Like with reference codes in their .sig.. I didn't see that either. So I simply asked stuff I didn't know, right? |
|
|
|
Can you see a newbie struggling with this? He just posted a few times in this thread... ;-) You don't need to run a full node or even the reference implementation if you want to use Bitcoin, alternatively you can just wait for 0.10 to come out where bootstrapping should work much faster. 1200 some posts makes you local super-hero hm? This my man is a sucker punch, a kick in the head to someone who is down. A glaring gloat.. I know what I can do, and I also know what can't be done in my situation now. Yeah, I have not been following devs for years, and yeah, I just took the new source, read the change log, and went on with business. While you were real busy creating your local super-hero status. You know nothing about who I am or how early I adopted Bitcoin. You know nothing about my systems knowledge. Nor about my knowledge of Bitcoin platforms and portability. You don't know if I had a time-window closing. The only thing you know is that I use bitcoind on Ubuntu 14.04 now. And I needed (!) to do it this way. You have not been of any help super-hero. You just did some lip-gymnastics here. But it's done now. I just made the mistake of trust. Once. Bye. |
|
|
|
Can you see a newbie struggling with this? He just posted a few times in this thread... ;-) You don't need to run a full node or even the reference implementation if you want to use Bitcoin, alternatively you can just wait for 0.10 to come out where bootstrapping should work much faster. Yeah.. Well it had to. |
|
|
|
|
Packing up..
I've compiled bitcoind and bitcoin-qt from source on Ubuntu 14.04. I mostly do that, but I was lazy this time so I got the canned version. I should've known better. Then I downloaded bootstrap.dat via Torrent and cleaned my system as to avoid any circumstance that could make things go FUBAR, and ran bitcoind. Nice, it worked: bitcoind was loading blocks from bootstrap.dat, and it seemed to work like a charm. No more corruption of the database like with the canned bitcoind. Good. When bitcoind finished loading from bootstrap.dat on block 31700, I stopped bitcoind. Then I ran bitcoin-qt . To read..: "No block source available. 1 year and 32 weeks behind." "19 active connections to the Bitcoin network," and "Catching up... Processed 232045 blocks of transaction history. ... " I know that my node seemed to be misbehaving because I had to reload the same blocks after every time the canned bitcoind seemed to corrupt the blockchain database. I have never ever experienced this with a self-compiled version of either bitcoind, or bitcoin-qt. Last night I pulled my blocks from famous 173.236.158.177, the blockchain database crashed a few times, and so I'm given no quarters anymore.
Can you see a newbie struggling with this? He or she doesn't want to be a programmer or systems expert, he or she just want to adopt this cool new fad.. Yeah, it shot up to $1,000 - hello.. geek millionaires - from nothing, and then crashed to like $275 - hello.. people who lost an arm and a leg - something, but hey people seem to think it's viable. Well, this single experience tells me that it is not. This is not a serious global payment system, decentralized or not. This is hobby stuff. And while fiat value - hey.. they CPU mined bitcoin - for some is still good, this is going nowhere really fast. I don't mean that bitcoin will disappear, because let's face it there is a lot of real money put in.. But like this? Like this one experience I am having now, after all these years? Just going it from the seat of my pants one time? Dudes, you are delusional..
Ok.. I will say it. This actually IRL screwed me over. Ok? There, now you can gloat. Another one bites the dust never to come back again. Happy now? Good.
|
|
|
|
-snip-
Answers or suggestions?
Launch with -connect=IP to a fast node for the rest. -cut- Well, that was a nice experience.. The database corrupted every single try and I couldn't find what did it.. So I compiled bitcoind from source and imported bootstrap.dat Then finally I went on to connect again to the IP's mentioned before, only to discover that.. I was blocked  Thanks guys.. The sole reason I appeared here was that I forgot.. one time only.. to backup the block chain database before re-installing a new OS on my computer. I got the grandfather instead of the father in the backup protocol. So.. Torrent'ing a bootstrap database, waiting for clues from the local super-heroes.. Because hey.. I just want to pay my insurance on Monday.. Then.. The realization that many 'contributors' just say "f*ck you, man.." in a newbie's face when he seems to be down and struggling.. I've seen this behavior before, and at the time I was disgusted by the apparent change. No one seemed to bother to read Virginia Shea anymore and just went on to become rampant egomaniacs. Yeah, I know.. This is frustration with the proceedings of a once promising protocol. But right now it seems you are in the tub with that frog. A question that reeds to be answered by each and every local bitcoin super-hero: Do you want a worldwide payment protocol, or just goof around for personal glory for some time. Of course there is some momentum still; you've got your new arrivals, and hey.. conferences where you can pat each other on shoulders how ultra-famous that guy is. That actually is my clue that you fail to see the significance of what you are holding in your hands right this minute. Later there will be the names, the guys with beards somewhere out there, telling how they had it in their own hands but lost it; fumbled, dropped the ball, and lost the game. So I smile, knowing that some of you will see, and many others will remain as blind as they are.. Now I really have that insurance to pay. And you're not helping, Eternal September people.. |
|
|
|
Hi, is anyone got a FRESH & CLEAN bootstrap.dat file around ?
Read the OP and download the torrent. I came as far as block 317000. That's more that 13 weeks old tells bitcoin-qt.. Then I got stuck. I have 12 active connections to the network. Is there a regularly, like every 24 hours, maintained version of bootstrap.dat out there? So.. I am pretty sure I can take this upon me. Automate it and let it rip. The only problem I see is the huge bandwidth capacity needed. Answers or suggestions? Please take the time to read OP.
=snip=
-cut-
Why not update the torrent more often?
A torrent works best when it is a large, static dataset that changes infrequently. That maximizes the ability to seed the data, enabling even part-timer seeders to contribute meaningfully. Less frequent changes also minimizes the risk that a malicious torrent will appear, with a long, malicious side chain. The current policy only updates the torrent after blocks are buried many thousands deep in the chain.
~~MZ~~ Yes, now I read the whole OP this makes sense. |
|
|
|
-snip-
Answers or suggestions?
Launch with -connect=IP to a fast node for the rest. -cut- Well, that was a nice experience.. The database corrupted every single try and I couldn't find what did it.. So I compiled bitcoind from source and imported bootstrap.dat Then finally I went on to connect again to the IP's mentioned before, only to discover that.. I was blocked Thanks guys.. |
|
|
|
-snip-
Answers or suggestions?
Launch with -connect=IP to a fast node for the rest. For windows hit Win+R to open the "run" window: enter: c:\Program Files\Bitcoin\bitcoin-qt.exe -connect=IPchange the IP to one from the list, the path as needed and click ok. For linux, open a terminal and enter bitcoind -connect=IPchange the IP and on some distros you have to give the full path to bitcoind. Note, this will not launch a GUI, use bitcoind getinfo so see the status. or run bitcoin-qt instead of bitcoind for GUI. Once synced, close bitcoin core and launch as usual. List of possible nodes: 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
Ah.. I didn't know that. Thanks! I used bitcoind and then tail'd the log file.. But this -connect=IP is very helpful. Much reading to do still |
|
|
|
Hi, is anyone got a FRESH & CLEAN bootstrap.dat file around ?
Read the OP and download the torrent. I came as far as block 317000. That's more that 13 weeks old tells bitcoin-qt.. Then I got stuck. I have 12 active connections to the network. Is there a regularly, like every 24 hours, maintained version of bootstrap.dat out there? So.. I am pretty sure I can take this upon me. Automate it and let it rip. The only problem I see is the huge bandwidth capacity needed. Answers or suggestions? |
|
|
|
|
