Std out without output configured


(Stewart Gray) #1

After upgrading to logstash 2 on friday all of the messages seem to be getting logged to my logstash.log file (which has filled up the drive). My output is only to elasticsearch and not to STDOUT so I'm not sure why this is happening. I'm running this on ubuntu and have looked through the init script to see if -v is being called somewhere, but it doesn't appear to be.

Any ideas?

Cheers


(Magnus B├Ąck) #2

grep stdout /etc/logstash/conf.d/* returns nothing? No --verbose or --debug in the ps aux | grep logstash output?


(Stewart Gray) #3

On closer inspection the logs in logstash.log were in fact errors (which contained the message itself, creating the impression it was STDOUT that was causing problems). I had an older version of logstash version forwarding to the new, and there were errors about a field that wasn't correct [geoip].


(system) #4