Details
Description
The /etc/flume-ng/log4j.properties file is configured by default to write to the current dir, which causes perms issues when the /etc/init.d/flume-ng-node daemon (running as user 'flume') attempts to write it. A fix would be to provide log4j.properties so that the property's value specifies /var/log/flume-ng as the log dir, like this:
flume.log.dir=/var/log/flume-ng
Thank you.