[WIP]XDC private blockchain Fail to create tx sign for signer error

Hello Fellow Members,

I am getting the below mentioned error while running XDC private masternode.

ERROR[02-20|03:51:49] Fail to add tx sign to local pool. error="nonce too low" number=120 hash=0x9382c04e84120118b80511fe5919005232c6e9853df37d1793d1c22dcaf4d8bb from=xdc757f225273eBA574196EF04f6c22bCC3Ec623aDB nonce=117 ERROR[02-20|03:51:49] Fail to create tx sign for signer error=err

Could someone throw some light on resolving this issue.

Discussion (8)

Daniel Liu • Mar 16 '23

You can try this PR: github.com/XinFinOrg/XDPoSChain/pu...

Raghuram Dharanipathy • Mar 22 '23

Hi Daniel,

Reported “PR 238" fix is applied to the codebase, and testing was done. The node is running after 41000 blocks successfully.  PR 238 includes the reported issues like “Fail to add tx sign to local pool. error="nonce too low””, "list M1 not found”

Though the fix is applied, when we are initiating the blockchain with 1 masternode, 2 signernode, then it is causing “brain split phenomenon” as mentioned in the link github.com/XinFinOrg/XDPoSChain/pu.... So, as a standard the blockchain was configured with 3 or 5 signer node with 1 masternode while starting up the private blockchain.  

The node was stopping at 1799 blocks, then re-configured the node with the Local_DPoS Repo of “gzliudan” and the nodes started up and running.  Deployed a smart contract on the private chain RPC, WSS and tested it out sucessfully.

Raghuram Dharanipathy • Mar 15 '23

@mitali_blocksscan As per the latest update from 'Jay_Bklocksscan' this issue is in WIP

Mitali_BlocksScan • Mar 28 '23

Hey @raghuram,
Devs have raised new PR please test it.
github.com/XinFinOrg/XDPoSChain/pu...
Also there is active devs discussion going on github please join it and it would be appreciable if you will share your inputs.
tell us if you still have any issues Looking forward to your reply…
Thank you

Mitali_BlocksScan • Mar 11 '23

Hello @raghuram
We hope that the above issue is resolved, if the issue still persists then please let us know about it so that the team can resolve it on priority. It will be grateful to get an update within 72 hours or else it will be considered resolved.
Thank You.