Quote from: John Tobey on June 18, 2013, 02:27:43 AM

Quote from: pointychimp on June 17, 2013, 09:22:29 PM

I keep getting a "RuntimeError: maximum recursion depth exceeded" error. It happens every time I start abe up, and every time I access a page the error shows up in the console.

This has been on the to-do list for a long time. I'll give it another look, but as I recall, it would take the better part of a day to code and test.

First, run Abe once with --rescan in case that solves it. If you know Python, you can try sys.setrecursionlimit(300000) as suggested here. (Replace 300000 with a few more than the number of blocks in your chain, or try lower numbers until either success or another kind of crash.)

I think this happens when the block files are "very" out of sequence: when a sequence of 1000 or more blocks all occur before one of their common ancestors. Could this be the case with your block files? Maybe this is normal for the latest Bitcoin versions, which I have not tested. Is there anything unusual about how your block files were created, or did you download the chain again after running Abe the first time?

I don't think I did anything unusual. I think I did copy block files from one of my computers to my server in order to speed up the chain download time. Problem is I don't remember if I did that before running abe for the first time or after. I'm currently letting abe rescan. If this doesn't work, I might just bite the bullet, remove everything from the mySQL database, delete my .bitcoin/ directory, download the blockchain the conventional way, and try again.

Thanks for the help. I'll try to remember to report back if I ever get this solved!