Failed to connect to node 9001

I’m upgrading SonarQube from 7.1 to 7.9.2 using this tutorial and everything goes well up until I run SonarQube, where it runs but isn’t showing up. The only error I get in the logs is below.

It says it cannot connect to the node, but the final line says it is connected to the elastic search node?

sonar.log:

2020.01.23 12:09:06 DEBUG app[][o.e.c.t.TransportClientNodesService] failed to connect to node [{#transport#-1}{xWfa6Tf6RzKU9B6Or7QcSQ}{127.0.0.1}{127.0.0.1:9001}], ignoring...
org.elasticsearch.transport.ConnectTransportException: [][127.0.0.1:9001] connect_exception
        at org.elasticsearch.transport.TcpTransport$ChannelsConnectedListener.onFailure(TcpTransport.java:1309)
        at org.elasticsearch.action.ActionListener.lambda$toBiConsumer$2(ActionListener.java:100)
        at org.elasticsearch.common.concurrent.CompletableContext.lambda$addListener$0(CompletableContext.java:42)
        at java.base/java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:859)
        at java.base/java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(CompletableFuture.java:837)
        at java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506)
        at java.base/java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:2088)
        at org.elasticsearch.common.concurrent.CompletableContext.completeExceptionally(CompletableContext.java:57)
        at org.elasticsearch.transport.netty4.Netty4TcpChannel.lambda$new$1(Netty4TcpChannel.java:72)
        at io.netty.util.concurrent.DefaultPromise.notifyListener0(DefaultPromise.java:511)
        at io.netty.util.concurrent.DefaultPromise.notifyListeners0(DefaultPromise.java:504)
        at io.netty.util.concurrent.DefaultPromise.notifyListenersNow(DefaultPromise.java:483)
        at io.netty.util.concurrent.DefaultPromise.notifyListeners(DefaultPromise.java:424)
        at io.netty.util.concurrent.DefaultPromise.tryFailure(DefaultPromise.java:121)
        at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.fulfillConnectPromise(AbstractNioChannel.java:327)
        at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.finishConnect(AbstractNioChannel.java:343)
        at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:644)
        at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:591)
        at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:508)
        at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:470)
        at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:909)
        at java.base/java.lang.Thread.run(Thread.java:834)
Caused by: io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: /127.0.0.1:9001
        at java.base/sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
        at java.base/sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:779)
        at io.netty.channel.socket.nio.NioSocketChannel.doFinishConnect(NioSocketChannel.java:327)
        at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.finishConnect(AbstractNioChannel.java:340)
        ... 6 common frames omitted
Caused by: java.net.ConnectException: Connection refused
        ... 10 common frames omitted
2020.01.23 12:09:06 DEBUG app[][o.s.a.e.EsConnectorImpl] Connected to Elasticsearch node: [127.0.0.1:9001]


.


2020.01.23 12:09:49 INFO  app[][o.s.a.SchedulerImpl] Process[ce] is up
2020.01.23 12:09:49 INFO  app[][o.s.a.SchedulerImpl] SonarQube is up

At the end of sonar.log it says SonarQube is running, and if i run sonar.sh status, that confirms SonarQube is running, but nothing is at localhost:9000.

I’m running Linux and my versions are:
SonarQube 7.9.2
PostgreSQL 10.11
Open JDK 11.0.6

Hi,

That error is at the DEBUG level because it’s not directly relevant. What do your other logs say?

Also, that tutorial suggests you edit your SQ port to 80. Did you do that? And if so, is anything running on localhost/localhost:80?

 
Ann

Hi Ann,

thanks for the reply. But no worries, it was a network issue on my end.

Hello,

I am seeing the same issue in my server. What was the network problem at your end?

Regards,
Rajeesh

I was trying to view it on the wrong host, so just my error rather than anything else. Probably not much help to you.

A post was split to a new topic: Startup error on docker