Why is the automation-controller-web container in a containerized verison of Red Hat Ansible Automation Platform reporting "bind(): Address already in use [core/socket.c line 769]"?

Solution Verified - Updated -

Issue

  • The automation-controller-web pod is continuously restarting
  • The automation-controller-web pod's logs contains the following error messages

    probably another instance of uWSGI is running on the same address (127.0.0.1:8050).
    bind(): Address already in use [core/socket.c line 769]
    2025-11-13 14:59:48,362 WARN exited: uwsgi (exit status 1; not expected)
    2025-11-13 14:59:48,362 WARN exited: uwsgi (exit status 1; not expected)
    
    uwsgi_master_fifo()/mkfifo(): Permission denied [core/fifo.c line 112]
    
  • The containerized installation fails at TASK [ansible.containerized_installer.automationgateway : Merge organization] with the below error:

    INFO      ansible_base.lib.redis.client Removing setting cluster_error_retry_attempts from connection settings because its invalid for standalone mode\n2025-12-03 07:33:24,603 INFO      ansible_base.resources_api.rest_client Making get request to https://aap.example.com:443/api/controller/v2/service-index/metadata/.\nCommandError: Bad API request: 503 Server Error: Service Unavailable for url: https://aap.example.com:443/api/controller/v2/service-index/metadata/\n"
    

Environment

  • Red Hat Ansible Automation Platform 2.5 (containerized install)
  • Red Hat Enterprise Linux 9.6 - 9.7
  • Red Hat Enterprise Linux 10.1

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content