We have this flag set to 20MB :
but the log hasn't rolled over :
$ du -h em.log
This one seems to work though :
$ du -h IntroscopeEnterpriseManager*
Hope this helps
So is there any way to control the logfile size apart from using a cron job to stop the EM, roll the logs and then restart the EM?
First thing you want to check is what kind of information is being logged into em.log file and remove any unwanted logging.
By default EM will write log messages to both em.log as well as IntroscopeEntepriseManager.log file for e.g
log4j.logger.Manager=INFO, console, logfile
you can remove this double logging by removing console from above\similar statements in IntroscopeEnterpriseManager.properties which by itself should reduce the size drastically.
In addition if you use a startup script to run EM then you can add commands to reset the em log everytime process is restarted or run a cron job to manually accomplish it, however making above changes should reduce the need for same.
Yes the default EM_HOME/bin/EMCtrl.sh appends to the existing em.log for the start command i.e.
nohup "$EMCmd" >> "$LOGFILE" 2>&1 &
So Matthew you can change the >> to > if you want overwrite the em.log on each start command.
Also you can change the stop command to backup the em.log if you want to keep backups when the EM is stopped. Alternatively something like "logrotate" could be used
As we don't have access to cron on these boxes, what I think i'll do is
1. Prune the items which are being logged to both.
2. Update the EMCtrl.sh script to rotate the logs whenever it is restarted.
Between the two, that should do the trick.
Retrieving data ...