# Replacing old master node and dremio UI will not start

**URL:** <https://community.dremio.com/t/replacing-old-master-node-and-dremio-ui-will-not-start/2430>\
**Category:** Uncategorized\
**Created:** [December 14, 2018, 1:41pm UTC](https://community.dremio.com/t/replacing-old-master-node-and-dremio-ui-will-not-start/2430 "2018-12-14T13:41:23Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![seth.wilhoite](https://avatars.discourse-cdn.com/v4/letter/s/ed8c4c/32.png) [@seth.wilhoite](https://community.dremio.com/u/seth.wilhoite)\
**Post date:** [December 14, 2018, 1:41pm UTC](https://community.dremio.com/t/replacing-old-master-node-and-dremio-ui-will-not-start/2430/1 "2018-12-14T13:41:23Z")

</div>

I am replacing an old master node that was used for testing with a bigger server to be the new master node fro Dremio. The issue that I am running into now is that I can’t get dremio start up. The last few lines in server.log that I am receiving is:  
2018-12-14 08:18:07,281 [main] INFO c.d.s.coordinator.zk.ZKClusterClient - Starting ZKClusterClient  
2018-12-14 08:18:07,309 [Curator-ConnectionStateManager-0] INFO c.d.s.coordinator.zk.ZKClusterClient - ZK connection state changed to CONNECTED  
2018-12-14 08:18:07,443 [main] INFO c.d.s.c.zk.ZKClusterCoordinator - ZKClusterCoordination is up  
2018-12-14 08:18:07,443 [main] INFO c.d.d.s.exec.MasterElectionService - Starting MasterElectionService  
2018-12-14 08:18:12,450 [main] INFO c.d.d.s.exec.MasterElectionService - Waiting until being elected as master node

What am I missing? I stopped the old dremio instance and cleaned out the hdfs directory that dremio was using.

---

<div class="post-metadata">

**Author:** ![seth.wilhoite](https://avatars.discourse-cdn.com/v4/letter/s/ed8c4c/32.png) [@seth.wilhoite](https://community.dremio.com/u/seth.wilhoite)\
**Post date:** [December 14, 2018, 2:02pm UTC](https://community.dremio.com/t/replacing-old-master-node-and-dremio-ui-will-not-start/2430/2 "2018-12-14T14:02:40Z")

</div>

I found that even though I removed all files on the old server and stopped Dremio service, there was a pid still running for dremio (ps -ef | grep dremio). Once I killed that pid, my new instance successfully runs after a restart.

---

<div class="post-metadata">

**Author:** ![balaji.ramaswamy](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/balaji.ramaswamy/32/843_2.png) [@balaji.ramaswamy](https://community.dremio.com/u/balaji.ramaswamy)\
**Post date:** [December 17, 2018, 2:23pm UTC](https://community.dremio.com/t/replacing-old-master-node-and-dremio-ui-will-not-start/2430/3 "2018-12-17T14:23:44Z")

</div>

Hi @seth.wilhoite,

Glad you figured it out. Always after a start or stop, good idea to do a `ps -ef | grep dremio` to make sure the previous instance is down

Thanks  
@balaji.ramaswamy

---

<div class="post-metadata">

**Author:** ![anthony](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/anthony/32/670_2.png) [@anthony](https://community.dremio.com/u/anthony)\
**Post date:** [December 17, 2018, 2:27pm UTC](https://community.dremio.com/t/replacing-old-master-node-and-dremio-ui-will-not-start/2430/4 "2018-12-17T14:27:22Z")

</div>

Another option (only if you are using an external ZK) is you can specify a new path - [https://docs.dremio.com/advanced-administration/zookeeper.html#multiple-dremio-clusters-using-a-single-zookeeper-cluster](https://docs.dremio.com/advanced-administration/zookeeper.html#multiple-dremio-clusters-using-a-single-zookeeper-cluster)