Hi,
Recently I am working on LBaaS service. When I set up a pool and it serves,
the haproxy process randomly returns 503:
503 Service Unavailabe
No server is available to handle this request
This could be easily reproduced and I am pretty sure when this happened,
member servers are up.
Meanwhile, I ran another haproxy process, started with CentOS init script.
And the problem never showed. I replaced /etc/haproxy/haproxy.cfg with
.../lbaas/{poo_id}/conf file (change stat socket path and group) and it
still OK.
So, I checked init script and LBaaS-agent code, found there is a "-D"
argument in the init script when creating Haproxy process. I killed haproxy
process for the pool, and restart it with one more "-D" argument in pool's
namespace, and the problem finally gone.
I don't know much about Haproxy, how could this "-D" argument make such
difference (since there "deamon" options in the configuration file) ?
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
