RE: Fixing Data Integrity Issues in Hive-Engine Nodes

here is a different one:

1_689_118 Jun 25 07:50:03 mina node[3626163]: 2026-06-25 07:50:03 info: [JsonRPCServer] successfully initialized
1_689_119 Jun 25 07:50:03 mina node[3626163]: RPC Node now listening on port 5000
1_689_120 Jun 25 07:50:03 mina node[3626163]: 2026-06-25 07:50:03 error: [Blockchain] MongoError: Transaction with { txnNumber: 1 }>
1_689_121 Jun 25 07:50:03 mina node[3626163]:     at MessageStream.messageHandler (/home/thecrazygm/github/hivesmartcontracts/node_>
1_689_122 Jun 25 07:50:03 mina node[3626163]:     at MessageStream.emit (node:events:519:28)
1_689_123 Jun 25 07:50:03 mina node[3626163]:     at processIncomingData (/home/thecrazygm/github/hivesmartcontracts/node_modules/m>
1_689_124 Jun 25 07:50:03 mina node[3626163]:     at MessageStream._write (/home/thecrazygm/github/hivesmartcontracts/node_modules/>
1_689_125 Jun 25 07:50:03 mina node[3626163]:     at writeOrBuffer (node:internal/streams/writable:572:12)
1_689_126 Jun 25 07:50:03 mina node[3626163]:     at _write (node:internal/streams/writable:501:10)
1_689_127 Jun 25 07:50:03 mina node[3626163]:     at Writable.write (node:internal/streams/writable:510:10)
1_689_128 Jun 25 07:50:03 mina node[3626163]:     at Socket.ondata (node:internal/streams/readable:1009:22)
1_689_129 Jun 25 07:50:03 mina node[3626163]:     at Socket.emit (node:events:519:28)
1_689_130 Jun 25 07:50:03 mina node[3626163]:     at addChunk (node:internal/streams/readable:561:12) {
1_689_131 Jun 25 07:50:03 mina node[3626163]:   ok: 0,
1_689_132 Jun 25 07:50:03 mina node[3626163]:   code: 251,
1_689_133 Jun 25 07:50:03 mina node[3626163]:   codeName: 'NoSuchTransaction',
1_689_134 Jun 25 07:50:03 mina node[3626163]:   '$clusterTime': {
1_689_135 Jun 25 07:50:03 mina node[3626163]:     clusterTime: Timestamp { _bsontype: 'Timestamp', low_: 1, high_: 1782388202 },
1_689_136 Jun 25 07:50:03 mina node[3626163]:     signature: { hash: [Binary], keyId: 0 }
1_689_137 Jun 25 07:50:03 mina node[3626163]:   },
1_689_138 Jun 25 07:50:03 mina node[3626163]:   operationTime: Timestamp { _bsontype: 'Timestamp', low_: 1, high_: 1782388202 },
1_689_139 Jun 25 07:50:03 mina node[3626163]:   [Symbol(errorLabels)]: Set(1) { 'TransientTransactionError' }
1_689_140 Jun 25 07:50:03 mina node[3626163]: }
1_689_141 Jun 25 07:50:03 mina node[3626163]: 2026-06-25 07:50:03 error: [Blockchain] Error: Error while procesing block
1_689_142 Jun 25 07:50:03 mina node[3626163]:     at /home/thecrazygm/github/hivesmartcontracts/plugins/Blockchain.js:154:17
1_689_143 Jun 25 07:50:03 mina node[3626163]:     at process.processTicksAndRejections (node:internal/process/task_queues:103:5)
1_689_144 Jun 25 07:50:03 mina node[3626163]:     at async producePendingTransactions (/home/thecrazygm/github/hivesmartcontracts/p>
1_689_145 Jun 25 07:50:03 mina node[3626163]:     at async produceNewBlockSync (/home/thecrazygm/github/hivesmartcontracts/plugins/>
1_689_146 Jun 25 07:50:03 mina node[3626163]: 2026-06-25 07:50:03 error: [Blockchain] node:internal/process/promises:394
1_689_147 Jun 25 07:50:03 mina node[3626163]:     triggerUncaughtException(err, true /* fromPromise */);
1_689_148 Jun 25 07:50:03 mina node[3626163]:     ^
1_689_149 Jun 25 07:50:03 mina node[3626163]: Error: Error while procesing block
1_689_150 Jun 25 07:50:03 mina node[3626163]:     at /home/thecrazygm/github/hivesmartcontracts/plugins/Blockchain.js:154:17
1_689_151 Jun 25 07:50:03 mina node[3626163]:     at process.processTicksAndRejections (node:internal/process/task_queues:103:5)
1_689_152 Jun 25 07:50:03 mina node[3626163]:     at async producePendingTransactions (/home/thecrazygm/github/hivesmartcontracts/p>
1_689_153 Jun 25 07:50:03 mina node[3626163]:     at async produceNewBlockSync (/home/thecrazygm/github/hivesmartcontracts/plugins/>
1_689_154 Jun 25 07:50:03 mina node[3626163]: Node.js v22.22.3
1_689_155 Jun 25 07:50:04 mina node[3626163]: 2026-06-25 07:50:04 error: [LightNode] (node:3626448) [MONGODB DRIVER] DeprecationWar>
1_689_156 Jun 25 07:50:04 mina node[3626163]: (Use `node --trace-deprecation ...` to show where the warning was created)
1_689_157 Jun 25 07:50:04 mina node[3626163]: 2026-06-25 07:50:04 info: [LightNode] successfully initialized```

Sort:

Trending

[-]

forkyishere 15 days ago (edited)

Need to look at these over debian... sorry

Mongo 7 or 8?

Share these with witnesses if you haven't yet...

0.00 ARCHON

1 vote

thecrazygm 15 days ago (edited)

$ mongod --version                                                                                                                                                                                                                                 took 1h38m34s  [09:55:43]
db version v8.2.11
Build Info: {
    "version": "8.2.11",
    "gitVersion": "ee01d36638a00a07a6aa42ee80a125890f11aeed",
    "openSSLVersion": "OpenSSL 3.6.3 9 Jun 2026",
    "modules": [],
    "allocator": "tcmalloc-google",
    "environment": {
        "distmod": "debian12",
        "distarch": "x86_64",
        "target_arch": "x86_64"
    }
}

Will do some testing this weekend. Since I am moving too many DBs around.

thecrazygm 15 days ago

Yeah, no worries, I'm not in any kind of hurry.

I will say it seems stable with this patch, but also could be a fluke, I'll know more if/when the power goes out. (not willing to willfully test hard power outage)

forkyishere 15 days ago

No, appreciate these... if non-consensus, usually these can be anywhere.

U know the deal...

forkyishere 14 days ago

When this happens again, can you try to find if the node is divergent?

I suspect it is, and that this is mostly a race problem of the disk failing to acknowledge the write, but having been able to write it, and Mongo does not know.

Let's see... funny that contributions for these projects depend on what people have problems with :D

Hence why diversity is important.

thecrazygm 14 days ago

Will do

Necessity is the mother of all invention after all.

3 votes