Yet another invalid internal transport message format error

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Yet another invalid internal transport message format error

Jack Park-2
The console trace snippet is below.

The bug started for reasons I do not understand.
Facts:
There is an instance of ES on 9300 on another box.
This instance was set to 9250 and was running fine until I attempted to start another localhost on this box at 9350 and noticed that they (9250 and 9350) wanted to play nice with each other, the upshot being that I couldn't boot into 9350 with any client. 

So, 9400 (was 9250) is running alone now, and still cannot get it to boot properly. I am booting from a NodeJS client es.js, and it has been running fine. In fact, the other ES instance on 9300 is driving an es.js online client.

A socket closes somewhere early in testing for index existence, and all the options being sent are the same as before.

What am I missing?
Many thanks in advance



[2014-11-10 10:38:00,085][WARN ][transport.netty          ] [Boomslang] exception caught on transport layer [[id: 0xe12df19f, /127.0.0.1:54752 => /127.0.0.1:9400]], closing connection
java.io.StreamCorruptedException: invalid internal transport message format
        at org.elasticsearch.transport.netty.SizeHeaderFrameDecoder.decode(SizeH
eaderFrameDecoder.java:46)
        at org.elasticsearch.common.netty.handler.codec.frame.FrameDecoder.callD
ecode(FrameDecoder.java:425)

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAH6s0fwM45f%3Dziz1%3DO6WCfW6c6-eq9_45o8r%3DZOXO6owAPJ9ow%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.