rancher: Unable to access Rancher UI after a reboot.

I’m on Ubuntu 14.04.2 LTS

I did docker run -d --restart=always -p 8080:8080 rancher/server

I was able to connect to Rancher UI with my server public IP. http://PUBLIC_IP:8080 Then if I reboot the server, I get an ERR_CONNECTION_TIMED_OUT.

I have a VPN installed, and the UI is still responding on the container IP. http://172.17.0.10:8080/

I tried again with docker run -d --restart=always -p 8090:8080 rancher/server, same thing happened.

docker ps

CONTAINER ID        IMAGE                           COMMAND                CREATED             STATUS              PORTS                                          NAMES
ec7bdcc144ac        rancher/server                  "/usr/bin/s6-svscan    24 minutes ago      Up 15 minutes       3306/tcp, 0.0.0.0:8090->8080/tcp               loving_wright
de3a8ef8cb23        rancher/agent-instance:v0.3.1   "/etc/init.d/agent-i   About an hour ago   Up 34 minutes       0.0.0.0:500->500/udp, 0.0.0.0:4500->4500/udp   acbc14ec-de64-4b8c-8fd8-3d2a8de39714
944718a36aa4        rancher/agent:v0.7.11           "/run.sh run"          About an hour ago   Up 36 minutes                                                      rancher-agent
5e8e126e9219        rancher/server                  "/usr/bin/s6-svscan    About an hour ago   Up 36 minutes       3306/tcp, 0.0.0.0:8080->8080/tcp               dreamy_morse

dockers logs 5e8e126e9219

15:46:07.513 [main] INFO  ConsoleStatus - [DONE ] [95213ms] Startup Succeeded, Listening on port 8081
time="2015-07-31T15:46:09Z" level=info msg="Starting websocket proxy. Listening on [:8080], Proxying to cattle API at [localhost:8081], Monitoring parent pid [7]."
time="2015-07-31T15:46:09Z" level=info msg="Setting log level" logLevel=info
time="2015-07-31T15:46:09Z" level=info msg="Starting go-machine-service..." gitcommit=102d311
time="2015-07-31T15:46:10Z" level=info msg="Initializing event router" workerCount=10
time="2015-07-31T15:46:12Z" level=info msg="Connection established"
2015-07-31 15:46:16,730 ERROR [:] [] [] [] [ecutorService-5] [i.c.p.a.s.ping.impl.PingMonitorImpl ] Failed to get ping from agent [1] count [1]
2015-07-31 15:46:21,718 ERROR [:] [] [] [] [ecutorService-2] [i.c.p.a.s.ping.impl.PingMonitorImpl ] Failed to get ping from agent [1] count [2]
time="2015-07-31T15:46:25Z" level=info msg="Registering backend for host [d448658b-823a-4fc2-a654-93a35283d7d0]"
2015-07-31 15:46:26,806 ERROR [:] [] [] [] [ecutorService-9] [i.c.p.a.s.ping.impl.PingMonitorImpl ] Failed to get ping from agent [1] count [1]

About this issue

  • Original URL
  • State: closed
  • Created 9 years ago
  • Comments: 50 (2 by maintainers)

Most upvoted comments

reproduced this in rancher 1.4.1:

deploy several stacks with port maps and load balancers

systemctl restart docker

rancher resets connection, load balancers and stacks continue to work and are accessible

workaround:

sudo iptables -F CATTLE_PREROUTING -t nat systemctl restart docker