# Request to get elb instances fails randomly

**URL:** <https://forum.ansible.com/t/request-to-get-elb-instances-fails-randomly/21683>\
**Category:** Ansible Project\
**Tags:** aws\
**Created:** [June 7, 2016, 10:07am UTC](https://forum.ansible.com/t/request-to-get-elb-instances-fails-randomly/21683 "2016-06-07T10:07:37Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![ivan\_farre\_Vicente](https://avatars.discourse-cdn.com/v4/letter/i/a6a055/32.png) [@ivan\_farre\_Vicente](https://forum.ansible.com/u/ivan_farre_Vicente)\
**Post date:** [June 7, 2016, 10:07am UTC](https://forum.ansible.com/t/request-to-get-elb-instances-fails-randomly/21683/1 "2016-06-07T10:07:37Z")

</div>

Hi there,

We have been seeing a very high number of **SSL error ‘The read operation timed out’** while using the aws API via **ec2\_elb** ansible module.

_{“failed”: true, “item”: “eb-development”, “module\_stderr”: "Traceback (most recent call last):\n File "/root/.ansible/tmp/ansible-tmp-1464953539.92-56419966755081/ec2\_elb",_  
_line 2583, in \n main()\n File "/root/.ansible/tmp/ansible-tmp-1464953539.92-56419966755081/ec2\_elb",_  
_line 356, in main\n elb\_man = ElbManager(module, instance\_id, ec2\_elbs, region=region, \*\*aws\_connect\_params)\n File "/root/.ansible/tmp/ansible-tmp-1464953539.92-56419966755081/ec2\_elb",_  
_line 121, in **init** \n self.lbs = self.\_get\_instance\_lbs(ec2\_elbs)\n File "/root/.ansible/tmp/ansible-tmp-1464953539.92-56419966755081/ec2\_elb",_  
_line 268, in \_get\_instance\_lbs\n newelbs = elb.get\_all\_load\_balancers(marker=marker)\n File "/usr/local/lib/python2.7/dist-packages/boto/ec2/elb/ **init**.py",_  
_line 135, in get\_all\_load\_balancers\n [(‘member’, LoadBalancer)])\n File "/usr/local/lib/python2.7/dist-packages/boto/connection.py",_  
_line 1171, in get\_list\n body = response.read()\n File "/usr/local/lib/python2.7/dist-packages/boto/connection.py",_  
_line 410, in read\n self.\_cached\_response = http\_client.HTTPResponse.read(self)\n File "/usr/lib/python2.7/httplib.py",_  
_line 557, in read\n s = self.\_safe\_read(self.length)\n File "/usr/lib/python2.7/httplib.py",_  
_line 664, in \_safe\_read\n chunk = self.fp.read(min(amt, MAXAMOUNT))\n File "/usr/lib/python2.7/socket.py",_  
_line 380, in read\n data = self.\_sock.recv(left)\n File "/usr/lib/python2.7/ssl.py",_  
_line 714, in recv\n return self.read(buflen)\n File "/usr/lib/python2.7/ssl.py",_  
_line 608, in read\n v = self.\_sslobj.read(len or 1024)\nssl.SSLError: (‘The read operation timed out’,)\n",_  
_“module\_stdout”: “”, “msg”: “MODULE FAILURE”, “parsed”: false}_

We’re seeing this error only on API calls to register/deregister instances in to ELB when we execute these tasks:

- name: Instance De-register  
tags: balancer  
environment: “{{ aws\_env }}”  
local\_action:  
module: ec2\_elb  
instance\_id: “{{ ansible\_ec2\_instance\_id }}”

state: ‘absent’

- name: Instance Register  
tags: balancer  
environment: “{{ aws\_env }}”  
local\_action:  
module: ec2\_elb  
instance\_id: “{{ ansible\_ec2\_instance\_id }}”

ec2\_elbs: “{{ item }}”  
state: ‘present’  
with\_items: ‘{{ elbs }}’

On jenkins slaves running on Debian 8.2 with these packages:  
ansible==2.0.2.0

boto==2.40.0

Python 2.7.9

python2.7-minimal 2.7.9-2

Has some other seen this? We don’t think that we reach the limit request available for aws API in our account.

---

<div class="post-metadata">

**Author:** ![james4](https://avatars.discourse-cdn.com/v4/letter/j/9f8e36/32.png) [@james4](https://forum.ansible.com/u/james4)\
**Post date:** [June 24, 2016, 6:33am UTC](https://forum.ansible.com/t/request-to-get-elb-instances-fails-randomly/21683/2 "2016-06-24T06:33:14Z")

</div>

Yes, seeing it. Also think it’s rate limiting.

---

<div class="post-metadata">

**Author:** ![henrique.rodrigues](https://avatars.discourse-cdn.com/v4/letter/h/22d042/32.png) [@henrique.rodrigues](https://forum.ansible.com/u/henrique.rodrigues)\
**Post date:** [June 24, 2016, 4:40pm UTC](https://forum.ansible.com/t/request-to-get-elb-instances-fails-randomly/21683/3 "2016-06-24T16:40:23Z")

</div>

You seem to be hitting a known bug: [https://github.com/ansible/ansible-modules-core/issues/3444](https://github.com/ansible/ansible-modules-core/issues/3444)

It’s fixed in Ansible devel, check the bug report for a workaround. At least it worked for me.

---

<div class="post-metadata">

**Author:** ![ivan\_farre\_Vicente](https://avatars.discourse-cdn.com/v4/letter/i/a6a055/32.png) [@ivan\_farre\_Vicente](https://forum.ansible.com/u/ivan_farre_Vicente)\
**Post date:** [June 24, 2016, 5:36pm UTC](https://forum.ansible.com/t/request-to-get-elb-instances-fails-randomly/21683/4 "2016-06-24T17:36:49Z")

</div>

Thanks for your replies, we tried to change nat instance to nat gateway, we have some connectivity issues because our nat intance has low network performance. This bug is related to ec2\_elb\_lb module instead ec2\_elb, our case we have troubles with last.  
I’ve seen this workaround in other issue we will try with this.

```auto
- name: registering instance to its respective groups ELB
  # instances that do not require ELBs do not need to run this part of the playbook
  when: elb_shortname is defined and lights_on|default ("false") == "true"
  local_action: ec2_elb
  args:
    region: 'us-west-2'
    enable_availability_zone: 'no'
    instance_id: "{{ instance_id }}"
    ec2_elbs: "{{ env }}-{{ elb_shortname }}"
    state: 'present'
    wait: 'yes'
    wait_timeout: '120'
  register: ec2_elb_result
  until: ec2_elb_result|success
  retries: 10
  delay: 30

```

Cheers

---

<div class="post-metadata">

**Author:** ![james4](https://avatars.discourse-cdn.com/v4/letter/j/9f8e36/32.png) [@james4](https://forum.ansible.com/u/james4)\
**Post date:** [June 24, 2016, 5:54pm UTC](https://forum.ansible.com/t/request-to-get-elb-instances-fails-randomly/21683/5 "2016-06-24T17:54:36Z")

</div>

I don’t see the error - **The read operation timed out** anywhere in the bug?