Juju Charms Collection
cinder package

  1. Bug #1403616
  2. Comment #4

Comment 4 for bug 1403616

Revision history for this message
Billy Olsen (billy-olsen) wrote : Re: not binding to tcp 8776 on precise

Nope, it appears that haproxy reliably fails to start:

2014-12-17 20:33:01 INFO config-changed * Starting haproxy haproxy
2014-12-17 20:33:01 INFO config-changed [ALERT] 350/203301 (10867) : Starting frontend tcp-in_cinder_api: cannot bind socket
2014-12-17 20:33:01 INFO config-changed ...fail!
2014-12-17 20:33:01 INFO config-changed * Starting web server apache2
2014-12-17 20:33:01 INFO config-changed ...done.

2014-12-17 20:35:49 INFO shared-db-relation-changed * Restarting haproxy haproxy
2014-12-17 20:35:49 INFO shared-db-relation-changed [ALERT] 350/203549 (12158) : Starting frontend tcp-in_cinder_api: cannot bind socket
2014-12-17 20:35:49 INFO shared-db-relation-changed ...fail!

2014-12-17 20:36:07 INFO amqp-relation-changed * Restarting haproxy haproxy
2014-12-17 20:36:07 INFO amqp-relation-changed [ALERT] 350/203607 (13617) : Starting frontend tcp-in_cinder_api: cannot bind socket
2014-12-17 20:36:07 INFO amqp-relation-changed ...fail!

2014-12-17 20:37:35 INFO storage-backend-relation-changed * Restarting haproxy haproxy
2014-12-17 20:37:35 INFO storage-backend-relation-changed [ALERT] 350/203735 (15720) : Starting frontend tcp-in_cinder_api: cannot bind socket
2014-12-17 20:37:35 INFO storage-backend-relation-changed ...fail!

2014-12-17 20:37:42 INFO identity-service-relation-changed * Restarting haproxy haproxy
2014-12-17 20:37:42 INFO identity-service-relation-changed [ALERT] 350/203742 (16379) : Starting frontend tcp-in_cinder_api: cannot bind socket
2014-12-17 20:37:42 INFO identity-service-relation-changed ...fail!