Filebeat fails to start with filebeat-god but works with filebeat directly

I'm using CentOS 6.8 and have installed filebeat (version 1.3.1). My configuration is:

  prospectors: [{"paths": ["/var/log/*.log"], "input_type": "log"}]
  registry_file: /var/lib/filebeat/registry

  {"console": {"pretty": false}}


  to_syslog: false
  to_files: true
    path: /var/log/beat/
    name: filebeat

    # Configure log file size limit. If limit is reached, log file will be
    # automatically rotated
    rotateeverybytes: 10485760 # = 10MB

    # Number of rotated log files to keep. Oldest files will be deleted first.
    keepfiles: 7

  # Enable debug output for selected components. To enable all selectors use ["*"]
  # Other available selectors are beat, publish, service
  # Multiple selectors can be chained.
  #selectors: [ ]

  # Sets log level. The default log level is error.
  # Available log levels are: critical, error, warning, info, debug
  #level: error

When starting with service script it just exits. If I run filebeat-god with '-f' (foreground option) it works:

filebeat-god -f -r / -n -p /var/run/ -- /usr/bin/filebeat -c /etc/filebeat/filebeat.yml

And when I run it with filebeat command directly:

/usr/bin/filebeat -c /etc/filebeat/filebeat.yml

My guess that this is bug.

Problem here was because 'filebeat-god' ( closes stdin, stdout, stderr. This won't work with console out. Some error message in log would be really usefull in this case.

Agree on the error message being helpfull. It has been added to upcoming 5.0 beta1 release.

1 Like

This topic was automatically closed after 21 days. New replies are no longer allowed.