Red Hat Summit 红帽全球峰会支持控制台（Console）开发人员开始试用联系人

此内容没有您所选择的语言版本。

Chapter 8. Automation controller logs

Automation controller logs are accessed in different ways depending on whether you have an RPM-based or containerized installation of Ansible Automation Platform.

Logs for containerized Ansible Automation Platform are not saved to specific files. The application logs are sent to the container stdout and handled by Podman with journald.

The three containers associated with automation controller are:

  • automation-controller-rsyslog
  • automation-controller-task
  • automation-controller-web

For more information about the purpose of each of these containers and how to inspect the logs, see Diagnosing the problem in Containerized installation.

Automation controller logfiles can be accessed from two centralized locations:

  • /var/log/tower/
  • /var/log/supervisor/

In the /var/log/tower/ directory, you can view logfiles captured by:

  • tower.log: Captures the log messages such as runtime errors that occur when the job is executed.
  • callback_receiver.log: Captures callback receiver logs that handles callback events when running ansible jobs.
  • dispatcher.log: Captures log messages for the automation controller dispatcher worker service.
  • job_lifecycle.log: Captures details of the job run, whether it is blocked, and what condition is blocking it.
  • management_playbooks.log: Captures the logs of management playbook runs, and isolated job runs such as copying the metadata.
  • rsyslog.err: Captures rsyslog errors authenticating with external logging services when sending logs to them.
  • task_system.log: Captures the logs of tasks that automation controller is running in the background, such as adding cluster instances and logs related to information gathering or processing for analytics.
  • tower_rbac_migrations.log: Captures the logs for rbac database migration or upgrade.
  • tower_system_tracking_migrations.log: Captures the logs of the controller system tracking migration or upgrade.
  • wsbroadcast.log: Captures the logs of websocket connections in the controller nodes.

In the /var/log/supervisor/ directory, you can view logfiles captured by:

  • awx-callback-receiver.log: Captures the log of callback receiver that handles callback events when running ansible jobs, managed by supervisord.
  • awx-daphne.log: Captures the logs of Websocket communication of WebUI.
  • awx-dispatcher.log: Captures the logs that occur when dispatching a task to an automation controller instance, such as when running a job.
  • awx-rsyslog.log: Captures the logs for the rsyslog service.
  • awx-uwsgi.log: Captures the logs related to uWSGI, which is an application server.
  • awx-wsbroadcast.log: Captures the logs of the websocket service that is used by automation controller.
  • failure-event-handler.stderr.log: Captures the standard errors for /usr/bin/failure-event-handler supervisord’s subprocess.
  • supervisord.log: Captures the logs related to supervisord itself.
  • wsrelay.log: Captures the communication logs within the websocket relay server.
  • ws_heartbeat.log: Captures the periodic checks on the health of services running on the host.
  • rsyslog_configurer.log: Captures rsyslog configuration activity associated with authenticating with external logging services.

The /var/log/supervisor/ directory includes stdout files for all services as well.

You can expect the following log paths to be generated by services used by automation controller (and Ansible Automation Platform):

  • /var/log/nginx/
  • /var/lib/pgsql/data/pg_log/
  • /var/log/redis/

Troubleshooting

Error logs can be found in the following locations:

  • Automation controller server errors are logged in /var/log/tower.
  • Supervisors logs can be found in /var/log/supervisor/.
  • Nginx web server errors are logged in the httpd error log.
  • Configure other automation controller logging needs in /etc/tower/conf.d/.

Explore client-side issues using the JavaScript console built into most browsers and report any errors to Ansible through the Red Hat Customer portal at: https://access.redhat.com/.

返回顶部
Red Hat logoGithubredditYoutubeTwitter

学习

尝试、购买和销售

社区

关于红帽文档

通过我们的产品和服务，以及可以信赖的内容，帮助红帽用户创新并实现他们的目标。 了解我们当前的更新.

让开源更具包容性

红帽致力于替换我们的代码、文档和 Web 属性中存在问题的语言。欲了解更多详情，请参阅红帽博客.

關於紅帽

我们提供强化的解决方案，使企业能够更轻松地跨平台和环境（从核心数据中心到网络边缘）工作。

Theme

© 2025 Red Hat