rancher: LoadBalancer stuck in "initializing"

Rancher Version: 1.1.2 Docker Version: 1.10.3

OS and where are the hosts located? (cloud, bare metal, etc): rancheros, kvm

Setup Details: (single node rancher vs. HA rancher, internal DB vs. external DB) no how, single node rancher server, single host, internal DB,

Environment Type: (Cattle/Kubernetes/Swarm/Mesos) cattle

Steps to Reproduce: Creating a load-balancer with port 443, ssl, add a certificate, add one destination in advanced mode

Results: Load balancer will stuck initialize


7/27/2016 2:47:08 AMINFO: Sending haproxy applied 3-d2f842d7d67d6531622dd524b6403ee66414b3b1264684299f4d5574ecaeb32a
7/27/2016 2:47:08 AMINFO: HOME -> ./
7/27/2016 2:47:08 AMINFO: HOME -> ./etc/
7/27/2016 2:47:08 AMINFO: HOME -> ./etc/cattle/
7/27/2016 2:47:08 AMINFO: HOME -> ./etc/cattle/startup-env
7/27/2016 2:47:08 AMINFO: ROOT -> ./
7/27/2016 2:47:08 AMINFO: ROOT -> ./etc/
7/27/2016 2:47:08 AMINFO: ROOT -> ./etc/init.d/
7/27/2016 2:47:08 AMINFO: ROOT -> ./etc/init.d/agent-instance-startup
7/27/2016 2:47:08 AMINFO: Sending agent-instance-startup applied 1-27397a5ab99f10ff81793e569df68fbbda1d8722fc47aa4014c98d9a1bc82958
7/27/2016 2:47:08 AMmonit: generated unique Monit id 21a546ad8a38aa962399ccf24172d1a4 and stored to '/var/lib/monit/id'
7/27/2016 2:47:08 AMStarting monit daemon with http interface at [localhost:2812]

Expected: Load balancer comes up. I had this load balancer up and running beforehand, i just remade it due to certificate processes, and the same settings do not work anymore.

A second, TCP only loadbalancer, comes up without issues.

I do neither think this is related to HA: https://github.com/rancher/rancher/issues/4634 nor probably related to https://github.com/rancher/rancher/issues/3462

About this issue

Original URL
State: closed
Created 8 years ago
Reactions: 1
Comments: 15 (2 by maintainers)

Most upvoted comments

Just tell me, if creating issue here is nonsense any. I can safe my time and you do not get flooded with things you do not care anyway about. Win-win, or lose lose, whatever you call it.

Please continue to file issues. We really do care and track all issues. We might not be immediate to respond. We will try to improve here. You have to understand the complexity of supporting a tool like this in an open source capacity. A tool like this has huge amount of permutations and there are a lot of moving parts.

One thing you can do is add log keyword to the globals section of haproxy. http://cbonte.github.io/haproxy-dconv/configuration-1.6.html#3-log The downside of that is that you have to setup a rsyslog server to accept the syslog.

ibuildthecloud on Jul 28, 2016