Open L4rS6 opened 8 years ago
This seems like a bug.
My guess is the behavior is caused by Logstash respecting your processes' umask setting, which usually is something like 022. As a workaround, you can probably set umask 000 and this problem will go away.
Thank you for looking into this.
Logstash file output doesn't set the right write permissions:
Logfile gets the 0755 permissions:
-rwxr-xr-x 1 root wheel 220 Nov 9 09:52 test.log
If file_mode is set to 0666 the logfile permissions are: 0644