Bm-core failed, impossible à démarrer

fbru · June 1, 2021, 11:59am

Bonjour,
Depuis quelques jours, je narrive plus à me connecter à la page d’accueil de blueMind sur le web.
J’ai essayé de redemarrer le service bm-core mais il met un failed.
dans les logs du bm-webserver: ERROR - error retrieving core state : net.bluemind.network.topology.TopologyException: topology not available
dans le log du bm-core : 2021-05-28 09:16:11,447 [vertx-blocked-thread-checker] i.v.c.i.BlockedThreadChecker WARN - Thread Thread[vert.x-worker-thread-14,5,main]=Thread[vert.x-worker-thread-14,5,main] has been blocked for 91061 ms, time limit is 60000 ms
io.vertx.core.VertxException: Thread blocked
at sun.misc.Unsafe.park(Native Method)
at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedNanos(AbstractQueuedSynchronizer.java:1037)
at java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireSharedNanos(AbstractQueuedSynchronizer.java:1328)
at java.util.concurrent.Semaphore.tryAcquire(Semaphore.java:409)
at net.bluemind.imap.impl.ClientSupport.lock(ClientSupport.java:131)
at net.bluemind.imap.impl.ClientSupport.lock(ClientSupport.java:142)
at net.bluemind.imap.impl.ClientSupport.run(ClientSupport.java:224)
at net.bluemind.imap.impl.ClientSupport.uidStore(ClientSupport.java:396)
at net.bluemind.imap.StoreClient.uidStore(StoreClient.java:355)
at net.bluemind.backend.cyrus.replication.link.probe.LatencyMonitorWorker.doProbe(LatencyMonitorWorker.java:145)
at net.bluemind.backend.cyrus.replication.link.probe.LatencyMonitorWorker.lambda$0(LatencyMonitorWorker.java:67)
at net.bluemind.backend.cyrus.replication.link.probe.LatencyMonitorWorker$$Lambda$293/1067198929.handle(Unknown Source)
at io.vertx.core.eventbus.impl.HandlerRegistration.deliver(HandlerRegistration.java:271)
at io.vertx.core.eventbus.impl.HandlerRegistration.handle(HandlerRegistration.java:249)
at io.vertx.core.eventbus.impl.EventBusImpl$InboundDeliveryContext^C
root@srvmail:/var/log/bm-webserver# ^C
root@srvmail:/var/log/bm-webserver# tail -f /var/log/bm/core.log
2021-06-01 11:21:22,456 [hz.ShutdownThread] c.h.n.t.TcpIpConnection INFO - [192.168.1.101]:5702 [bluemind-72D26E8A-5BB1-48A4-BC71-EEE92E0CE4EE] [3.12.5] Connection[id=4, /192.168.1.101:5702->/192.168.1.101:44917, qualifier=null, endpoint=[192.168.1.101]:44917, alive=false, type=JAVA_CLIENT] closed. Reason: EndpointManager is stopping
2021-06-01 11:21:22,457 [Thread-7] n.b.a.l.ApplicationLauncher INFO - BlueMind Core stopped.
2021-06-01 11:21:22,463 [hz.ShutdownThread] c.h.n.t.TcpIpConnection INFO - [192.168.1.101]:5702 [bluemind-72D26E8A-5BB1-48A4-BC71-EEE92E0CE4EE] [3.12.5] Connection[id=5, /192.168.1.101:5702->/192.168.1.101:32811, qualifier=null, endpoint=[192.168.1.101]:32811, alive=false, type=JAVA_CLIENT] closed. Reason: EndpointManager is stopping
2021-06-01 11:21:22,464 [hz.ShutdownThread] c.h.n.t.TcpIpConnection INFO - [192.168.1.101]:5702 [bluemind-72D26E8A-5BB1-48A4-BC71-EEE92E0CE4EE] [3.12.5] Connection[id=6, /192.168.1.101:5702->/192.168.1.101:43721, qualifier=null, endpoint=[192.168.1.101]:43721, alive=false, type=JAVA_CLIENT] closed. Reason: EndpointManager is stopping
2021-06-01 11:21:22,464 [hz.ShutdownThread] c.h.n.t.TcpIpConnection INFO - [192.168.1.101]:5702 [bluemind-72D26E8A-5BB1-48A4-BC71-EEE92E0CE4EE] [3.12.5] Connection[id=7, /192.168.1.101:5702->/192.168.1.101:38745, qualifier=null, endpoint=[192.168.1.101]:38745, alive=false, type=JAVA_CLIENT] closed. Reason: EndpointManager is stopping
2021-06-01 11:21:22,465 [hz.ShutdownThread] c.h.i.Node INFO - [192.168.1.101]:5702 [bluemind-72D26E8A-5BB1-48A4-BC71-EEE92E0CE4EE] [3.12.5] Shutting down node engine…
2021-06-01 11:21:22,490 [hz.ShutdownThread] c.h.i.NodeExtension INFO - [192.168.1.101]:5702 [bluemind-72D26E8A-5BB1-48A4-BC71-EEE92E0CE4EE] [3.12.5] Destroying node NodeExtension.
2021-06-01 11:21:22,490 [hz.ShutdownThread] c.h.i.Node INFO - [192.168.1.101]:5702 [bluemind-72D26E8A-5BB1-48A4-BC71-EEE92E0CE4EE] [3.12.5] Hazelcast Shutdown is completed in 63 ms.
2021-06-01 11:21:23,305 [hz.ShutdownThread] c.h.c.LifecycleService INFO - [192.168.1.101]:5702 [bluemind-72D26E8A-5BB1-48A4-BC71-EEE92E0CE4EE] [3.12.5] [192.168.1.101]:5702 is SHUTDOWN
2021-06-01 11:21:23,305 [hz.ShutdownThread] n.b.h.c.i.ClusterMember INFO - HZ cluster switched to state SHUTDOWN, running: false.
Merci pour votre aide.
FB

