# Cannnot connect executor node to master coordinator

**URL:** <https://community.dremio.com/t/cannnot-connect-executor-node-to-master-coordinator/469>\
**Category:** Uncategorized\
**Created:** [November 17, 2017, 4:17pm UTC](https://community.dremio.com/t/cannnot-connect-executor-node-to-master-coordinator/469 "2017-11-17T16:17:27Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![antoine](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/antoine/32/296_2.png) [@antoine](https://community.dremio.com/u/antoine)\
**Post date:** [November 17, 2017, 4:17pm UTC](https://community.dremio.com/t/cannnot-connect-executor-node-to-master-coordinator/469/1 "2017-11-17T16:17:27Z")

</div>

Hi,

I’m having issues setting up a simple cluster on EC2. I have a coordinator which also servers a executor, and an executor.

Symptoms: the web UI shows only the coordinator and not the executor node.

server log on executor keeps repeating `[main] INFO c.d.d.s.exec.MasterStatusListener - Waiting for master [[master fqdn]]:45678`

fqdn is a record on aws route 53 which points to the master. A `dig +short [fqdn]` shows the master’s actual private IP. I’ve also tested with mentionning the master’s private IP and master’s hostname (declared in executor’s /etc/hosts), with the same results.

Setup: coordinator and executor are c5.large instances running Amazon Linux. Dremio installed with latest rpm.  
Both use the same security group, which is pretty lax and should not be an issue:  
 ![image](https://us1.discourse-cdn.com/flex020/uploads/dremio/original/1X/b4d4d8d817551f41da1e755c7d61404fee40cf66.png)

dremio-env is left untouched.  
Coordinator dremio.conf:

```
master: {
  # the name of the master server. If this node matches the name, it starts the master service
  name: master.dremio.internal.swaven.com,
  port: 45678
}

paths: {
  # the local path for dremio to store data.
  local: "/data/dremio"

  # the distributed path Dremio data including job results, downloads, uploads, etc
  #dist: "pdfs://"${paths.local}"/pdfs"
}

services: {
  coordinator.enabled: true,
  executor.enabled: true
}

```

Executor dremio.conf:

```
master: {
  # the name of the master server. If this node matches the name, it starts the master service
  name: master.dremio.internal.swaven.com,
  port: 45678
}

paths: {
  # the local path for dremio to store data.
  local: "/data/dremio"

  # the distributed path Dremio data including job results, downloads, uploads, etc
  #dist: "pdfs://"${paths.local}"/pdfs"
}

services: {
  coordinator.enabled: false,
  executor.enabled: true
}

```

Instances can be pinged from each other.  
I hav seen [this thread](https://community.dremio.com/t/executor-does-not-connect-to-coordinator/242) and [this thread](https://community.dremio.com/t/ec2-installation/129), and tried what’s suggested in them, to no avail.

I’ve rebuilt both nodes from scratch a few times, with the same result each time. Is there anything I might have missed?

Thank you.

---

<div class="post-metadata">

**Author:** ![yufeldman](https://avatars.discourse-cdn.com/v4/letter/y/c77e96/32.png) [@yufeldman](https://community.dremio.com/u/yufeldman)\
**Post date:** [November 17, 2017, 8:08pm UTC](https://community.dremio.com/t/cannnot-connect-executor-node-to-master-coordinator/469/2 "2017-11-17T20:08:15Z")

</div>

Does master:name from dremio.conf matches one from your error message or in error it is different?

> [@antoine](#):
>
> master: {  
> name: [master.dremio.internal.swaven.com](http://master.dremio.internal.swaven.com),  
> port: 45678  
> }

> [@antoine](#):
>
> Waiting for master [[master fqdn]]:45678

---

<div class="post-metadata">

**Author:** ![antoine](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/antoine/32/296_2.png) [@antoine](https://community.dremio.com/u/antoine)\
**Post date:** [November 20, 2017, 8:26am UTC](https://community.dremio.com/t/cannnot-connect-executor-node-to-master-coordinator/469/3 "2017-11-20T08:26:33Z")

</div>

Yes, that’s the same name. I forgot to redact it consistently.

---

<div class="post-metadata">

**Author:** ![yufeldman](https://avatars.discourse-cdn.com/v4/letter/y/c77e96/32.png) [@yufeldman](https://community.dremio.com/u/yufeldman)\
**Post date:** [November 20, 2017, 5:59pm UTC](https://community.dremio.com/t/cannnot-connect-executor-node-to-master-coordinator/469/4 "2017-11-20T17:59:14Z")

</div>

Could you change following in \<dremio\_install\>/conf/logback.xml or if you installed via rpm conf is probably in /etc/dremio/logback.xml

```
<logger name="com.dremio">
  <level value="${dremio.log.level:-info}"/>
</logger>

```

to (changing info to debug)

> ```
> <logger name="com.dremio">
> <level value="${dremio.log.level:-debug}"/>
> </logger>
> 
> ```

On the executor node and restart executor. After that could you check for following statements in server.log  
"Master node ‘masternode’ resolves to ‘address’.  
It feels like ‘masternode’ and ‘address’ may not show the same.

---

<div class="post-metadata">

**Author:** ![antoine](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/antoine/32/296_2.png) [@antoine](https://community.dremio.com/u/antoine)\
**Post date:** [November 21, 2017, 8:28am UTC](https://community.dremio.com/t/cannnot-connect-executor-node-to-master-coordinator/469/5 "2017-11-21T08:28:29Z")

</div>

Ok, that’s resolved now. You were on the right path, that was a network configuration error. On the master coordinator, I had associated its hostname with 127.0.0.1 in `/etc/hosts`. Hence it was starting on the local interface and could not be contacted by the executor.

Thanks for your help!