Author

Topic: [ANN][XCN] Cryptonite - NEW Thread | 1st mini-blockchain coin | Bounties! - page 209. (Read 215807 times)

full member
Activity: 952
Merit: 105
Does not work on Windows 7:

Assertion failed!
Program: C:\...\cryptonite-qt.exe
File:trieview.cpp, Line 305

Expression: blockCacha.ReadBlockFromDisk(block, pindex)

More info please: did you upgrade or start from scratch? Was the data dir populated already?

Besides: as a general rule, it's wise to BACKUP YOUR PRIVATE KEYS (in some encrypted form). That way, if the wallet db gets corrupted, or is incompatible with a future release (which shouldn't in the case of XCN, but you never know), you can always import the key and get your coins.

I downloaded the wallet from Official Site, launched it (the directory created a new one), it was synchronized for a long time and closed with an error. I restarted it, it waits a bit and produces an error with the error
Assertion failed!
Program: C:\...\cryptonite-qt.exe
File:trieview.cpp, Line 305"

My debug.log https://yadi.sk/i/13lRyzzW3GXNb5
i met with the same problem
newbie
Activity: 13
Merit: 0
Does not work on Windows 7:

Assertion failed!
Program: C:\...\cryptonite-qt.exe
File:trieview.cpp, Line 305

Expression: blockCacha.ReadBlockFromDisk(block, pindex)

More info please: did you upgrade or start from scratch? Was the data dir populated already?

Besides: as a general rule, it's wise to BACKUP YOUR PRIVATE KEYS (in some encrypted form). That way, if the wallet db gets corrupted, or is incompatible with a future release (which shouldn't in the case of XCN, but you never know), you can always import the key and get your coins.

I downloaded the wallet from Official Site, launched it (the directory created a new one), it was synchronized for a long time and closed with an error. I restarted it, it waits a bit and produces an error with the error
Assertion failed!
Program: C:\...\cryptonite-qt.exe
File:trieview.cpp, Line 305"

My debug.log https://yadi.sk/i/13lRyzzW3GXNb5
legendary
Activity: 2716
Merit: 1094
Black Belt Developer
Embarrassed hi pallas,


i have a personal data folder, now, all working again, not touched or moved, or copied or deleted any file,
just put /resync behind those 2 wallets, and have backups offcourse of the priv.key or wallet.dat files etc.

then woosh all fixed itself, under 10minutes, maybe 15 at another, synced working fine, thanks so much Pallas,


you are welcome, and thanks for reporting your experience.

@everybody: please keep in mind some block operations are still a bit slow; since sync from scratch is fast (because of mini-blockchain), you may get confused when comparing to the speed of catching up and other operations.
full member
Activity: 431
Merit: 105
 Embarrassed hi pallas,


i have a personal data folder, now, all working again, not touched or moved, or copied or deleted any file,
just put /resync behind those 2 wallets, and have backups offcourse of the priv.key or wallet.dat files etc.

then woosh all fixed itself, under 10minutes, maybe 15 at another, synced working fine, thanks so much Pallas,
member
Activity: 196
Merit: 15
Today +22.2% +33.3% and 27.532 31.07 BTC daily volume on BTC38!
I'm gonna bother them all day to get that wallet working again!

I think they are fixed the wallet
And buying cheap before running it Grin
legendary
Activity: 2716
Merit: 1094
Black Belt Developer
someone is pumping XCN on btc38... wonder what that means...

I hope they are planning to finally fix the wallet Grin

I got in contact with a couple english speaking guys working for btc38, they said they are going to try what I suggested and let me know :-)
legendary
Activity: 1208
Merit: 1003
someone is pumping XCN on btc38... wonder what that means...

I hope they are planning to finally fix the wallet Grin
legendary
Activity: 2716
Merit: 1094
Black Belt Developer
someone is pumping XCN on btc38... wonder what that means...
legendary
Activity: 1208
Merit: 1003
Today +22.2% and 27.532 BTC daily volume on BTC38!
I'm gonna bother them all day to get that wallet working again!

