Sorry, this is an issue with Python modules on Mac, and I have no relevant experience. Put this in a file and run it with "python FILE.py". It will have to complete without error before you can use Abe:

Code:

import MySQLdb

Thank you John, also for your respond on my PN.Indeed, this helps me as a non abe-experienced to locate the mac-based problem.

If I leave it off, the error message is "../Application Support/Bitcoin/blck0001.dat not found".In case I use /blocks, the error message points correctly to "../Application Support/Bitcoin/blocks/blck0001.dat".Now I am even more confused.

While ABE searches after blck0001.dat, blck00001.dat is existent, and would be perhaps the correct file?Is this a misconfiguration?

The blockchain loading is still at the very beginning, I just ran bitcoin-qt once, as listed in the read me.

Now after about 14 days of importing it's finally done Anyway everything seems to be working just fine I only got one small problem. It's only importing new blocks when I load a new webpage in the Abe interface. Should it really be like that? So if I for example stop using the web interface for about 1 hour then when I request one page load it will star importing the 6 missing blocks. Why doesn't Abe just import the block as soon my bitcoin-qt instance accepts the new block?

Now after about 14 days of importing it's finally done Anyway everything seems to be working just fine I only got one small problem. It's only importing new blocks when I load a new webpage in the Abe interface. Should it really be like that? So if I for example stop using the web interface for about 1 hour then when I request one page load it will star importing the 6 missing blocks. Why doesn't Abe just import the block as soon my bitcoin-qt instance accepts the new block?

Yup, this is an underdocumented quirk. There are many ways to keep Abe up to date, an no one fits every need.

You can use a script like abe_loader. Actually, abe_loader is more complex than needed. It watches bitcoind's debug.log for hints that a block has arrived. Now that bitcoind supports blocknotify, we could just add something like this to bitcoin.conf:

One more question is there a way to check so the information in the mysql database is intact? (That does not take 14 days)

A complete check of all invariants does not exist. It would be a nice feature. Abe/verify.py does a small fraction of the work, calculating Merkle roots from stored transaction hashes. I haven't tested it lately.

The resulting block explorer (or part of one up to block 643 only, which is where it stops) can be seen on my test page at http://exploretheblocks.com:27700/chain/ElephantCoin?count=500. (I've changed everything to port 27700 for testing purposes). This part-block-explorer seems to have a number of very odd-looking blocks, for example block 513, 515 and 517 and the "final" block 643

Yes, you're right, Elephantcoin does have transaction messages. I had a feeling that might be something to do with the problems I've been having. Is there any fix that might allow an Abe Explorer to be set up?

If I leave it off, the error message is "../Application Support/Bitcoin/blck0001.dat not found".In case I use /blocks, the error message points correctly to "../Application Support/Bitcoin/blocks/blck0001.dat".Now I am even more confused.

While ABE searches after blck0001.dat, blck00001.dat is existent, and would be perhaps the correct file?Is this a misconfiguration?

Old versions of Bitcoin start with blk0001.dat, and new (0.8.x) ones start with blocks/blk00000.dat. To accommodate all known versions, including users who upgrade, Abe first searches in datadir for the blk*.dat series, and then in the blocks subdirectory for blk00000.dat. Since you use a new bitcoin-qt, it should not find blk0001.dat but should continue and load blocks/blk00000.dat.

The blockchain loading is still at the very beginning, I just ran bitcoin-qt once, as listed in the read me.

How many blk*.dat files are in "../Application Support/Bitcoin/blocks" ? Does Abe exit after the error message about blck0001.dat? Is that a typo, and did you mean blk0001.dat? Please paste the last several lines of output if Abe exits before it finishes loading.

Hey John, I scanned a coin in with the wrong address version, and now addresses appear incorrectly. I would reload te whole database, but there are 36 coins and it would take over 24 hours. Is there a way to drop a single chain and reload it?

Hey John, I scanned a coin in with the wrong address version, and now addresses appear incorrectly. I would reload te whole database, but there are 36 coins and it would take over 24 hours. Is there a way to drop a single chain and reload it?

If you have not enabled firstbits, use SQL to update chain.chain_address_version with the correct value. That should magically fix all the addresses. To find the correct value, you could start loading the chain in a new database, identically configured except for that address version. Then:

This may require conversion to and from a printable format such as hex, if you use binary_type=binary, which is now the default. In MySQL, replace chain_address_version with HEX(chain_address_version) in the select statement, and replace 'value' with UNHEX('hex value') in the update.

Ideally, we would have a command-line and web interface to manage chains.

With Bytecoin it appears to add the new blocks but it's not showing them.

This can result from a block being skipped or incorrectly loaded. Have you tried rescanning the blockfiles? Use --rescan or, if you have many coins in one database, you can rescan just the one by setting blkfile_number=1, blkfile_offset=0 in the appropriate row in the datadir table.