masternode: Lelantus verification failed due sigma verification

[NorseGaud]

Node running 0.14.12.1-gc7e3ef0e6 got a PoSe Penalty and the logs are showing:

2023-04-09 09:33:07 HDmint: UpdateSpendStateFromBlock. [height: 656661]
2023-04-09 09:33:23 AcceptToMemoryPool(), transaction: b24871a7435fa934533f71800aa397917146bbe12679fa41383d3db64c021481
2023-04-09 09:33:23 AcceptToMemoryPoolWorker(), tx.IsSpend()=true, fTestNet=false
2023-04-09 09:33:23 CheckTransaction nHeight=2147483647, isVerifyDB=false, isCheckWallet=true, txHash=b24871a7435fa934533f71800aa397917146bbe12679fa41383d3db64c021481
2023-04-09 09:33:24 CheckLelantusJoinSplitTransaction: tx version=47, tx metadata hash=825c62cc814195e3380233fb105867372adbbfeef1d74f4ac15c348f03d83143
2023-04-09 09:33:24 CheckLelantusJMintTransaction txHash = 0831f85a01c7c17b5e2c5098f042a61c6406f89d1e26e3f9b024872f7a339d29
2023-04-09 09:33:30 Lelantus verification failed due sigma verification failed.CheckLelantusJoinSplitTransaction: verification failed at block 2147483647
2023-04-09 09:33:30 CheckTransaction() failed!receive version message: /Satoshi:0.14.12/: version 90031, blocks=656670, us=54.94.107.130:8168, peer=9644
2023-04-09 09:33:31 receive version message: /Satoshi:0.14.11.1/: version 90031, blocks=656670, us=54.94.107.130:8168, peer=9645

2023-04-09 09:33:33 ConnectBlock nHeight=656662, hash=3c58ada693b125187f128634bbd3518c37761b2b42ec1cf66cc342be0722e639
2023-04-09 09:33:33 CheckBlock() nHeight=656662, blockHash= 3c58ada693b125187f128634bbd3518c37761b2b42ec1cf66cc342be0722e639, isVerifyDB = false
2023-04-09 09:33:35 CDeterministicMNList::PoSePunish -- punished MN 06bbba88bfdf8e068ee3ef6ff1dbf613800ea223c04f0d8d34cd89f98e606068, penalty 2524->4696 (max=4696)

. . . 6 other nodes Punished in here . . .

2023-04-09 09:33:35 CDeterministicMNList::PoSePunish -- punished MN f42255f53a978f6dc39e417dcad3c22f796ac347daeaf60c247867086f872043, penalty 0->3099 (max=4696)

My node: f42255f53a978f6dc39e417dcad3c22f796ac347daeaf60c247867086f872043

Here is what was going on for resource usage and the quorum command:

Sun Apr  9 09:28:03 UTC 2023
[
  {
    "height": 656064,
    "type": "llmq_400_85",
    "quorumHash": "e88a5ca3d826346f4b709fff95a88506089f6714505a92c6188645bc3fb07323",
    "minedBlock": "4908550a252488791d7c2f6d6f5988d03a7f035a2e01d55bc16131396b748a3e",
    "quorumPublicKey": "0a8a62bcb38a59ce194280447be21000fc4c01179a0bd17617bc2d0f14ff7c60f0bb1c21ac0748d9f17b11e51718cf92",
    "isValidMember": true,
    "memberIndex": 195
  }
]

==========
Sun Apr  9 09:28:11 UTC 2023
 09:28:12 up 176 days, 19:55,  0 users,  load average: 1.88, 1.42, 1.11
              total        used        free      shared  buff/cache   available
Mem:           922M        854M         38M         72K         28M         20M
Swap:          2.0G        1.0G        1.0G
USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
firo-user 22257  2.5 86.2 3405320 814764 ?      S<Lsl Mar24 572:42 /usr/local/bin/firod
root         1  0.0  0.1   8308  1196 ?        Ss    2022   9:01 /usr/lib/systemd/systemd --system --deserialize 26
root         2  0.0  0.0      0     0 ?        S     2022   0:03 [kthreadd]

It looks as if maybe memory was low when the Lelantus verification was being attempted and it ran out? Do we know if this verification process requires a certain amount of memory to function properly?

[reubenyap]

Related to #1235 so closing this as a duplicate.

[NorseGaud]

Hi @reubenyap , can you please reopen this? It is not related. I need help from someone to determine what causes Lelantus verification failed due sigma verification failed

[justanwar]

According to @levonpetrosyan93 this can happen when the memory is full.

[NorseGaud]

Thanks, where do I submit a dev request/ticket to indicate memory exhaustion in the logs?

Also, I had plenty of swap when memory runs out on my MNs, it was just slow IO. So what I believe is happening is instead the swap performance caused it to think it was out of memory due to delays in memory negotiation/etc.