None of the configured nodes are available

[neilneyman]

Version 2.0.0 is failing, with the message None of the configured nodes are available: {#transport#-1}{127.0.0.1}{localhost/127.0.0.1:9300}

I know elasticsearch is running and listening on the correct ports. Do you have any idea what's causing this?

The riverweb logfile looks like this where it fails:

2016-02-09 16:30:10,983 [main] INFO  Lasta Di boot successfully.
2016-02-09 16:30:10,986 [main] INFO    SmartDeploy Mode: Warm Deploy
2016-02-09 16:30:10,986 [main] INFO    Smart Package: org.codelibs.riverweb.app
2016-02-09 16:30:11,002 [main] INFO  Disconnected to elasticsearch:localhost:9300
2016-02-09 16:30:11,093 [main] INFO  [Saint Anna] loaded [], sites []
2016-02-09 16:30:11,901 [main] INFO  [Saint Anna] failed to get node info for {#transport#-1}{127.0.0.1}{localhost/127.0.0.1:9300}, disconnecting...
RemoteTransportException[[Failed to deserialize response of type [org.elasticsearch.action.admin.cluster.node.liveness.LivenessResponse]]];
  nested: TransportSerialization         Exception[Failed to deserialize response of type [org.elasticsearch.action.admin.cluster.node.liveness.LivenessResponse]]; 
  nested: NoClassDefFoundError[org/apache/lucene/         search/suggest/Lookup]; 
  nested: ClassNotFoundException[org.apache.lucene.search.suggest.Lookup];
Caused by: TransportSerializationException[Failed to deserialize response of type [org.elasticsearch.action.admin.cluster.node.liveness.LivenessResponse]]; 
  nested: NoClas sDefFoundError[org/apache/lucene/search/suggest/Lookup];
   nested: ClassNotFoundException[org.apache.lucene.search.suggest.Lookup];
        at org.elasticsearch.transport.netty.MessageChannelHandler.handleResponse(MessageChannelHandler.java:179)
        at org.elasticsearch.transport.netty.MessageChannelHandler.messageReceived(MessageChannelHandler.java:138)
        at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70)
        at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564)
        at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791)

(snip)

2016-02-09 16:30:11,909 [main] INFO  Connected to localhost:9300
2016-02-09 16:30:11,953 [Thread-0] INFO  Disconnected to elasticsearch:localhost:9300

[marevol]

Hmm..., it's a problem about elasticsearch version...

[neilneyman]

Oh I see, probably it. This is ES 2.2.0, looks like the river is only compatible up to 2.1. Any plan for an upcoming version for 2.2 or do I need to use it with 2.1?

Thanks!

[marevol]

I'll release it this weekend :)