PascalS · June 1, 2021, 12:27pm

Salut,

je suppose que tu es en BM4.x
Tu peux lancer la commande “bmctl all_status”, histoire de voir ce qui tourne ou pas.

Le résultat chez moi :

root@uruviel:~# bmctl all_status
bm-core.service is running.
bm-cyrus-imapd.service is running.
bm-eas.service is running.
bm-elasticsearch.service is running.
bm-hps.service is running.
bm-iptables.service is running.
bm-lmtpd.service is running.
bm-milter.service is running.
bm-node.service is running.
bm-pimp.service is running.
bm-postgresql.service is running.
bm-sds-proxy.service is running.
bm-tika.service is running.
bm-webserver.service is running.
bm-xmpp.service is running.
bm-ysnp.service is running.
networking.service is running.
network-online.target is running.
postgresql.service is running.

fbru · June 1, 2021, 12:44pm

bm-core.service fail - check systemctl status bm-core.service and journalctl -xe -u bm-core.service
bm-cyrus-imapd.service is running.
bm-eas.service is running.
bm-hps.service is running.
bm-iptables.service is running.
bm-lmtpd.service is running.
bm-locator.service is running.
bm-milter.service is running.
bm-node.service is running.
bm-pimp.service is running.
bm-postgresql.service is running.
bm-sds-proxy.service is running.
bm-tika.service is running.
bm-webserver.service is running.
bm-xmpp.service is running.
bm-ysnp.service is running.
postgresql.service is running.

PascalS · June 1, 2021, 1:01pm

T’as installé TICK, l’outil de monitoring/métrologie sur ta machine?
En ce qui me concerne, je l’ai dégagée. Elle me mangeait trop de ressource et impactait le bon fonctionnement des services (dont le démarrage)

tommy · June 1, 2021, 1:30pm

Hello,
C’est quelle version 4 que tu utilises ?
Tu as des erreurs dans /var/log/mail.info ou /var/log/mail.err ?

fbru · June 1, 2021, 6:20pm

