Zcashd (core dumped)?

Hi
My wallet will not run ... it was fine yesterday nothing has changed i just started the laptop today and the wallet won't run ,, has there been an update ??

cd zcash/
./scr/zcashd

it gets to where it shows the last block count then shows

Aborted (core dumped)

does anyone know what this means

Can you share the relevant part of your debug.log (found in ~/.zcash/)?

you mean the last bit yeah ?,, ll

Yeah, the part relevant to the time when you see the abort message.

2017-02-15 12:10:13 Opened LevelDB successfully
2017-02-15 12:10:15 LoadBlockIndexDB: last block file = 8
2017-02-15 12:10:15 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=5277, size=107728411, heights=57252...62545, time=2017-02-04...2017-02-13)
2017-02-15 12:10:15 Checking all blk files are present...
2017-02-15 12:10:15 LoadBlockIndexDB: transaction index disabled
2017-02-15 12:10:15 LoadBlockIndexDB: hashBestChain=0000000014045f9fd9fe8122441a3d94f574059741afc654583e501c078b4681 height=62545 date=2017-02-13 21:58:12 progress=0.972818
2017-02-15 12:10:15 Verifying last 288 blocks at level 3
2017-02-15 12:10:47 No coin database inconsistencies in last 122 blocks (469 transactions)
2017-02-15 12:10:47 block index 34261ms
2017-02-15 12:10:55 nFileVersion = 1000350
2017-02-15 12:10:55 Keys: 104 plaintext, 0 encrypted, 104 w/ metadata, 104 total
2017-02-15 12:10:55 ZKeys: 1 plaintext, 0 encrypted, 1 w/metadata, 1 total
2017-02-15 12:10:55 wallet 7990ms
2017-02-15 12:10:55 UpdateTip: new best=000000005469a4ec77eb604160c74adceef24890ce770b1d83d5e541da01d647 height=62544 log2_work=48.519132 tx=307204 date=2017-02-13 21:58:01 progress=0.972808 cache=0.0MiB(2tx)
2017-02-15 12:10:56 UpdateTip: new best=0000000077bf9e3aa22fb44883016461d66a63b7aa0aebe7d8a895ff7acc8542 height=62545 log2_work=48.519156 tx=307206 date=2017-02-13 21:58:12 progress=0.972810 cache=0.0MiB(3tx)
2017-02-15 12:10:56 mapBlockIndex.size() = 62567
2017-02-15 12:10:56 nBestHeight = 62545
2017-02-15 12:10:56 setKeyPool.size() = 101
2017-02-15 12:10:56 mapWallet.size() = 187
2017-02-15 12:10:56 mapAddressBook.size() = 3
2017-02-15 12:10:56 Loaded 282 addresses from peers.dat 2ms
2017-02-15 12:10:56 dnsseed thread start
2017-02-15 12:10:56 net thread start
2017-02-15 12:10:56 addcon thread start
2017-02-15 12:10:56 msghand thread start
2017-02-15 12:10:56 opencon thread start
2017-02-15 12:10:56 AddToWallet 2f7277d01a7b13cd0b7c598f3014af46d648c329ec54f5ee847c44307640b78b
2017-02-15 12:10:56 receive version message: /MagicBean:1.0.6/: version 170002, blocks=63469, us=2.26.253.122:56410, peer=1
2017-02-15 12:10:56 Added time data, samples 2, offset +0 (+0 minutes)
2017-02-15 12:10:57 connect() to [2601:240:c700:2e65:2983:b041:4b59:3b76]:8233 failed: Network is unreachable (101)

Can you run zcashd under gdb and get a stack trace (using the bt command)?

Specifically, run gdb ./src/zcashd and once it crashes, type bt.

Ok thanks I should say at this point that I am very new to lynux,,
So I type in this ?

cd zcash/
run gdb ./scr/zcashd

do i need to install "gdb" ?

