tlrx/transport-zeromq — Issue #5: Errors when shutting down
Author: clintongormley
Created: 2011-12-05 16:18:54+00:00
State: open

Hiya

I'm still getting errors when trying to shut down ES with the zeromq plugin enabled. i try starting ES in foreground mode, then Ctrl-C'ing it and I get either:

[17:15:38,290][INFO ][node ] [Torpedo] {0.18.5}[23697]: stopping ...
[17:15:38,346][INFO ][node ] [Torpedo] {0.18.5}[23697]: stopped
[17:15:38,346][INFO ][node ] [Torpedo] {0.18.5}[23697]: closing ...
[17:15:38,348][INFO ][zeromq.impl ] [Torpedo] ØMQ dealer socket closed
[17:15:38,348][INFO ][zeromq.impl ] [Torpedo] ØMQ router socket closed
Exception in thread "elasticsearch[Torpedo]zeromq_server-pool-10-thread-1" org.elasticsearch.ElasticSearchIllegalStateException: Can't move to started state when closed
at org.elasticsearch.common.component.Lifecycle.moveToStarted(Lifecycle.java:137)
at org.elasticsearch.common.component.AbstractLifecycleComponent.start(AbstractLifecycleComponent.java:81)
at org.elasticsearch.zeromq.ZMQServer$1.run(ZMQServer.java:56)
at java.lang.Thread.run(Thread.java:662)

or

[17:15:44,396][INFO ][node ] [Lorelei] {0.18.5}[23770]: stopping ...
[17:15:44,400][INFO ][node ] [Lorelei] {0.18.5}[23770]: stopped
[17:15:44,400][INFO ][node ] [Lorelei] {0.18.5}[23770]: closing ...
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGFPE (0x8) at pc=0x00007fb491777dd3, pid=23770, tid=140413491730176
#
# JRE version: 6.0_29-b11
# Java VM: Java HotSpot(TM) 64-Bit Server VM (20.4-b02 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C [libzmq.so.1+0x15dd3] zmq::lb_t::send(zmq_msg_t*, int)+0x153
#
# An error report file with more information is saved as:
# /opt/elasticsearch/hs_err_pid23770.log
#
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
Aborted

See https://gist.github.com/d39f002d853e7584a34b for the error report mentioned above