From: Yipei Niu [mailto:newy...@gmail.com]
Sent: Monday, June 26, 2017 11:34 PM
To: OpenStack Development Mailing List (not for usage questions)
<openstack-dev@lists.openstack.org>
Subject: Re: [openstack-dev] [octavia] fail to plug vip to amphora
Hi, Micheal,
Thanks a lot for you
Hi, Ganpat,
Thanks a lot for your comments. I do not really understand your solution.
Do you mean I need to create a dummy file and verify it in the amphora?
Best regards,
Yipei
__
OpenStack Development Mailing List (not for
Hello Yipei,
"*octavia.amphorae.backends.agent.api_server.listener [-] Failed to verify
haproxy file: Command '['haproxy', '-c', '-L', 'NK20KVuD6oi5NrRP7KOVflM*
*3MsQ', '-f',
'/var/lib/octavia/bca2c985-471a-4477-8217-92fa71d04cb7/haproxy.cfg.new']'
returned non-zero exit status 1*"
Verification
Hi, Michael,
Thanks for your help. I have already created a load balancer successfully,
but failed creating a listener. The detailed errors of amphora-agent and
syslog in the amphora are as follows.
In amphora-agent.log:
[2017-06-28 08:54:12 +] [1209] [INFO] Starting gunicorn 19.7.0
Hi, Micheal,
Thanks a lot for your help, but I still have one question.
In Octavia, once the controller worker fails plugging VIP to the amphora,
the amphora is deleted immediately, making it impossible to trace the
error. How to prevent Octavia from stopping and deleting the amphora?
Best
Hello Yipei,
You are on the track to debug this.
When you are logged into the amphora, please check the following logs to see
what the amphora-agent error is:
/var/log/amphora-agent.log
And
/var/log/syslog
One of those two logs will have the error information.
Michael