Smiley Hey pallas, please take a look at the pm box.
legendary
Activity: 2716
Merit: 1094
Black Belt Developer
Today +22.2% +33.3% and 27.532 31.07 BTC daily volume on BTC38!
I'm gonna bother them all day to get that wallet working again!
legendary
Activity: 2716
Merit: 1094
Black Belt Developer
Does not work on Windows 7:

Assertion failed!
Program: C:\...\cryptonite-qt.exe
File:trieview.cpp, Line 305

Expression: blockCacha.ReadBlockFromDisk(block, pindex)

More info please: did you upgrade or start from scratch? Was the data dir populated already?

Besides: as a general rule, it's wise to BACKUP YOUR PRIVATE KEYS (in some encrypted form). That way, if the wallet db gets corrupted, or is incompatible with a future release (which shouldn't in the case of XCN, but you never know), you can always import the key and get your coins.
newbie
Activity: 13
Merit: 0
Does not work on Windows 7:

Assertion failed!
Program: C:\...\cryptonite-qt.exe
File:trieview.cpp, Line 305

Expression: blockCacha.ReadBlockFromDisk(block, pindex)
full member
Activity: 140
Merit: 100
your damned if you do, your damned if you dont lol
heres how i upgraded to new wallet in windows 10 from the old wallet and kept all my coins n no issues .. this is not official method but it works good and is a logical method .

1 - sync your old wallet , close it .
2 - rename the cryptonite folder in app data to somethign else say "cryptoniteisgood" whateva u want rly .
3 - install the newer cryptonite wallet .. let it open ... then close it ... (it wont install over the top of the old one as u renamed the directory)
4 - go to old wallet directory u renamed and copy contents .
5 - paste that into the newer crypronite directory
6 - open new wallet and yeeew its now upgrade . synced and all my coins are there Smiley

i backed up everything on my old wallet as a saftey measure as well but it was not needed . it was smooth sailing for me and ive had no issues ... if this method does not work ... then there is another issue that must have already preexisted before the upgrade .

hope that can help any noobs like me Smiley
legendary
Activity: 2716
Merit: 1094
Black Belt Developer
HI pallas,
is there something wrong with xcn, network or so? the started wallets mining, just crashed out,
\how why all kinds of strange things in log.

could you explain maybe. resync did make the wallet start again, and then gets in at 2 years 31 weeks ago.
is this ok, but i notice its scanning the blocks dang fast, and tx index is enabled somehow, shows log,

and another wallet also just been working closed by me, had a power cut btw, was on did it off, restarting it,
not even showing error, not even starting, while typing, the resyncing one, at 23 weeks behind,

the synced one saying downloading trie now at 100% and currently balance showing 0 wich was not 0.!
but showing the tx's on the right side,
and now it froze the whole windows 10 system, saying runtime error, visual c++ runtime library, unusual way.

What's your current height? How does it compare to the block explorer?
legendary
Activity: 2716
Merit: 1094
Black Belt Developer
Quote

2017-03-31 05:44:40 Cryptonite version v0.1.2.0-gedc4e25-beta (Tue, 21 Mar 2017 15:34:46 +0100)
2017-03-31 05:44:40 Using OpenSSL version OpenSSL 1.0.1l 15 Jan 2015
2017-03-31 05:44:40 Default data directory C:\Users\coiner\AppData\Roaming\Cryptonite
2017-03-31 05:44:40 Using data directory F:\XCN\data
2017-03-31 05:44:40 Using at most 125 connections (2048 file descriptors available)
2017-03-31 05:44:40 Using 8 threads for script verification
2017-03-31 05:44:40 Using wallet wallet.dat
2017-03-31 05:44:40 init message: Verifying wallet...
2017-03-31 05:44:40 CDBEnv::Open : LogDir=F:\XCN\data\database ErrorFile=F:\XCN\data\db.log
2017-03-31 05:44:40 Renamed wallet.dat to wallet.1490939080.bak
2017-03-31 05:44:40 CDBEnv::Salvage : Database salvage found errors, all data may not be recoverable.
2017-03-31 05:44:40 Salvage(aggressive) found no records in wallet.1490939080.bak.
2017-03-31 05:44:44 Initialization result: 0
2017-03-31 05:44:44 Requesting shutdown
2017-03-31 05:44:44 Running Shutdown in thread
2017-03-31 05:44:44 Shutdown : In progress...
2017-03-31 05:44:44 StopNode()
2017-03-31 05:44:44 Shutdown : done
2017-03-31 05:44:44 Shutdown finished
2017-03-31 05:44:44 Shutdown result: 1
2017-03-31 05:44:44 Stopping thread
2017-03-31 05:44:44 Stopped thread

