# Executor does not connect to Coordinator **URL:** \ **Category:** Uncategorized\ **Created:** [September 4, 2017, 8:05pm UTC](https://community.dremio.com/t/executor-does-not-connect-to-coordinator/242 "2017-09-04T20:05:01Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![allan.sene](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/allan.sene/32/144_2.png) [@allan.sene](https://community.dremio.com/u/allan.sene)\ **Post date:** [September 4, 2017, 8:05pm UTC](https://community.dremio.com/t/executor-does-not-connect-to-coordinator/242/1 "2017-09-04T20:05:01Z")
Hi, guys! I’ve just installed another node to be an Executor but it is not been recognized by the Coordinator. Both `dremio.conf` are pointing to my MASTER\_INTERNAL\_IP. I’m obtaining this message on `server.log` from the **Executor** : `2017-09-04 18:21:00,359 [main] INFO c.d.d.s.exec.MasterStatusListener - Waiting for master :45678` My **Master** is logging something like this: `2017-09-04 19:37:31,092 [FABRIC-6] INFO c.d.services.fabric.FabricServer - [FABRIC]: Channel closed /:45678 <--> /:43408 (control server)` but the Slave port is changing randomly sometimes (to 4340\*) `netstat -tunaup` is giving me `tcp6 0 0 SLAVE_INTERNAL_IP:41548 MASTER_INTERNAL_IP:2181 ESTABLISHED 1536/java` I’m using EC2 on Amazon. I’ve already opened these ports for connections on both nodes, but the Executor still not been visible. What am I missing? ---
**Author:** ![can](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/can/32/40_2.png) [@can](https://community.dremio.com/u/can)\ **Post date:** [September 5, 2017, 7:02pm UTC](https://community.dremio.com/t/executor-does-not-connect-to-coordinator/242/2 "2017-09-05T19:02:51Z")
@allan.sene could you give this a shot with fully qualified host names that are resolvable on all nodes? Also just in case, here is the [list of ports](http://docs.dremio.com/deployment/system-requirements.html#network) needed by Dremio. ---
**Author:** ![allan.sene](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/allan.sene/32/144_2.png) [@allan.sene](https://community.dremio.com/u/allan.sene)\ **Post date:** [September 5, 2017, 9:06pm UTC](https://community.dremio.com/t/executor-does-not-connect-to-coordinator/242/3 "2017-09-05T21:06:54Z")
Thanks for replying! I can `telnet` all those ports from my **executor** node to the **coordinator**. Actually, as `netstat -tunaup` shows, both are connected (slave dremio \<-\> master zookeeper), but with no send/received signals. =/ Here goes my Security Group configuration: ![23](https://us1.discourse-cdn.com/flex020/uploads/dremio/original/1X/85a448f147ba7e7bde4df85a4b3c64b165958773.png) ---
**Author:** ![can](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/can/32/40_2.png) [@can](https://community.dremio.com/u/can)\ **Post date:** [September 5, 2017, 9:48pm UTC](https://community.dremio.com/t/executor-does-not-connect-to-coordinator/242/4 "2017-09-05T21:48:37Z")
All nodes need to be able to allow communication on 42678 and 2181 to all other nodes. That could be the issue here. Also, have you tried using FQDNs instead of IPs? Also, looks like the network requirements on the docs are not clear regarding inbound vs. outbound needs, we’ll take a look. ---
**Author:** ![allan.sene](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/allan.sene/32/144_2.png) [@allan.sene](https://community.dremio.com/u/allan.sene)\ **Post date:** [September 6, 2017, 5:59pm UTC](https://community.dremio.com/t/executor-does-not-connect-to-coordinator/242/5 "2017-09-06T17:59:48Z")
Yes, I’m using FQDN to point the Master… Both machines are reachable from each other (via `ping `). I’m using the same SG to all Dremio nodes, but the Dremio Executor’s service does even open connections on those ports, unlike the master: ``` ubuntu@dremio-executor-1:~$ sudo netstat -lptu Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 *:ssh *:* LISTEN 1243/sshd tcp6 0 0 [::]:ssh [::]:* LISTEN 1243/sshd udp 0 0 *:bootpc *:* 1109/dhclient ``` On Master: ``` ubuntu@dremio-master-1:~$ sudo netstat -lptu Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 *:ssh *:* LISTEN 1287/sshd tcp6 0 0 [::]:31010 [::]:* LISTEN 16942/java tcp6 0 0 [::]:2181 [::]:* LISTEN 16942/java tcp6 0 0 [::]:45678 [::]:* LISTEN 16942/java tcp6 0 0 [::]:ssh [::]:* LISTEN 1287/sshd tcp6 0 0 [::]:9047 [::]:* LISTEN 16942/java udp 0 0 *:bootpc *:* 1108/dhclient ``` If I restart the Dremio service on Master, the executor **logs the disconnection and connect again**! 😂 **very strange** 🤔: ``` 2017-09-06 17:38:44,260 [Curator-Framework-0] ERROR org.apache.curator.ConnectionState - Connection timed out for connection string (dremio-master-1:2181) and timeout (5000) / elapsed (54009) org.apache.curator.CuratorConnectionLossException: KeeperErrorCode = ConnectionLoss at org.apache.curator.ConnectionState.checkTimeouts(ConnectionState.java:225) [curator-client-2.12.0.jar:na] at org.apache.curator.ConnectionState.getZooKeeper(ConnectionState.java:94) [curator-client-2.12.0.jar:na] at org.apache.curator.CuratorZookeeperClient.getZooKeeper(CuratorZookeeperClient.java:117) [curator-client-2.12.0.jar:na] at org.apache.curator.framework.imps.CuratorFrameworkImpl.performBackgroundOperation(CuratorFrameworkImpl.java:835) [curator-framework-2.12.0.jar:na] at org.apache.curator.framework.imps.CuratorFrameworkImpl.backgroundOperationsLoop(CuratorFrameworkImpl.java:809) [curator-framework-2.12.0.jar:na] at org.apache.curator.framework.imps.CuratorFrameworkImpl.access$300(CuratorFrameworkImpl.java:64) [curator-framework-2.12.0.jar:na] at org.apache.curator.framework.imps.CuratorFrameworkImpl$4.call(CuratorFrameworkImpl.java:267) [curator-framework-2.12.0.jar:na] at java.util.concurrent.FutureTask.run(FutureTask.java:266) [na:1.8.0_131] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [na:1.8.0_131] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [na:1.8.0_131] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [na:1.8.0_131] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [na:1.8.0_131] at java.lang.Thread.run(Thread.java:748) [na:1.8.0_131] 2017-09-06 17:39:09,118 [Curator-ConnectionStateManager-0] INFO c.d.s.coordinator.zk.ZKClusterClient - ZK connection state changed to RECONNECTED 2017-09-06 17:39:35,095 [main] INFO c.d.d.s.exec.MasterStatusListener - Waiting for master dremio-master-1:45678 2017-09-06 17:40:35,097 [main] INFO c.d.d.s.exec.MasterStatusListener - Waiting for master dremio-master-1:45678 2017-09-06 17:41:35,100 [main] INFO c.d.d.s.exec.MasterStatusListener - Waiting for master dremio-master-1:45678 ``` I will try to redo the installation on another EC2 instance… maybe I screwed something… Thanks! 😄 ---
**Author:** ![allan.sene](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/allan.sene/32/144_2.png) [@allan.sene](https://community.dremio.com/u/allan.sene)\ **Post date:** [September 11, 2017, 6:58pm UTC](https://community.dremio.com/t/executor-does-not-connect-to-coordinator/242/6 "2017-09-11T18:58:48Z")
Any idea, guys? I’ve already tried changing the master to slave and install on another clean EC2 instance and nothing works ☹ I’m always installing using the TAR Ball. Do you think will change anything if I use the RPM package or provision with YARN? ---
**Author:** ![yufeldman](https://avatars.discourse-cdn.com/v4/letter/y/c77e96/32.png) [@yufeldman](https://community.dremio.com/u/yufeldman)\ **Post date:** [September 11, 2017, 9:32pm UTC](https://community.dremio.com/t/executor-does-not-connect-to-coordinator/242/7 "2017-09-11T21:32:16Z")
Could you look at: [EC2 installation](https://community.dremio.com/t/ec2-installation/129/16) And see if that might help you solving your issue ---
**Author:** ![allan.sene](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/allan.sene/32/144_2.png) [@allan.sene](https://community.dremio.com/u/allan.sene)\ **Post date:** [September 11, 2017, 10:25pm UTC](https://community.dremio.com/t/executor-does-not-connect-to-coordinator/242/8 "2017-09-11T22:25:35Z")
Actually, I’ve tried some things punctuated on this thread, @yufeldman, like use FQDNs, and configure the same Inbound/Outbound Rules, as I showed above… I don’t know what I am missing 😥 A thing that differs from my case is the EC2 instance image: mine is Ubuntu. I’m gonna try using Amazon Linux and install with RPM files. Maybe the tar build is broken or something… ---
**Author:** ![yufeldman](https://avatars.discourse-cdn.com/v4/letter/y/c77e96/32.png) [@yufeldman](https://community.dremio.com/u/yufeldman)\ **Post date:** [September 11, 2017, 11:20pm UTC](https://community.dremio.com/t/executor-does-not-connect-to-coordinator/242/9 "2017-09-11T23:20:45Z")
Can you paste here dremio.conf from both executor and coordinator? ---
**Author:** ![allan.sene](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/allan.sene/32/144_2.png) [@allan.sene](https://community.dremio.com/u/allan.sene)\ **Post date:** [September 12, 2017, 12:05am UTC](https://community.dremio.com/t/executor-does-not-connect-to-coordinator/242/10 "2017-09-12T00:05:14Z")
FINALLY! Guys… what a **epic**! _lol_ 😂 Seems that: **or** the TAR build is broken **or** Dremio’s clusters are only functional with Amazon Linux on EC2 😕 🤔 Anyway, I think that will be a valuable shot, anyone tries to simulate this problem: Install a cluster with the TAR on Ubuntu servers. Thank you so much @yufeldman and @can for caring 🙂