tripleo

haproxy start failed loop with 'Starting proxy horizon: cannot bind socket'

Bug #1393643 reported by jiangfei on 2014-11-18

This bug report is a duplicate of: Bug #1352924: apache2 can be start of sysv script before o-r-c configures it blocking the o-r-c run. Edit Remove

This bug affects 2 people

Affects		Status	Importance	Assigned to	Milestone
	tripleo	Confirmed	High	jiangfei

Bug Description

deploy the HA overcloud in ubuntu 12.04, 3 controller node, 2 computer node.

there one controller node haproxy start failed with "". I found the error message in /var/log/os-collect-config.log like this:

Nov 17 11:31:45 overcloud-controller2-rnw2wnqycd7h os-collect-config: dib-run-parts Mon Nov 17 11:31:45 UTC 2014 Running /opt/stack/os-config-refresh/configure.d/21-haproxy
Nov 17 11:31:45 overcloud-controller2-rnw2wnqycd7h os-collect-config: + os-svc-enable -n haproxy
Nov 17 11:31:45 overcloud-controller2-rnw2wnqycd7h os-collect-config: System start/stop links for /etc/init.d/haproxy already exist.
Nov 17 11:31:45 overcloud-controller2-rnw2wnqycd7h os-collect-config: + service haproxy status
Nov 17 11:31:45 overcloud-controller2-rnw2wnqycd7h os-collect-config: haproxy is running.
Nov 17 11:31:45 overcloud-controller2-rnw2wnqycd7h os-collect-config: + service haproxy reload
Nov 17 11:31:45 overcloud-controller2-rnw2wnqycd7h os-collect-config: * Reloading haproxy haproxy
Nov 17 11:31:45 overcloud-controller2-rnw2wnqycd7h os-collect-config: [WARNING] 320/113145 (3810) : config : log format ignored for proxy 'keystone_admin' since it has no log address.
Nov 17 11:31:45 overcloud-controller2-rnw2wnqycd7h os-collect-config: [WARNING] 320/113145 (3810) : config : log format ignored for proxy 'keystone_public' since it has no log address.
Nov 17 11:31:45 overcloud-controller2-rnw2wnqycd7h os-collect-config: [WARNING] 320/113145 (3810) : config : log format ignored for proxy 'horizon' since it has no log address.
Nov 17 11:31:45 overcloud-controller2-rnw2wnqycd7h os-collect-config: [WARNING] 320/113145 (3810) : config : log format ignored for proxy 'neutron' since it has no log address.
Nov 17 11:31:45 overcloud-controller2-rnw2wnqycd7h os-collect-config: [WARNING] 320/113145 (3810) : config : log format ignored for proxy 'cinder' since it has no log address.
Nov 17 11:31:45 overcloud-controller2-rnw2wnqycd7h os-collect-config: [WARNING] 320/113145 (3810) : config : log format ignored for proxy 'glance_api' since it has no log address.
Nov 17 11:31:45 overcloud-controller2-rnw2wnqycd7h os-collect-config: [WARNING] 320/113145 (3810) : config : log format ignored for proxy 'glance_registry' since it has no log address.
Nov 17 11:31:45 overcloud-controller2-rnw2wnqycd7h os-collect-config: [WARNING] 320/113145 (3810) : config : log format ignored for proxy 'heat_api' since it has no log address.
Nov 17 11:31:45 overcloud-controller2-rnw2wnqycd7h os-collect-config: [WARNING] 320/113145 (3810) : config : log format ignored for proxy 'heat_cloudwatch' since it has no log address.
Nov 17 11:31:45 overcloud-controller2-rnw2wnqycd7h os-collect-config: [WARNING] 320/113145 (3810) : config : log format ignored for proxy 'heat_cfn' since it has no log address.
Nov 17 11:31:45 overcloud-controller2-rnw2wnqycd7h os-collect-config: [WARNING] 320/113145 (3810) : config : missing timeouts for proxy 'mysql'.
Nov 17 11:31:45 overcloud-controller2-rnw2wnqycd7h os-collect-config: | While not properly invalid, you will certainly encounter various problems
Nov 17 11:31:45 overcloud-controller2-rnw2wnqycd7h os-collect-config: | with such a configuration. To fix this, please ensure that all following
Nov 17 11:31:45 overcloud-controller2-rnw2wnqycd7h os-collect-config: | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
Nov 17 11:31:45 overcloud-controller2-rnw2wnqycd7h os-collect-config: [WARNING] 320/113145 (3810) : config : log format ignored for proxy 'mysql' since it has no log address.
Nov 17 11:31:45 overcloud-controller2-rnw2wnqycd7h os-collect-config: [WARNING] 320/113145 (3810) : config : log format ignored for proxy 'nova_ec2' since it has no log address.
Nov 17 11:31:45 overcloud-controller2-rnw2wnqycd7h os-collect-config: [WARNING] 320/113145 (3810) : config : log format ignored for proxy 'nova_osapi' since it has no log address.
Nov 17 11:31:45 overcloud-controller2-rnw2wnqycd7h os-collect-config: [WARNING] 320/113145 (3810) : config : log format ignored for proxy 'nova_metadata' since it has no log address.
Nov 17 11:31:45 overcloud-controller2-rnw2wnqycd7h os-collect-config: [WARNING] 320/113145 (3810) : config : log format ignored for proxy 'nova_novncproxy' since it has no log address.
Nov 17 11:31:45 overcloud-controller2-rnw2wnqycd7h os-collect-config: [WARNING] 320/113145 (3810) : config : log format ignored for proxy 'ceilometer' since it has no log address.
Nov 17 11:31:45 overcloud-controller2-rnw2wnqycd7h os-collect-config: [WARNING] 320/113145 (3810) : config : log format ignored for proxy 'swift_proxy_server' since it has no log address.
Nov 17 11:31:45 overcloud-controller2-rnw2wnqycd7h os-collect-config: [WARNING] 320/113145 (3810) : config : missing timeouts for proxy 'rabbitmq'.
Nov 17 11:31:45 overcloud-controller2-rnw2wnqycd7h os-collect-config: | While not properly invalid, you will certainly encounter various problems
Nov 17 11:31:45 overcloud-controller2-rnw2wnqycd7h os-collect-config: | with such a configuration. To fix this, please ensure that all following
Nov 17 11:31:45 overcloud-controller2-rnw2wnqycd7h os-collect-config: | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
Nov 17 11:31:45 overcloud-controller2-rnw2wnqycd7h os-collect-config: [WARNING] 320/113145 (3810) : config : log format ignored for proxy 'rabbitmq' since it has no log address.
Nov 17 11:31:45 overcloud-controller2-rnw2wnqycd7h os-collect-config: [WARNING] 320/113145 (3810) : config : log format ignored for proxy 'haproxy.stats' since it has no log address.
Nov 17 11:31:47 overcloud-controller2-rnw2wnqycd7h os-collect-config: [ALERT] 320/113145 (3810) : Starting proxy horizon: cannot bind socket
Nov 17 11:31:47 overcloud-controller2-rnw2wnqycd7h os-collect-config: [ALERT] 320/113145 (3810) : Starting proxy horizon: cannot bind socket
Nov 17 11:31:47 overcloud-controller2-rnw2wnqycd7h os-collect-config: ...fail!
Nov 17 11:31:47 overcloud-controller2-rnw2wnqycd7h os-collect-config: [2014-11-17 11:31:47,491] (os-refresh-config) [ERROR] during configure phase. [Command '['dib-run-parts', '/opt/stack/os-config-refresh/configure.d']' returned non-zero exit status 2]
Nov 17 11:31:47 overcloud-controller2-rnw2wnqycd7h os-collect-config:
Nov 17 11:31:47 overcloud-controller2-rnw2wnqycd7h os-collect-config: ERROR:os-refresh-config:during configure phase. [Command '['dib-run-parts', '/opt/stack/os-config-refresh/configure.d']' returned
non-zero exit status 2]
Nov 17 11:31:47 overcloud-controller2-rnw2wnqycd7h os-collect-config:
Nov 17 11:31:47 overcloud-controller2-rnw2wnqycd7h os-collect-config: [2014-11-17 11:31:47,491] (os-refresh-config) [ERROR] Aborting...
Nov 17 11:31:47 overcloud-controller2-rnw2wnqycd7h os-collect-config: ERROR:os-refresh-config:Aborting...
Nov 17 11:31:47 overcloud-controller2-rnw2wnqycd7h os-collect-config: 2014-11-17 11:31:47.496 1392 ERROR os-collect-config [-] Command failed, will not cache new data. Command 'os-refresh-config' ret
urned non-zero exit status 1

root@overcloud-controller2-rnw2wnqycd7h:~# netstat -lnp |grep 80
tcp6 0 0 :::80 :::* LISTEN 2936/apache2
udp6 0 0 fe80::235:32ff:fedd:123 :::* 1145/ntpd
unix 2 [ ACC ] STREAM LISTENING 9512 801/ovs-vswitchd /var/run/openvswitch/ovs-vswitchd.801.ctl
root@overcloud-controller2-rnw2wnqycd7h:~#

haproxy start depend on apache2, i think we should stop the apache2 before start the haproxy.