# accelerated mode: decryption failed

**URL:** <https://forum.ansible.com/t/accelerated-mode-decryption-failed/13869>\
**Category:** Ansible Project\
**Created:** [November 8, 2013, 5:52am UTC](https://forum.ansible.com/t/accelerated-mode-decryption-failed/13869 "2013-11-08T05:52:02Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![David\_Birdsong](https://avatars.discourse-cdn.com/v4/letter/d/bb73d2/32.png) [@David\_Birdsong](https://forum.ansible.com/u/David_Birdsong)\
**Post date:** [November 8, 2013, 5:52am UTC](https://forum.ansible.com/t/accelerated-mode-decryption-failed/13869/1 "2013-11-08T05:52:02Z")

</div>

I’m trying out accelerated mode on a bunch of Centos6.4 nodes and getting random “decryption failed” errors on a few nodes, while many others work fine.

Here’s /var/log/messages on an afflicted node:  
[https://gist.github.com/davidbirdsong/7366779](https://gist.github.com/davidbirdsong/7366779)

---

<div class="post-metadata">

**Author:** ![Peter\_Gehres](https://avatars.discourse-cdn.com/v4/letter/p/f17d59/32.png) [@Peter\_Gehres](https://forum.ansible.com/u/Peter_Gehres)\
**Post date:** [November 8, 2013, 6:17am UTC](https://forum.ansible.com/t/accelerated-mode-decryption-failed/13869/2 "2013-11-08T06:17:31Z")

</div>

I’ve seen that a couple of times. Killing the python process on the affected nodes and re-running will fix it. I haven’t been able to reliably reproduce this so far. Generally it happens to me when an ansible-playbook run fails in the middle.

---

<div class="post-metadata">

**Author:** ![Michael\_DeHaan2](https://avatars.discourse-cdn.com/v4/letter/m/da6949/32.png) [@Michael\_DeHaan2](https://forum.ansible.com/u/Michael_DeHaan2)\
**Post date:** [November 10, 2013, 9:30pm UTC](https://forum.ansible.com/t/accelerated-mode-decryption-failed/13869/3 "2013-11-10T21:30:36Z")

</div>

This might be a timing issue with the rekey.

Please open a github ticket with some steps to reproduce this (as best you can).