firstly i successful synced from crash with new latest binary, then i close the wallet.
Then i delete old wallet.data file and override with my old wallet before, and this happen  Huh

this means every coins in old wallet gone?

Not sure I understand: what's the "old wallet" and the "old wallet before"?
Are you sure the "old wallet before" wasn't corrupted already?
legendary
Activity: 2716
Merit: 1094
Black Belt Developer
I had a similar crash issue once, it looks like there is some broken or very old wallet on the network, generating invalid tx/blocks.
When it happened to me, I just restarted it and all went fine.
hero member
Activity: 781
Merit: 501
Quote

2017-03-31 05:44:40 Cryptonite version v0.1.2.0-gedc4e25-beta (Tue, 21 Mar 2017 15:34:46 +0100)
2017-03-31 05:44:40 Using OpenSSL version OpenSSL 1.0.1l 15 Jan 2015
2017-03-31 05:44:40 Default data directory C:\Users\coiner\AppData\Roaming\Cryptonite
2017-03-31 05:44:40 Using data directory F:\XCN\data
2017-03-31 05:44:40 Using at most 125 connections (2048 file descriptors available)
2017-03-31 05:44:40 Using 8 threads for script verification
2017-03-31 05:44:40 Using wallet wallet.dat
2017-03-31 05:44:40 init message: Verifying wallet...
2017-03-31 05:44:40 CDBEnv::Open : LogDir=F:\XCN\data\database ErrorFile=F:\XCN\data\db.log
2017-03-31 05:44:40 Renamed wallet.dat to wallet.1490939080.bak
2017-03-31 05:44:40 CDBEnv::Salvage : Database salvage found errors, all data may not be recoverable.
2017-03-31 05:44:40 Salvage(aggressive) found no records in wallet.1490939080.bak.
2017-03-31 05:44:44 Initialization result: 0
2017-03-31 05:44:44 Requesting shutdown
2017-03-31 05:44:44 Running Shutdown in thread
2017-03-31 05:44:44 Shutdown : In progress...
2017-03-31 05:44:44 StopNode()
2017-03-31 05:44:44 Shutdown : done
2017-03-31 05:44:44 Shutdown finished
2017-03-31 05:44:44 Shutdown result: 1
2017-03-31 05:44:44 Stopping thread
2017-03-31 05:44:44 Stopped thread

firstly i successful synced from crash with new latest binary, then i close the wallet.
Then i delete old wallet.data file and override with my old wallet before, and this happen  Huh

this means every coins in old wallet gone?
member
Activity: 115
Merit: 10
Not B troll & do something!
service staff 小欣: Hello, XCN wallet fault can't sync, can only contact the official repair, to purse repair after completion of the operation, we handled for you, the hope can help you, I wish you a happy life
(03-31 11:12) about this ticket, you feel: good | ordinary | bad
full member
Activity: 431
Merit: 105
HI pallas,
is there something wrong with xcn, network or so? the started wallets mining, just crashed out,
\how why all kinds of strange things in log.

could you explain maybe. resync did make the wallet start again, and then gets in at 2 years 31 weeks ago.
is this ok, but i notice its scanning the blocks dang fast, and tx index is enabled somehow, shows log,

and another wallet also just been working closed by me, had a power cut btw, was on did it off, restarting it,
not even showing error, not even starting, while typing, the resyncing one, at 23 weeks behind,

thanks for help

