tripleo

  1. Bug #1352924
  2. Comment #2

Comment 2 for bug 1352924

Revision history for this message
Michael Kerrin (michael-kerrin-w) wrote :

This is still an issue

From os-collect-config.log on controller0 in the 3 node controller setup

Nov 7 15:52:57 overcloud-controller0-uxaia6rkgy4e os-collect-config: dib-run-parts Fri Nov 7 15:52:57 UTC 2014 Running /opt/stack/os-config-refresh/configure.d/21-haproxy
Nov 7 15:52:57 overcloud-controller0-uxaia6rkgy4e os-collect-config: + os-svc-enable -n haproxy
Nov 7 15:52:57 overcloud-controller0-uxaia6rkgy4e os-collect-config: System start/stop links for /etc/init.d/haproxy already exist.
Nov 7 15:52:57 overcloud-controller0-uxaia6rkgy4e os-collect-config: + service haproxy status
Nov 7 15:52:57 overcloud-controller0-uxaia6rkgy4e os-collect-config: haproxy is running.
Nov 7 15:52:57 overcloud-controller0-uxaia6rkgy4e os-collect-config: + service haproxy reload
Nov 7 15:52:57 overcloud-controller0-uxaia6rkgy4e os-collect-config: * Reloading haproxy haproxy
Nov 7 15:52:57 overcloud-controller0-uxaia6rkgy4e os-collect-config: [WARNING] 310/155257 (27153) : config : log format ignored for proxy 'keystone_admin' since it has no log address.
Nov 7 15:52:57 overcloud-controller0-uxaia6rkgy4e os-collect-config: [WARNING] 310/155257 (27153) : config : log format ignored for proxy 'keystone_public' since it has no log address.
Nov 7 15:52:57 overcloud-controller0-uxaia6rkgy4e os-collect-config: [WARNING] 310/155257 (27153) : config : log format ignored for proxy 'horizon' since it has no log address.
Nov 7 15:52:57 overcloud-controller0-uxaia6rkgy4e os-collect-config: [WARNING] 310/155257 (27153) : config : log format ignored for proxy 'neutron' since it has no log address.
Nov 7 15:52:57 overcloud-controller0-uxaia6rkgy4e os-collect-config: [WARNING] 310/155257 (27153) : config : log format ignored for proxy 'cinder' since it has no log address.
Nov 7 15:52:57 overcloud-controller0-uxaia6rkgy4e os-collect-config: [WARNING] 310/155257 (27153) : config : log format ignored for proxy 'glance_api' since it has no log address.
Nov 7 15:52:57 overcloud-controller0-uxaia6rkgy4e os-collect-config: [WARNING] 310/155257 (27153) : config : log format ignored for proxy 'glance_registry' since it has no log address.
Nov 7 15:52:57 overcloud-controller0-uxaia6rkgy4e os-collect-config: [WARNING] 310/155257 (27153) : config : log format ignored for proxy 'heat_api' since it has no log address.
Nov 7 15:52:57 overcloud-controller0-uxaia6rkgy4e os-collect-config: [WARNING] 310/155257 (27153) : config : log format ignored for proxy 'heat_cloudwatch' since it has no log address.
Nov 7 15:52:57 overcloud-controller0-uxaia6rkgy4e os-collect-config: [WARNING] 310/155257 (27153) : config : log format ignored for proxy 'heat_cfn' since it has no log address.
Nov 7 15:52:57 overcloud-controller0-uxaia6rkgy4e os-collect-config: [WARNING] 310/155257 (27153) : config : missing timeouts for proxy 'mysql'.
Nov 7 15:52:57 overcloud-controller0-uxaia6rkgy4e os-collect-config: | While not properly invalid, you will certainly encounter various problems
Nov 7 15:52:57 overcloud-controller0-uxaia6rkgy4e os-collect-config: | with such a configuration. To fix this, please ensure that all following
Nov 7 15:52:57 overcloud-controller0-uxaia6rkgy4e os-collect-config: | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
Nov 7 15:52:57 overcloud-controller0-uxaia6rkgy4e os-collect-config: [WARNING] 310/155257 (27153) : config : log format ignored for proxy 'mysql' since it has no log address.
Nov 7 15:52:57 overcloud-controller0-uxaia6rkgy4e os-collect-config: [WARNING] 310/155257 (27153) : config : log format ignored for proxy 'nova_ec2' since it has no log address.
Nov 7 15:52:57 overcloud-controller0-uxaia6rkgy4e os-collect-config: [WARNING] 310/155257 (27153) : config : log format ignored for proxy 'nova_osapi' since it has no log address.
Nov 7 15:52:57 overcloud-controller0-uxaia6rkgy4e os-collect-config: [WARNING] 310/155257 (27153) : config : log format ignored for proxy 'nova_metadata' since it has no log address.
Nov 7 15:52:57 overcloud-controller0-uxaia6rkgy4e os-collect-config: [WARNING] 310/155257 (27153) : config : log format ignored for proxy 'nova_novncproxy' since it has no log address.
Nov 7 15:52:57 overcloud-controller0-uxaia6rkgy4e os-collect-config: [WARNING] 310/155257 (27153) : config : log format ignored for proxy 'ceilometer' since it has no log address.
Nov 7 15:52:57 overcloud-controller0-uxaia6rkgy4e os-collect-config: [WARNING] 310/155257 (27153) : config : log format ignored for proxy 'swift_proxy_server' since it has no log address.
Nov 7 15:52:57 overcloud-controller0-uxaia6rkgy4e os-collect-config: [WARNING] 310/155257 (27153) : config : missing timeouts for proxy 'rabbitmq'.
Nov 7 15:52:57 overcloud-controller0-uxaia6rkgy4e os-collect-config: | While not properly invalid, you will certainly encounter various problems
Nov 7 15:52:57 overcloud-controller0-uxaia6rkgy4e os-collect-config: | with such a configuration. To fix this, please ensure that all following
Nov 7 15:52:57 overcloud-controller0-uxaia6rkgy4e os-collect-config: | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
Nov 7 15:52:57 overcloud-controller0-uxaia6rkgy4e os-collect-config: [WARNING] 310/155257 (27153) : config : log format ignored for proxy 'rabbitmq' since it has no log address.
Nov 7 15:52:57 overcloud-controller0-uxaia6rkgy4e os-collect-config: [WARNING] 310/155257 (27153) : config : log format ignored for proxy 'haproxy.stats' since it has no log address.
Nov 7 15:53:00 overcloud-controller0-uxaia6rkgy4e os-collect-config: [ALERT] 310/155257 (27153) : Starting proxy horizon: cannot bind socket
Nov 7 15:53:00 overcloud-controller0-uxaia6rkgy4e os-collect-config: [ALERT] 310/155257 (27153) : Starting proxy horizon: cannot bind socket
Nov 7 15:53:00 overcloud-controller0-uxaia6rkgy4e os-collect-config: ...fail!
Nov 7 15:53:00 overcloud-controller0-uxaia6rkgy4e os-collect-config: [2014-11-07 15:53:00,041] (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 7 15:53:00 overcloud-controller0-uxaia6rkgy4e os-collect-config:
Nov 7 15:53:00 overcloud-controller0-uxaia6rkgy4e 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 7 15:53:00 overcloud-controller0-uxaia6rkgy4e os-collect-config:
Nov 7 15:53:00 overcloud-controller0-uxaia6rkgy4e os-collect-config: [2014-11-07 15:53:00,041] (os-refresh-config) [ERROR] Aborting...

And I can see the following

root@overcloud-controller0-uxaia6rkgy4e:/var/log# netstat -ltnp 80
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:11211 0.0.0.0:* LISTEN 1847/memcached
tcp 0 0 0.0.0.0:53 0.0.0.0:* LISTEN 1716/dnsmasq
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 1692/sshd
tcp 0 0 0.0.0.0:3260 0.0.0.0:* LISTEN 1676/tgtd
tcp 0 0 0.0.0.0:1993 0.0.0.0:* LISTEN 2844/haproxy
tcp6 0 0 :::80 :::* LISTEN 3518/apache2
tcp6 0 0 :::53 :::* LISTEN 1716/dnsmasq
tcp6 0 0 :::22 :::* LISTEN 1692/sshd
tcp6 0 0 :::3260 :::* LISTEN 1676/tgtd