reth-indexer db panics on `osal_rdt_unlock` while syncing new block headers

[halljson]

This has popped up twice once the indexer catches up and starts syncing new block headers, it runs fine for hours before hitting this:

new block(s) found check from: 17713275... last seen: 17713274... latest block: 17713275
new block(s) found check from: 17713276... last seen: 17713275... latest block: 17713276
reth-database-reader: mdbx:0: panic: Assertion `osal_rdt_unlock() failed: err 1
' failed.
Aborted (core dumped)

real    594m0.578s
user    0m13.813s
sys     0m2.265s

[joshstevens19]

hmm interesting il take a look

[halljson]

noticed today that this happens a lot more often while reth is catching up to the current chain state and reth-indexer is syncing. makes me think this may have something to do with reth writing while reth-indexer is reading?

[joshstevens19]

Need to raise this on reth lib itself il do it tomorrow

[halljson]

get this in place of the initial error once today, first time seeing it:

reth-database-reader: pthread_mutex_lock.c:438: __pthread_mutex_lock_full: Assertion `e != ESRCH || !robust' failed.
Aborted (core dumped)

[gakonst]

Hi guys -- can we get a repro of this as a Github issue? We want to investigate!