4 Marked 0000000011cd4d74282832a071e4cc7e45beb8a905999a69c4b830247083d6a6 as descending from invalid
2017-03-30 19:44:44 Marked 0000000017614c0660ee7f9e31115a7f4babd2e0f90f60289dd237b7d72cc930 as descending from invalid
Requesting initialize
Running AppInit2 in thread
2017-03-31 01:00:55
UpdateTip: new best=0000000011cd4d74282832a071e4cc7e45beb8a905999a69c4b830247083d6a6  height=1395502  log2_work=57.467737  tx=497  date=2017-03-30 14:17:21 progress=1.000000
2017-03-30 19:44:37 Connect tip : 0000000017614c0660ee7f9e31115a7f4babd2e0f90f60289dd237b7d72cc930
2017-03-30 19:44:38 AddToWallet e8a09ab5ed828f38b83a11403263c10d4b824da0cf2c9bd41fe4cddc8bddd464  new
2017-03-30 19:44:38 UpdateTip()
2017-03-30 19:44:38 UpdateTip: new best=0000000017614c0660ee7f9e31115a7f4babd2e0f90f60289dd237b7d72cc930  height=1395503  log2_work=57.467737  tx=499  date=2017-03-30 14:21:09 progress=1.000000
2017-03-30 19:44:38 AddToWallet e8a09ab5ed828f38b83a11403263c10d4b824da0cf2c9bd41fe4cddc8bddd464  
2017-03-30 19:44:42 Activate 0000000017614c0660ee7f9e31115a7f4babd2e0f90f60289dd237b7d72cc930
2017-03-30 19:44:44 Master hash mismatch: 0000000000fa0dd19770db2d0da664525ccc302f3180f510b9e4a645bd93e595 a21b09d0146c5c2626c3e696cbc035948f74425712cd10d229f7c869e9497d74 7c5484a5aaa9b9a97e45a189a83c3adc5858ab8d499ac7971868cbe3d6dacf0e
2017-03-30 19:44:44 Activate failed
2017-03-30 19:44:44 ERROR: ActivateBestChain() : inputs missing/spent
2017-03-30 19:44:44 Marked 0000000000fa0dd19770db2d0da664525ccc302f3180f510b9e4a645bd93e595 as invalid
2017-03-30 19:43:39 CheckForkWarningConditions(): bestForkTip=00000000064841420c17c7bb43b3d8e1d422232a0ff815f8c4684ef7448b9052(1395400) bestForkBase=0000000019313fb625a2086ca8a519cdef73a890a35b6e461d6e41152ccef9df(1395399)
2017-03-30 19:43:39 CheckForkWarningConditions(): best fork is not dangerousInvalidBlockFound: invalid block=0000000000fa0dd19770db2d0da664525ccc302f3180f510b9e4a645bd93e595  height=1395243  log2_work=57.467666  date=2017-03-30 08:34:52
2017-03-30 19:43:39 InvalidChainFound:  current best=000000001bc59065fdb5aee6c476a71bf84c623a9695712532ea18a4ab6d1b81  height=1395772  log2_work=57.467808  date=2017-03-30 19:41:39
2017-03-30 19:43:39 Disconnect tip : 000000001bc59065fdb5aee6c476a71bf84c623a9695712532ea18a4ab6d1b81

