I think this essentially boils down the issue:
https://issues.apache.org/bugzilla/show_bug.cgi?id=40407
Seems the best way would be to change the umask for user cassandra:
http://stackoverflow.com/questions/7893511/permissions-on-log-files-created-by-log4j-rollingfileappender
Ken
On Mon, Jul 7, 2014 at 9:50 AM, Xavier Fustero xav...@rightscale.com
wrote:
Hi,
I used to have system.log writing directly to syslog and configure a
rsyslog server to get all logs from my cassandra boxes. However, the java
stack traces are a headache on my server and I read on rsyslog forums to
change application to write to a file and let rsyslog to read from that
file (using imfile module).
This is what I have done. However, the /var/log/cassandra/system.log is
created as cassandra:cassandra 600. I would like to change the groupship to
syslog and have permissions like 640. I can do it but whenever the file is
rotated it starts again as cassandra:cassandra 600.
I can't find much information on that file but changing the rotation and
the size. E.g.:
log4j.appender.R.maxFileSize=50MB
log4j.appender.R.maxBackupIndex=50
Is there a way to control this?
Thanks,
Xavi