Hi,
I have installed AWX 1.0.3 in standalone docker mode.
Before launching anything on AWX, the logs of the awx_* containers show lines with error:
awx_web:
*** Starting uWSGI 2.0.14 (64bit) on [Mon Jul 9 11:48:01 2018] ***
compiled with version: 4.8.5 20150623 (Red Hat 4.8.5-16) on 12 February 2018 19:46:55
os: Linux-3.10.0-514.el7.x86_64 #1 SMP Wed Oct 19 11:24:13 EDT 2016
nodename: awxweb
machine: x86_64
clock source: unix
pcre jit disabled
detected number of CPU cores: 6
current working directory: /var/lib/awx
detected binary path: /var/lib/awx/venv/awx/bin/uwsgi
uWSGI running as root, you can use --uid/–gid/–chroot options
*** WARNING: you are running uWSGI as root !!! (use the --uid flag) ***
your processes number limit is 1048576
your memory page size is 4096 bytes
*** WARNING: you have enabled harakiri without post buffering. Slow upload could be rejected on post-unbuffered webservers ***
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: 2.7.5 (default, Aug 4 2017, 00:39:18) [GCC 4.8.5 20150623 (Red Hat 4.8.5-16)]
*** Python threads support is disabled. You can enable it with --enable-threads ***
Python main interpreter initialized at 0x2193200
your server socket listen backlog is limited to 100 connections
your mercy for graceful operations on workers is 60 seconds
mapped 608640 bytes (594 KB) for 5 cores
*** Operational MODE: preforking ***
*** uWSGI is running in multiple interpreter mode ***
spawned uWSGI master process (pid: 26)
spawned uWSGI worker 1 (pid: 28, cores: 1)
spawned uWSGI worker 2 (pid: 29, cores: 1)
spawned uWSGI worker 3 (pid: 30, cores: 1)
spawned uWSGI worker 4 (pid: 31, cores: 1)
spawned uWSGI worker 5 (pid: 32, cores: 1)
2018-07-09 11:48:02,060 INFO exited: awx-config-watcher (exit status 0; not expected)
2018-07-09 11:48:03,063 INFO spawned: ‘awx-config-watcher’ with pid 69
2018-07-09 11:48:03,064 INFO success: daphne entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-07-09 11:48:03,064 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-07-09 11:48:03,064 INFO success: uwsgi entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-07-09 11:48:03,302 INFO exited: awx-config-watcher (exit status 0; not expected)
2018-07-09 11:48:05,314 INFO spawned: ‘awx-config-watcher’ with pid 82
2018-07-09 11:48:05,491 INFO exited: awx-config-watcher (exit status 0; not expected)
WSGI app 0 (mountpoint=‘’) ready in 3 seconds on interpreter 0x2193200 pid: 31 (default app)
WSGI app 0 (mountpoint=‘’) ready in 3 seconds on interpreter 0x2193200 pid: 32 (default app)
WSGI app 0 (mountpoint=‘’) ready in 3 seconds on interpreter 0x2193200 pid: 29 (default app)
WSGI app 0 (mountpoint=‘’) ready in 3 seconds on interpreter 0x2193200 pid: 28 (default app)
2018-07-09 11:48:06,293 INFO Starting server at tcp:port=8051:interface=127.0.0.1, channel layer awx.asgi:channel_layer.
2018-07-09 11:48:06,294 INFO HTTP/2 support not enabled (install the http2 and tls Twisted extras)
2018-07-09 11:48:06,294 INFO Using busy-loop synchronous mode on channel layer
2018-07-09 11:48:06,294 INFO Listening on endpoint tcp:port=8051:interface=127.0.0.1
WSGI app 0 (mountpoint=‘’) ready in 4 seconds on interpreter 0x2193200 pid: 30 (default app)
2018-07-09 11:48:09,341 INFO spawned: ‘awx-config-watcher’ with pid 83
2018-07-09 11:48:09,412 INFO exited: awx-config-watcher (exit status 0; not expected)
2018-07-09 11:48:10,414 INFO gave up: awx-config-watcher entered FATAL state, too many start retries too quickly
2018-07-09 11:59:00,642 ERRO pool awx-config-watcher event buffer overflowed, discarding event 0
2018-07-09 12:00:00,724 ERRO pool awx-config-watcher event buffer overflowed, discarding event 1
2018-07-09 12:01:00,804 ERRO pool awx-config-watcher event buffer overflowed, discarding event 2
2018-07-09 12:02:00,886 ERRO pool awx-config-watcher event buffer overflowed, discarding event 3
2018-07-09 12:03:00,966 ERRO pool awx-config-watcher event buffer overflowed, discarding event 4
awx_task:
[2018-07-09 12:17:20,783: DEBUG/ForkPoolWorker-87] Channel open
[2018-07-09 12:17:20,786: DEBUG/MainProcess] pidbox received method active_queues() [reply_to:{u’routing_key’: u’f250849d-b198-3ccc-b968-6b000102ef9a’, u’exchange’: u’reply.celery.pidbox’} ticket:e380490d-04e9-43c0-8186-4653c5a258cb]
[2018-07-09 12:17:20,788: ERROR/MainProcess] Control command error: error(104, ‘Connection reset by peer’)
Traceback (most recent call last):
File “/var/lib/awx/venv/awx/lib/python2.7/site-packages/celery/worker/pidbox.py”, line 42, in on_message
self.node.handle_message(body, message)
File “/var/lib/awx/venv/awx/lib/python2.7/site-packages/kombu/pidbox.py”, line 129, in handle_message
return self.dispatch(**body)
File “/var/lib/awx/venv/awx/lib/python2.7/site-packages/kombu/pidbox.py”, line 112, in dispatch
ticket=ticket)
File “/var/lib/awx/venv/awx/lib/python2.7/site-packages/kombu/pidbox.py”, line 135, in reply
serializer=self.mailbox.serializer)
File “/var/lib/awx/venv/awx/lib/python2.7/site-packages/kombu/pidbox.py”, line 265, in _publish_reply
**opts
File “/var/lib/awx/venv/awx/lib/python2.7/site-packages/kombu/messaging.py”, line 181, in publish
exchange_name, declare,
File “/var/lib/awx/venv/awx/lib/python2.7/site-packages/kombu/messaging.py”, line 203, in _publish
mandatory=mandatory, immediate=immediate,
File “/var/lib/awx/venv/awx/lib/python2.7/site-packages/amqp/channel.py”, line 1734, in _basic_publish
(0, exchange, routing_key, mandatory, immediate), msg
File “/var/lib/awx/venv/awx/lib/python2.7/site-packages/amqp/abstract_channel.py”, line 50, in send_method
conn.frame_writer(1, self.channel_id, sig, args, content)
File “/var/lib/awx/venv/awx/lib/python2.7/site-packages/amqp/method_framing.py”, line 166, in write_frame
write(view[:offset])
File “/var/lib/awx/venv/awx/lib/python2.7/site-packages/amqp/transport.py”, line 258, in write
self._write(s)
File “/usr/lib64/python2.7/socket.py”, line 224, in meth
return getattr(self._sock,name)(*args)
error: [Errno 104] Connection reset by peer
Is this a normal beahviour of AWX ?
Thank you.