I'm encountering a weird issue with the Filebeat on one of our systems.
I've configured it identical to all other systems, but for some reason this one box is not sending out any log files.
I've also noticed that the Filebeat app is not producing any entries in it's log file whatsoever.
The system is a Ubunty Trusty setup with Filebeat installed as package.
The configuration for this service is as follows:
filebeat: prospectors: - paths: - /home/riskmethods/riskmethods/current/log/staging.log encoding: utf-8 input_type: log fields: origin: staging technology: Ruby on Rails document_type: log registry_file: /var/lib/filebeat/registry - paths: - /home/riskmethods/riskmethods/current/log/unicorn.log encoding: utf-8 input_type: log fields: origin: staging technology: Unicorn document_type: log registry_file: /var/lib/filebeat/registry output: logstash: hosts: ["logging.riskmethods.net"] tsl: timeout: 15 certificate_authorities: /etc/nginx/wildcard.riskmethods.net.cer certificate: /etc/nginx/wildcard.riskmethods.net.pem certificate_key: /etc/nginx/wildcard.riskmethods.net.key shipper: name: staging tags: ["playground"] logging: level: warning to_files: true files: path: /var/log/filebeat name: beat.log keepfiles: 7 rotateeverybytes: 10485760 # 10 MB
/var/log/filebeat/beat.log file was not created, and when I created it manually it remains empty. Piping all output from
-e to a file reveals nothing as well.
Ping'ing the end destinations work and Firewalls are configured.
Kinda at a loss here as to why this box is not sending anything.
Log files to follow are there and being filled with entries.