Comment 23 for bug 1701426
Revision history for this message
| Sundaresan Rajangam (srajanga) wrote | #23 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
From the logs #20, I could see query for /analytics/
During this period, I analytics-api was not not able to connect to the redis @ 172.23.10.194
The following Exception was continuously logged in the contrail-
09/15/2017 01:14:18 PM [contrail-
(u'Error 99 connecting 172.23.10.194:6379. Cannot assign requested address.',) : traceback Traceback (most recent call last):
File "/usr/lib/
tfilter, ackfilter, False)
File "/usr/lib/
pperes = ppe.execute()
File "/usr/lib/
return execute(conn, stack, raise_on_error)
File "/usr/lib/
connection.
File "/usr/lib/
self.connect()
File "/usr/lib/
raise ConnectionError
ConnectionError: Error 99 connecting 172.23.10.194:6379. Cannot assign requested address.
So, either there was some connectivity issue to 172.23.10.194 or redis server couldn't accept new connections due to max client connections reached. I had seen the latter case when haproxy continuously connects to redis. Can you please check if the following line is present in haproxy config? If so, please remove this line and restart haproxy and redis service - https:/
tcp-check connect port 6379
openc52-
-------
bash-3.2$ grep -r "virtual-
log/contrail/
log/contrail/
log/contrail/
log/contrail/
log/contrail/
log/contrail/
openc15-
-------
bash-3.2$ grep -r "virtual-
log/contrail/
log/contrail/
log/contrail/
log/contrail/
log/contrail/
log/contrail/
log/contrail/
openc51-
-------
bash-3.2$ grep -r "virtual-
log/contrail/
log/contrail/
log/contrail/
log/contrail/
log/contrail/
log/contrail/
log/contrail/
log/contrail/