v0.22.6 Node Crashed Post "CreateCoinStake"

[americanpatriotdave]

Describe the bug
Node abruptly stopped after winning a POS stake reward.

To Reproduce
Unknown.

Expected behavior
Not crash.

Screenshots
debug.log excerpt: (trx ID redacted)

2024-08-23T03:57:32Z [default wallet] SelectCoinsForStaking() : available UTXO count=1268 BestHeader: 2904455 d27bc297f3c6336e099b95cdca8055a4adbe0e247faa80536d3151d4d09401fd
2024-08-23T03:57:37Z [default wallet] SelectCoinsForStaking() : available UTXO count=1268 BestHeader: 2904455 d27bc297f3c6336e099b95cdca8055a4adbe0e247faa80536d3151d4d09401fd
2024-08-23T03:57:37Z [default wallet] CreateCoinStake : kernel found at txNew.nTime=2024-08-23T03:57:36Z - 0 sec
2024-08-23T03:57:37Z [default wallet] CreateCoinStake : parsed kernel type=pubkey
2024-08-23T03:57:37Z [default wallet] CreateCoinStake : added kernel type=pubkey, chained tx value=15865500016, tx time=2024-06-16T18:29:52Z
2024-08-23T03:57:37Z Created coin stake
2024-08-23T03:57:37Z === Staking : new PoS block found hash: 2904456 - fdbd92c7f2441993a4c584ebe9d78e4aaa2acb81f37c31fd12ad0349fc20b421
2024-08-23T03:57:37Z [default wallet] SelectCoinsForStaking() : available UTXO count=1268 BestHeader: 2904455 d27bc297f3c6336e099b95cdca8055a4adbe0e247faa80536d3151d4d09401fd
2024-08-23T03:57:38Z +++ Block connected to chain: 2904456 BH: fdbd92c7f2441993a4c584ebe9d78e4aaa2acb81f37c31fd12ad0349fc20b421
2024-08-23T03:57:38Z [default wallet] Transaction e43bf703518305a6881428b86abf761b8a5055a1f2dd0230d36e734d9c9a5b27 (in block fdbd92c7f2441993a4c584ebe9d78e4aaa2acb81f37c31fd12ad0349fc20b421) conflicts with wallet transaction 9505f0adfe72b4bd75772a5149ed6a561bbd443e8eeadad101b195ee68518231 (both spend 367286.....4824c65703e3:2)
2024-08-23T03:58:27Z ping timeout: 1200.002392s

Server (please complete the following information):

• OS: Ubuntu 22.04 headless, fully patched.

Additional context
Recently updated from v0.22.5.
This issue appears suspiciously like the same issue as before.
Wondering if this is a corrupt wallet.
I noticed that the BH of 2904456 has a block-explorer hash of:
66d7c2be8eb21fa467e184c252cc336441af3da6170d98537962daef69118b76
and the reported has in the debugl.log has a reported hash of:
fdbd92c7f2441993a4c584ebe9d78e4aaa2acb81f37c31fd12ad0349fc20b421

[andyoknen]

Perhaps the problem is really in the damaged wallet. I have no idea yet where exactly the failure might occur.

[andyoknen]

@americanpatriotdave Is the problem relevant after upgrading to 0.22.7 or 0.22.8?

[americanpatriotdave]

No trouble since the upgrades. I think it's a non-issue at this point. thanks for checking in on this.

[the-real-vortex-v]

Remember to fix a wallet you should dump your private keys, move the wallet file (for a backup just in case) and then import the wallet keys back again.
dumpwallet "walletdump.txt"
then load it back
importwallet "walletdump.txt"

I haven't done it this way before but as far as I understand that won't save broken transactions in the recreated wallet as it's just pulling wallet crypto keys etc.

Is this wrong/correct? It might be worth having a small script that'll do this for people in certain errors are found? like maybe if a wallet integrity check in done then an automatic wallet dump could happen with a flag when checking? I.e Check and dump on error. Automating some of this stuff can be a pain otherwise.

[andyoknen]

@the-real-vortex-v I am more and more inclined to the idea of using HDSEED as a wallet backup - I do not understand why bitcoin does not use this by default..

The gethdseed and sethdseed RPC methods are available in version 0.22.8