Post your technical support queries here

Technical Support
65

Are you restoring with a private key or a seed phrase (I assume a seed)?

66

Hello. When starting zcash 5.10.0 from a clean shutdown, I always receive this error:

2024-09-30T17:46:57.121296Z  INFO Init: main: Verifying last 288 blocks at level 3
2024-09-30T17:46:59.186983Z  INFO Init: main: No coin database inconsistencies in last 289 blocks (945 transactions)
2024-09-30T17:46:59.190071Z  INFO Init: main:  block index           66427ms
2024-09-30T17:46:59.536651Z  INFO Init: main: nFileVersion = 5100050
2024-09-30T17:46:59.536683Z  INFO Init: main: Keys: 112 plaintext, 0 encrypted, 112 w/ metadata, 112 total
2024-09-30T17:46:59.536694Z  INFO Init: main: ZKeys: 3 plaintext, 0 encrypted, 3 w/metadata, 3 total
2024-09-30T17:46:59.551395Z  INFO Init: main:  wallet                  361ms
2024-09-30T17:46:59.793156Z  INFO Init: main: LoadWallet: inconsistency detected between available Orchard notes & spend information; starting with -rescan.
2024-09-30T17:46:59.793214Z  INFO Init: main: CWallet::InitLoadWallet(): Rescanning last 2664806 blocks (from block 0)...
2024-09-30T17:47:59.000743Z  INFO Init: main: Still rescanning. At block 22057. Progress=0.008763

This is very painful for me, because it takes about 3 days to complete the rescan.

My configuration is as follows:

txindex=1
rpcbind=::1
rpcallowip=::1
exportdir=/root/.zcash/backup
maxconnections=1024
metricsbind=::1
metricsallowip=::1/128
prometheusport=9000

How may I avoid having to complete a rescan every time I start the software?

67

If you added txindex = 1, this is expected behaviour. You just need to keep it running until it is synced.

68

Thank you, @daira. It was fully sync’d when I performed a graceful shutdown, which is why I am confused.

69

From what I understand adding txindex=1 tells the node to “index all transactions that have ever happened” every time you start the node. This makes it faster to search for data in your local saved files. This could be useful for a person running a block explorer for example.

So if you don’t want it to reindex the entire chain when you start the node you should leave that off.

Otherwise just leave the node running 24/7 and you won’t need to wait for the resync when you restart.

70

The txindex flag does not induce a reindex every time by default.
What command are you issuing to actually stop it? zcash-cli stop?

1 Like
71

Thank you, @Shawn. When I see “LoadWallet: inconsistency detected” in the logs, it indicates to me that the wallet is corrupt in some way. You are saying that this is not an error, but rather an artifact of txindex=1. To test this, I commented out the txindex option and ran zcashd -reindex. It completed successfully, and then I safely shut down the node. Upon restarting the node, I saw the following:

024-10-07T01:17:15.516285Z  INFO Init: main: LoadWallet: inconsistency detected between available Orchard notes & spend information; starting with -rescan.
2024-10-07T01:17:15.516349Z  INFO Init: main: CWallet::InitLoadWallet(): Rescanning last 2672029 blocks (from block 0)...
2024-10-07T01:18:15.001886Z  INFO Init: main: Still rescanning. At block 18536. Progress=0.007690
2024-10-07T01:19:15.000761Z  INFO Init: main: Still rescanning. At block 44142. Progress=0.014013
2024-10-07T01:20:15.003225Z  INFO Init: main: Still rescanning. At block 71418. Progress=0.020541

This indicates to me that the txindex option was not at fault, and the issue lies elsewhere.

72

Ctrl+C from a foregrounded zcashd session running in tmux.

These are the logs emitted when I stop the node using ctrl+c:

2024-10-07T01:15:23.885255Z  INFO main: tor: Thread interrupt
2024-10-07T01:15:23.885338Z  INFO main: torcontrol thread exit
2024-10-07T01:15:23.908537Z  INFO main: opencon thread interrupt
2024-10-07T01:15:23.908660Z  INFO main: net thread interrupt
2024-10-07T01:15:23.908798Z  INFO main: metrics-ui thread interrupt
2024-10-07T01:15:23.908835Z  INFO main: msghand thread interrupt
2024-10-07T01:15:23.908849Z  INFO main: scheduler thread interrupt
2024-10-07T01:15:23.909113Z  INFO main: addcon thread interrupt
2024-10-07T01:15:23.966084Z  INFO main: txnotify thread interrupt
2024-10-07T01:15:23.966485Z  INFO Shutdown: main: StopRPC: waiting for async rpc workers to stop
2024-10-07T01:15:23.966717Z  INFO Shutdown: main: StopNode()
2024-10-07T01:15:24.562160Z  INFO Shutdown: main: done

This looks healthy to me.

1 Like
73

I believe you are correct, I misunderstood how txindex works.

1 Like