2017-03-30 19:35:39 ReadBlockFromDisk: Could not find block 0000000003d02d31b24fcf4c7385f77f0ceb8672996709fc44b1d3529bb5cdca
2017-03-30 19:36:03 Requesting 1 blocks from 46.105.118.15:8253
2017-03-30 19:36:03 Connect tip : 0000000013711063ff9c3efb4416bac5b069487e8de337a4d5bdaa600310304f
2017-03-30 19:36:03 UpdateTip()
2017-03-30 19:36:03 UpdateTip: new best=0000000013711063ff9c3efb4416bac5b069487e8de337a4d5bdaa600310304f  height=1395769  log2_work=57.467808  tx=821  date=2017-03-30 19:35:21 progress=1.000000
2017-03-30 19:36:08 Activate 0000000013711063ff9c3efb4416bac5b069487e8de337a4d5bdaa600310304f
2017-03-30 19:36:10 Writing file 0000000013711063ff9c3efb4416bac5b069487e8de337a4d5bdaa600310304f
2017-03-30 19:36:10 Serialized: 224378 bytes
2017-03-30 19:36:10 ProcessBlock: ACCEPTED 1395769
2017-03-30 19:36:10 ProcessBlock: ACCEPTED 1395769
2017-03-30 19:37:07 Requesting 1 blocks from 46.105.118.15:8253
2017-03-30 19:37:08 Connect tip : 0000000009c00983838e897d498266d8b66f47ceaf16d2e5e650df8e2ce9a994
2017-03-30 19:37:08 UpdateTip()
2017-03-30 19:37:08 UpdateTip: new best=0000000009c00983838e897d498266d8b66f47ceaf16d2e5e650df8e2ce9a994  height=1395770  log2_work=57.467808  tx=822  date=2017-03-30 19:35:51 progress=1.000000
2017-03-30 19:37:12 Activate 0000000009c00983838e897d498266d8b66f47ceaf16d2e5e650df8e2ce9a994
2017-03-30 19:37:14 Writing file 0000000009c00983838e897d498266d8b66f47ceaf16d2e5e650df8e2ce9a994
2017-03-30 19:37:14 Serialized: 224378 bytes
2017-03-30 19:37:14 ProcessBlock: ACCEPTED 1395770
2017-03-30 19:37:14 ProcessBlock: ACCEPTED 1395770
2017-03-30 19:38:40 Requesting 1 blocks from 46.105.118.15:8253
2017-03-30 19:38:41 Connect tip : 000000000c8cf75c8d40d984ae97004c4dd316d7bde15e55a715dba4077d1c8e
2017-03-30 19:38:41 UpdateTip()
2017-03-30 19:38:41 UpdateTip: new best=000000000c8cf75c8d40d984ae97004c4dd316d7bde15e55a715dba4077d1c8e  height=1395771  log2_work=57.467808  tx=823  date=2017-03-30 19:37:53 progress=1.000000
2017-03-30 19:38:45 Activate 000000000c8cf75c8d40d984ae97004c4dd316d7bde15e55a715dba4077d1c8e
2017-03-30 19:38:47 Writing file 000000000c8cf75c8d40d984ae97004c4dd316d7bde15e55a715dba4077d1c8e
2017-03-30 19:38:47 Serialized: 224378 bytes
2017-03-30 19:38:47 ProcessBlock: ACCEPTED 1395771
2017-03-30 19:38:47 ProcessBlock: ACCEPTED 1395771
2017-03-30 19:40:18 Activate 000000001d839951da6571154f2b33c7bbcbddf938509096abf6fcd51b03a111
2017-03-30 19:40:20 ERROR: DisconnectBlock() : no undo pos vailable
2017-03-30 19:40:20 ERROR: slice failed to materialize = 000000001d839951da6571154f2b33c7bbcbddf938509096abf6fcd51b03a111
2017-03-30 19:40:20 ProcessMessage(getslice, 72 bytes) FAILED
2017-03-30 19:40:22 UPnP Port Mapping successful.
2017-03-30 19:40:24 Activate 000000001d839951da6571154f2b33c7bbcbddf938509096abf6fcd51b03a111
2017-03-30 19:40:26 ERROR: DisconnectBlock() : no undo pos vailable
2017-03-30 19:40:26 ERROR: slice failed to materialize = 000000001d839951da6571154f2b33c7bbcbddf938509096abf6fcd51b03a111
2017-03-30 19:40:26 ProcessMessage(getslice, 72 bytes) FAILED
2017-03-30 19:43:09 Requesting 1 blocks from 46.105.118.15:8253
2017-03-30 19:43:33 Requesting 1 blocks from 46.105.118.15:8253
2017-03-30 19:43:33 Connect tip : 000000001bc59065fdb5aee6c476a71bf84c623a9695712532ea18a4ab6d1b81
2017-03-30 19:43:33 UpdateTip()
2017-03-30 19:43:33 UpdateTip: new best=000000001bc59065fdb5aee6c476a71bf84c623a9695712532ea18a4ab6d1b81  height=1395772  log2_work=57.467808  tx=824  date=2017-03-30 19:41:39 progress=1.000000
2017-03-30 19:43:33 Cannot fastforward chain because of missing data: 0000000013b6114a382882b409ac660a1a2db70c99cfc4a72e057dd613545338
2017-03-30 19:43:37 Activate 000000001bc59065fdb5aee6c476a71bf84c623a9695712532ea18a4ab6d1b81
2017-03-30 19:43:39 Master hash mismatch: 0000000000fa0dd19770db2d0da664525ccc302f3180f510b9e4a645bd93e595 a21b09d0146c5c2626c3e696cbc035948f74425712cd10d229f7c869e9497d74 7c5484a5aaa9b9a97e45a189a83c3adc5858ab8d499ac7971868cbe3d6dacf0e
2017-03-30 19:43:39 Activate failed
2017-03-30 19:43:39 ERROR: ActivateBestChain() : inputs missing/spent
2017-03-30 19:43:39 Marked 0000000000fa0dd19770db2d0da664525ccc302f3180f510b9e4a645bd93e595 as invalid
2017-03-30 19:43:39 Marked 000000001355ff50daae0f9575cb48b8e056b6a89b1d25b8978f98f8a2171d91 as descending from invalid


