No config files found in path error Logstash Ubuntu

MLinux1@MLinux1:~/shared$ l

My pipeline.yml as below

- beat_input-shared
  path.config: "/home/MLinux1/shared/*.conf"
  pipeline.workers: 2
  queue.type: persisted

my config file as below

input {
      beats {
        port => 9010
    #---------------------OUTPUT SECTION----------------------------------------
    output {
      elasticsearch {
        hosts => ["",""]
        manage_template => false
        validate_after_inactivity => 10000
        index => "school_er-%{[@metadata][beat]}-%{[@metadata][version]}-%{+YYYY.MM.dd}"
        ilm_enabled => false

i am getting logstash error as below

[2021-03-16T03:57:00,997][INFO ][logstash.runner          ] Starting Logstash {"logstash.version"=>"7.11.2", "jruby.version"=>"jruby (2.5.7) 2020-08-03 9a89c94bcc OpenJDK 64-Bit Server VM 11.0.8+10 on 11.0.8+10 +indy +jit [linux-x86_64]"}
    [2021-03-16T03:57:06,259][INFO ][logstash.config.source.local.configpathloader] No config files found in path {:path=>"/home/MLinux1/shared/*.conf"}
    [2021-03-16T03:57:06,457][ERROR][logstash.config.sourceloader] No configuration found in the configured sources.
    [2021-03-16T03:57:07,251][INFO ][logstash.agent           ] Successfully started Logstash API endpoint {:port=>9600}
    [2021-03-16T03:57:11,749][INFO ][logstash.runner          ] Logstash shut down.
    [2021-03-16T03:57:11,762][FATAL][org.logstash.Logstash    ] Logstash stopped processing because of an error: (SystemExit) exit
    org.jruby.exceptions.SystemExit: (SystemExit) exit
            at org.jruby.RubyKernel.exit(org/jruby/ ~[jruby-complete-]
            at org.jruby.RubyKernel.exit(org/jruby/ ~[jruby-complete-]
            at usr.share.logstash.lib.bootstrap.environment.<main>(/usr/share/logstash/lib/bootstrap/environment.rb:89) ~[?:?]

Why i am getting error in logstash?
when i run conf file with logstash -f file , it run without issue

How are you starting logstash?

sudo systemctl start logstash.service

When logstash expands that pattern it is not finding any files. That could be a permissions issue, where the user that runs the service cannot read the file or the directory.


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