Common Errors

Assertion and block failures

Symptoms
Any of the following error messages:

Assertion failed!

Expression: !setBlockIndexCandidates.empty()

Expression: hashPrevBlock == view.GetBestBlock()

pivx-qt: main.cpp:2300: bool ConnectBlock(const CBlock&, CValidationState&, CBlockIndex*, CCoinsViewCache&, bool): Assertion `hashPrevBlock == view.GetBestBlock()' failed.

pivxd: main.cpp:2300: bool ConnectBlock(const CBlock&, CValidationState&, CBlockIndex*, CCoinsViewCache&, bool): Assertion `hashPrevBlock == view.GetBestBlock()' failed.

Failed reading from database. PcoinsTip best block is not correct. The block database is in an inconsistent state and may cause issues in the future. To force start use -forcestart

(OSX) A fatal error occurred. PIVX can no longer continue safely and will quit
Exception: St13runtime_error TopupKeyPool() : writing generated key failed
pivx in Runaway exception

Cause
An abnormal exit of the wallet could result in a blockchain inconsistency from that point forward. This can happen due to a PC reboot without first closing the wallet gracefully or if the local copy of the blockchain became corrupted (due to environmental issues etc) and caused the wallet to crash.


Solution
To fix the problem with your local copy of the blockchain, follow these instructions
https://pivx.freshdesk.com/support/solutions/articles/30000004661-wallet-crashes-or-has-crashed-and-now-won-t-launch-fails-every-time-what-do-i-do-

 

My passphrase is not working / Forgotten passphrase

The simple fix for you never to forget your password!

Make sure it is written down and is correct. There is no fix for a typo'd password as something like this would be an obvious security flaw.

If you believe you have been inputting the right password, please try common typos you could commit. This includes hitting the wrong letters next to the one you pressed.

The wallet was unlocked only to anonymize coins

Symptom

When trying to send coins or optimize for staking the following error appears:

pivx21.PNG

Cause

The wallet was unlocked, but only for staking. This is a security measure that allows you to stake safely without opening up your coins to easy theft.

Solution

To continue, you will need to lock your wallet (which stops staking) and then fully unlock it.

For the GUI or qt wallet, you can follow these steps:

1. Select Settings > Lock Wallet
2. Select Settings > Unlock Wallet
3. Provide your passphrase as requested and do not check 'For anonymization and staking only'
4. You should be able to proceed without the error

For the command line wallet, you can follow these steps (more info here):

1. Enter pivx-cli walletlock
2. Enter pivx-cli walletpassphrase <your passphrase> <timeout in seconds, 0 for indefinite> <true/false unlock for staking/anon only>

In other words: pivx-cli CorrectHorseBatteryStaple 0 false

Now you should be able to proceed without the error

PIVX client or daemon crashes on startup or randomly

Symptoms

The PIVX software crashes out with no error message or log file entries on startup or at random intervals


Cause

This is often caused by a memory shortage


Solution

As of v3.0.0, zerocoin does have slightly higher memory requirements. Minimum specs have not been published, but 2GB RAM on linux and 4GB on Windows and Mac seem to run ok. As more data comes in this article can be updated

Command line error: code 32601 message: Method not found

Symptoms

Attempts to start the daemon and check the status with getinfo on command line return:
error: code 32601 message: Method not found


Cause

The PIVX daemon is not running properly


Solution

Use the -daemon switch when starting pivxd:

Example:

pivx22.PNG

Known Error: st13runtime_error

Symptoms:

A similar error appears on startup or in a debug log:

pivx23.PNG

Cause:

A bug in the code for invalidating fraudulent zPIV spends


Resolution:

Update to v3.0.5.1 or newer. If you have problems syncing, follow the instructions in the link

https://github.com/PIVX-Project/PIVX/releases/tag/v3.0.5.1

coinspend: accumulator witness does not verify

Symptoms:

When trying to spend zPIV, the following error appears: coinspend: accumulator witness does not verify

Cause:

A bug in v3.0.5 and v3.0.5.1 affecting some users

Solution:

This issue is resolved beginning with the v3.0.6 release and the binaries are available here

In the Privacy tab, set the security to 100 and rescan/reset the the wallet. If not solved, re-open the wallet and ensure the wallet is completely synced.

Open a ticket if issue isn't fully solved

I've banned all my peers and now I can't sync

Symptoms

The PIVX Core wallet will not sync and you are not getting any peers or find all new peers are added to your banlist.


Cause

This can be caused by running a forked chain or old wallet. Your wallet would not accept any of the blocks the real network provides it and bans everyone.

There is currently a bug going around where an improper shutdown can cause bad data in the zerocoin cache, resulting in rejection of all blocks and banning peers as outlined above. Luckily the devs have identified the issue, created the fix, and pulled it into the master branch on github so it will be included in the next update.


Resolution
Make sure you are running the latest wallet software from: https://pivx.org/wallet/

Make sure you are not forked off onto the incorrect chain: https://pivx.bitcoiner.me/am-i-forked/
If you are forked, please follow the steps on this page: https://pivx.freshdesk.com/support/solutions/articles/30000029354-how-to-resync-your-blockchain-cache

pivx-qt (GUI): Use the debug dialog to enter the command 'clearbanned'
pivx-cli (CLI): Use the command "pivx-cli clearbanned"

See if your wallet starts syncing within a few minutes, otherwise proceed to step 4

Follow the steps in this link and use Method 4: https://pivx.freshdesk.com/support/solutions/articles/30000029354-how-to-resync-your-blockchain-cache

Your wallet will sync from scratch and you should be all set. If not, please contact support