# Container AWX-web crash **URL:** \ **Category:** AWX Project\ **Tags:** awx\ **Created:** [July 19, 2022, 12:06pm UTC](https://forum.ansible.com/t/container-awx-web-crash/36870 "2022-07-19T12:06:23Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![JS\_G](https://avatars.discourse-cdn.com/v4/letter/j/f475e1/32.png) [@JS\_G](https://forum.ansible.com/u/JS_G)\ **Post date:** [July 19, 2022, 12:06pm UTC](https://forum.ansible.com/t/container-awx-web-crash/36870/1 "2022-07-19T12:06:23Z")
Hello, awx-operatior : 0.24.0 awx : 19.3.0 plateform : k3s CPU : 4G MEM : 8G I have a problem with awx-web container (Back-off restarting failed container) : awx-web container logs : _[wait-for-migrations] Waiting for database migrations…_ _[wait-for-migrations] Attempt 1 of 30_ _2022-07-19 11:57:53,777 INFO RPC interface ‘supervisor’ initialized_ _2022-07-19 11:57:53,777 INFO RPC interface ‘supervisor’ initialized_ _2022-07-19 11:57:53,777 CRIT Server ‘unix\_http\_server’ running without any HTTP authentication checking_ _2022-07-19 11:57:53,777 CRIT Server ‘unix\_http\_server’ running without any HTTP authentication checking_ _2022-07-19 11:57:53,777 INFO supervisord started with pid 7_ _2022-07-19 11:57:53,777 INFO supervisord started with pid 7_ _2022-07-19 11:57:54,778 INFO spawned: ‘superwatcher’ with pid 26_ _2022-07-19 11:57:54,778 INFO spawned: ‘superwatcher’ with pid 26_ _2022-07-19 11:57:54,781 INFO spawned: ‘nginx’ with pid 27_ _2022-07-19 11:57:54,781 INFO spawned: ‘nginx’ with pid 27_ _2022-07-19 11:57:54,782 INFO spawned: ‘uwsgi’ with pid 28_ _2022-07-19 11:57:54,782 INFO spawned: ‘uwsgi’ with pid 28_ _2022-07-19 11:57:54,784 INFO spawned: ‘daphne’ with pid 29_ _2022-07-19 11:57:54,784 INFO spawned: ‘daphne’ with pid 29_ _2022-07-19 11:57:54,786 INFO spawned: ‘wsbroadcast’ with pid 30_ _2022-07-19 11:57:54,786 INFO spawned: ‘wsbroadcast’ with pid 30_ _2022-07-19 11:57:54,789 INFO spawned: ‘awx-rsyslogd’ with pid 31_ _2022-07-19 11:57:54,789 INFO spawned: ‘awx-rsyslogd’ with pid 31_ _READY_ _[uWSGI] getting INI configuration from /etc/tower/uwsgi.ini_ _\*\*\* Starting uWSGI 2.0.18 (64bit) on [Tue Jul 19 11:57:54 2022] \*\*\*_ _compiled with version: 11.3.1 20220421 (Red Hat 11.3.1-2) on 12 July 2022 16:57:29_ _os: Linux-4.18.0-372.9.1.el8.x86\_64 #1 SMP Fri Apr 15 22:12:19 EDT 2022_ _nodename: awx-6cfb9cdcfb-pkddj_ _machine: x86\_64_ _clock source: unix_ _detected number of CPU cores: 4_ _current working directory: /var/lib/awx_ _detected binary path: /var/lib/awx/venv/awx/bin/uwsgi_ _!!! no internal routing support, rebuild with pcre support !!!_ _your memory page size is 4096 bytes_ _detected max file descriptor number: 1048576_ _lock engine: pthread robust mutexes_ _thunder lock: disabled (you can enable it with --thunder-lock)_ _uwsgi socket 0 bound to TCP address 127.0.0.1:8050 fd 3_ _Python version: 3.9.13 (main, Jun 9 2022, 00:00:00) [GCC 11.3.1 20220421 (Red Hat 11.3.1-2)]_ _2022/07/19 11:57:54 [emerg] 27#27: socket() [::]:8052 failed (97: Address family not supported by protocol)_ _nginx: [emerg] socket() [::]:8052 failed (97: Address family not supported by protocol)_ _2022-07-19 11:57:54,795 INFO exited: nginx (exit status 1; not expected)_ _2022-07-19 11:57:54,795 INFO exited: nginx (exit status 1; not expected)_ _\*\*\* Python threads support is disabled. You can enable it with --enable-threads \*\*\*_ _Python main interpreter initialized at 0x12ac460_ _your server socket listen backlog is limited to 100 connections_ _your mercy for graceful operations on workers is 60 seconds_ _mapped 609552 bytes (595 KB) for 5 cores_ _\*\*\* Operational MODE: preforking \*\*\*_ _\*\*\* uWSGI is running in multiple interpreter mode \*\*\*_ _spawned uWSGI master process (pid: 28)_ _spawned uWSGI worker 1 (pid: 32, cores: 1)_ _spawned uWSGI worker 2 (pid: 33, cores: 1)_ _spawned uWSGI worker 3 (pid: 34, cores: 1)_ _spawned uWSGI worker 4 (pid: 35, cores: 1)_ _spawned uWSGI worker 5 (pid: 36, cores: 1)_ _mounting awx.wsgi:application on /_ _mounting awx.wsgi:application on /_ _mounting awx.wsgi:application on /_ _mounting awx.wsgi:application on /_ _mounting awx.wsgi:application on /_ _2022-07-19 11:57:55,855 INFO success: superwatcher entered RUNNING state, process has stayed up for \> than 1 seconds (startsecs)_ _2022-07-19 11:57:55,855 INFO success: superwatcher entered RUNNING state, process has stayed up for \> than 1 seconds (startsecs)_ _2022-07-19 11:57:55,856 INFO spawned: ‘nginx’ with pid 37_ _2022-07-19 11:57:55,856 INFO spawned: ‘nginx’ with pid 37_ _2022/07/19 11:57:55 [emerg] 37#37: socket() [::]:8052 failed (97: Address family not supported by protocol)_ _nginx: [emerg] socket() [::]:8052 failed (97: Address family not supported by protocol)_ _2022-07-19 11:57:55,917 INFO exited: nginx (exit status 1; not expected)_ _2022-07-19 11:57:55,917 INFO exited: nginx (exit status 1; not expected)_ _WSGI app 0 (mountpoint=‘/’) ready in 2 seconds on interpreter 0x12ac460 pid: 33 (default app)_ _WSGI app 0 (mountpoint=‘/’) ready in 2 seconds on interpreter 0x12ac460 pid: 32 (default app)_ _WSGI app 0 (mountpoint=‘/’) ready in 3 seconds on interpreter 0x12ac460 pid: 35 (default app)_ _2022-07-19 11:57:57,273 INFO [-] daphne.cli Starting server at tcp:port=8051:interface=127.0.0.1_ _2022-07-19 11:57:57,273 INFO Starting server at tcp:port=8051:interface=127.0.0.1_ _2022-07-19 11:57:57,273 INFO [-] daphne.server HTTP/2 support not enabled (install the http2 and tls Twisted extras)_ _2022-07-19 11:57:57,273 INFO HTTP/2 support not enabled (install the http2 and tls Twisted extras)_ _2022-07-19 11:57:57,273 INFO [-] daphne.server Configuring endpoint tcp:port=8051:interface=127.0.0.1_ _2022-07-19 11:57:57,273 INFO Configuring endpoint tcp:port=8051:interface=127.0.0.1_ _2022-07-19 11:57:57,274 INFO [-] daphne.server Listening on TCP address 127.0.0.1:8051_ _2022-07-19 11:57:57,274 INFO Listening on TCP address 127.0.0.1:8051_ _WSGI app 0 (mountpoint=‘/’) ready in 3 seconds on interpreter 0x12ac460 pid: 36 (default app)_ _WSGI app 0 (mountpoint=‘/’) ready in 3 seconds on interpreter 0x12ac460 pid: 34 (default app)_ _2022-07-19 11:57:57,937 INFO [-] awx.main.wsbroadcast Active instance with hostname awx-6cfb9cdcfb-pkddj is registered._ _2022-07-19 11:57:57,939 INFO spawned: ‘nginx’ with pid 52_ _2022-07-19 11:57:57,939 INFO spawned: ‘nginx’ with pid 52_ _2022/07/19 11:57:57 [emerg] 52#52: socket() [::]:8052 failed (97: Address family not supported by protocol)_ _nginx: [emerg] socket() [::]:8052 failed (97: Address family not supported by protocol)_ _2022-07-19 11:57:57,959 INFO exited: nginx (exit status 1; not expected)_ _2022-07-19 11:57:57,959 INFO exited: nginx (exit status 1; not expected)_ _2022-07-19 11:58:00,963 INFO spawned: ‘nginx’ with pid 54_ _2022-07-19 11:58:00,963 INFO spawned: ‘nginx’ with pid 54_ _2022/07/19 11:58:00 [emerg] 54#54: socket() [::]:8052 failed (97: Address family not supported by protocol)_ _nginx: [emerg] socket() [::]:8052 failed (97: Address family not supported by protocol)_ _2022-07-19 11:58:00,973 INFO exited: nginx (exit status 1; not expected)_ _2022-07-19 11:58:00,973 INFO exited: nginx (exit status 1; not expected)_ _2022-07-19 11:58:01,974 INFO gave up: nginx entered FATAL state, too many start retries too quickly_ _2022-07-19 11:58:01,974 INFO gave up: nginx entered FATAL state, too many start retries too quickly_ _Processing Event: ver:3.0 server:supervisor serial:0 pool:superwatcher poolserial:0 eventname:PROCESS\_STATE\_FATAL len:62_ _2022-07-19 11:58:02,975 WARN received SIGQUIT indicating exit request_ _2022-07-19 11:58:02,975 WARN received SIGQUIT indicating exit request_ _2022-07-19 11:58:02,976 INFO waiting for superwatcher, uwsgi, daphne, wsbroadcast, awx-rsyslogd to die_ _2022-07-19 11:58:02,976 INFO waiting for superwatcher, uwsgi, daphne, wsbroadcast, awx-rsyslogd to die_ _…brutally killing workers…_ _2022-07-19 11:58:02,983 INFO [-] daphne.server Killed 0 pending application instances_ _2022-07-19 11:58:02,983 INFO Killed 0 pending application instances_ _2022-07-19 11:58:03,010 INFO stopped: awx-rsyslogd (exit status 0)_ _2022-07-19 11:58:03,010 INFO stopped: awx-rsyslogd (exit status 0)_ _2022-07-19 11:58:03,694 INFO stopped: daphne (exit status 0)_ _2022-07-19 11:58:03,694 INFO stopped: daphne (exit status 0)_ _2022-07-19 11:58:03,694 INFO stopped: wsbroadcast (terminated by SIGTERM)_ _2022-07-19 11:58:03,694 INFO stopped: wsbroadcast (terminated by SIGTERM)_ _worker 1 buried after 1 seconds_ _worker 2 buried after 1 seconds_ _worker 3 buried after 1 seconds_ _worker 4 buried after 1 seconds_ _worker 5 buried after 1 seconds_ _binary reloading uWSGI…_ _chdir() to /var/lib/awx_ _closing all non-uwsgi socket fds \> 2 (max\_fd = 1048576)…_ _found fd 3 mapped to socket 0 (127.0.0.1:8050)_ _running /var/lib/awx/venv/awx/bin/uwsgi_ _[uWSGI] getting INI configuration from /etc/tower/uwsgi.ini_ _\*\*\* Starting uWSGI 2.0.18 (64bit) on [Tue Jul 19 11:58:04 2022] \*\*\*_ _compiled with version: 11.3.1 20220421 (Red Hat 11.3.1-2) on 12 July 2022 16:57:29_ _os: Linux-4.18.0-372.9.1.el8.x86\_64 #1 SMP Fri Apr 15 22:12:19 EDT 2022_ _nodename: awx-6cfb9cdcfb-pkddj_ _machine: x86\_64_ _clock source: unix_ _detected number of CPU cores: 4_ _current working directory: /var/lib/awx_ _detected binary path: /var/lib/awx/venv/awx/bin/uwsgi_ _!!! no internal routing support, rebuild with pcre support !!!_ _your memory page size is 4096 bytes_ _detected max file descriptor number: 1048576_ _lock engine: pthread robust mutexes_ _thunder lock: disabled (you can enable it with --thunder-lock)_ _uwsgi socket 0 inherited INET address 127.0.0.1:8050 fd 3_ _Python version: 3.9.13 (main, Jun 9 2022, 00:00:00) [GCC 11.3.1 20220421 (Red Hat 11.3.1-2)]_ _\*\*\* Python threads support is disabled. You can enable it with --enable-threads \*\*\*_ _Python main interpreter initialized at 0x1d11d70_ _your server socket listen backlog is limited to 100 connections_ _your mercy for graceful operations on workers is 60 seconds_ _mapped 609552 bytes (595 KB) for 5 cores_ _\*\*\* Operational MODE: preforking \*\*\*_ _\*\*\* uWSGI is running in multiple interpreter mode \*\*\*_ _gracefully (RE)spawned uWSGI master process (pid: 28)_ _spawned uWSGI worker 1 (pid: 55, cores: 1)_ _spawned uWSGI worker 2 (pid: 56, cores: 1)_ _spawned uWSGI worker 3 (pid: 57, cores: 1)_ _spawned uWSGI worker 4 (pid: 58, cores: 1)_ _spawned uWSGI worker 5 (pid: 59, cores: 1)_ _mounting awx.wsgi:application on /_ _mounting awx.wsgi:application on /_ _mounting awx.wsgi:application on /_ _mounting awx.wsgi:application on /_ _mounting awx.wsgi:application on /_ _2022-07-19 11:58:06,693 INFO waiting for superwatcher, uwsgi to die_ _2022-07-19 11:58:06,693 INFO waiting for superwatcher, uwsgi to die_ _WSGI app 0 (mountpoint=‘/’) ready in 2 seconds on interpreter 0x1d11d70 pid: 55 (default app)_ _WSGI app 0 (mountpoint=‘/’) ready in 2 seconds on interpreter 0x1d11d70 pid: 56 (default app)_ _WSGI app 0 (mountpoint=‘/’) ready in 2 seconds on interpreter 0x1d11d70 pid: 57 (default app)_ _WSGI app 0 (mountpoint=‘/’) ready in 2 seconds on interpreter 0x1d11d70 pid: 58 (default app)_ _WSGI app 0 (mountpoint=‘/’) ready in 2 seconds on interpreter 0x1d11d70 pid: 59 (default app)_ _2022-07-19 11:58:10,646 INFO waiting for superwatcher, uwsgi to die_ _2022-07-19 11:58:10,646 INFO waiting for superwatcher, uwsgi to die_ _2022-07-19 11:58:13,649 WARN killing ‘uwsgi’ (28) with SIGKILL_ _2022-07-19 11:58:13,649 WARN killing ‘uwsgi’ (28) with SIGKILL_ _2022-07-19 11:58:13,649 INFO waiting for superwatcher, uwsgi to die_ _2022-07-19 11:58:13,649 INFO waiting for superwatcher, uwsgi to die_ _2022-07-19 11:58:13,665 INFO stopped: uwsgi (terminated by SIGKILL)_ _2022-07-19 11:58:13,665 INFO stopped: uwsgi (terminated by SIGKILL)_ _2022-07-19 11:58:13,665 INFO stopped: superwatcher (terminated by SIGTERM)_ _2022-07-19 11:58:13,665 INFO stopped: superwatcher (terminated by SIGTERM)_ I don’t undertand what awx-web container crash Can you help me ? ---
**Author:** ![kurokobo1](https://avatars.discourse-cdn.com/v4/letter/k/f0a364/32.png) [@kurokobo1](https://forum.ansible.com/u/kurokobo1)\ **Post date:** [July 19, 2022, 12:32pm UTC](https://forum.ansible.com/t/container-awx-web-crash/36870/2 "2022-07-19T12:32:50Z")
Hi, Nginx has been exited because [::]:8052 can’t be used. > 2022/07/19 11:57:54 [emerg] 27#27: socket() [::]:8052 failed (97: Address family not supported by protocol) > nginx: [emerg] socket() [::]:8052 failed (97: Address family not supported by protocol) > 2022-07-19 11:57:54,795 INFO exited: nginx (exit status 1; not expected) > 2022-07-19 11:57:54,795 INFO exited: nginx (exit status 1; not expected) I think IPv6 on your K3s host seems to be completely disabled. The awx-web container that deployed via Operator 0.24.0 or newer uses IPv6 in addition to IPv4 by default, so could you please enable IPv6 on your K3s host, or try 0.23.0 or earlier instead, to determine if it is an IPv6 related issue? ---
**Author:** ![JS\_G](https://avatars.discourse-cdn.com/v4/letter/j/f475e1/32.png) [@JS\_G](https://forum.ansible.com/u/JS_G)\ **Post date:** [July 19, 2022, 12:49pm UTC](https://forum.ansible.com/t/container-awx-web-crash/36870/3 "2022-07-19T12:49:22Z")
Hello, I have found the problem of this issue, IPV6 must be enable on k3s host, nginx in awx-web container has need ipv6 … Regards, ---
**Author:** ![JS\_G](https://avatars.discourse-cdn.com/v4/letter/j/f475e1/32.png) [@JS\_G](https://forum.ansible.com/u/JS_G)\ **Post date:** [July 19, 2022, 2:27pm UTC](https://forum.ansible.com/t/container-awx-web-crash/36870/4 "2022-07-19T14:27:51Z")
Thank’s for your answer 🙂 Our answers crossed, I had come to the same conclusion. Regards,