I'm getting that same error. Anyone have any solutions that don't involve reloading everything? Heh...

I got my erupters yesterday and they've been hashing away like crazy ever since! I'm using bfgminer on Ubuntu 12.04 and getting over 330 Mh/sec per erupter and roughly 1% HW errors, which is negligible. Thanks!

The latest update seems to have done the trick! Thanks!

I really know nothing about git except how to use it to grab a copy of some code from Github. Running that git command in either my bitcoin-abe directory or its parent isn't showing anything, so I must have moved things around enough that git became confused. I can see in my command history where I fetched Abe using "git clone," so I know that's how I originally got it.

I did think to save a slice of the transaction history. I was running Abe in an infinite loop where it was using RPC to fetch the latest blocks/transactions from bitcoind, sleeping 60 seconds, and doing it again. The last block I got successfully was 251552 ("block_tx 251552 21898522") followed by several minutes of successful "mempool tx" commits, the last one being "mempool tx 21898948", then one of my script's 60-second sleeps, then the error I posted above. There were no successful transactions after that last "mempool tx" one.

I have made no local modifications to the code at all.

After having Abe running for weeks with no issues at all, I suddenly ran into this:


Any ideas? It's using MySQL as the back.

I've never done a group buy before, so I just want to be clear - US shipping is 0.12 BTC for any quantitiy up to 100 miners, right? So the cost for one miner with shipping and no insurance would be 0.33 + 0.12 for a total of 0.45?

Can someone explain what "leaking shares" means? I've been mining for a few months now but there's still quite a bit of the nitty-gritty details I don't fully understand.

Something's still not right. I'm getting a whole bunch of these:

Thanks, that worked perfectly! Now the only weirdness is that this keeps showing up in my Apache error log every time I search by Bitcoin address (address redacted in example below):


Everything still works just fine, though. Thanks again!

Is there any way for Abe to not update the database with the latest transactions? Running in FastCGI mode, most requests take a long time to return a result because Abe is reading the most recent transactions and inserting them into the database. I know I can start in standalone mode, but then what's the point of FastCGI mode at all? Ideally what I'd like to do is have a process that runs in the background loading new transactions, sleeping for a few seconds or minutes, and loading again, forever. And the FastCGI side of things would just be a user interface to the back-end database, basically. Is that possible? Am I missing something obvious?

Ha! "The Dark Lord" - that's perfect! It looks like the Dark Lord has himself some serious ASIC hardware.

Manually setting the chain_id with sqlite3 seems to have worked! Thanks!

Hi! I'm trying to get Abe working through RPC instead of reading my blockchain files directly and I'm having problems. I believe I've met all the requirements listed at the end of abe.conf regarding RPC, but when I try to start Abe, I get this:


I see almost no references in the documentation to "chain_id" so I'm really not sure what to do. Google has been no help. I tried renaming abe.sqlite and hoping it would just rebuild the entire database from scratch using RPC and in that case I get this:


Any ideas?

At current difficulties I reach the payout queue (0.16777216 BTC, a.k.a. 100 "tonal bitcoins") in about 5 days. Depending on luck and speed of block confirmation I'll then wait another day or so to actually get my payout.

I'm not sure what feedback you're looking for, but I'm only running about 520 Mh/sec and Eligius has been good to me. I've maintained a very steady hash rate since the recent problems have been resolved and I get my payouts like I should.

As of a few days ago I was also seeing screwiness with hash rate unless I stuck to using stratum instead of GBT. My hash rate would be quite variable and, as I said before, sometimes one of my miners would get stuck in a state where it would constantly throw an error about "unknown user" until I killed and restarted it. Using stratum, none of these problems appear, so I've stuck with that. My hash rate is where it should be and I don't see any weird errors.

I might be interested. Is there a datasheet available for the Avalon chips? I've got years of experience with electronics as a hobbyist but I'm not an engineer, so I have limits as to what I'm capable of designing/building.

My understanding, as a newcomer to Bitcoin and to mining, and as someone with an order for a Little Single SC that I hope to see delivered some day:

BFL produced and shipped some decent FPGA-based mining hardware in the past. They are making the transition to ASIC hardware and have had a bitch of a time getting things right. ASIC engineering is really hard, even when you're used to designing and manufacturing electronics at a higher level (printed circuit boards, etc.) It took a long time to get the ASIC design right and it uses a lot more power than they thought it would. Their problems stem not from their engineering so much as their management of expectations. They were way too optimistic about their timeline and now some people are beyond pissed because they pre-ordered last summer and have yet to receive their promised hardware. But the ASIC design is done, the first Jalapenos have shipped, the redesigned cases and power supplies for the Singles and Little Singles are almost done, and it looks like there's finally a light at the end of the tunnel. A lot of people will accuse BFL of being scammers, but I don't personally believe that to be the case. They've produced ASIC hardware and gotten it into the hands of third parties for testing. Yes, it took a lot longer than expected, but I have no reason to think I won't eventually get my Little Single.

I think this is a fantastic idea!

I'll send a note to myself at home to throw a few testnet coins your way. When I was first experimenting with mining I mined on testnet with a GPU that gave me a whopping 15 MH/sec. It was absolutely worthless in the real world but got me a few blocks in a day or two on the test network. I think I did donate the vast majority of them back to the Mojocoin faucet since I'd used it before, but I'm happy to do so again.