You are not logged in.

Announcement

Bonjour, avant de poster, merci de vérifier que vous avez respecté les pré-requis de l'installation et consultez notre documentation : http://docs.blue-mind.net !

Hi, before posting on the forum, please check that you followed installation prerequisites and get a look to our documentation space : http://docs.blue-mind.net

#1 2019-07-26 09:28:21

dani
Member
From: Bordeaux
Registered: 2018-10-13
Posts: 62
Website

Shared Elasticsearch corrompue, comment réinitialiser

Bonjour.

Suite à un problème sur un SAN (dont j'analyse encore la nature), j'ai retrouvé le filsystem hébergeant /var/spool endommagé, j'ai du le réparer avec xfs_repair. Dans l'ensemble, les données bluemind semblent intactes, sauf pour Elasticsearch, qui refuse de démarrer :

[2019-07-26T10:08:20,813][WARN ][o.e.i.e.Engine           ] [eSN6uxf] [mailspool_2][0] failed engine [corrupt file (source: [start])]
org.apache.lucene.index.CorruptIndexException: Problem reading index. (resource=/var/spool/bm-elasticsearch/data/nodes/0/indices/ljtHz4kbRtCx-A95_VuLhQ/0/index/_2dx_Lucene50_0.tim)
        at org.apache.lucene.index.SegmentCoreReaders.<init>(SegmentCoreReaders.java:143) ~[lucene-core-7.4.0.jar:7.4.0 9060ac689c270b02143f375de0348b7f626adebc - jpountz - 2018-06-18 16:51:45]
        at org.apache.lucene.index.SegmentReader.<init>(SegmentReader.java:82) ~[lucene-core-7.4.0.jar:7.4.0 9060ac689c270b02143f375de0348b7f626adebc - jpountz - 2018-06-18 16:51:45]
        at org.apache.lucene.index.ReadersAndUpdates.getReader(ReadersAndUpdates.java:172) ~[lucene-core-7.4.0.jar:7.4.0 9060ac689c270b02143f375de0348b7f626adebc - jpountz - 2018-06-18 16:51:45]
        at org.apache.lucene.index.ReadersAndUpdates.getReadOnlyClone(ReadersAndUpdates.java:211) ~[lucene-core-7.4.0.jar:7.4.0 9060ac689c270b02143f375de0348b7f626adebc - jpountz - 2018-06-18 16:51:45]
        at org.apache.lucene.index.StandardDirectoryReader.open(StandardDirectoryReader.java:105) ~[lucene-core-7.4.0.jar:7.4.0 9060ac689c270b02143f375de0348b7f626adebc - jpountz - 2018-06-18 16:51:45]
        at org.apache.lucene.index.IndexWriter.getReader(IndexWriter.java:523) ~[lucene-core-7.4.0.jar:7.4.0 9060ac689c270b02143f375de0348b7f626adebc - jpountz - 2018-06-18 16:51:45]
        at org.apache.lucene.index.DirectoryReader.open(DirectoryReader.java:103) ~[lucene-core-7.4.0.jar:7.4.0 9060ac689c270b02143f375de0348b7f626adebc - jpountz - 2018-06-18 16:51:45]
        at org.apache.lucene.index.DirectoryReader.open(DirectoryReader.java:79) ~[lucene-core-7.4.0.jar:7.4.0 9060ac689c270b02143f375de0348b7f626adebc - jpountz - 2018-06-18 16:51:45]
        at org.elasticsearch.index.engine.InternalEngine.createSearcherManager(InternalEngine.java:537) ~[elasticsearch-6.4.3.jar:6.4.3]
        at org.elasticsearch.index.engine.InternalEngine.<init>(InternalEngine.java:209) ~[elasticsearch-6.4.3.jar:6.4.3]
        at org.elasticsearch.index.engine.InternalEngine.<init>(InternalEngine.java:160) ~[elasticsearch-6.4.3.jar:6.4.3]
        at org.elasticsearch.index.engine.InternalEngineFactory.newReadWriteEngine(InternalEngineFactory.java:25) ~[elasticsearch-6.4.3.jar:6.4.3]
        at org.elasticsearch.index.shard.IndexShard.newEngine(IndexShard.java:2188) ~[elasticsearch-6.4.3.jar:6.4.3]
        at org.elasticsearch.index.shard.IndexShard.createNewEngine(IndexShard.java:2170) ~[elasticsearch-6.4.3.jar:6.4.3]
        at org.elasticsearch.index.shard.IndexShard.innerOpenEngineAndTranslog(IndexShard.java:1377) ~[elasticsearch-6.4.3.jar:6.4.3]
        at org.elasticsearch.index.shard.IndexShard.openEngineAndRecoverFromTranslog(IndexShard.java:1332) ~[elasticsearch-6.4.3.jar:6.4.3]
        at org.elasticsearch.index.shard.StoreRecovery.internalRecoverFromStore(StoreRecovery.java:421) ~[elasticsearch-6.4.3.jar:6.4.3]
        at org.elasticsearch.index.shard.StoreRecovery.lambda$recoverFromStore$0(StoreRecovery.java:95) ~[elasticsearch-6.4.3.jar:6.4.3]
        at org.elasticsearch.index.shard.StoreRecovery.executeRecovery(StoreRecovery.java:301) ~[elasticsearch-6.4.3.jar:6.4.3]
        at org.elasticsearch.index.shard.StoreRecovery.recoverFromStore(StoreRecovery.java:93) ~[elasticsearch-6.4.3.jar:6.4.3]
        at org.elasticsearch.index.shard.IndexShard.recoverFromStore(IndexShard.java:1603) ~[elasticsearch-6.4.3.jar:6.4.3]
        at org.elasticsearch.index.shard.IndexShard.lambda$startRecovery$4(IndexShard.java:2055) ~[elasticsearch-6.4.3.jar:6.4.3]
        at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:624) [elasticsearch-6.4.3.jar:6.4.3]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_212]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_212]
        at java.lang.Thread.run(Thread.java:748) [?:1.8.0_212]

