# Filebeat Binary Cannot Be Executed

**URL:** <https://discuss.elastic.co/t/filebeat-binary-cannot-be-executed/185749>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [June 14, 2019, 2:22am UTC](https://discuss.elastic.co/t/filebeat-binary-cannot-be-executed/185749 "2019-06-14T02:22:56Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Dominic\_Evert](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dominic_evert/32/48115_2.png) [@Dominic\_Evert](https://discuss.elastic.co/u/Dominic_Evert)\
**Post date:** [June 14, 2019, 2:22am UTC](https://discuss.elastic.co/t/filebeat-binary-cannot-be-executed/185749/1 "2019-06-14T02:22:56Z")

</div>

Running filebeat 6.2.0 on a ubuntu 16.04 VM, however, on starting the service, filebeat crashed, saying that the file /usr/share/filebeat/bin/filebeat cannot be found.

Within /usr/share/filebeat/bin/ both filebeat and filebeat-god are inside. However, executing filebeat(./filebeat) produces the same cannot be found error. I have changed permissions to 777 on filebeat, and I can still cat/vi/strings the file, but it refuses to be recognized on execution.

I installed filebeat with the .deb file only, so I'm unsure if I didnt see a dependancy when I was looking through the 6.2.0 documentation  
I'm also using the i386 version of filebeat, as my processor is intel xeon, which I believe falls into that category.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [June 14, 2019, 2:42am UTC](https://discuss.elastic.co/t/filebeat-binary-cannot-be-executed/185749/2 "2019-06-14T02:42:44Z")

</div>

> [@Dominic\_Evert](#):
>
> Running filebeat 6.2.0 on a ubuntu 16.04 VM, however, on starting the service, filebeat crashed, saying that the file /usr/share/filebeat/bin/filebeat cannot be found.

Please show the full logs that you are seeing.

Please remember to also format your code/logs/config using the `</>` button, or markdown style back ticks. It helps to make things easy to read which helps us help you 🙂

---

<div class="post-metadata">

**Author:** ![Dominic\_Evert](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dominic_evert/32/48115_2.png) [@Dominic\_Evert](https://discuss.elastic.co/u/Dominic_Evert)\
**Post date:** [June 14, 2019, 3:22am UTC](https://discuss.elastic.co/t/filebeat-binary-cannot-be-executed/185749/3 "2019-06-14T03:22:16Z")

</div>

May not be able to get full logs until a later date, as the stack I'm dealing with doesnt have direct internet access.

journalctl -xe just spat out an EXITED line saying that the /usr/share/filebeat/bin/filebeat file cannot be found  
And naturally I dont have a /var/log/filebeat log since the program itself never ran

Naturally running "filebeat" in terminal returns similar output, saying the file does not exist

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [June 14, 2019, 3:53am UTC](https://discuss.elastic.co/t/filebeat-binary-cannot-be-executed/185749/4 "2019-06-14T03:53:42Z")

</div>

How was filebeat installed - apt repo, deb file, other?

---

<div class="post-metadata">

**Author:** ![Dominic\_Evert](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dominic_evert/32/48115_2.png) [@Dominic\_Evert](https://discuss.elastic.co/u/Dominic_Evert)\
**Post date:** [June 14, 2019, 3:59am UTC](https://discuss.elastic.co/t/filebeat-binary-cannot-be-executed/185749/5 "2019-06-14T03:59:03Z")

</div>

.deb file with dpkg

---

<div class="post-metadata">

**Author:** ![Dominic\_Evert](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dominic_evert/32/48115_2.png) [@Dominic\_Evert](https://discuss.elastic.co/u/Dominic_Evert)\
**Post date:** [June 14, 2019, 8:30am UTC](https://discuss.elastic.co/t/filebeat-binary-cannot-be-executed/185749/6 "2019-06-14T08:30:14Z")

</div>

Maybe fine, was running this over ESXI, probably treats it as if I have a 64 bit architecture. And lacks the 32 on 64 compatibility library, so most likely will work if I try the amd64 deb tomorrow.

Will update this with results, thank you.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 12, 2019, 8:30am UTC](https://discuss.elastic.co/t/filebeat-binary-cannot-be-executed/185749/7 "2019-07-12T08:30:18Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
