Updated Frequently Asked Questions
Greetings all,
Wow, I can't believe it has been so long since my last blog post.
I am going to put together a quick updated Frequently Ask Questions post as this keeps coming up time and time again in the nodes tech support on discord.
ERROR: AcceptToMemoryPool: joinsplit requirements not met
Many people have asked about whether this "error" is causing their node to fail. ERROR: AcceptToMemoryPool: joinsplit requirements not met
can be observed in the ~/.zen/debug.log and can be misleading. Each full zend daemon process (node) validates transactions sent to the network mempool, and this "error" means that someone has sent a transaction to the network mempool that does not meet the requirements for inclusion in a block.
ERROR: AcceptToMemoryPool: inputs already spent
This "error" is similar to the above message in the debug.log. This "error" means that someone has sent a transaction to the network mempool but the inputs for the transactions have already been used in another transaction. In other words, someone is trying to double spend the inputs and the daemon has recognised this and throws this message to the log.
How to send manual challenges
It is possible to send a manual challenge to both either your securenode or supernode using the following commands.
Securenodes
curl -s "https://$(cat ~/nodetracker/config/config.json | jq -r '.secure.home').zensystem.io/$(zen-cli listaddresses | jq -r '.[0]')/$(cat ~/nodetracker/config/config.json | jq -r '.secure.nodeid')/send"
Supernodes
curl -s "https://$(cat ~/nodetracker/config/config.json | jq -r '.super.home').zensystem.io/$(zen-cli listaddresses | jq -r '.[0]')/$(cat ~/nodetracker/config/config.json | jq -r '.super.nodeid')/send"
If you have any questions that you cannot seem to find an answer, please don't hesitate to post it in the comments below or hit me up on discord (psyrax, UTC +10 (AEST)#8184)