Jump to content
DarkClaw

Xaya bug?

Recommended Posts

This has happened a couple times now to me even if I reinstall from scratch. Basically I can install xaya and run it once to sync the chain, but after that it will always crash.

 

xxx@xxx:~/xaya$ xaya-qt
qt5ct: using qt5ct plugin
xaya-qt: chain.cpp:111: const CBlockIndex* CBlockIndex::GetAncestor(int) const: Assertion `pindexWalk->pprev' failed.
Aborted (core dumped)
xxx@xxx:~/xaya$ xayad
2019-01-23T02:50:38Z Xaya version v1.1 (release build)
2019-01-23T02:50:38Z InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2019-01-23T02:50:38Z Assuming ancestors of block e685ccaa62025c5c5075cfee80e498589bd4788614dcbe397e12bf2b8e887e47 have valid signatures.
2019-01-23T02:50:38Z Setting nMinimumChainWork=0000000000000000000000000000000000000000000f469d71a33ceda65de424
2019-01-23T02:50:38Z Using the 'shani(1way,2way)' SHA256 implementation
2019-01-23T02:50:38Z Using RdRand as an additional entropy source
2019-01-23T02:50:38Z Default data directory /home/xxx/.xaya
2019-01-23T02:50:38Z Using data directory /home/xxx/.xaya
2019-01-23T02:50:38Z Config file: /home/xxx/.xaya/xaya.conf (not found, skipping)
2019-01-23T02:50:38Z Using at most 125 automatic connections (1024 file descriptors available)
2019-01-23T02:50:38Z Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements
2019-01-23T02:50:39Z Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements
2019-01-23T02:50:39Z Using 16 threads for script verification
2019-01-23T02:50:39Z scheduler thread start
2019-01-23T02:50:39Z HTTP: creating work queue of depth 16
2019-01-23T02:50:39Z No rpcpassword set - using random cookie authentication.
2019-01-23T02:50:39Z Generated RPC authentication cookie /home/xxx/.xaya/.cookie
2019-01-23T02:50:39Z HTTP: starting 4 worker threads
2019-01-23T02:50:39Z Using wallet directory /home/xxx/.xaya/wallets
2019-01-23T02:50:39Z init message: Verifying wallet(s)...
2019-01-23T02:50:39Z Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
2019-01-23T02:50:39Z Using wallet wallet.dat
2019-01-23T02:50:39Z BerkeleyEnvironment::Open: LogDir=/home/xxx/.xaya/wallets/database ErrorFile=/home/xxx/.xaya/wallets/db.log
2019-01-23T02:50:39Z Cache configuration:
2019-01-23T02:50:39Z * Using 2.0MiB for block index database
2019-01-23T02:50:39Z * Using 8.0MiB for chain state database
2019-01-23T02:50:39Z * Using 440.0MiB for in-memory UTXO set (plus up to 286.1MiB of unused mempool space)
2019-01-23T02:50:39Z init message: Loading block index...
2019-01-23T02:50:39Z Opening LevelDB in /home/xxx/.xaya/blocks/index
2019-01-23T02:50:39Z Opened LevelDB successfully
2019-01-23T02:50:39Z Using obfuscation key for /home/xxx/.xaya/blocks/index: 0000000000000000
xayad: chain.cpp:111: const CBlockIndex* CBlockIndex::GetAncestor(int) const: Assertion `pindexWalk->pprev' failed.
Aborted (core dumped)

And my debug.log is attached (had to rename with a .txt extension to upload here). This records me exiting xaya-qt, attempting to start xaya-qt, and then attempting to start xayad.

Also, not sure if it is related but I have been getting intermittent errors when trying to load the forum as well.

 

debug.log.txt

Share this post


Link to post
Share on other sites

On a different windows pc xaya-electron now crashes if I try to restart it (like on mint, it works fine during/after the initial sync). Here is the debug.log:

