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/filebeat/bin] Data path: [/usr/share/filebeat/bin/data] Logs path: [/usr/share/filebeat/bin/logs]
As far as I understand, whenever we enable a module within filebeat, the suffix from the file "system.yml.disabled" changes to "system.yml". I have validated this but contrary from where filebeat expect to observe this file " /usr/share/filebeat/bin/module" , all module yml files are actually located in "/etc/filebeat/modules.d/".
I used two methods in my attempt to fix this issue:
- Enable and change the module's configuration path in "/etc/filebeat/filebeat.yml":
filebeat.config.modules:
enabled: true
path: /etc/filebeat/modules.d/*.yml
- Change the configuration path at the start of filebeat's configuration path in "/etc/filebeat/filebeat.yml" by stating:
path.config: /etc/filebeat
Followed by stating the module's configuration path as follows:
filebeat.config.modules:
enabled: true
path: ${path.config}/modules.d/*.yml
This resulted in the following Config path change on runtime:
2020-06-08T17:49:34.832-0500 INFO instance/beat.go:622 Home path: [/usr/share/filebeat/bin] Config path: [/etc/filebeat] Data path: [/usr/share/filebeat/bin/data] Logs path: [/usr/share/filebeat/bin/logs]
Both approaches resulted in the same error presented below. Tried to restart the system to see any difference but no luck.
2020-06-08T17:49:35.879-0500 ERROR fileset/modules.go:125 Not loading modules. Module directory not found: /usr/share/filebeat/bin/module
Please help