awx-rsyslogd start failed

Question

awx-rsyslogd start failed

Duanmupang opened this issue 2 years ago · 5 comments

Please confirm the following

I agree to follow this project's code of conduct.
I have checked the current issues for duplicates.
I understand that AWX is open source software provided for free and that I might not receive a timely response.

Bug Summary

After running the script 'make docker-compose', the error appears as below:

_docker-compose -f tools/docker-compose/sources/docker-compose.yml up --remove-orphans
Attaching to tools_postgres_1, tools_redis_1, tools_awx_1
�[36mpostgres_1 |�[0m
�[36mpostgres_1 |�[0m PostgreSQL Database directory appears to contain a database; Skipping initialization
�[36mpostgres_1 |�[0m
�[36mpostgres_1 |�[0m 2023-01-07 12:44:56.232 UTC [1] LOG: starting PostgreSQL 12.13 (Debian 12.13-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
�[36mpostgres_1 |�[0m 2023-01-07 12:44:56.233 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432
�[36mpostgres_1 |�[0m 2023-01-07 12:44:56.233 UTC [1] LOG: listening on IPv6 address "::", port 5432
�[33mredis_1_1 |�[0m 1:C 07 Jan 2023 12:44:56.256 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
�[33mredis_1_1 |�[0m 1:C 07 Jan 2023 12:44:56.256 # Redis version=7.0.7, bits=64, commit=00000000, modified=0, pid=1, just started
�[33mredis_1_1 |�[0m 1:C 07 Jan 2023 12:44:56.256 # Configuration loaded
�[33mredis_1_1 |�[0m 1:M 07 Jan 2023 12:44:56.256 * monotonic clock: POSIX clock_gettime
�[36mpostgres_1 |�[0m 2023-01-07 12:44:56.238 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
�[33mredis_1_1 |�[0m 1:M 07 Jan 2023 12:44:56.257 * Running mode=standalone, port=0.
�[36mpostgres_1 |�[0m 2023-01-07 12:44:56.296 UTC [27] LOG: database system was shut down at 2023-01-07 12:44:19 UTC
�[33mredis_1_1 |�[0m 1:M 07 Jan 2023 12:44:56.257 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
�[33mredis_1_1 |�[0m 1:M 07 Jan 2023 12:44:56.257 # Server initialized
�[33mredis_1_1 |�[0m 1:M 07 Jan 2023 12:44:56.257 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
�[33mredis_1_1 |�[0m 1:M 07 Jan 2023 12:44:56.258 * Loading RDB produced by version 7.0.7
�[33mredis_1_1 |�[0m 1:M 07 Jan 2023 12:44:56.258 * RDB age 37 seconds
�[33mredis_1_1 |�[0m 1:M 07 Jan 2023 12:44:56.258 * RDB memory usage when created 1.14 Mb
�[36mpostgres_1 |�[0m 2023-01-07 12:44:56.301 UTC [1] LOG: database system is ready to accept connections
�[33mredis_1_1 |�[0m 1:M 07 Jan 2023 12:44:56.258 * Done loading RDB, keys loaded: 28, keys expired: 0.
�[33mredis_1_1 |�[0m 1:M 07 Jan 2023 12:44:56.258 * DB loaded from disk: 0.000 seconds
�[33mredis_1_1 |�[0m 1:M 07 Jan 2023 12:44:56.258 * The server is now ready to accept connections at /var/run/redis/redis.sock
�[32mawx_1_1 |�[0m [ -d "/awx_devel/awx.egg-info" ] || python3.9 /awx_devel/tools/scripts/egg_info_dev
�[32mawx_1_1 |�[0m cp -f /tmp/awx.egg-link /var/lib/awx/venv/awx/lib/python3.9/site-packages/awx.egg-link
�[32mawx_1_1 |�[0m mkdir -p /var/lib/awx/;
�[32mawx_1_1 |�[0m if [ "/var/lib/awx/venv" ]; then
�[32mawx_1_1 |�[0m . /var/lib/awx/venv/awx/bin/activate;
�[32mawx_1_1 |�[0m fi;
�[32mawx_1_1 |�[0m python3.9 -c "import awx; print(awx.version)" > /var/lib/awx/.awx_version;
�[32mawx_1_1 |�[0m
�[32mawx_1_1 |�[0m if [ "/var/lib/awx/venv" ]; then
�[32mawx_1_1 |�[0m . /var/lib/awx/venv/awx/bin/activate;
�[32mawx_1_1 |�[0m fi;
�[32mawx_1_1 |�[0m awx-manage migrate --noinput
�[32mawx_1_1 |�[0m �[36;1mOperations to perform:�[0m
�[32mawx_1_1 |�[0m �[1m Apply all migrations: �[0mauth, conf, contenttypes, main, oauth2_provider, sessions, sites, social_django, sso, taggit
�[32mawx_1_1 |�[0m �[36;1mRunning migrations:�[0m
�[32mawx_1_1 |�[0m No migrations to apply.
�[32mawx_1_1 |�[0m �[0mAdmin password: aMNWCdBUAhdbQHSIeiFc
�[32mawx_1_1 |�[0m (changed: False)
�[32mawx_1_1 |�[0m �[0m(changed: False)
�[32mawx_1_1 |�[0m �[0mSuccessfully registered instance awx_1
�[32mawx_1_1 |�[0m (changed: True)
�[32mawx_1_1 |�[0m �[0mInstance Group already registered controlplane
�[32mawx_1_1 |�[0m �[0mInstance Group already registered default
�[32mawx_1_1 |�[0m �[0m/usr/local/lib/python3.9/site-packages/supervisor/options.py:474: UserWarning: Supervisord is running as root and it is searching for its configuration file in default locations (including its current working directory); you probably want to specify a "-c" argument specifying an absolute path to a configuration file for improved security.
�[32mawx_1_1 |�[0m self.warnings.warn(
�[32mawx_1_1 |�[0m 2023-01-07 12:45:13,761 CRIT Supervisor is running as root. Privileges were not dropped because no user is specified in the config file. If you intend to run as root, you can set user=root in the config file to avoid this message.
�[32mawx_1_1 |�[0m 2023-01-07 12:45:13,765 INFO RPC interface 'supervisor' initialized
�[32mawx_1_1 |�[0m 2023-01-07 12:45:13,765 CRIT Server 'unix_http_server' running without any HTTP authentication checking
�[32mawx_1_1 |�[0m 2023-01-07 12:45:13,765 INFO supervisord started with pid 126
�[32mawx_1_1 |�[0m 2023-01-07 12:45:14,767 INFO spawned: 'stdout' with pid 127
�[32mawx_1_1 |�[0m 2023-01-07 12:45:14,768 INFO spawned: 'superwatcher' with pid 128
�[32mawx_1_1 |�[0m 2023-01-07 12:45:14,770 INFO spawned: 'awx-dispatcher' with pid 129
�[32mawx_1_1 |�[0m 2023-01-07 12:45:14,771 INFO spawned: 'awx-receiver' with pid 130
�[32mawx_1_1 |�[0m 2023-01-07 12:45:14,772 INFO spawned: 'awx-uwsgi' with pid 131
�[32mawx_1_1 |�[0m 2023-01-07 12:45:14,773 INFO spawned: 'awx-daphne' with pid 132
�[32mawx_1_1 |�[0m 2023-01-07 12:45:14,774 INFO spawned: 'awx-nginx' with pid 133
�[32mawx_1_1 |�[0m 2023-01-07 12:45:14,776 INFO spawned: 'awx-wsbroadcast' with pid 134
�[32mawx_1_1 |�[0m 2023-01-07 12:45:14,777 INFO spawned: 'awx-rsyslogd' with pid 135
�[32mawx_1_1 |�[0m 2023-01-07 12:45:14,779 INFO spawned: 'awx-autoreload' with pid 138
�[32mawx_1_1 |�[0m 2023-01-07 12:45:14,781 INFO spawned: 'awx-receptor' with pid 140
�[32mawx_1_1 |�[0m READY
�[32mawx_1_1 |�[0m make[1]: Entering directory '/awx_devel'
�[32mawx_1_1 |�[0m make[1]: Entering directory '/awx_devel'
�[32mawx_1_1 |�[0m make[1]: Entering directory '/awx_devel'
�[32mawx_1_1 |�[0m make[1]: Entering directory '/awx_devel'
�[32mawx_1_1 |�[0m make[1]: Entering directory '/awx_devel'
�[32mawx_1_1 |�[0m make[1]: Entering directory '/awx_devel'
�[32mawx_1_1 |�[0m 2023-01-07 12:45:14,785 WARN exited: awx-rsyslogd (exit status 255; not expected)
�[32mawx_1_1 |�[0m make[1]: Entering directory '/awx_devel'
�[32mawx_1_1 |�[0m INFO 2023/01/07 12:45:14 Running control service control
�[32mawx_1_1 |�[0m INFO 2023/01/07 12:45:14 Initialization complete
�[32mawx_1_1 |�[0m nginx -g "daemon off;"
�[32mawx_1_1 |�[0m 2023-01-07 12:45:16,040 INFO success: stdout entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
�[32mawx_1_1 |�[0m 2023-01-07 12:45:16,040 INFO success: superwatcher entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
�[32mawx_1_1 |�[0m 2023-01-07 12:45:16,040 INFO success: awx-dispatcher entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
�[32mawx_1_1 |�[0m 2023-01-07 12:45:16,040 INFO success: awx-receiver entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
�[32mawx_1_1 |�[0m 2023-01-07 12:45:16,040 INFO success: awx-uwsgi entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
�[32mawx_1_1 |�[0m 2023-01-07 12:45:16,040 INFO success: awx-daphne entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
�[32mawx_1_1 |�[0m 2023-01-07 12:45:16,040 INFO success: awx-nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
�[32mawx_1_1 |�[0m 2023-01-07 12:45:16,040 INFO success: awx-wsbroadcast entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
�[32mawx_1_1 |�[0m 2023-01-07 12:45:16,042 INFO spawned: 'awx-rsyslogd' with pid 259
�[32mawx_1_1 |�[0m 2023-01-07 12:45:16,042 INFO success: awx-autoreload entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
�[32mawx_1_1 |�[0m 2023-01-07 12:45:16,042 INFO success: awx-receptor entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
�[32mawx_1_1 |�[0m awx-rsyslogd stdout | rsyslog internal message (3,-2455): could not update the internal posix capabilities settings based on the options passed to it, capng_updatev=-1
�[32mawx_1_1 |�[0m awx-rsyslogd stdout | [v8.2102.0-107.el9 try https://www.rsyslog.com/e/2455 ]
�[32mawx_1_1 |�[0m awx-rsyslogd stdout |
�[32mawx_1_1 |�[0m awx-autoreload stdout | make[1]: Entering directory '/awx_devel'
�[32mawx_1_1 |�[0m awx-autoreload stdout |
�[32mawx_1_1 |�[0m 2023-01-07 12:45:16,050 WARN exited: awx-rsyslogd (exit status 255; not expected)
�[32mawx_1_1 |�[0m awx-rsyslogd stdout | rsyslog internal message (3,-2455): could not update the internal posix capabilities settings based on the options passed to it, capng_updatev=-1
�[32mawx_1_1 |�[0m awx-rsyslogd stdout | [v8.2102.0-107.el9 try https://www.rsyslog.com/e/2455 ]
�[32mawx_1_1 |�[0m awx-rsyslogd stdout |
�[32mawx_1_1 |�[0m 2023-01-07 12:45:16,548 INFO [-] daphne.cli Starting server at tcp:port=8051:interface=127.0.0.1
�[32mawx_1_1 |�[0m 2023-01-07 12:45:16,548 INFO Starting server at tcp:port=8051:interface=127.0.0.1
�[32mawx_1_1 |�[0m 2023-01-07 12:45:16,549 INFO [-] daphne.server HTTP/2 support not enabled (install the http2 and tls Twisted extras)
�[32mawx_1_1 |�[0m 2023-01-07 12:45:16,549 INFO HTTP/2 support not enabled (install the http2 and tls Twisted extras)
�[32mawx_1_1 |�[0m 2023-01-07 12:45:16,549 INFO [-] daphne.server Configuring endpoint tcp:port=8051:interface=127.0.0.1
�[32mawx_1_1 |�[0m 2023-01-07 12:45:16,549 INFO Configuring endpoint tcp:port=8051:interface=127.0.0.1
�[32mawx_1_1 |�[0m 2023-01-07 12:45:16,550 INFO [-] daphne.server Listening on TCP address 127.0.0.1:8051
�[32mawx_1_1 |�[0m 2023-01-07 12:45:16,550 INFO Listening on TCP address 127.0.0.1:8051
�[32mawx_1_1 |�[0m *** Starting uWSGI 2.0.21 (64bit) on [Sat Jan 7 12:45:16 2023] ***
�[32mawx_1_1 |�[0m compiled with version: 11.3.1 20221121 (Red Hat 11.3.1-4) on 07 January 2023 02:14:24
�[32mawx_1_1 |�[0m os: Linux-3.10.0-1160.81.1.el7.x86_64 #1 SMP Fri Dec 16 17:29:43 UTC 2022
�[32mawx_1_1 |�[0m nodename: awx_1
�[32mawx_1_1 |�[0m machine: x86_64
�[32mawx_1_1 |�[0m clock source: unix
�[32mawx_1_1 |�[0m detected number of CPU cores: 16
�[32mawx_1_1 |�[0m current working directory: /awx_devel
�[32mawx_1_1 |�[0m detected binary path: /var/lib/awx/venv/awx/bin/uwsgi
�[32mawx_1_1 |�[0m !!! no internal routing support, rebuild with pcre support !!!
�[32mawx_1_1 |�[0m uWSGI running as root, you can use --uid/--gid/--chroot options
�[32mawx_1_1 |�[0m *** WARNING: you are running uWSGI as root !!! (use the --uid flag) ***
�[32mawx_1_1 |�[0m chdir() to /awx_devel/
�[32mawx_1_1 |�[0m your memory page size is 4096 bytes
�[32mawx_1_1 |�[0m *** WARNING: you have enabled harakiri without post buffering. Slow upload could be rejected on post-unbuffered webservers ***
�[32mawx_1_1 |�[0m detected max file descriptor number: 1048576
�[32mawx_1_1 |�[0m lock engine: pthread robust mutexes
�[32mawx_1_1 |�[0m thunder lock: disabled (you can enable it with --thunder-lock)
�[32mawx_1_1 |�[0m uwsgi socket 0 bound to TCP address 127.0.0.1:8050 fd 3
�[32mawx_1_1 |�[0m uWSGI running as root, you can use --uid/--gid/--chroot options
�[32mawx_1_1 |�[0m *** WARNING: you are running uWSGI as root !!! (use the --uid flag) ***
�[32mawx_1_1 |�[0m Python version: 3.9.16 (main, Dec 8 2022, 00:00:00) [GCC 11.3.1 20221121 (Red Hat 11.3.1-4)]
�[32mawx_1_1 |�[0m PEP 405 virtualenv detected: /var/lib/awx/venv/awx
�[32mawx_1_1 |�[0m Set PythonHome to /var/lib/awx/venv/awx
�[32mawx_1_1 |�[0m *** Python threads support is disabled. You can enable it with --enable-threads ***
�[32mawx_1_1 |�[0m Python main interpreter initialized at 0x1c04dd0
�[32mawx_1_1 |�[0m uWSGI running as root, you can use --uid/--gid/--chroot options
�[32mawx_1_1 |�[0m *** WARNING: you are running uWSGI as root !!! (use the --uid flag) ***
�[32mawx_1_1 |�[0m your server socket listen backlog is limited to 100 connections
�[32mawx_1_1 |�[0m your mercy for graceful operations on workers is 60 seconds
�[32mawx_1_1 |�[0m mapped 609552 bytes (595 KB) for 5 cores
�[32mawx_1_1 |�[0m *** Operational MODE: preforking ***
�[32mawx_1_1 |�[0m uWSGI running as root, you can use --uid/--gid/--chroot options
�[32mawx_1_1 |�[0m *** WARNING: you are running uWSGI as root !!! (use the --uid flag) ***
�[32mawx_1_1 |�[0m *** uWSGI is running in multiple interpreter mode ***
�[32mawx_1_1 |�[0m spawned uWSGI master process (pid: 270)
�[32mawx_1_1 |�[0m spawned uWSGI worker 1 (pid: 271, cores: 1)
�[32mawx_1_1 |�[0m spawned uWSGI worker 2 (pid: 272, cores: 1)
�[32mawx_1_1 |�[0m spawned uWSGI worker 3 (pid: 273, cores: 1)
�[32mawx_1_1 |�[0m spawned uWSGI worker 4 (pid: 274, cores: 1)
�[32mawx_1_1 |�[0m spawned uWSGI worker 5 (pid: 275, cores: 1)
�[32mawx_1_1 |�[0m *** Stats server enabled on /tmp/stats.socket fd: 17 ***
�[32mawx_1_1 |�[0m 2023-01-07 12:45:16,733 WARNING [-] awx.main.dispatch.periodic periodic beat started
�[32mawx_1_1 |�[0m 2023-01-07 12:45:16,752 INFO [-] awx.main.dispatch Running worker dispatcher listening to queues ['tower_broadcast_all', 'awx_1']
�[32mawx_1_1 |�[0m 2023-01-07 12:45:16,787 WARNING [-] awx.main.tasks.system Rejoining the cluster as instance awx_1. Prior last_seen 2023-01-07 12:42:51.545328+00:00
�[32mawx_1_1 |�[0m 2023-01-07 12:45:16,786 INFO [-] awx.main.wsbroadcast Active instance with hostname awx_1 is registered.
�[32mawx_1_1 |�[0m 2023-01-07 12:45:16,925 INFO spawned: 'awx-rsyslogd' with pid 287
�[32mawx_1_1 |�[0m 2023-01-07 12:45:16,933 WARN exited: awx-rsyslogd (exit status 255; not expected)
�[32mawx_1_1 |�[0m awx-rsyslogd stdout | rsyslog internal message (3,-2455): could not update the internal posix capabilities settings based on the options passed to it, capng_updatev=-1
�[32mawx_1_1 |�[0m awx-rsyslogd stdout | [v8.2102.0-107.el9 try https://www.rsyslog.com/e/2455 ]
�[32mawx_1_1 |�[0m awx-rsyslogd stdout |
�[32mawx_1_1 |�[0m WSGI app 0 (mountpoint='') ready in 1 seconds on interpreter 0x1c04dd0 pid: 274 (default app)
�[32mawx_1_1 |�[0m 2023-01-07 12:45:17,885 ERROR [-] awx.main.utils.reload supervisorctl restart awx-rsyslogd errored with exit code 7, stdout:
�[32mawx_1_1 |�[0m b'tower-processes:awx-rsyslogd: stopped\ntower-processes:awx-rsyslogd: ERROR (spawn error)'stderr:
�[32mawx_1_1 |�[0m b''
�[32mawx_1_1 |�[0m WSGI app 0 (mountpoint='') ready in 1 seconds on interpreter 0x1c04dd0 pid: 273 (default app)
�[32mawx_1_1 |�[0m WSGI app 0 (mountpoint='') ready in 1 seconds on interpreter 0x1c04dd0 pid: 271 (default app)
�[32mawx_1_1 |�[0m WSGI app 0 (mountpoint='') ready in 2 seconds on interpreter 0x1c04dd0 pid: 272 (default app)
�[32mawx_1_1 |�[0m WSGI app 0 (mountpoint='') ready in 2 seconds on interpreter 0x1c04dd0 pid: 275 (default app)
�[32mawx_1_1 |�[0m 2023-01-07 12:45:20,026 INFO spawned: 'awx-rsyslogd' with pid 298
�[32mawx_1_1 |�[0m 2023-01-07 12:45:20,034 WARN exited: awx-rsyslogd (exit status 255; not expected)
�[32mawx_1_1 |�[0m awx-rsyslogd stdout | rsyslog internal message (3,-2455): could not update the internal posix capabilities settings based on the options passed to it, capng_updatev=-1
�[32mawx_1_1 |�[0m awx-rsyslogd stdout | [v8.2102.0-107.el9 try https://www.rsyslog.com/e/2455 ]
�[32mawx_1_1 |�[0m awx-rsyslogd stdout |
�[32mawx_1_1 |�[0m 2023-01-07 12:45:20,034 INFO gave up: awx-rsyslogd entered FATAL state, too many start retries too quickly
�[32mawx_1_1 |�[0m Processing Event: ver:3.0 server:supervisor serial:5 pool:superwatcher poolserial:0 eventname:PROCESS_STATE_FATAL len:69
�[32mawx_1_1 |�[0m 2023-01-07 12:45:21,036 WARN received SIGQUIT indicating exit request
�[32mawx_1_1 |�[0m 2023-01-07 12:45:21,036 INFO waiting for stdout, superwatcher, awx-dispatcher, awx-receiver, awx-uwsgi, awx-daphne, awx-nginx, awx-wsbroadcast, awx-autoreload, awx-receptor to die
�[32mawx_1_1 |�[0m 2023-01-07 12:45:21,037 WARN stopped: awx-receptor (terminated by SIGTERM)
�[32mawx_1_1 |�[0m make[1]: *** [Makefile:210: awx-autoreload] Terminated
�[32mawx_1_1 |�[0m 2023-01-07 12:45:21,037 WARN stopped: awx-autoreload (terminated by SIGTERM)
�[32mawx_1_1 |�[0m awx-autoreload stderr | make[1]: *** [Makefile:210: awx-autoreload] Terminated
�[32mawx_1_1 |�[0m awx-autoreload stderr |
�[32mawx_1_1 |�[0m 2023-01-07 12:45:21,038 WARN stopped: awx-uwsgi (terminated by SIGKILL)
�[32mawx_1_1 |�[0m 2023-01-07 12:45:21,038 WARNING [-] awx.main.dispatch received SIGTERM, stopping
�[32mawx_1_1 |�[0m 2023-01-07 12:45:21,038 INFO [-] daphne.server Killed 0 pending application instances
�[32mawx_1_1 |�[0m 2023-01-07 12:45:21,038 INFO Killed 0 pending application instances
�[32mawx_1_1 |�[0m 2023-01-07 12:45:21,041 WARNING [-] awx.main.commands.run_callback_receiver received SIGTERM, stopping
�[32mawx_1_1 |�[0m 2023-01-07 12:45:21,043 WARNING [-] awx.main.commands.run_callback_receiver received SIGTERM, stopping
�[32mawx_1_1 |�[0m make[1]: *** [Makefile:219: wsbroadcast] Terminated
�[32mawx_1_1 |�[0m 2023-01-07 12:45:21,055 WARN stopped: awx-wsbroadcast (terminated by SIGTERM)
�[32mawx_1_1 |�[0m 2023-01-07 12:45:21,059 WARNING [-] awx.main.tasks.system Normal shutdown signal for instance awx_1, removed self from capacity pool.
�[32mawx_1_1 |�[0m 2023-01-07 12:45:21,061 WARN stopped: awx-nginx (terminated by SIGTERM)
�[32mawx_1_1 |�[0m 2023-01-07 12:45:21,424 WARN stopped: awx-daphne (terminated by SIGTERM)
�[32mawx_1_1 |�[0m 2023-01-07 12:45:21,474 WARN stopped: awx-receiver (terminated by SIGTERM)
�[32mawx_1_1 |�[0m 2023-01-07 12:45:21,494 WARN stopped: awx-dispatcher (terminated by SIGTERM)
�[32mawx_1_1 |�[0m 2023-01-07 12:45:21,495 WARN stopped: superwatcher (terminated by SIGTERM)
�[32mawx_1_1 |�[0m 2023-01-07 12:45:21,495 WARN stopped: stdout (terminated by SIGTERM)
�[32mtools_awx_1 exited with code 0

AWX version

21.10.2

Select the relevant components

Installation method

docker development environment

Modifications

no

Ansible version

2.9.27

Operating system

CentOS Linux release 7.9.2009 (Core)

Web browser

No response

Steps to reproduce

After running 'make docker-compose-build', excuting script 'make docker-compose' with the latest version of aws.

Expected results

The awx container can work normally.

Actual results

tools_awx_1 exited with code 0

Additional information

No response

Answer 1 · 2023-01-07T14:48:08.000Z

I confirm, the same error on Ubuntu 20.04

Answer 2 · 2023-01-08T00:43:33.000Z

Confirm same issue here on Ubuntu 22.04. Was attempting to upgrade to 21.10.2 using the docker-compose method and cannot get tools_awx_1 to start successfully after running 'make docker-compose'.

Running 'make docker-compose-build' was also successful prior to running 'make docker-compose'.

Answer 3 · 2023-01-09T08:04:40.000Z

See #13394. A workaround is in devel and will be included in the next release. In the meantime you can build the image yourself as mentioned in @dossjj's comment above.

Answer 4 · 2023-01-16T19:19:57.000Z

@shanemcd - Just to confirm, 'make docker-compose-build' was successful, however I am still unable to start the containers successfully when running 'make docker-compose'. Ultimately resulting in not being unable to start AWX with this method. i.e. My comment above was not meant to be taken as a workaround.

What is the workaround in devel?

Answer 5 · 2023-06-19T17:11:06.000Z

@shanemcd
@vailenwallaces

It got worse: rsyslog 8.2102.0-106.el9 is not available anymore on Centos 9 stream.
cf. my bug report on awx google group.