the synced one saying downloading trie now at 100% and currently balance showing 0 wich was not 0.!
but showing the tx's on the right side,
and now it froze the whole windows 10 system, saying runtime error, visual c++ runtime library, unusual way.
member
Activity: 96
Merit: 25
This is from before the crash where errors first started:

Code:
2017-03-30 19:20:07 receive version message: /Satoshi:0.1.2/: version 10100, blocks=1381164, us=49.197.214.164:43690, them=0.0.0.0:0, peer=95.25.185.82:8253
2017-03-30 19:20:07 Added time data, samples 13, offset -42 (+0 minutes)
2017-03-30 19:20:07 nTimeOffset = -55  (+0 minutes)
2017-03-30 19:20:09 Requesting 1 blocks from 46.105.118.15:8253
2017-03-30 19:20:10 Connect tip : 000000001b6a21f23aad79884aee1202e80c0d67554be26f4413de3879586a75
2017-03-30 19:20:10 UpdateTip()
2017-03-30 19:20:10 UpdateTip: new best=000000001b6a21f23aad79884aee1202e80c0d67554be26f4413de3879586a75  height=1395759  log2_work=57.467805  tx=362  date=2017-03-30 19:18:37 progress=1.000000
2017-03-30 19:20:18 Activate 000000001b6a21f23aad79884aee1202e80c0d67554be26f4413de3879586a75
2017-03-30 19:20:22 Writing file 000000001b6a21f23aad79884aee1202e80c0d67554be26f4413de3879586a75
2017-03-30 19:20:22 Serialized: 224378 bytes
2017-03-30 19:20:22 ProcessBlock: ACCEPTED 1395759
2017-03-30 19:20:22 ERROR: ReadBlockFromDisk : OpenBlockFile failed
2017-03-30 19:20:22 ReadBlockFromDisk: Could not find block 0000000008e42dc53b54dd7e9eef09ca77449d851d48e05ef058996567088613
2017-03-30 19:20:22 ProcessBlock: ACCEPTED 1395759
2017-03-30 19:20:22 ERROR: ReadBlockFromDisk : OpenBlockFile failed
2017-03-30 19:20:22 ReadBlockFromDisk: Could not find block 00000000095d1faaed21a39335cae476db3664113f969d6f2c49e584093c349d
2017-03-30 19:20:22 ERROR: ReadBlockFromDisk : OpenBlockFile failed
2017-03-30 19:20:22 ReadBlockFromDisk: Could not find block 000000000a325326a9a15f4fca0539df887b4b932a0a112144d9a22a6b28b3a9
2017-03-30 19:20:22 ERROR: ReadBlockFromDisk : OpenBlockFile failed
2017-03-30 19:20:22 ReadBlockFromDisk: Could not find block 00000000134c8cec2fadafef8c1b61b30dfa4842aadf8e77275e9f83630bf074
2017-03-30 19:20:22 ERROR: ReadBlockFromDisk : OpenBlockFile failed
Jump to: