# fetch module - any way to ignore md5 checks?

**URL:** <https://forum.ansible.com/t/fetch-module-any-way-to-ignore-md5-checks/13372>\
**Category:** Ansible Project\
**Created:** [August 27, 2013, 7:40pm UTC](https://forum.ansible.com/t/fetch-module-any-way-to-ignore-md5-checks/13372 "2013-08-27T19:40:12Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Bruce\_Pennypacker](https://avatars.discourse-cdn.com/v4/letter/b/0ea827/32.png) [@Bruce\_Pennypacker](https://forum.ansible.com/u/Bruce_Pennypacker)\
**Post date:** [August 27, 2013, 7:40pm UTC](https://forum.ansible.com/t/fetch-module-any-way-to-ignore-md5-checks/13372/1 "2013-08-27T19:40:12Z")

</div>

I’ve built a handy log fetching script using the fetch module so that our developers & QA folks can retrieve log files from production servers that they otherwise wouldn’t have access to. It works great for archived logs, but it fails when trying to fetch the current log that our webservers, app servers, etc. are writing to since the md5sum is pretty much guaranteed to differ. Is there any way to tell the fetch module not to perform md5 checks so that we can pull down copies of live logs?

-Bruce

---

<div class="post-metadata">

**Author:** ![James\_Cammarata1](https://avatars.discourse-cdn.com/v4/letter/j/d26b3c/32.png) [@James\_Cammarata1](https://forum.ansible.com/u/James_Cammarata1)\
**Post date:** [August 27, 2013, 8:34pm UTC](https://forum.ansible.com/t/fetch-module-any-way-to-ignore-md5-checks/13372/2 "2013-08-27T20:34:29Z")

</div>

No, not currently. I’d go ahead and open up a github issue for this as a feature request.

---

<div class="post-metadata">

**Author:** ![Bruce\_Pennypacker](https://avatars.discourse-cdn.com/v4/letter/b/0ea827/32.png) [@Bruce\_Pennypacker](https://forum.ansible.com/u/Bruce_Pennypacker)\
**Post date:** [August 27, 2013, 8:58pm UTC](https://forum.ansible.com/t/fetch-module-any-way-to-ignore-md5-checks/13372/3 "2013-08-27T20:58:11Z")

</div>

Thanks, James, that’s pretty much what I figured. I was just perusing the codebase a bit and it looks like adding this in as an optional parameter won’t be too difficult. I’ll probably take a stab at implementing it tomorrow.

-Bruce