Hi,I get the following error when I execute query task,I have got the tables list in DB,but I can’t query the message in tables.The error message :
No connection active, opening new connection to 192.168.2.2:45678.
I install a single node,and my firewall has stoped.
ifconfig message is :
eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 10.0.0.5 netmask 255.255.0.0 broadcast 0.0.0.0
inet6 fe80::219:6ff:fed2:dfa6 prefixlen 64 scopeid 0x20
ether 00:19:06:d2:df:a6 txqueuelen 1000 (Ethernet)
RX packets 101248 bytes 680141038 (648.6 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 106132 bytes 29877137 (28.4 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10
loop txqueuelen 1 (Local Loopback)
RX packets 27958 bytes 2984633 (2.8 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 27958 bytes 2984633 (2.8 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
I don’t know how does the IP 192.168.2.2 come from ?
Hi @hongyan_zhao
Can you please send us the server.log and sever.out?
If you click on Admin-Node Activity, what IP does it show?
Are you able to query other tables?
Where do you see the message “No connection active, opening new connection to 192.168.2.2:45678”? Doe this happen when you click on the table? Can you share the job profile with us
Dremio Logs
Share A Job Profile
Thanks
@balaji.ramaswamy
I got the message from server.log,I can get all table name,but I can’t query any table.
All error message:
2019-01-17 11:43:45,199 [23c006a4-9b37-54d1-d2c8-f71d86756700:foreman] INFO c.d.s.fabric.FabricConnectionManager - [FABRIC]: No connection active, opening new connection to 192.168.2.2:45678.
2019-01-17 11:43:45,200 [FABRIC-2] ERROR c.d.exec.work.foreman.QueryManager - Failure while attempting to CANCEL fragment 23c006a4-9b37-54d1-d2c8-f71d86756700:1:3 on endpoint 192.168.2.2:31010 with {}.
com.dremio.exec.rpc.ConnectionFailedException: com.dremio.exec.rpc.RpcException: Command failed while establishing connection. Failure type CONNECTION.
at com.dremio.exec.rpc.ConnectionFailedException.mapException(ConnectionFailedException.java:31) ~[dremio-services-base-rpc-3.0.6-201812082352540436-1f684f9.jar:3.0.6-201812082352540436-1f684f9]
at com.dremio.exec.rpc.ListeningCommand.connectionFailed(ListeningCommand.java:65) ~[dremio-services-base-rpc-3.0.6-201812082352540436-1f684f9.jar:3.0.6-201812082352540436-1f684f9]
at com.dremio.services.fabric.FabricServiceImpl$ProxyCommand.connectionFailed(FabricServiceImpl.java:200) [dremio-services-fabric-rpc-3.0.6-201812082352540436-1f684f9.jar:3.0.6-201812082352540436-1f684f9]
at com.dremio.exec.rpc.ReconnectingConnection$ConnectionListeningFuture.connectionFailed(ReconnectingConnection.java:179) [dremio-services-base-rpc-3.0.6-201812082352540436-1f684f9.jar:3.0.6-201812082352540436-1f684f9]
at com.dremio.exec.rpc.BasicClient$ConnectionMultiListener$ConnectionEstablishmentListener.operationComplete(BasicClient.java:308) [dremio-services-base-rpc-3.0.6-201812082352540436-1f684f9.jar:3.0.6-201812082352540436-1f684f9]
at com.dremio.exec.rpc.BasicClient$ConnectionMultiListener$ConnectionEstablishmentListener.operationComplete(BasicClient.java:273) [dremio-services-base-rpc-3.0.6-201812082352540436-1f684f9.jar:3.0.6-201812082352540436-1f684f9]
at io.netty.util.concurrent.DefaultPromise.notifyListener0(DefaultPromise.java:511) [netty-common-4.1.22.Final.jar:4.1.22.Final]
at io.netty.util.concurrent.DefaultPromise.notifyListeners0(DefaultPromise.java:504) [netty-common-4.1.22.Final.jar:4.1.22.Final]
at io.netty.util.concurrent.DefaultPromise.notifyListenersNow(DefaultPromise.java:483) [netty-common-4.1.22.Final.jar:4.1.22.Final]
at io.netty.util.concurrent.DefaultPromise.notifyListeners(DefaultPromise.java:424) [netty-common-4.1.22.Final.jar:4.1.22.Final]
at io.netty.util.concurrent.DefaultPromise.tryFailure(DefaultPromise.java:121) [netty-common-4.1.22.Final.jar:4.1.22.Final]
at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe$1.run(AbstractNioChannel.java:269) [netty-transport-4.1.22.Final.jar:4.1.22.Final]
at io.netty.util.concurrent.PromiseTask$RunnableAdapter.call(PromiseTask.java:38) [netty-common-4.1.22.Final.jar:4.1.22.Final]
at io.netty.util.concurrent.ScheduledFutureTask.run(ScheduledFutureTask.java:125) [netty-common-4.1.22.Final.jar:4.1.22.Final]
at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:163) [netty-common-4.1.22.Final.jar:4.1.22.Final]
at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:404) [netty-common-4.1.22.Final.jar:4.1.22.Final]
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:463) [netty-transport-4.1.22.Final.jar:4.1.22.Final]
at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:886) [netty-common-4.1.22.Final.jar:4.1.22.Final]
at java.lang.Thread.run(Thread.java:748) [na:1.8.0_172]
Caused by: com.dremio.exec.rpc.RpcException: Command failed while establishing connection. Failure type CONNECTION.
at com.dremio.exec.rpc.RpcException.mapException(RpcException.java:71) ~[dremio-services-base-rpc-3.0.6-201812082352540436-1f684f9.jar:3.0.6-201812082352540436-1f684f9]
… 18 common frames omitted
Caused by: io.netty.channel.ConnectTimeoutException: connection timed out: /192.168.2.2:45678
at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe$1.run(AbstractNioChannel.java:267) [netty-transport-4.1.22.Final.jar:4.1.22.Final]
… 7 common frames omitted
2019-01-17 11:43:45,202 [FABRIC-2] INFO c.d.services.fabric.FabricClient - [FABRIC]: Channel closed null <–> null (fabric client)
2019-01-17 11:44:15,203 [FABRIC-3] ERROR com.dremio.exec.rpc.BasicClient - Failed to establish connection
Thanks
@balaji.ramaswamy Hi,Admin-node Active is empty,no one
Hi @hongyan_zhao
It looks like your coordinator did not come up clean. Can you please try the below steps
- dremio stop
- ps -ef | grep dremio should not return anything
- If process is still running then kill -9
- start dremio again (tail -f server.out)
- If no errors then review server.log for any errors
- Open UI-admin-node activity, should show your coordinator and executor running
- Try your query now
Thanks
@balaji.ramaswamy
Hi @balaji.ramaswamy
I have stoped and restarted dremio,but it can’t come up clean,when it started,I got the message:
2019-01-17 15:53:04,184 [main] INFO c.d.exec.server.NodeRegistration - Starting NodeRegistration for 192.168.2.2:31010
2019-01-17 15:53:04,199 [main] INFO c.d.exec.server.NodeRegistration - NodeRegistration is up for 192.168.2.2:31010
and then it will throw ExecutionException: connection timed out: /192.168.2.2:45678
My config file is:
services: {
coordinator.enabled: true,
coordinator.master.enabled: true,
executor.enabled: true
}
And my ifconfig is:
eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 10.0.0.5 netmask 255.255.0.0 broadcast 0.0.0.0
inet6 fe80::219:6ff:fed2:dfa6 prefixlen 64 scopeid 0x20<link>
ether 00:19:06:d2:df:a6 txqueuelen 1000 (Ethernet)
RX packets 103982 bytes 680737037 (649.2 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 108550 bytes 31549695 (30.0 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1 (Local Loopback)
RX packets 29995 bytes 3363002 (3.2 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 29995 bytes 3363002 (3.2 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
I don’t know where does the IP 192.168.2.2 come from?
Thanks
Hi @balaji.ramaswamy
I know where the IP 192.168.2.2 come from,my office’s dns server’error, it will parse every domain name it don’t know to 192.168.2.2,I have resolve this problem,I’m so sorry.
Think you very much!