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:
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?
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.
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”.