Jun 1 20:10:01 srvmail cyrus/sync_client[27893]: Can not connect to server ‘192.168.1.101’
Jun 1 20:10:02 srvmail cyrus/sync_client[27900]: connect(192.168.1.101) failed: Connection refused
Jun 1 20:10:02 srvmail cyrus/sync_client[27902]: connect(192.168.1.101) failed: Connection refused
Jun 1 20:10:02 srvmail cyrus/sync_client[27901]: connect(192.168.1.101) failed: Connection refused
Jun 1 20:10:02 srvmail cyrus/sync_client[27901]: Can not connect to server ‘192.168.1.101’
Jun 1 20:10:02 srvmail cyrus/sync_client[27900]: Can not connect to server ‘192.168.1.101’
Jun 1 20:10:02 srvmail cyrus/sync_client[27902]: Can not connect to server ‘192.168.1.101’
Jun 1 20:10:08 srvmail cyrus/sync_client[9416]: connect(192.168.1.101) failed: Connection refused
Jun 1 20:10:08 srvmail cyrus/sync_client[9413]: connect(192.168.1.101) failed: Connection refused
Jun 1 20:10:08 srvmail cyrus/sync_client[9414]: connect(192.168.1.101) failed: Connection refused
Jun 1 20:10:08 srvmail cyrus/sync_client[9415]: connect(192.168.1.101) failed: Connection refused
Jun 1 20:10:23 srvmail cyrus/sync_client[9413]: connect(192.168.1.101) failed: Connection refused
Jun 1 20:10:23 srvmail cyrus/sync_client[9416]: connect(192.168.1.101) failed: Connection refused
Jun 1 20:10:23 srvmail cyrus/sync_client[9414]: connect(192.168.1.101) failed: Connection refused
Jun 1 20:10:23 srvmail cyrus/sync_client[9415]: connect(192.168.1.101) failed: Connection refused
Jun 1 20:10:53 srvmail cyrus/sync_client[9413]: connect(192.168.1.101) failed: Connection refused
Jun 1 20:10:53 srvmail cyrus/sync_client[9416]: connect(192.168.1.101) failed: Connection refused
Jun 1 20:10:53 srvmail cyrus/sync_client[9414]: connect(192.168.1.101) failed: Connection refused
Jun 1 20:10:53 srvmail cyrus/sync_client[9415]: connect(192.168.1.101) failed: Connection refused
Jun 1 20:11:53 srvmail cyrus/sync_client[9413]: connect(192.168.1.101) failed: Connection refused
Jun 1 20:11:53 srvmail cyrus/sync_client[9416]: connect(192.168.1.101) failed: Connection refused
Jun 1 20:11:53 srvmail cyrus/sync_client[9414]: connect(192.168.1.101) failed: Connection refused
Jun 1 20:11:53 srvmail cyrus/sync_client[9415]: connect(192.168.1.101) failed: Connection refused
Jun 1 20:13:53 srvmail cyrus/sync_client[9413]: connect(192.168.1.101) failed: Connection refused
Jun 1 20:13:53 srvmail cyrus/sync_client[9416]: connect(192.168.1.101) failed: Connection refused
Jun 1 20:13:53 srvmail cyrus/sync_client[9414]: connect(192.168.1.101) failed: Connection refused
Jun 1 20:13:53 srvmail cyrus/sync_client[9415]: connect(192.168.1.101) failed: Connection refused
Jun 1 20:17:53 srvmail cyrus/sync_client[9413]: connect(192.168.1.101) failed: Connection refused
Jun 1 20:17:53 srvmail cyrus/sync_client[9416]: connect(192.168.1.101) failed: Connection refused
Jun 1 20:17:53 srvmail cyrus/sync_client[9414]: connect(192.168.1.101) failed: Connection refused
Jun 1 20:17:53 srvmail cyrus/sync_client[9415]: connect(192.168.1.101) failed: Connection refused
root@srvmail:/var/log/bm-webserver#

fbru · June 1, 2021, 6:21pm

Non, je ne pense pas

Toony · June 2, 2021, 7:58am

Quelles sont les caractéristiques de la machine (CPU, RAM…) ?

fbru · June 4, 2021, 6:53am

Bonjur, voici la VM:

Merci d’avance,

fbru · June 4, 2021, 7:10am

j’ai augmenté les CPU + la memoire à 8 G, c’est toujours le mêmepb.

fbru · June 4, 2021, 7:11am

Ah non, je viens de refaire un essai mon service Core est démarré

fbru · June 4, 2021, 7:23am

Merci à tous, pb resolu

Toony · June 4, 2021, 8:09am

Cette page décrit les préconisations matérielles pour un serveur de production .

Suivant les composants utilisés et le but du serveur (tests/petit serveur personnel…), il peut-être possible de diminuer un peu, cependant une bonne compréhension du logiciel et des conséquences potentielles sont nécessaires.

fbru · June 4, 2021, 8:35am

Pourquoi, je suis obligé de faire un bmctl restart en manuel, car mes services ne redemarrent pas apres un redémarrage de la VM ?
Merci

Toony · June 4, 2021, 8:44am

Sûrement des temps de démarrage trop long liés à une manque de mémoire vive et/ou charge CPU trop importante (possiblement, la charge de l’hyperviseur aussi - le nombre de vCPU alloués au total à l’ensemble des VMs peut avoir un impact sur les performances globales de l’hyperviseur).

Le démarrage d’un service BlueMind est limité à 90s par défaut. Il est possible de surcharger ces paramètres via des override systemd.
Cependant, nous vous préconisons plutôt d’adapter les ressources de la VM.

invisart · June 8, 2021, 10:00am

Comment est-ce que l’on supprime TICK?

PascalS · June 9, 2021, 4:57am

Salut,
voici la commande (au yum prêt )

(yum|apt) remove bm-telegraf bm-influxdb bm-chronograf bm-kapacitor

ou

(yum|apt) remove bm-tick-full