Agenda - Disparition d'évenement

BlueMind - FR Discussions
1

Bonjour,

J’ai quelque fois des disparitions d’événements sur l’agenda.

Une petite idée ?

Merci

Ci joint les logs :

2016-02-21 17:33:19,274 [vert.x-worker-thread-10] net.bluemind.core.calendar.CalendarHome INFO - *********** MARK_CAL_UPDATED (event 510)
2016-02-21 17:33:19,277 [vert.x-worker-thread-10] net.bluemind.core.calendar.CalendarHome ERROR - ut was rolled-back
org.elasticsearch.client.transport.NoNodeAvailableException: None of the configured nodes are available: ]
	at org.elasticsearch.client.transport.TransportClientNodesService.ensureNodesAreAvailable(TransportClientNodesService.java:278) ~[elasticsearch-1.4.1.jar:na]
	at org.elasticsearch.client.transport.TransportClientNodesService.execute(TransportClientNodesService.java:197) ~[elasticsearch-1.4.1.jar:na]
	at org.elasticsearch.client.transport.support.InternalTransportClient.execute(InternalTransportClient.java:106) ~[na:na]
	at org.elasticsearch.client.support.AbstractClient.index(AbstractClient.java:98) ~[na:na]
	at org.elasticsearch.client.transport.TransportClient.index(TransportClient.java:334) ~[elasticsearch-1.4.1.jar:na]
	at org.elasticsearch.action.index.IndexRequestBuilder.doExecute(IndexRequestBuilder.java:313) ~[elasticsearch-1.4.1.jar:na]
	at org.elasticsearch.action.ActionRequestBuilder.execute(ActionRequestBuilder.java:91) ~[elasticsearch-1.4.1.jar:na]
	at org.elasticsearch.action.ActionRequestBuilder.execute(ActionRequestBuilder.java:65) ~[elasticsearch-1.4.1.jar:na]
	at net.bluemind.lib.elasticsearch.ESearchActivator.asyncIndexImpl(ESearchActivator.java:195) ~[net.bluemind.lib.elasticsearch_1.0.0.b13769.jar:na]
	at net.bluemind.lib.elasticsearch.ESearchActivator.index(ESearchActivator.java:108) ~[net.bluemind.lib.elasticsearch_1.0.0.b13769.jar:na]
	at net.bluemind.core.calendar.CalendarHome.index(CalendarHome.java:6354) ~[net.bluemind.core_1.0.0.b13769.jar:na]
	at net.bluemind.core.calendar.CalendarHome.createEvent(CalendarHome.java:337) ~[net.bluemind.core_1.0.0.b13769.jar:na]
	at net.bluemind.core.calendar.CalendarHome.createEvent(CalendarHome.java:204) ~[net.bluemind.core_1.0.0.b13769.jar:na]
	at net.bluemind.core.calendar.CalendarBindingImpl.create(CalendarBindingImpl.java:502) [net.bluemind.core_1.0.0.b13769.jar:na]
	at net.bluemind.core.calendar.CalendarBindingImpl.doSync(CalendarBindingImpl.java:1654) [net.bluemind.core_1.0.0.b13769.jar:na]
	at net.bluemind.core.server.EventHandler$48.execute(EventHandler.java:1285) [net.bluemind.core_1.0.0.b13769.jar:na]
	at net.bluemind.core.server.SecureMethod.execute(SecureMethod.java:54) [net.bluemind.core_1.0.0.b13769.jar:na]
	at net.bluemind.core.server.vertx.CoreRpcReceiver.handle(CoreRpcReceiver.java:81) [net.bluemind.core_1.0.0.b13769.jar:na]
	at net.bluemind.core.server.vertx.CoreRpcReceiver.handle(CoreRpcReceiver.java:1) [net.bluemind.core_1.0.0.b13769.jar:na]
	at org.vertx.java.core.eventbus.impl.DefaultEventBus$11.run(DefaultEventBus.java:963) [vertx-core-2.1.6.jar:na]
	at org.vertx.java.core.impl.DefaultContext$3.run(DefaultContext.java:175) [vertx-core-2.1.6.jar:na]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [na:1.7.0_60]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [na:1.7.0_60]
	at java.lang.Thread.run(Thread.java:745) [na:1.7.0_60]
