Service bm-core ne démarre plus

Bonjour,
Problème survenu sur un serveur en fonctionnement depuis plusieurs semaines, le service bm-core s’est stoppé, et ne démarre plus (mire de maintenance sur l’interface web).
Il est bloqué par un timeout avec vert.x

C’est un serveur qui est en pré prod, avec une seule boite active pour le moment, donc loin d’être surchargé

Redémarrage de la VM, sans effet (Ubuntu 24.04)

Si quelqu’un a une idée ?

Ci dessous le statut des services

bmctl status

bm-nginx is running.
bm-core.service fail - check systemctl status bm-core.service and journalctl -xe -u bm-core.service
bm-eas.service is running.
bm-elasticsearch.service is running.
bm-iptables.service is running.
bm-keycloak.service is running.
bm-milter.service is running.
bm-node.service is running.
bm-pimp.service is running.
bm-postgresql.service is running.
bm-tika.service is running.
bm-webserver.service is running.
bm-ysnp.service is running.
postgresql.service is running.

2025-08-15 08:00:01,993 [vertx-blocked-thread-checker] [none:anon:0] i.v.c.i.BlockedThreadChecker WARN - Thread Thread[vert.x-eventloop-thread-2,5,main] has been blocked for 30172 ms, time limit is 2000 ms
io.vertx.core.VertxException: Thread blocked
at org.rocksdb.RocksDB.open(Native Method)
at org.rocksdb.RocksDB.open(RocksDB.java:325)
at net.bluemind.retry.support.rocks.RocksQueue.openDb(RocksQueue.java:152)
at net.bluemind.retry.support.rocks.RocksQueue.(RocksQueue.java:124)
at net.bluemind.retry.support.RetryQueueVerticle.(RetryQueueVerticle.java:74)
at net.bluemind.core.auditlogs.client.es.datastreams.AuditQueueFactory$AuditQueue.(AuditQueueFactory.java:77)
at net.bluemind.core.auditlogs.client.es.datastreams.AuditQueueFactory.(AuditQueueFactory.java:86)
at java.base/jdk.internal.reflect.DirectConstructorHandleAccessor.newInstance(DirectConstructorHandleAccessor.java:62)
at java.base/java.lang.reflect.Constructor.newInstanceWithCaller(Constructor.java:502)
at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:486)
at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:204)
at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:920)
at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:246)
at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:63)
at net.bluemind.eclipse.common.RunnableExtensionLoader.loadExtensions(RunnableExtensionLoader.java:127)
at net.bluemind.lib.vertx.internal.BMModule.start(BMModule.java:38)
at io.vertx.core.impl.DeploymentManager.lambda$doDeploy$5(DeploymentManager.java:210)
at io.vertx.core.impl.ContextInternal.dispatch(ContextInternal.java:279)
at io.vertx.core.impl.ContextInternal.dispatch(ContextInternal.java:261)
at io.vertx.core.impl.ContextInternal.lambda$runOnContext$0(ContextInternal.java:59)
at io.netty.util.concurrent.AbstractEventExecutor.runTask(AbstractEventExecutor.java:173)
at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:166)
at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:469)
at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:408)
at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:994)
at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
at java.base/java.lang.Thread.run(Thread.java:1583)

Finalement, solution trouvée sur un autre post non catégorisé.

Lancer la commande ci dessous, qui fait un reset du fichier d’audit de la base de données Rock

mv /var/cache/bm-core/retry-rocks-audit /var/cache/bm-core/retry-rocks-audit-old && bmctl restart