Ok I put this in one terminal
~/zcash$ gdb ./src/zcashd

and get this
Reading symbols from ./src/zcashd...done.
(gdb)

then in new terminal i run wallet till it crashes then typ bt in first terminal and get this
(gdb) bt
No stack.
(gdb)

First type: gdb ./src/zcashd
Then when you see:
Reading symbols from ./src/zcashd...done.
(gdb)

Type run in the same terminal window which will start zcashd with tracing.

Then when it crashes, type bt.

So, basically do everything inside the same terminal and let us know what you get after crash.

Note that symbols are only included in a zcashd that has been built from source. So the stack trace will be more useful to us if you've done that, rather than using the Debian/Ubuntu package.

Since starting this node 1 minutes, 4 seconds ago:
- You have validated 1100 transactions!

[Press Ctrl+C to exit] [Set 'showmetrics=0' to hide]
[New Thread 0x7fffbebd0700 (LWP 2852)]
zcashd: main.cpp:2116: bool ConnectBlock(const CBlock&, CValidationState&, CBlockIndex*, CCoinsViewCache&, bool): Assertion `tree.root() == old_tree_root' failed.

Thread 17 "zcash-msghand" received signal SIGABRT, Aborted.
[Switching to Thread 0x7fffd490f700 (LWP 2849)]
0x00007ffff6b5f428 in _GIraise (sig=sig@entry=6)
at ../sysdeps/unix/sysv/linux/raise.c:54
54 ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt

0 0x00007ffff6b5f428 in _GIraise (sig=sig@entry=6)

at ../sysdeps/unix/sysv/linux/raise.c:54

1 0x00007ffff6b6102a in _GIabort () at abort.c:89

2 0x00007ffff6b57bd7 in _assertfail_base (fmt=,

assertion=assertion@entry=0x555555bc76ad "tree.root() == old_tree_root", 
file=file@entry=0x555555bc6d31 "main.cpp", line=line@entry=2116, 
function=function@entry=0x555555bd9a60 <ConnectBlock(CBlock const&, CValidationState&, CBlockIndex*, CCoinsViewCache&, bool)::__PRETTY_FUNCTION__> "bool ConnectBlock(const CBlock&, CValidationState&, CBlockIndex*, CCoinsViewCache&, bool)") at assert.c:92

3 0x00007ffff6b57c82 in _GI___assertfail (

assertion=assertion@entry=0x555555bc76ad "tree.root() == old_tree_root", 
file=file@entry=0x555555bc6d31 "main.cpp", line=line@entry=2116, 
function=function@entry=0x555555bd9a60 <ConnectBlock(CBlock const&, CValidationState&, CBlockIndex*, CCoinsViewCache&, bool)::__PRETTY_FUNCTION__> "bool ConnectBlock(const CBlock&, CValidationState&, CBlockIndex*, CCoinsViewCache&, bool)") at assert.c:101

4 0x000055555560d290 in ConnectBlock (block=..., state=...,

pindex=pindex@entry=0x7fffb8001300, view=..., 
fJustCheck=fJustCheck@entry=false) at main.cpp:2116

5 0x0000555555611b79 in ConnectTip (pblock=0x7fffd490ddb0,

pindexNew=0x7fffb8001300, state=...) at main.cpp:2479

6 ActivateBestChainStep (pblock=,

---Type to continue, or q to quit---

HI, thanks. What version of zcash are you running? Also is this reproducible, does this happen every time you launch zcash?

We filed a github ticket here for better tracking: https://github.com/zcash/zcash/issues/2136

Thanks for your help guy's
the wallet was built around the date 2016-11-24 I have never updated it,,, the wallet was just it that state it would never run so yes it was reproducible ,,,, I've had to rebuild the wallet now to get things moving ,,, I do still have copy of broken zcash and .zcash folders

Hi @semajjames let us know if you have any issues with the rebuild. Closing current ticket above for now.