Comment 7 for bug 1485644
Revision history for this message
| Aleksandr Didenko (adidenko) wrote Re: Keystone wsgi might run out of connections limits for the apache proces | #7 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
7020100
(Get the code!)
This is what I get when I use all the avail Apache sockets and it can't accept new connections:
keystone-1 keystone-1/<NOSRV> 0/-1/-1/-1/0 503 212 - - SC-- 0/0/0/0/0 0/0 "GET /v3/endpoints HTTP/1.1"
This is what I get when I turn Apache off completely:
keystone-1 keystone-1/<NOSRV> 0/-1/-1/-1/0 503 212 - - SC-- 0/0/0/0/0 0/0 "GET /v3/endpoints HTTP/1.1"
This is what I get when I turn Apache back on, but it's still in "Status: DOWN 5/150" status (raising UP from DOWN for 5 minutes):
keystone-1 keystone-1/<NOSRV> 0/-1/-1/-1/0 503 212 - - SC-- 0/0/0/0/0 0/0 "GET /v3/endpoints HTTP/1.1"
As you can see, there's no difference, we're getting those messages in haproxy.log when keystone backend is down. So I don't think that TCP or Apache limits are the problem here. I'm pretty sure, that https:/
So I'm marking this bug as duplicate of 1472675