onap-discuss@lists.onap.org | Included AWX service not working

Home Messages Hashtags Subgroups

Topics

Date Date 1 - 3 of 3

Included AWX service not working
#kubernetes #nodeport #elalto

jas.dhillon@... #20654 Hello, The `awx-service` (running at port 30478) results in connection-refused. It seems like the actual `awx_task` process is running on port 8050, but the k8s-service is created on port 8052: --- apiVersion: v1 kind: Service metadata: labels: app: awx chart: awx-5.0.0 heritage: Tiller release: onap-contrib name: awx-web namespace: onap spec: ports: - name: web nodePort: 30478 port: 80 protocol: TCP targetPort: 8052 selector: app: onap-contrib-awx release: onap-contrib type: NodePort --- And inside the awx-pod: --- bash-4.4$ ps -aux USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND awx 1 0.0 0.0 4412 804 ? Ss Apr08 0:20 /tini -- /bin/sh -c /usr/bin/launch_awx.sh awx 6 0.0 0.0 38076 5060 ? S Apr08 0:00 bash /usr/bin/launch_awx.sh awx 119 0.0 0.0 106740 25376 ? S Apr08 3:49 /usr/bin/python3.6 /usr/local/bin/supervisord -c /supervisor.conf awx 122 0.0 0.0 83664 18732 ? S Apr08 0:08 python3 /usr/bin/config-watcher awx 124 0.0 0.0 47544 12812 ? S Apr08 0:34 /var/lib/awx/venv/awx/bin/uwsgi --socket 127.0.0.1:8050 --module=awx.wsgi:application --vacuum --processes=5 - awx 125 0.0 0.0 294732 113964 ? S Apr08 6:48 /var/lib/awx/venv/awx/bin/python3 /var/lib/awx/venv/awx/bin/daphne -b 127.0.0.1 -p 8051 --websocket_timeout -1 awx 126 0.0 0.0 299184 113152 ? S Apr08 0:04 /var/lib/awx/venv/awx/bin/uwsgi --socket 127.0.0.1:8050 --module=awx.wsgi:application --vacuum --processes=5 - awx 127 0.0 0.0 299184 113152 ? S Apr08 0:04 /var/lib/awx/venv/awx/bin/uwsgi --socket 127.0.0.1:8050 --module=awx.wsgi:application --vacuum --processes=5 - awx 128 0.0 0.0 299184 113152 ? S Apr08 0:04 /var/lib/awx/venv/awx/bin/uwsgi --socket 127.0.0.1:8050 --module=awx.wsgi:application --vacuum --processes=5 - awx 129 0.0 0.0 299184 113148 ? S Apr08 0:03 /var/lib/awx/venv/awx/bin/uwsgi --socket 127.0.0.1:8050 --module=awx.wsgi:application --vacuum --processes=5 - awx 130 0.0 0.0 299184 113148 ? S Apr08 0:04 /var/lib/awx/venv/awx/bin/uwsgi --socket 127.0.0.1:8050 --module=awx.wsgi:application --vacuum --processes=5 - awx 198 0.3 0.0 15680 4436 pts/0 Ss 15:42 0:00 bash awx 204 0.0 0.0 49348 3880 pts/0 R+ 15:43 0:00 ps -aux --- However, even after changing service to point to 8052, the `connection refused` issue persists. When running curl inside container on port 8050, it seems to respond fine though. Will appreciate any ideas about this. The deployment is ElAlto.
More All Messages By This Member
Sylvain Desbureaux #20684 Hello, I took a look on a master: nginx: [emerg] bind() to 0.0.0.0:80 failed (13: Permission denied) 2020-04-16 05:37:44,301 INFO exited: nginx (exit status 1; not expected) 2020-04-16 05:37:45,303 INFO gave up: nginx entered FATAL state, too many start retries too quickly RESULT 2 so it cannot work as it's done :-/ you can fill a Jira (on OOM project) but the best would be to propose a contribution to solve it :( De : onap-discuss@... [onap-discuss@...] de la part de jas.dhillon@... [jas.dhillon@...] Envoyé : mardi 14 avril 2020 18:04 À : onap-discuss@... Objet : [onap-discuss] Included AWX service not working #kubernetes #elalto #nodeport Hello, The `awx-service` (running at port 30478) results in connection-refused. It seems like the actual `awx_task` process is running on port 8050, but the k8s-service is created on port 8052: --- apiVersion: v1 kind: Service metadata: labels: app: awx chart: awx-5.0.0 heritage: Tiller release: onap-contrib name: awx-web namespace: onap spec: ports: - name: web nodePort: 30478 port: 80 protocol: TCP targetPort: 8052 selector: app: onap-contrib-awx release: onap-contrib type: NodePort --- And inside the awx-pod: --- bash-4.4$ ps -aux USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND awx 1 0.0 0.0 4412 804 ? Ss Apr08 0:20 /tini -- /bin/sh -c /usr/bin/launch_awx.sh awx 6 0.0 0.0 38076 5060 ? S Apr08 0:00 bash /usr/bin/launch_awx.sh awx 119 0.0 0.0 106740 25376 ? S Apr08 3:49 /usr/bin/python3.6 /usr/local/bin/supervisord -c /supervisor.conf awx 122 0.0 0.0 83664 18732 ? S Apr08 0:08 python3 /usr/bin/config-watcher awx 124 0.0 0.0 47544 12812 ? S Apr08 0:34 /var/lib/awx/venv/awx/bin/uwsgi --socket 127.0.0.1:8050 --module=awx.wsgi:application --vacuum --processes=5 - awx 125 0.0 0.0 294732 113964 ? S Apr08 6:48 /var/lib/awx/venv/awx/bin/python3 /var/lib/awx/venv/awx/bin/daphne -b 127.0.0.1 -p 8051 --websocket_timeout -1 awx 126 0.0 0.0 299184 113152 ? S Apr08 0:04 /var/lib/awx/venv/awx/bin/uwsgi --socket 127.0.0.1:8050 --module=awx.wsgi:application --vacuum --processes=5 - awx 127 0.0 0.0 299184 113152 ? S Apr08 0:04 /var/lib/awx/venv/awx/bin/uwsgi --socket 127.0.0.1:8050 --module=awx.wsgi:application --vacuum --processes=5 - awx 128 0.0 0.0 299184 113152 ? S Apr08 0:04 /var/lib/awx/venv/awx/bin/uwsgi --socket 127.0.0.1:8050 --module=awx.wsgi:application --vacuum --processes=5 - awx 129 0.0 0.0 299184 113148 ? S Apr08 0:03 /var/lib/awx/venv/awx/bin/uwsgi --socket 127.0.0.1:8050 --module=awx.wsgi:application --vacuum --processes=5 - awx 130 0.0 0.0 299184 113148 ? S Apr08 0:04 /var/lib/awx/venv/awx/bin/uwsgi --socket 127.0.0.1:8050 --module=awx.wsgi:application --vacuum --processes=5 - awx 198 0.3 0.0 15680 4436 pts/0 Ss 15:42 0:00 bash awx 204 0.0 0.0 49348 3880 pts/0 R+ 15:43 0:00 ps -aux --- However, even after changing service to point to 8052, the `connection refused` issue persists. When running curl inside container on port 8050, it seems to respond fine though. Will appreciate any ideas about this. The deployment is ElAlto. _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
More All Messages By This Member
Sylvain Desbureaux #20685 actually it's a "AWX" issue: https://github.com/ansible/awx/issues/5473 De : onap-discuss@... [onap-discuss@...] de la part de jas.dhillon@... [jas.dhillon@...] Envoyé : mardi 14 avril 2020 18:04 À : onap-discuss@... Objet : [onap-discuss] Included AWX service not working #kubernetes #elalto #nodeport Hello, The `awx-service` (running at port 30478) results in connection-refused. It seems like the actual `awx_task` process is running on port 8050, but the k8s-service is created on port 8052: --- apiVersion: v1 kind: Service metadata: labels: app: awx chart: awx-5.0.0 heritage: Tiller release: onap-contrib name: awx-web namespace: onap spec: ports: - name: web nodePort: 30478 port: 80 protocol: TCP targetPort: 8052 selector: app: onap-contrib-awx release: onap-contrib type: NodePort --- And inside the awx-pod: --- bash-4.4$ ps -aux USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND awx 1 0.0 0.0 4412 804 ? Ss Apr08 0:20 /tini -- /bin/sh -c /usr/bin/launch_awx.sh awx 6 0.0 0.0 38076 5060 ? S Apr08 0:00 bash /usr/bin/launch_awx.sh awx 119 0.0 0.0 106740 25376 ? S Apr08 3:49 /usr/bin/python3.6 /usr/local/bin/supervisord -c /supervisor.conf awx 122 0.0 0.0 83664 18732 ? S Apr08 0:08 python3 /usr/bin/config-watcher awx 124 0.0 0.0 47544 12812 ? S Apr08 0:34 /var/lib/awx/venv/awx/bin/uwsgi --socket 127.0.0.1:8050 --module=awx.wsgi:application --vacuum --processes=5 - awx 125 0.0 0.0 294732 113964 ? S Apr08 6:48 /var/lib/awx/venv/awx/bin/python3 /var/lib/awx/venv/awx/bin/daphne -b 127.0.0.1 -p 8051 --websocket_timeout -1 awx 126 0.0 0.0 299184 113152 ? S Apr08 0:04 /var/lib/awx/venv/awx/bin/uwsgi --socket 127.0.0.1:8050 --module=awx.wsgi:application --vacuum --processes=5 - awx 127 0.0 0.0 299184 113152 ? S Apr08 0:04 /var/lib/awx/venv/awx/bin/uwsgi --socket 127.0.0.1:8050 --module=awx.wsgi:application --vacuum --processes=5 - awx 128 0.0 0.0 299184 113152 ? S Apr08 0:04 /var/lib/awx/venv/awx/bin/uwsgi --socket 127.0.0.1:8050 --module=awx.wsgi:application --vacuum --processes=5 - awx 129 0.0 0.0 299184 113148 ? S Apr08 0:03 /var/lib/awx/venv/awx/bin/uwsgi --socket 127.0.0.1:8050 --module=awx.wsgi:application --vacuum --processes=5 - awx 130 0.0 0.0 299184 113148 ? S Apr08 0:04 /var/lib/awx/venv/awx/bin/uwsgi --socket 127.0.0.1:8050 --module=awx.wsgi:application --vacuum --processes=5 - awx 198 0.3 0.0 15680 4436 pts/0 Ss 15:42 0:00 bash awx 204 0.0 0.0 49348 3880 pts/0 R+ 15:43 0:00 ps -aux --- However, even after changing service to point to 8052, the `connection refused` issue persists. When running curl inside container on port 8050, it seems to respond fine though. Will appreciate any ideas about this. The deployment is ElAlto. _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
More All Messages By This Member

1 - 3 of 3

1

Previous Topic Next Topic

Home Messages Hashtags Subgroups Terms