2019-01-23T03:23:37Z Xaya version v1.1.0.0-52bc22138-dirty (release build)
2019-01-23T03:23:37Z InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2019-01-23T03:23:37Z Assuming ancestors of block e685ccaa62025c5c5075cfee80e498589bd4788614dcbe397e12bf2b8e887e47 have valid signatures.
2019-01-23T03:23:37Z Setting nMinimumChainWork=0000000000000000000000000000000000000000000f469d71a33ceda65de424
2019-01-23T03:23:37Z Using the 'sse4(1way),sse41(4way)' SHA256 implementation
2019-01-23T03:23:38Z Default data directory C:\Users\xxx\AppData\Roaming\Xaya
2019-01-23T03:23:38Z Using data directory C:\Users\xxx\AppData\Roaming\Xaya
2019-01-23T03:23:38Z Config file: C:\Users\xxx\AppData\Roaming\Xaya\xaya.conf
2019-01-23T03:23:38Z Using at most 125 automatic connections (2048 file descriptors available)
2019-01-23T03:23:38Z Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements
2019-01-23T03:23:38Z Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements
2019-01-23T03:23:38Z Using 12 threads for script verification
2019-01-23T03:23:38Z scheduler thread start
2019-01-23T03:23:38Z HTTP: creating work queue of depth 16
2019-01-23T03:23:38Z No rpcpassword set - using random cookie authentication.
2019-01-23T03:23:38Z Generated RPC authentication cookie C:\Users\xxx\AppData\Roaming\Xaya\.cookie
2019-01-23T03:23:38Z HTTP: starting 4 worker threads
2019-01-23T03:23:38Z Using wallet directory C:\Users\xxx\AppData\Roaming\Xaya\wallets
2019-01-23T03:23:38Z init message: Verifying wallet(s)...
2019-01-23T03:23:38Z Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
2019-01-23T03:23:38Z Using wallet wallet.dat
2019-01-23T03:23:38Z BerkeleyEnvironment::Open: LogDir=C:\Users\xxx\AppData\Roaming\Xaya\wallets\vault.dat\database ErrorFile=C:\Users\xxx\AppData\Roaming\Xaya\wallets\vault.dat\db.log
2019-01-23T03:23:38Z Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
2019-01-23T03:23:38Z Using wallet wallet.dat
2019-01-23T03:23:38Z BerkeleyEnvironment::Open: LogDir=C:\Users\xxx\AppData\Roaming\Xaya\wallets\game.dat\database ErrorFile=C:\Users\xxx\AppData\Roaming\Xaya\wallets\game.dat\db.log
2019-01-23T03:23:38Z Cache configuration:
2019-01-23T03:23:38Z * Using 2.0MiB for block index database
2019-01-23T03:23:38Z * Using 56.0MiB for transaction index database
2019-01-23T03:23:38Z * Using 8.0MiB for chain state database
2019-01-23T03:23:38Z * Using 384.0MiB for in-memory UTXO set (plus up to 286.1MiB of unused mempool space)
2019-01-23T03:23:38Z init message: Loading block index...
2019-01-23T03:23:38Z Opening LevelDB in C:\Users\xxx\AppData\Roaming\Xaya\blocks\index
2019-01-23T03:23:38Z Opened LevelDB successfully
2019-01-23T03:23:38Z Using obfuscation key for C:\Users\xxx\AppData\Roaming\Xaya\blocks\index: 0000000000000000
2019-01-23T03:23:39Z ThreadRPCServer incorrect password attempt from 127.0.0.1:57395
2019-01-23T03:23:39Z ThreadRPCServer incorrect password attempt from 127.0.0.1:57397
2019-01-23T03:23:39Z ThreadRPCServer incorrect password attempt from 127.0.0.1:57396

 

Share this post


Link to post
Share on other sites