Et donc des erreurs de ce genre dans bm-core

2019-07-26 08:25:43,634 [BM-Core26] n.b.c.r.b.RestServiceMethodHandler ERROR - Error during restcall RestRequest [path=/internal-api/db_message_bodies/bm-master__fws_fr/9fe1ad87ed2378960d6be6cafba330fbab50e569, method=PUT, User-Agent=null
, params=, remoteAddresses=[10.29.3.14], origin=null]:  class net.bluemind.core.api.fault.ServerFault: java.util.concurrent.ExecutionException: UnavailableShardsException[[mailspool_pending][4] primary shard is not active Timeout: [1m], r
equest: [BulkShardRequest [[mailspool_pending][4]] containing [index {[mailspool_pending][eml][9fe1ad87ed2378960d6be6cafba330fbab50e569], source[{"preview":"rp.fws.fr: L'adresse 10.29.2.12 ne répond plus au ping: OK Date: 2019.07.26 à 09:
44:04 Criticité: Disaster Item: Réponse au ping (icmpping[,2,,,2000]) Valeur : ","date":"2019-07-26T07:52:07Z","cc":[],"headers":{"cc":null,"from":"<zabbix@firewall-services.com>","to":"<daniel@firewall-services.com>"},"subject":"rp.fws.f
r: L'adresse 10.29.2.12 ne répond plus au ping: OK","content":["rp.fws.fr: L'adresse 10.29.2.12 ne répond plus au ping: OK","rp.fws.fr: L'adresse 10.29.2.12 ne répond plus au ping: OK Date: 2019.07.26 à 09:44:04 Criticité: Disaster Item: 
Réponse au ping (icmpping[,2,,,2000]) Valeur : 1","zabbix@firewall-services.com","daniel@firewall-services.com"],"subject_kw":"rp.fws.fr: L'adresse 10.29.2.12 ne répond plus au ping: OK","with":["zabbix@firewall-services.com","daniel@fire
wall-services.com"],"size":2442,"content-type":"text/plain","from":["zabbix@firewall-services.com"],"to":["daniel@firewall-services.com"],"has":[]}]}]]]
        at net.bluemind.backend.mail.replica.service.internal.DbMessageBodiesService.create(DbMessageBodiesService.java:107)
        ... 19 common frames omitted
Caused by:
  class java.util.concurrent.ExecutionException: UnavailableShardsException[[mailspool_pending][4] primary shard is not active Timeout: [1m], request: [BulkShardRequest [[mailspool_pending][4]] containing [index {[mailspool_pending][eml][9fe1ad87ed2378960d6be6cafba330fbab50e569], source[{"preview":"rp.fws.fr: L'adresse 10.29.2.12 ne répond plus au ping: OK Date: 2019.07.26 à 09:44:04 Criticité: Disaster Item: Réponse au ping (icmpping[,2,,,2000]) Valeur : ","date":"2019-07-26T07:52:07Z","cc":[],"headers":{"cc":null,"from":"<zabbix@firewall-services.com>","to":"<daniel@firewall-services.com>"},"subject":"rp.fws.fr: L'adresse 10.29.2.12 ne répond plus au ping: OK","content":["rp.fws.fr: L'adresse 10.29.2.12 ne répond plus au ping: OK","rp.fws.fr: L'adresse 10.29.2.12 ne répond plus au ping: OK Date: 2019.07.26 à 09:44:04 Criticité: Disaster Item: Réponse au ping (icmpping[,2,,,2000]) Valeur : 1","zabbix@firewall-services.com","daniel@firewall-services.com"],"subject_kw":"rp.fws.fr: L'adresse 10.29.2.12 ne répond plus au ping: OK","with":["zabbix@firewall-services.com","daniel@firewall-services.com"],"size":2442,"content-type":"text/plain","from":["zabbix@firewall-services.com"],"to":["daniel@firewall-services.com"],"has":[]}]}]]]
        at java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:357)
        at java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1915)
        at net.bluemind.backend.mail.replica.service.internal.DbMessageBodiesService.create(DbMessageBodiesService.java:104)
        ... 19 common frames omitted

Comment je peux faire pour remettre tout ça en ordre ? Comment réinitialiser l'ensemble des indexes elasticsearch et les reconstruire ?


Firewall Services: la sécurité des réseaux

Offline

#2 2019-07-26 14:39:27

Toony
BlueMind Team
From: Toulouse
Registered: 2012-03-29
Posts: 1,823
Website

Re: Shared Elasticsearch corrompue, comment réinitialiser

Quelle est votre version de BlueMind ?

Offline

#3 2019-07-26 14:40:51

dani
Member
From: Bordeaux
Registered: 2018-10-13
Posts: 62
Website

Re: Shared Elasticsearch corrompue, comment réinitialiser

4.0.7 (avec souscription)


Firewall Services: la sécurité des réseaux

Offline

#4 2019-07-29 08:43:20

dani
Member
From: Bordeaux
Registered: 2018-10-13
Posts: 62
Website

Re: Shared Elasticsearch corrompue, comment réinitialiser

Personne ?


Firewall Services: la sécurité des réseaux

Offline

#5 2019-07-29 11:51:14

Toony
BlueMind Team
From: Toulouse
Registered: 2012-03-29
Posts: 1,823
Website

Re: Shared Elasticsearch corrompue, comment réinitialiser

Est-ce que le service ElasticSearch est démarré ?

Offline

#6 2019-07-29 11:53:08

dani
Member
From: Bordeaux
Registered: 2018-10-13
Posts: 62
Website

Re: Shared Elasticsearch corrompue, comment réinitialiser

Nop, comme indiqué dans le premier message, le service refuse de démarrer à cause des donnes corrompues


Firewall Services: la sécurité des réseaux

Offline

#7 2019-07-29 11:53:33

PascalS
Member
From: Bain de Bretagne
Registered: 2012-11-18
Posts: 200
Website

Re: Shared Elasticsearch corrompue, comment réinitialiser

Salut,

tu as regardé dans la doc, à cette URL : https://forge.bluemind.net/confluence/d … indexation ?

Pascal

Offline

#8 2019-07-29 15:48:50

dani
Member
From: Bordeaux
Registered: 2018-10-13
Posts: 62
Website

Re: Shared Elasticsearch corrompue, comment réinitialiser

OK, j'avais en effet raté cette page. Ça semble OK (en cours de réindexation). Je viendrai crier à l'aide si j'ai d'autre pb. Merci :-)


Firewall Services: la sécurité des réseaux

Offline

Board footer

Powered by FluxBB