-
Notifications
You must be signed in to change notification settings - Fork 177
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash in AppInit() upon start (EXCEPTION: NSt8ios_base7failureE) #115
Comments
This means that one of the unserialisation routines fails. It is probably really related to corrupt data files (or a bug in the format upgrades done recently, but since the upgrade works in general, I don't see why it would fail for you). I don't really see what we could do about corrupt data files. If you still want to find out more, you can run namecoind in a debugger (e. g., gdb with "catch throw") and see where exactly (backtrace) the exception is thrown. |
I ran into this one once when I had renamed/deleted blkindex.dat IIRC. I had to rename my Namecoin directory and redownload the blockchain (once it is finished you can copy the wallet.dat to the new data folder). |
I'll most probably end up doing what phelixbtc suggests.
Going up the trace I found dbset to contain references of blkindex.dat and nameindex.dat. |
I know it's bad to suggest root causes, but could it be that a previous blkindex.dat rewrite didn't complete properly? Namecoind isn't running and this is my ~/.namecoin:
|
From your backtrace it is clear that blkindex.dat is the problem. Also, as you observed, the rewrite should have finished. However, actually I believe that even if you killed the daemon while it was rewriting, there "shouldn't" be a problem (the database file would just be larger than necessary and contain lots of empty pages). However, I've not actually tested that, of course. So hopefully this doesn't indicate a "real" bug. |
I don't know. Anyway, I removed blkindex.dat and restarted it and it's On Tue, Jun 17, 2014 at 6:16 PM, Daniel Kraft [email protected]
Pysiak |
Note that, as far as my understanding goes, you can't "recover" from a missing/corrupted blkindex.dat in the same way as you can recreate the nameindex. I believe that if you delete blkindex.dat (or have to delete it), then you also should remove the blk*.dat files since the whole blockchain will be downloaded again anyway. (Since I do not yet know fully how the networking code works, this may be wrong - but I believe it is the case. You should be able to see whether or not the blk0001.dat file is double its initial size after you have finished syncing.) |
Well, that's what I thought so too and I figured blk.dat files need to go On Wed, Jun 18, 2014 at 11:15 AM, Daniel Kraft [email protected]
Pysiak |
Closing as this issue did not bubble up any more. |
b0210a9 Merge pull request namecoin#135 ee3eb4b Fix a memory leak and add a number of small tests. 4d879a3 Merge pull request namecoin#134 d5e8362 Merge pull request namecoin#127 7b92cf6 Merge pull request namecoin#132 0bf70a5 Merge pull request namecoin#133 29ae131 Make scalar_add_bit test's overflow detection exact 9048def Avoid undefined shift behaviour efb7d4b Use constant-time conditional moves instead of byte slicing d220062 Merge pull request namecoin#131 82f9254 Fix typo 601ca04 Merge pull request namecoin#129 35399e0 Bugfix: b is restricted, not r c35ff1e Convert lambda splitter to pure scalar code. cc604e9 Avoid division when decomposing scalars ff8746d Add secp256k1_scalar_mul_shift_var bd313f7 Merge pull request namecoin#119 276f987 Merge pull request namecoin#124 25d125e Merge pull request namecoin#126 24b3c65 Add a test case for ECDSA recomputing infinity 32600e5 Add a test for r >= order signature handling 4d4eeea Make secp256k1_fe_mul_inner use the r != property be82e92 Require that r and b are different for field multiplication. 597128d Make num optional 659b554 Make constant initializers independent from num 0af5b47 Merge pull request namecoin#120 e2e8a36 Merge pull request namecoin#117 c76be9e Remove unused num functions 4285a98 Move lambda-splitting code to scalar. f24041d Switch all EC/ECDSA logic from num to scalar 6794be6 Add scalar splitting functions d1502eb Add secp256k1_scalar_inverse_var which delegates to GMP b5c9ee7 Make test_point_times_order test meaningful again 0b73059 Switch wnaf splitting from num-based to scalar-based 1e6c77c Generalize secp256k1_scalar_get_bits 5213207 Add secp256k1_scalar_add_bit 3c0ae43 Merge pull request namecoin#122 6e05287 Do signature recovery/verification with 4 possible recid case e3d692f Explain why no y=0 check is necessary for doubling f7dc1c6 Optimize doubling: secp256k1 has no y=0 point 666d3b5 Merge pull request namecoin#121 2a54f9b Correct typo in comment 9d64145 Merge pull request namecoin#114 99f0728 Fix secp256k1_num_set_bin handling of 0 d907ebc Add bounds checking to field element setters bb2cd94 Merge pull request namecoin#116 665775b Don't split the g factor when not using endomorphism 9431d6b Merge pull request namecoin#115 e2274c5 build: osx: attempt to work with homebrew keg-only packages git-subtree-dir: src/secp256k1 git-subtree-split: b0210a95da433e048a11d298efbcc14eb423c95f
Hi,
On latest git, one of my namecoin installations is crashing upon start.
I suppose it might be reacting this way to corrupt files.
Any way I can help debugging it and hopefully find a way for namecoin to handle this?
The text was updated successfully, but these errors were encountered: