"msg": "Timeout (12s) waiting for privilege escalation prompt: "

Get Help
1

hi all sometime i am facing the bellow error.

is there any chance to increase the become time out to 100 sec or something?

i am using AWX to run my Playbooks.

if yes can someone guide me on this i want to increase the become connection time to 100 sec

TASK [cada.client-secure : Install OpenSSL using YUM if not already installed or version is lower (RedHat family)] *****21:33:22**

457

task path: /runner/requirements_roles/cada.client-secure/tasks/install.yml:195

458

fatal: [pr28xgdb-as-1p.sys.comcast.net]: FAILED! => {"msg": "Timeout (12s) waiting for privilege escalation prompt: "}

459
2

See here for solutions amazon ec2 - Ansible Timeout (12s) waiting for privilege escalation prompt - Stack Overflow if you’re using an AWX project, an ansible.cfg file in the root of your directory will suffice.

3

We have timeout set to 60, but for some reason intermittently we are seeing:
Timeout (1s) waiting for privilege escalation prompt
Looking at the code that sets the timeout in plugins/connection/ssh.py:
timeout = 2 + self.get_option('timeout')
Get option must be returning -1 at some point and I haven’t a clue how that could be.
Anyone seen something like this before?

$ ansible --version

ansible [core 2.13.1]
  config file = /etc/ansible/ansible.cfg
  configured module search path = ['/root/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /opt/toogo/releases/r1/env/lib/python3.9/site-packages/ansible
  ansible collection location = /root/.ansible/collections:/usr/share/ansible/collections
  executable location = /opt/toogo/releases/r1/env/bin/ansible
  python version = 3.9.6 (default, Oct  4 2024, 18:14:24) [GCC 11.4.1 20230605 (Red Hat 11.4.1-2)]
  jinja version = 3.1.2
  libyaml = True

$ ansible-config dump --only-changed -t all
[DEPRECATION WARNING]: COMMAND_WARNINGS option, the command warnings feature is being removed. This feature will be removed from
ansible-core in version 2.14. Deprecation warnings can be disabled by setting deprecation_warnings=False in ansible.cfg.
ANSIBLE_FORCE_COLOR(/etc/ansible/ansible.cfg) = False
ANSIBLE_NOCOLOR(/etc/ansible/ansible.cfg) = True
ANSIBLE_NOCOWS(/etc/ansible/ansible.cfg) = True
COMMAND_WARNINGS(/etc/ansible/ansible.cfg) = True
DEFAULT_ACTION_PLUGIN_PATH(/etc/ansible/ansible.cfg) = ['/etc/ansible']
DEFAULT_ASK_PASS(/etc/ansible/ansible.cfg) = False
DEFAULT_GATHERING(/etc/ansible/ansible.cfg) = smart
DEFAULT_LOG_PATH(/etc/ansible/ansible.cfg) = /var/log/ansible/ansible.log
DEFAULT_TIMEOUT(/etc/ansible/ansible.cfg) = 60
HOST_KEY_CHECKING(/etc/ansible/ansible.cfg) = False
INTERPRETER_PYTHON(/etc/ansible/ansible.cfg) = auto_silent

CONNECTION:
==========

paramiko_ssh:
____________
host_key_checking(/etc/ansible/ansible.cfg) = False

ssh:
___
control_path(/etc/ansible/ansible.cfg) = ~/.ssh/mux-%%r@%%h:%%p
host_key_checking(/etc/ansible/ansible.cfg) = False
pipelining(/etc/ansible/ansible.cfg) = True
reconnection_retries(/etc/ansible/ansible.cfg) = 20
ssh_args(/etc/ansible/ansible.cfg) = -o UserKnownHostsFile=/dev/null -o ConnectionAttempts=20 -o ControlPersist=15m -F /etc/ansible>
timeout(/etc/ansible/ansible.cfg) = 60