2016-02-21 17:33:19,277 [vert.x-worker-thread-10] net.bluemind.core.calendar.CalendarBindingImpl ERROR - UNKNOWN None of the configured nodes are available: ]
2016-02-21 17:33:19,277 [vert.x-worker-thread-10] net.bluemind.core.server.EventHandler$48 ERROR - None of the configured nodes are available: ]
net.bluemind.core.api.fault.ServerFault: None of the configured nodes are available: ]
	at net.bluemind.core.calendar.CalendarHome.createEvent(CalendarHome.java:213) ~[net.bluemind.core_1.0.0.b13769.jar:na]
	at net.bluemind.core.calendar.CalendarBindingImpl.create(CalendarBindingImpl.java:502) ~[net.bluemind.core_1.0.0.b13769.jar:na]
	at net.bluemind.core.calendar.CalendarBindingImpl.doSync(CalendarBindingImpl.java:1654) ~[net.bluemind.core_1.0.0.b13769.jar:na]
	at net.bluemind.core.server.EventHandler$48.execute(EventHandler.java:1285) ~[net.bluemind.core_1.0.0.b13769.jar:na]
	at net.bluemind.core.server.SecureMethod.execute(SecureMethod.java:54) [net.bluemind.core_1.0.0.b13769.jar:na]
	at net.bluemind.core.server.vertx.CoreRpcReceiver.handle(CoreRpcReceiver.java:81) [net.bluemind.core_1.0.0.b13769.jar:na]
	at net.bluemind.core.server.vertx.CoreRpcReceiver.handle(CoreRpcReceiver.java:1) [net.bluemind.core_1.0.0.b13769.jar:na]
	at org.vertx.java.core.eventbus.impl.DefaultEventBus$11.run(DefaultEventBus.java:963) [vertx-core-2.1.6.jar:na]
	at org.vertx.java.core.impl.DefaultContext$3.run(DefaultContext.java:175) [vertx-core-2.1.6.jar:na]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [na:1.7.0_60]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [na:1.7.0_60]
	at java.lang.Thread.run(Thread.java:745) [na:1.7.0_60]
2

Il semblerait que le service ElasticSearch ne fonctionne pas.

Est-il démarré:

# ps auwx | grep elastic

Que donne la commande:

# ls -al /var/log/*hprof
3

Bonjour,

Ci dessous les infos :

Est-il démarré:

# ps auwx | grep elastic

root@inbox:~# ps auwx | grep elastic
root     22169  0.0  0.0  10948   932 pts/0    S+   07:57   0:00 grep --color=auto elastic

Que donne la commande:

# ls -al /var/log/*hprof

root@inbox:~# ls -al /var/log/*hprof
ls: cannot access /var/log/*hprof: No such file or directory

Merci de votre aide !

4

Le service ElasticSearch n’est pas démarré.

Faites:

# bmctl restart

Quand le service semble revenu, que donne:

# ps auwx | grep elastic
5

Ci dessous :

root@inbox:~#  ps auwx | grep elastic
root     23739  1.3 17.0 1200216 672060 pts/0  SLl  08:21   0:23 /usr/lib/jvm/bm                                                                                                                     -jdk/bin/java -Xloggc:/var/log/garbage-collector/bm-elasticsearch/gc.pause.log -                                                                                                                     XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=4 -XX:GCLogFileSize=4M -XX:+Prin                                                                                                                     tGCApplicationStoppedTime -server -Xms256m -Xmx256m -XX:MaxPermSize=128m -Xss256                                                                                                                     k -XX:MaxDirectMemorySize=256m -XX:+UseCompressedOops -XX:+UseG1GC -XX:MaxGCPaus                                                                                                                     eMillis=500 -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/var/log -Djava.net                                                                                                                     .preferIPv4Stack=true -Delasticsearch -Des.pidfile=/var/run/bm-elasticsearch.pid                                                                                                                      -Des.path.home=/usr/share/bm-elasticsearch -cp :/usr/share/bm-elasticsearch/lib                                                                                                                     /elasticsearch-1.0.3.jar:/usr/share/bm-elasticsearch/lib/*:/usr/share/bm-elasti                                                                                                                      search/lib/sigar/* org.elasticsearch.bootstrap.Elasticsearch
root     26105  0.0  0.0  10952   936 pts/0    S+   08:51   0:00 grep --color=au                                                                                                                     to elastic

Le service est redemarré. Ce problème est récurrent et le service plante régulièrement. Est-ce possible d’en trouver la cause ?

6

Il y a des chances pour que ce soit lié à un manque de ressources. Lorsqu’il se retrouve arrếté, il faut vérifier ses logs, ainsi que ceux du kernel, ce dernier pouvant prendre la décision de tuer un processus qu’il juge trop gourmand pour les ressources disponibles.

Vérifiez aussi la présences de fichier leak dans /root ou de *hprof dans /var/log.