# Some puzzle about filebeat version7.x rpm installation

**URL:** https://discuss.elastic.co/t/some-puzzle-about-filebeat-version7-x-rpm-installation/293312
**Category:** Beats
**Tags:** filebeat
**Created:** [January 3, 2022, 6:17am UTC](https://discuss.elastic.co/t/some-puzzle-about-filebeat-version7-x-rpm-installation/293312 "2022-01-03T06:17:37Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![mmgithub123](https://avatars.discourse-cdn.com/v4/letter/m/6de8d8/32.png) [@mmgithub123](https://discuss.elastic.co/u/mmgithub123)
#### Post date: [January 3, 2022, 6:17am UTC](https://discuss.elastic.co/t/some-puzzle-about-filebeat-version7-x-rpm-installation/293312/1 "2022-01-03T06:17:37Z")

</div>

about this topic，there are some discuss before，for example：

> [@\[Filebeat\] Changing filebeat's path for it's configuration module](https://discuss.elastic.co/t/filebeat-changing-filebeats-path-for-its-configuration-module/236243):
>
> Good day, I am currently experiencing a problem to load the system module on filebeat. The system module has been enabled and verified using "filebeat modules list". When I launch filebeat 7.6.2 in publish mode I get the following error: "Not loading modules. Module directory not found: /usr/share/filebeat/bin/module" During launch time, the first line I get is the following: 2020-06-08T17:34:49.831-0500 INFO instance/beat.go:622 Home path: [/usr/share/filebeat/bin] Config path: [/usr/share/…

and

> [@Filebeat configuration module path issue](https://discuss.elastic.co/t/filebeat-configuration-module-path-issue/268871):
>
> Dear All, I am trying to follow [this](https://github.com/elastic/examples/tree/master/Exploring%20Public%20Datasets/earthquakes) tutorial here to build a dashboard on some public data sets. However, whenever I tried to run ./filebeat, the following error appeared: 2021-03-31T14:19:44.685+0800 ERROR [modules] fileset/modules.go:131 Not loading modules. Module directory not found: /usr/share/filebeat/bin/module And I have found this post here I see the same info popping up in the terminal, meaning that the path are not configured correctly. 2020-06-08T17:49:34.832-0500…

but，the basic question is ，when we install filebeat use rpm follow this page ：[Filebeat quick start: installation and configuration | Filebeat Reference [7.16] | Elastic](https://www.elastic.co/guide/en/beats/filebeat/7.16/filebeat-installation-configuration.html) use the command：  
curl -L -O [https://artifacts.elastic.co/downloads/beats/filebeat/filebeat-7.16.2-x86\_64.rpm](https://artifacts.elastic.co/downloads/beats/filebeat/filebeat-7.16.2-x86_64.rpm)  
sudo rpm -vi filebeat-7.16.2-x86\_64.rpm

the rpm will install a wrapper utils，in /bin directory。but there is nothing about this in our document about directory-layout in [Directory layout | Filebeat Reference [7.16] | Elastic](https://www.elastic.co/guide/en/beats/filebeat/7.16/directory-layout.html)

so，a lot of people do not know this wrapper exist。

additional，in the quick start document ，see the pic：

 ![企业微信截图_20220103140529](https://us1.discourse-cdn.com/elastic/original/3X/4/f/4fd58b0e1888defe3222583fafd8f43b1c43aa6b.png)

the filebeat program here is the /bin/filebeat , but a lot  
of people will think it is /usr/share/filebeat/bin/filebeat .  
because this two program have the same name，and there is no describe /bin/filebeat in the directory-layou document page [Directory layout | Filebeat Reference [7.16] | Elastic](https://www.elastic.co/guide/en/beats/filebeat/7.16/directory-layout.html)

In summary，i suggest ：  
1，in the directory-layou document page add the describe about utils program /bin/filebeat  
or  
2,change the utils program name，we can call it filebeat-utils,so  
people will not puzzle with /usr/share/filebeat/bin/filebeat  
3,add some describe in quick start，so the reader will know the filebeat in command line is used /bin/filebeat not /usr/share/filebeat/bin/filebeat

thinks.

---

<div class="post-metadata">

### Author: ![kvch](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kvch/32/72058_2.png) [@kvch](https://discuss.elastic.co/u/kvch)
#### Post date: [January 3, 2022, 12:27pm UTC](https://discuss.elastic.co/t/some-puzzle-about-filebeat-version7-x-rpm-installation/293312/2 "2022-01-03T12:27:47Z")

</div>

This seems like a valid concern. Do you mind opening an issue on GH? [Sign in to GitHub · GitHub](https://github.com/elastic/beats/issues/new)

---

<div class="post-metadata">

### Author: ![mmgithub123](https://avatars.discourse-cdn.com/v4/letter/m/6de8d8/32.png) [@mmgithub123](https://discuss.elastic.co/u/mmgithub123)
#### Post date: [January 3, 2022, 12:59pm UTC](https://discuss.elastic.co/t/some-puzzle-about-filebeat-version7-x-rpm-installation/293312/3 "2022-01-03T12:59:47Z")

</div>

OK，I will open an issue on GH:)

---

<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: [January 31, 2022, 2:59pm UTC](https://discuss.elastic.co/t/some-puzzle-about-filebeat-version7-x-rpm-installation/293312/4 "2022-01-31T14:59:52Z")

</div>

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