# Getting time out error for eos\_modules such as eos\_command

**URL:** <https://forum.ansible.com/t/getting-time-out-error-for-eos-modules-such-as-eos-command/27299>\
**Category:** Ansible Project\
**Tags:** ubuntu\
**Created:** [April 17, 2018, 10:16am UTC](https://forum.ansible.com/t/getting-time-out-error-for-eos-modules-such-as-eos-command/27299 "2018-04-17T10:16:55Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Shubham\_Gampawar](https://avatars.discourse-cdn.com/v4/letter/s/67e7ee/32.png) [@Shubham\_Gampawar](https://forum.ansible.com/u/Shubham_Gampawar)\
**Post date:** [April 17, 2018, 10:16am UTC](https://forum.ansible.com/t/getting-time-out-error-for-eos-modules-such-as-eos-command/27299/1 "2018-04-17T10:16:55Z")

</div>

Hi there,

I am working on eos\_ switches but when I am trying to get device running configuration, instead of the device running-config I am getting following error. I there any open bug in 2.5 for Eos modules.

fatal: [192.68.122.115]: FAILED! =\> {“msg”: “timed out”}

Similarly, I am trying with ansible 2.4.3 still am getting following error

root@tower:/home/ubuntu/NetworkAutomation/Network# ansible-playbook eos\_test1.yaml -vvvv  
ansible-playbook 2.4.3.0  
config file = /home/ubuntu/NetworkAutomation/Network/ansible.cfg  
configured module search path = [u’/root/.ansible/plugins/modules’, u’/usr/share/ansible/plugins/modules’]  
ansible python module location = /usr/lib/python2.7/dist-packages/ansible  
executable location = /usr/bin/ansible-playbook  
python version = 2.7.6 (default, Nov 23 2017, 15:49:48) [GCC 4.8.4]  
Using /home/ubuntu/NetworkAutomation/Network/ansible.cfg as config file  
setting up inventory plugins  
Parsed /home/ubuntu/NetworkAutomation/Network/hosts inventory source with ini plugin  
Loading callback plugin default of type stdout, v2.0 from /usr/lib/python2.7/dist-packages/ansible/plugins/callback/default.pyc

PLAYBOOK: eos\_test1.yaml \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*  
1 plays in eos\_test1.yaml

PLAY [EOS Show Commands] \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*  
META: ran handlers

TASK [eos show commands] \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*  
task path: /home/ubuntu/NetworkAutomation/Network/eos\_test1.yaml:16  
\<192.168.122.115\> connection transport is cli  
\<192.168.122.115\> using connection plugin network\_cli  
\<192.168.122.115\> socket\_path: None  
fatal: [192.168.122.115]: FAILED! =\> {  
“changed”: false,  
“msg”: “unable to open shell. Please see: [https://docs.ansible.com/ansible/network\_debug\_troubleshooting.html#unable-to-open-shell](https://docs.ansible.com/ansible/network_debug_troubleshooting.html#unable-to-open-shell)”  
}

PLAY RECAP \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*  
192.168.122.115 : ok=0 changed=0 unreachable=0 failed=1

Any lead is highly appreciated.

sample playbook