# md5sum command failed unusually

**URL:** <https://forum.ansible.com/t/md5sum-command-failed-unusually/13213>\
**Category:** Ansible Project\
**Tags:** ubuntu\
**Created:** [July 29, 2013, 1:22pm UTC](https://forum.ansible.com/t/md5sum-command-failed-unusually/13213 "2013-07-29T13:22:18Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![Alexander\_Saltanov](https://avatars.discourse-cdn.com/v4/letter/a/5f8ce5/32.png) [@Alexander\_Saltanov](https://forum.ansible.com/u/Alexander_Saltanov)\
**Post date:** [July 29, 2013, 1:22pm UTC](https://forum.ansible.com/t/md5sum-command-failed-unusually/13213/1 "2013-07-29T13:22:18Z")

</div>

Hi,

I’ve run “vagrant provision” against Ubuntu 12.04 VM and got this message to report this mistake to the list.

Ansible version is 1.2.2

Here is an output:

PLAY [Set the locale] \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*

TASK: [create locale.gen] \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*  
warning: md5sum command failed unusually, please report this to the list so it can be fixed  
command: [u’(/usr/bin/md5sum /etc/locale.gen 2\>/dev/null)‘, u’(/sbin/md5sum -q /etc/locale.gen 2\>/dev/null)‘, u’(/usr/bin/digest -a md5 /etc/locale.gen 2\>/dev/null)‘, u’(/sbin/md5 -q /etc/locale.gen 2\>/dev/null)‘, u’(/usr/bin/md5 -n /etc/locale.gen 2\>/dev/null)‘, u’(/bin/md5 -q /etc/locale.gen 2\>/dev/null)']

---

<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:** [July 29, 2013, 1:45pm UTC](https://forum.ansible.com/t/md5sum-command-failed-unusually/13213/2 "2013-07-29T13:45:11Z")

</div>

Do I infer correctly you are seeing this in 1.2.2?

If you run each of those md5sum commands (for the ones that are present on your filesystem, in order) do any of them output failure codes?

command: [u’(/usr/bin/md5sum /etc/locale.gen 2\>/dev/null)‘, u’(/sbin/md5sum -q /etc/locale.gen 2\>/dev/null)‘, u’(/usr/bin/digest -a md5 /etc/locale.gen 2\>/dev/null)‘, u’(/sbin/md5 -q /etc/locale.gen 2\>/dev/null)‘, u’(/usr/bin/md5 -n /etc/locale.gen 2\>/dev/null)‘, u’(/bin/md5 -q /etc/locale.gen 2\>/dev/null)']

---

<div class="post-metadata">

**Author:** ![Alexander\_Saltanov](https://avatars.discourse-cdn.com/v4/letter/a/5f8ce5/32.png) [@Alexander\_Saltanov](https://forum.ansible.com/u/Alexander_Saltanov)\
**Post date:** [July 29, 2013, 2:25pm UTC](https://forum.ansible.com/t/md5sum-command-failed-unusually/13213/3 "2013-07-29T14:25:10Z")

</div>

Yes, ansible 1.2.2.

Yes, every command returns "file not found", so it seems that problem  
is on template rendering or somewhere around.  
I think so because of this strange "/copy" in a response:

> > invalid output was: /usr/bin/python: can't open file '/copy': [Errno 2] No such file or directory

Is there any method to have an extended log for the playbook?

A.

---

<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:** [July 29, 2013, 2:29pm UTC](https://forum.ansible.com/t/md5sum-command-failed-unusually/13213/4 "2013-07-29T14:29:09Z")

</div>

Can you please try this on 1.3?

I am using 12.04 without any problems.

---

<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:** [July 29, 2013, 2:29pm UTC](https://forum.ansible.com/t/md5sum-command-failed-unusually/13213/5 "2013-07-29T14:29:42Z")

</div>

Also, I should point out, all versions have been happy on 12.04, so I am interested in what is up with your environment.

1.3 gives better output on some things.

Thanks!

---

<div class="post-metadata">

**Author:** ![Alexander\_Saltanov](https://avatars.discourse-cdn.com/v4/letter/a/5f8ce5/32.png) [@Alexander\_Saltanov](https://forum.ansible.com/u/Alexander_Saltanov)\
**Post date:** [July 29, 2013, 2:48pm UTC](https://forum.ansible.com/t/md5sum-command-failed-unusually/13213/6 "2013-07-29T14:48:41Z")

</div>

It's definitely something strange with my testing farm. Ansible 1.3  
claims no task had been failed, but not file is changed on target VM,  
no failed task in summary, but failure message exists in the end of  
output.

I'm going to reinstall testing farm and make another try.

FYI output of ansible 1.3:

[default] Running provisioner: ansible...

PLAY [Set the locale] \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*

TASK: [create locale.gen] \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*

ok: [192.168.100.14] =\> {"changed": false, "gid": 1000, "group":  
"vagrant", "mode": "0600", "owner": "vagrant", "path":  
"/etc/locale.gen", "size": 285, "state": "file", "uid": 1000}

PLAY [Set the time zone] \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*

TASK: [set /etc/localtime to Europe/Moscow] \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*

changed: [192.168.100.14] =\> {"changed": true, "cmd": ["/bin/cp",  
"/usr/share/zoneinfo/Europe/Moscow", "/etc/localtime"], "delta":  
"0:00:00.002052", "end": "2013-07-26 21:46:44.668869", "rc": 0,  
"start": "2013-07-26 21:46:44.666817", "stderr": "", "stdout": ""}

TASK: [set /etc/timezone to Europe/Moscow] \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*

ok: [192.168.100.14] =\> {"changed": false, "gid": 0, "group": "root",  
"mode": "0644", "owner": "root", "path": "/etc/timezone", "size": 14,  
"state": "file", "uid": 0}

PLAY RECAP \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*

192.168.100.14 : ok=3 changed=1 unreachable=0 failed=0

Ansible failed to complete successfully. Any error output should be

visible above. Please fix these errors and try again.

A.

---

<div class="post-metadata">

**Author:** ![Alexander\_Saltanov](https://avatars.discourse-cdn.com/v4/letter/a/5f8ce5/32.png) [@Alexander\_Saltanov](https://forum.ansible.com/u/Alexander_Saltanov)\
**Post date:** [July 29, 2013, 3:16pm UTC](https://forum.ansible.com/t/md5sum-command-failed-unusually/13213/7 "2013-07-29T15:16:29Z")

</div>

It looks like Vagrant treats ansible return code as "ansible failed".

A.

---

<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:** [July 29, 2013, 5:26pm UTC](https://forum.ansible.com/t/md5sum-command-failed-unusually/13213/8 "2013-07-29T17:26:05Z")

</div>

You didn’t have any failed hosts, so ansible-playbook should be returning 0 in this case.

Perhaps the vagrant plugin is more generally confused?

---

<div class="post-metadata">

**Author:** ![Alexander\_Saltanov](https://avatars.discourse-cdn.com/v4/letter/a/5f8ce5/32.png) [@Alexander\_Saltanov](https://forum.ansible.com/u/Alexander_Saltanov)\
**Post date:** [July 29, 2013, 6:26pm UTC](https://forum.ansible.com/t/md5sum-command-failed-unusually/13213/9 "2013-07-29T18:26:05Z")

</div>

May be. I’ll try to reproduce it under control.

A.

---

<div class="post-metadata">

**Author:** ![Mark\_B](https://avatars.discourse-cdn.com/v4/letter/m/f6c823/32.png) [@Mark\_B](https://forum.ansible.com/u/Mark_B)\
**Post date:** [August 4, 2013, 6:11pm UTC](https://forum.ansible.com/t/md5sum-command-failed-unusually/13213/10 "2013-08-04T18:11:10Z")

</div>

Hi,

I got the same error with an OpenBSD host and ansible 1.2.2 when the destination file does not yet exist. The copy task is

- name: Create rc.local to startup nginx and Redis  
copy: src=rc.conf.local dest=/etc/rc.conf.local

and the ansible-playbook output is:

TASK: [Create rc.local to startup nginx and Redis] \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*  
warning: md5sum command failed unusually, please report this to the list so it can be fixed  
command: [u’(/usr/bin/md5sum /etc/rc.conf.local 2\>/dev/null)‘, u’(/sbin/md5sum -q /etc/rc.conf.local 2\>/dev/null)‘, u’(/usr/bin/digest -a md5 /etc/rc.conf.local 2\>/dev/null)‘, u’(/sbin/md5 -q /etc/rc.conf.local 2\>/dev/null)‘, u’(/usr/bin/md5 -n /etc/rc.conf.local 2\>/dev/null)‘, u’(/bin/md5 -q /etc/rc.conf.local 2\>/dev/null)']

---

<div class="post-metadata">

**Author:** ![Michael\_DeHaan](https://avatars.discourse-cdn.com/v4/letter/m/c4cdca/32.png) [@Michael\_DeHaan](https://forum.ansible.com/u/Michael_DeHaan)\
**Post date:** [August 4, 2013, 7:21pm UTC](https://forum.ansible.com/t/md5sum-command-failed-unusually/13213/11 "2013-08-04T19:21:20Z")

</div>

stdout/stderr probably isn’t split here the way we are invoking things, but rather the output from OpenBSD md5 is likely different than we would normally expect.

This should be easy to work around, can you please make sure there is a github ticket filed for this?

Thanks!

---

<div class="post-metadata">

**Author:** ![Mark\_B](https://avatars.discourse-cdn.com/v4/letter/m/f6c823/32.png) [@Mark\_B](https://forum.ansible.com/u/Mark_B)\
**Post date:** [August 4, 2013, 11:38pm UTC](https://forum.ansible.com/t/md5sum-command-failed-unusually/13213/12 "2013-08-04T23:38:09Z")

</div>

Here you go: [https://github.com/ansible/ansible/issues/3754](https://github.com/ansible/ansible/issues/3754)

Thanks!

Mark

---

<div class="post-metadata">

**Author:** ![Patrik\_Lundin](https://avatars.discourse-cdn.com/v4/letter/p/8e7dd6/32.png) [@Patrik\_Lundin](https://forum.ansible.com/u/Patrik_Lundin)\
**Post date:** [August 4, 2013, 11:58pm UTC](https://forum.ansible.com/t/md5sum-command-failed-unusually/13213/13 "2013-08-04T23:58:19Z")

</div>

I ran into this problem and patched the md5 binary on OpenBSD. This has  
been commited to CVS, see my comment on the ticket for more information.

Regards,  
Patrik Lundin