Setup problem: No handler for action exception on 9300

Elastic Stack Elasticsearch
1

Hi all,

I just followed the guide to create elasticsearch on ubuntu. It works fine when I access it
through http://localhost:9200. But when I try to connect to it through the java client,
at port 9300, it throws an error at me.

12/06/21 10:23:31 WARN client.transport: [Stryfe] failed to get node info for [#transport#-1][inet[/localhost:9300]]
org.elasticsearch.transport.RemoteTransportException: [Tinkerer][inet[/127.0.0.1:9300]][]
Caused by: org.elasticsearch.transport.ActionNotFoundTransportException: No handler for action []

I think it is a problem of configuration. could someone give me a suggestion what might be missing?

I have the following in my /etc/elasticsearch/elasticsearch.yml file:

cluster.name: elasticsearch
path.data: /var/data/elasticsearch
network.bind_host: 127.0.0.1
network.publish_host: 127.0.0.1
network.host: 127.0.0.1
transport.tcp.port: 9300

Thank you.

Yuhan

2

What is your java code ?

David :wink:
Twitter : @dadoonet / @elasticsearchfr

Le 21 juin 2012 à 19:39, Yuhan yzhang@onescreen.com a écrit :

Hi all,

I just followed the guide to create elasticsearch on ubuntu. It works fine
when I access it
through http://localhost:9200. But when I try to connect to it through the
java client,
at port 9300, it throws an error at me.

12/06/21 10:23:31 WARN client.transport: [Stryfe] failed to get node info
for [#transport#-1][inet[/localhost:9300]]
org.elasticsearch.transport.RemoteTransportException:
[Tinkerer][inet[/127.0.0.1:9300]]
Caused by: org.elasticsearch.transport.ActionNotFoundTransportException: No
handler for action

I think it is a problem of configuration. could someone give me a suggestion
what might be missing?

I have the following in my /etc/elasticsearch/elasticsearch.yml file:

cluster.name: elasticsearch
path.data: /var/data/elasticsearch
network.bind_host: 127.0.0.1
network.publish_host: 127.0.0.1
network.host: 127.0.0.1
transport.tcp.port: 9300

Thank you.

Yuhan

--
View this message in context: http://elasticsearch-users.115913.n3.nabble.com/setup-problem-No-handler-for-action-exception-on-9300-tp4019579.html
Sent from the Elasticsearch Users mailing list archive at Nabble.com.

3

hi David,

Thanks for the reply. here's how I initialized the client.

public Client newSearchClient() {
    String host = "127.0.0.1";
    int port = 9300;
    InetSocketTransportAddress address = new

InetSocketTransportAddress(host, port);
return new TransportClient().addTransportAddress( address );
}

The exception was thrown from "addTransportAddress". I'm using a version
0.18.5 client on a 0.19.4 server. could this be a problem?

Thank you.

Yuhan

On Thu, Jun 21, 2012 at 10:48 AM, David Pilato david@pilato.fr wrote:

What is your java code ?

David :wink:
Twitter : @dadoonet / @elasticsearchfr

Le 21 juin 2012 à 19:39, Yuhan yzhang@onescreen.com a écrit :

Hi all,

I just followed the guide to create elasticsearch on ubuntu. It works
fine
when I access it
through http://localhost:9200. But when I try to connect to it through
the
java client,
at port 9300, it throws an error at me.

12/06/21 10:23:31 WARN client.transport: [Stryfe] failed to get node info
for [#transport#-1][inet[/localhost:9300]]
org.elasticsearch.transport.RemoteTransportException:
[Tinkerer][inet[/127.0.0.1:9300]]
Caused by: org.elasticsearch.transport.ActionNotFoundTransportException:
No
handler for action

I think it is a problem of configuration. could someone give me a
suggestion
what might be missing?

I have the following in my /etc/elasticsearch/elasticsearch.yml file:

cluster.name: elasticsearch
path.data: /var/data/elasticsearch
network.bind_host: 127.0.0.1
network.publish_host: 127.0.0.1
network.host: 127.0.0.1
transport.tcp.port: 9300

Thank you.

Yuhan

--
View this message in context:
http://elasticsearch-users.115913.n3.nabble.com/setup-problem-No-handler-for-action-exception-on-9300-tp4019579.html
Sent from the Elasticsearch Users mailing list archive at Nabble.com.

4

Yes ! It is the problem.

David :wink:
Twitter : @dadoonet / @elasticsearchfr

Le 21 juin 2012 à 21:06, Yuhan Zhang yzhang@onescreen.com a écrit :

hi David,

Thanks for the reply. here's how I initialized the client.

public Client newSearchClient() {
    String host = "127.0.0.1";
    int port = 9300;
    InetSocketTransportAddress address = new InetSocketTransportAddress(host, port);
    return new TransportClient().addTransportAddress( address ); 
}

The exception was thrown from "addTransportAddress". I'm using a version 0.18.5 client on a 0.19.4 server. could this be a problem?

Thank you.

Yuhan

On Thu, Jun 21, 2012 at 10:48 AM, David Pilato david@pilato.fr wrote:
What is your java code ?

David :wink:
Twitter : @dadoonet / @elasticsearchfr

Le 21 juin 2012 à 19:39, Yuhan yzhang@onescreen.com a écrit :

Hi all,

I just followed the guide to create elasticsearch on ubuntu. It works fine
when I access it
through http://localhost:9200. But when I try to connect to it through the
java client,
at port 9300, it throws an error at me.

12/06/21 10:23:31 WARN client.transport: [Stryfe] failed to get node info
for [#transport#-1][inet[/localhost:9300]]
org.elasticsearch.transport.RemoteTransportException:
[Tinkerer][inet[/127.0.0.1:9300]]
Caused by: org.elasticsearch.transport.ActionNotFoundTransportException: No
handler for action

I think it is a problem of configuration. could someone give me a suggestion
what might be missing?

I have the following in my /etc/elasticsearch/elasticsearch.yml file:

cluster.name: elasticsearch
path.data: /var/data/elasticsearch
network.bind_host: 127.0.0.1
network.publish_host: 127.0.0.1
network.host: 127.0.0.1
transport.tcp.port: 9300

Thank you.

Yuhan

--
View this message in context: http://elasticsearch-users.115913.n3.nabble.com/setup-problem-No-handler-for-action-exception-on-9300-tp4019579.html
Sent from the Elasticsearch Users mailing list archive at Nabble.com.

5

hi David,

Thanks for the anwser. I downgraded the server to 0.18.5 and it works.

Yuhan

On Thu, Jun 21, 2012 at 12:29 PM, David Pilato david@pilato.fr wrote:

Yes ! It is the problem.

David :wink:
Twitter : @dadoonet / @elasticsearchfr

Le 21 juin 2012 à 21:06, Yuhan Zhang yzhang@onescreen.com a écrit :

hi David,

Thanks for the reply. here's how I initialized the client.

public Client newSearchClient() {
    String host = "127.0.0.1";
    int port = 9300;
    InetSocketTransportAddress address = new

InetSocketTransportAddress(host, port);
return new TransportClient().addTransportAddress( address );
}

The exception was thrown from "addTransportAddress". I'm using a version
0.18.5 client on a 0.19.4 server. could this be a problem?

Thank you.

Yuhan

On Thu, Jun 21, 2012 at 10:48 AM, David Pilato david@pilato.fr wrote:

What is your java code ?

David :wink:
Twitter : @dadoonet / @elasticsearchfr

Le 21 juin 2012 à 19:39, Yuhan yzhang@onescreen.com a écrit :

Hi all,

I just followed the guide to create elasticsearch on ubuntu. It works
fine
when I access it
through http://localhost:9200. But when I try to connect to it through
the
java client,
at port 9300, it throws an error at me.

12/06/21 10:23:31 WARN client.transport: [Stryfe] failed to get node
info
for [#transport#-1][inet[/localhost:9300]]
org.elasticsearch.transport.RemoteTransportException:
[Tinkerer][inet[/127.0.0.1:9300]]
Caused by:
org.elasticsearch.transport.ActionNotFoundTransportException: No
handler for action

I think it is a problem of configuration. could someone give me a
suggestion
what might be missing?

I have the following in my /etc/elasticsearch/elasticsearch.yml file:

cluster.name: elasticsearch
path.data: /var/data/elasticsearch
network.bind_host: 127.0.0.1
network.publish_host: 127.0.0.1
network.host: 127.0.0.1
transport.tcp.port: 9300

Thank you.

Yuhan

--
View this message in context:
http://elasticsearch-users.115913.n3.nabble.com/setup-problem-No-handler-for-action-exception-on-9300-tp4019579.html
Sent from the Elasticsearch Users mailing list archive at Nabble.com.

--
Yuhan Zhang
Application Developer
OneScreen Inc.
yzhang@onescreen.com ehorne@onescreen.com
www.onescreen.com

The information contained in this e-mail is for the exclusive use of the
intended recipient(s) and may be confidential, proprietary, and/or legally
privileged. Inadvertent disclosure of this message does not constitute a
waiver of any privilege. If you receive this message in error, please do
not directly or indirectly print, copy, retransmit, disseminate, or
otherwise use the information. In addition, please delete this e-mail and
all copies and notify the sender.