Load Balancer stay in "Initializing" state

Archive Rancher 1.x
22

Problem still exists in 1.3.3, too. stderr of the loadbalancer container is:

1/25/2017 11:06:14 AMtime="2017-01-25T10:06:14Z" level=info msg="KUBERNETES_URL is not set, skipping init of kubernetes controller"
1/25/2017 11:06:14 AMtime="2017-01-25T10:06:14Z" level=info msg="Starting Rancher LB service"
1/25/2017 11:06:14 AMtime="2017-01-25T10:06:14Z" level=info msg="LB controller: rancher"
1/25/2017 11:06:14 AMtime="2017-01-25T10:06:14Z" level=info msg="LB provider: haproxy"
1/25/2017 11:06:14 AMtime="2017-01-25T10:06:14Z" level=info msg="starting rancher controller"
1/25/2017 11:06:14 AMtime="2017-01-25T10:06:14Z" level=info msg="Healthcheck handler is listening on :10241"
1/25/2017 11:06:15 AMtime="2017-01-25T10:06:15Z" level=info msg=" -- starting haproxy\n[ALERT] 024/100614 (28) : Starting frontend GLOBAL: cannot bind UNIX socket [/run/haproxy/admin.sock]\n"
1/25/2017 11:06:15 AMtime="2017-01-25T10:06:15Z" level=info msg=" -- reloading haproxy config with the new config changes\n[WARNING] 024/100615 (39) : config : 'option forwardfor' ignored for proxy 'default' as it requires HTTP mode.\n"