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/13lRyzzW3GXNb5from the debug log, it looks like it found a chain in the data directory, are you sure it was empty? also note that sync from scratch should take half an hour to a couple hours max. try with a clean datadir or running with the /rescan option. With a clean directory, the wallet starts, loads the blocks, then hangs on block 160 and then issues an error. All in the attached file https://yadi.sk/d/Y-AuKoeU3GXxLvThank you for your analysis Just ignore the error about block 160 and let it go. |
|
|
|
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!
+66.7% 24H Change 62.268 BTC 24H volume  |
|
|
|
Who put the snapshot of today's block up, my update a few days, and eight thousand did not update finished, but very slow very slow.
I'm uploading a new one now... please wait Here it is: https://mega.nz/#!UMA0jIJC!G6eu_06rhizCxmRDUb4MWaBVLmq4Uklz9tZTplERb6A |
|
|
|
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/13lRyzzW3GXNb5from the debug log, it looks like it found a chain in the data directory, are you sure it was empty? also note that sync from scratch should take half an hour to a couple hours max. try with a clean datadir or running with the /rescan option. |
|
|
|
 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. |
|
|
|
someone is pumping XCN on btc38... wonder what that means...
I hope they are planning to finally fix the wallet  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 :-) |
|
|
|
|
someone is pumping XCN on btc38... wonder what that means...
|
|
|
|
|
My ISP doesn't have IPv6 :-(
|
|
|
|
|
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!
|
|
|
|
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. |
|
|
|
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? |
|
|
|
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  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? |
|
|
|
|
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.
|
|
|
|
|
A block doesn't change its reward depending on the time it takes to mine it.
|
|
|
|
I downloaded the QT wallet on the official website, and then synchronized update a few days, today updated. Then close, and then re open the wallet, the above problems
That error message doesn't tell a lot, it just means that the headers it got are more than 1000 blocks newer than the current active block. It also means that the trie is active and OK. I need more information from the debug.log file, could you post more of it? |
|
|
|
Re open wallet display ：warning:saved state too old.Fast forward sync may not be possible.Run Resync!!!
Downloading blocks... 1394882 behind-may need resync-Click to resync
How long did you left the wallet closed? |
|
|
|
Getting the following errors:
./configure --with-crypto --with-curl Thanks, this worked and I got a successful compile. Next question. Is it possible to get a statically linked compile so I can copy this to other machines which do not have all the tools installed? Im asking because it was a real hurdle to get all the stuff setup on a single VM to compile, but I want to deploy to a large number of servers who do not have all the same setup/configuration. Not as trivial as it may seem. Start by trying "./configure LDFLAGS=-static" |
|
|
|
Coinmarketcap just updated XCN info with the new BE and ANN link  Pallas, did you happen to send the coin request to Bittrex? And did Bitfreak pass you the control of Twitter account? P.S. And btw, someone has to really explain to btc38 in their native language about the wallet, cuz: "service staff 小妮: Hello, XCN wallet malfunction, suspended deposit and deposit, please operation after the repair, to inconvenience you, I'm very sorry."
upd. BTC38 support last answer: "service staff 小妮: Wallet can normal open and synchronization, but can't import the old wallet data, shown as "unknown", can you solve?" I still don't understand what they can't see: old transactions? old addresses? I already sent them the blockchain snapshot link, it should include the block data they need. Or, maybe, their wallet is corrupted, difficult to understand. They should have backups, though. old wallet.dat can not import the new program no old transactions and old addresses The database library, used to make the wallet dat file, is unchanged (from the old windows wallet binary). There is no reason it should not load, unless it is corrupted. Could you try a wallet backup? Other ideas: - export private keys from old wallet to new one - usa a blockchain snapshot to load old transactions (syncing from scratch will not load transactions older than two weeks, because of how mini-blockchain works); see first post for snapshot links - use your old blockchain, if available and not corrupted - try "repairwallet" (of course do a backup beforehand) |
|
|
|
|
I explained the mini-blockchain to BTC38 again:
"Hello, thank you very much for your information, we will try."
At least they are trying to make it work fully, and not enabling the wallet without having all the transactions accredited (as people would expect).
|
|
|
|
Getting the following errors:
./configure --with-crypto --with-curl |
|
|
|
|
Show Posts
