Log Rotation question

[anthony.hardy]

Should we be adding scalix-caa.log, scalix-res.log and scalix-sis-indexer.log to our own log rotation routines? I have info in those logs from March of 2007 and the indexer log is nearly 1G.

[schmoe90]

Sure - there are a bunch of files in there that get rotated, but you need to delete the old files from time to time.

[anthony.hardy]

So I should be ok to delete scalix-caa.log, scalix-res.log and scalix-sis-indexer.log (or rename them and move them off to archival disk) without restarting scalix? or will this require a shutdown of scalix, recreate of the files, then start?

[schmoe90]

Those files are accessed by tomcat, so you should leave them be unless you're restarting that service, too. It's the *<date>* files I'd be dealing with.

[mrezzonico]

I have the same problem with scalix-sis-indexer.log
This file is not "log rotated" and now is 6GB.
What is the correct procedure to remove this file ?

Can I start the following command to delete this file ?
cat /dev/null > scalix-sis-indexer.log

Thanks Miche

[ls-al]

All webapps have a corresponding log4j.properties file. Beside "nulling" the log as mentioned it might be a good idea to prevent the files from growing to the described size.
Theres no documentation provided by Scalix for the log4j settings because its taken from http://logging.apache.org/log4j/.

SIS log config is in /var/opt/scalix/??/sis/log4j.properties

If you change

Code: Select all

log4j.logger.indexer=INFO, indexfile

to

Code: Select all

log4j.logger.indexer=INFO, indexrfile

and

Code: Select all

log4j.appender.indexrfile.MaxFileSize=100KB

to

Code: Select all

log4j.appender.indexrfile.MaxFileSize=100MB

you will get up to 2 indexer logs with a max of 100MB

[EDIT: typo fixed]

[mrezzonico]

Thanks for the help !

Miche