# Can't get Rancher back up

**URL:** https://forums.suse.com/t/cant-get-rancher-back-up/7040
**Category:** Rancher 1.x
**Created:** [August 7, 2017, 1:34am UTC](https://forums.suse.com/t/cant-get-rancher-back-up/7040 "2017-08-07T01:34:42Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![palermomatt](https://avatars.discourse-cdn.com/v4/letter/p/8c91f0/32.png) [@palermomatt](https://forums.suse.com/u/palermomatt)
#### Post date: [August 7, 2017, 1:34am UTC](https://forums.suse.com/t/cant-get-rancher-back-up/7040/1 "2017-08-07T01:34:42Z")

</div>

i had Rancher previously installed and working. I setup a couple environments and some stacks inside them. then suddenly my Rancher access stopped working today, so i rebooted the server and couldn’t get it to come back up. I am using an external DB with the following command to run the server:

sudo docker run -d --restart=unless-stopped -p 8080:8080 rancher/server   
–db-host [myhost.example.com](http://myhost.example.com) --db-port 3306 --db-user username --db-pass password --db-name cattle

but the logs show its stuck at this:

2017-08-06 18:03:12,830 INFO [main] [ConsoleStatus] Starting DB migration  
2017-08-06 18:03:15,292 INFO [main] [ConsoleStatus] DB migration done  
2017-08-06 18:03:15,879 INFO [main] [ConsoleStatus] Cluster membership changed [127.0.0.1:9345]  
2017-08-06 18:03:15,881 INFO [main] [ConsoleStatus] Checking cluster state on start-up  
2017-08-06 18:03:15,881 INFO [main] [ConsoleStatus] Waiting to become master

it’s been there for several hours now and i’ve tried multiple times. any idea how to fix this?

---

<div class="post-metadata">

### Author: ![palermomatt](https://avatars.discourse-cdn.com/v4/letter/p/8c91f0/32.png) [@palermomatt](https://forums.suse.com/u/palermomatt)
#### Post date: [August 8, 2017, 5:21am UTC](https://forums.suse.com/t/cant-get-rancher-back-up/7040/2 "2017-08-08T05:21:59Z")

</div>

In case anyone runs into this, I was able to fix it by going into the external Rancher DB. It appears that when I was running the `docker run...` command, it was creating 2 records in the `cluster_membership` table. I just deleted the first record that it created, then it was able to finish getting up and running after that.

---

<div class="post-metadata">

### Author: ![scippio](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/scippio/32/2716_2.png) [@scippio](https://forums.suse.com/u/scippio)
#### Post date: [September 14, 2017, 11:42am UTC](https://forums.suse.com/t/cant-get-rancher-back-up/7040/3 "2017-09-14T11:42:15Z")

</div>

I have similiar problem now with rancher server 1.6.7. I have two servers connected HA with shared database. I started third now and this stopped on “INFO [main] [ConsoleStatus] Waiting to become master”. It does not matter how many more I run, all this new servers will stop at “Waiting to become master”.

---

<div class="post-metadata">

### Author: ![scippio](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/scippio/32/2716_2.png) [@scippio](https://forums.suse.com/u/scippio)
#### Post date: [September 14, 2017, 12:59pm UTC](https://forums.suse.com/t/cant-get-rancher-back-up/7040/4 "2017-09-14T12:59:55Z")

</div>

I found the problem with my setup:

I started servers via docker-compose and there:

This is good:

```
command: --db-host sqlserver --db-port 3306 --db-user root --db-pass abcd1234 --db-name rancher --advertise-address myserver1:9345 --advertise-http-port 443

```

This is bad:

```
 environment:
    - CATTLE_DB_CATTLE_MYSQL_HOST=sqlserver
    - CATTLE_DB_CATTLE_MYSQL_PORT=3306
    - CATTLE_DB_CATTLE_MYSQL_NAME=rancher
    - CATTLE_DB_CATTLE_USERNAME=root
    - CATTLE_DB_CATTLE_PASSWORD=abcd1234
    - CATTLE_CLUSTER_ADVERTISE_ADDRESS=myserver1:9345
    - CATTLE_CLUSTER_ADVERTISE_HTTP_PORT=443

```

!!
