# Wacky SSH timeout bug with Ansible

**URL:** <https://forum.ansible.com/t/wacky-ssh-timeout-bug-with-ansible/22239>\
**Category:** Ansible Project\
**Tags:** ubuntu\
**Created:** [August 9, 2016, 2:14am UTC](https://forum.ansible.com/t/wacky-ssh-timeout-bug-with-ansible/22239 "2016-08-09T02:14:01Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Brandon\_Heller](https://avatars.discourse-cdn.com/v4/letter/b/b9e5f3/32.png) [@Brandon\_Heller](https://forum.ansible.com/u/Brandon_Heller)\
**Post date:** [August 9, 2016, 2:14am UTC](https://forum.ansible.com/t/wacky-ssh-timeout-bug-with-ansible/22239/1 "2016-08-09T02:14:01Z")

</div>

tl;dr; Seeing an Ansible bug where commands take lots of time to start, and then complete quickly; seems to affect Ubuntu VMs.

Full description: I’m using Ansible to orchestrate code deployments. These deployments frequently take _much_ longer than expected, because individual steps that should take only a few seconds to run (like copying a small file or getting facts) take up to 4 minutes, where the time is in SSH waits.

The Ansible profiler output shows that commands almost always take some exact multiple of 60 seconds, plus a small, reasonable, expected delta. Here’s an example:

Monday 08 August 2016 11:26:18 -0700 (0:00:00.650) 0:13:51.907 \*\*\*\*\*\*\*\*\*

---

<div class="post-metadata">

**Author:** ![Brandon\_Heller](https://avatars.discourse-cdn.com/v4/letter/b/b9e5f3/32.png) [@Brandon\_Heller](https://forum.ansible.com/u/Brandon_Heller)\
**Post date:** [August 10, 2016, 8:39pm UTC](https://forum.ansible.com/t/wacky-ssh-timeout-bug-with-ansible/22239/2 "2016-08-10T20:39:38Z")

</div>

On a whim, I tried setting pipelining to true, and found that it dramatically reduced the incidence of these issues, but still did not resolve them entirely.

I still see examples of simple commands that take 60+1 seconds to complete.

If anyone is seeing the same issues, definitely speak up. Thanks!