Interesting - especially the failed assertion in the first debug log, that should not happen (or it means that your data is corrupted somehow).  The code there is the same for Bitcoin, though, so likely this is an upstream issue.  (It could also be caused by some interference with other Namecoin/Xaya changes, but I think that's unlikely.)

Can you reproduce this reliably, or did it just happen once?

Share this post


Link to post
Share on other sites

I reinstalled and resynced a couple of times and always see the same problem now. Also, xaya-electron has started crashing on windows, and this is also not fixed by a reinstall. I saw some people complaining about this same issue earlier today/yesterday in the telegram chat as well. So I suspect somehow someone got a "bad" block included that is preventing xaya from finding its parent.

Share this post


Link to post
Share on other sites
1 hour ago, domob said:

Interesting - especially the failed assertion in the first debug log, that should not happen (or it means that your data is corrupted somehow).  The code there is the same for Bitcoin, though, so likely this is an upstream issue.  (It could also be caused by some interference with other Namecoin/Xaya changes, but I think that's unlikely.)

Can you reproduce this reliably, or did it just happen once?

This looks similar: https://github.com/bitcoin/bitcoin/issues/14750

But if I try running "xayad -reindex" it doesnt work, I get a segfault right away. I need to delete the chain and resync, then it works.

Share this post


Link to post
Share on other sites

same here, today i got mining crash twice, restart not work, so i have the chain resync

Share this post


Link to post
Share on other sites

After restarting the client, I received an error.
After deleting all the files associated with the program, I install everything from the very beginning. After installation from the first start, everything runs smoothly! I close the application, replace the files wallet.dat and run. Returning to the same error.

Quote

2019-01-23T06:53:59Z Xaya version v1.1.0.0-52bc22138-dirty (release build)
2019-01-23T06:53:59Z InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2019-01-23T06:53:59Z Assuming ancestors of block e685ccaa62025c5c5075cfee80e498589bd4788614dcbe397e12bf2b8e887e47 have valid signatures.
2019-01-23T06:53:59Z Setting nMinimumChainWork=0000000000000000000000000000000000000000000f469d71a33ceda65de424
2019-01-23T06:53:59Z Using the 'sse4(1way),sse41(4way),avx2(8way)' SHA256 implementation
2019-01-23T06:53:59Z Using RdRand as an additional entropy source
2019-01-23T06:53:59Z Default data directory C:\Users\Osya\AppData\Roaming\Xaya
2019-01-23T06:53:59Z Using data directory C:\Users\Osya\AppData\Roaming\Xaya
2019-01-23T06:53:59Z Config file: C:\Users\Osya\AppData\Roaming\Xaya\xaya.conf (not found, skipping)
2019-01-23T06:53:59Z Using at most 125 automatic connections (2048 file descriptors available)
2019-01-23T06:53:59Z Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements
2019-01-23T06:53:59Z Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements
2019-01-23T06:53:59Z Using 8 threads for script verification
2019-01-23T06:53:59Z scheduler thread start
2019-01-23T06:53:59Z HTTP: creating work queue of depth 16
2019-01-23T06:53:59Z No rpcpassword set - using random cookie authentication.
2019-01-23T06:53:59Z Generated RPC authentication cookie C:\Users\Osya\AppData\Roaming\Xaya\.cookie
2019-01-23T06:53:59Z HTTP: starting 4 worker threads
2019-01-23T06:53:59Z Using wallet directory C:\Users\Osya\AppData\Roaming\Xaya\wallets
2019-01-23T06:53:59Z init message: Verifying wallet(s)...
2019-01-23T06:53:59Z Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
2019-01-23T06:53:59Z Using wallet wallet.dat
2019-01-23T06:53:59Z BerkeleyEnvironment::Open: LogDir=C:\Users\Osya\AppData\Roaming\Xaya\wallets\vault.dat\database ErrorFile=C:\Users\Osya\AppData\Roaming\Xaya\wallets\vault.dat\db.log
2019-01-23T06:53:59Z Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
2019-01-23T06:53:59Z Using wallet wallet.dat
2019-01-23T06:53:59Z BerkeleyEnvironment::Open: LogDir=C:\Users\Osya\AppData\Roaming\Xaya\wallets\game.dat\database ErrorFile=C:\Users\Osya\AppData\Roaming\Xaya\wallets\game.dat\db.log
2019-01-23T06:53:59Z Cache configuration:
2019-01-23T06:53:59Z * Using 2.0MiB for block index database
2019-01-23T06:53:59Z * Using 8.0MiB for chain state database
2019-01-23T06:53:59Z * Using 440.0MiB for in-memory UTXO set (plus up to 286.1MiB of unused mempool space)
2019-01-23T06:53:59Z init message: Loading block index...
2019-01-23T06:53:59Z Opening LevelDB in C:\Users\Osya\AppData\Roaming\Xaya\blocks\index
2019-01-23T06:54:01Z Opened LevelDB successfully
2019-01-23T06:54:01Z Using obfuscation key for C:\Users\Osya\AppData\Roaming\Xaya\blocks\index: 0000000000000000
 

 

debug.txt

Share this post


Link to post
Share on other sites

a fix has been issued in this branch but we are still testing

https://github.com/xaya/xaya/tree/crashfix

if anyone wants to help test that would be great:

Here is the fix:

https://github.com/xaya/xaya/commit/f064cfd2b141e0ceae224a1bc8152cf1df057795

Quote

Fix disk block index for non-zero nNonce values.


After the post-ICO fork, nNonce values in blocks are allowed to be
non-zero.  This is fine from a consensus point of view (and was tested),
but it caused corruption to the on-disk block index.

The reason for this is that the nNonce value was not included in the
C(Disk)BlockIndex instances, and was assumed to be zero when computing
the block hash from a CDiskBlockIndex that is being loaded.  Thus blocks
would be inserted into mapBlockIndex at a wrong hash, so that the pprev
pointer of the next block (referring to the correct block index) was
pointing to an empty struct instead.

This fix adds back nNonce to C(Disk)BlockIndex, so that all works fine.
Users who synced beyond the first affected block (529761 on mainnet).

This happened when the new pool started mining (not their fault).

When you test and when the fix is applied (if all is well), you will need to sync from scratch.

Share this post


Link to post
Share on other sites

I have synced from scratch and restarted the wallet with this change on windows only atm. Also sent some coins around (game to vault etc).

all seems working.

Share this post


Link to post
Share on other sites
7 hours ago, snailbrain said:

I have synced from scratch and restarted the wallet with this change on windows only atm. Also sent some coins around (game to vault etc).

all seems working.

 

I'm still not working! Maybe I should do something extra? In addition to the new synchronization.

Edited by OSYA

Share this post


Link to post
Share on other sites
1 hour ago, OSYA said:

I'm still not working! Maybe I should do something extra? In addition to the new synchronization.

Can you show what version you are running? All I did is delete all the files in the blocks and blocks/index directories then restart. You should be running "Xaya version v1.1.99.0-f064cfd2b (release build)"

 

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...

Important Information

Your use of this site is governed by our Terms of Use and Privacy Policy. We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.