On Tue, Jan 08, 2019 at 11:40:21AM +0000, Milosz Wasilewski wrote:
On Tue, 8 Jan 2019 at 11:21, suker suker@nexell.co.kr wrote:
Dear Milosz
I am sorry for repeated questions. Your answers are helpful in a variety of ways.
I went back to the beginning. To build a squad system, use 'git clone https://github.com/Linaro/squad'
I received a clone of github's squad. I modified the dev-docker slightly to suit my server environment.
could you list your changes here?
Using submit_for_testing.py as in the configuration at https://ci.linaro.org submit. Is there anything wrong with what I've done so far?
No, looks OK. However if you didn't add it to dockerfile you're only running frontend at this point. Which means...
I have additional questions. Should I use https protocol instead of http protocol? I traced at the source level using pdb, Eventually there will not get out of the loop at
/usr/local/lib/python3.5/dist-packages/kombu/utils/functional.py(341) retry_over_time()
And it appears to be connection refused (*** ConnectionRefusedError: [Errno 111] Connection refused) at
/usr/local/lib/python3.5/dist-packages/kombu/connection.py
... you're not able to connect to the message queue and workers. This is what this error is about. In our production instance we're using RabbitMQ as message queue. If you plan to use sth else you'll need to modify squad settings as well.
So to recover you need to make sure you're running:
- squad frontend
- squad worker (celery)
- rabbitmq
- squad listener (optional, but required for prompt result retrieval from LAVA)
I hope this helps.
In particular, the `dev-docker` script is intended at ... development, as the name implies. For production usage, I would recommend using the "Installation Instructions for production environments" section of the documentation.