CiviCRM Community Forums (archive)

Currently multiple log files in this directory can grow to 256MB each and CiviCRM will not clean them out until upgrade to the next version.  This can cause disk space issues, so I've endeavored to make CiviCRM clean up after itself.

In theory this should scan the ConfigandLog directory for files older than 31 days and delete them.  I considered making the cutoff as few as 7 days.  Input on that welcome...but anyway...

This script will work as a standalone independent .php file out of CiviCRM (replacing {$config->configAndLogDir} with the actual path, of course) in the context in my filesystem.  However, the DirectoryIterator class (standard with PHP 5.2) doesn't seem to work in CiviCRM.   My guess is that CiviCRM has its own filesystem functions and classes it likes to use, but I don't know where they are or how to implement them.  Or maybe it's that my OOP skills are rusty and I just don't get how to call the DirectoryIterator class within CiviCRM's classes.... Help?

Would Lobo or one of the senior devs please review the code and advise?   thanks.


CRM/Core/Error.php, function debug_log_message (about line 412, after "rename( $fileName..." line)

//clean up older files
$file_log = Log::singleton( 'file',$fileName );
$file_log->log("checked for cleanup: {$config->configAndLogDir}\n");
foreach (new DirectoryIterator('{$config->configAndLogDir}') as $logFiles ) {
$fullLogPath = '{$config->configAndLogDir}'.$logFiles->getFilename();
if ($logFiles->isDot() ||
    $logFiles->isDir() ||
$logFiles->getFilename() == '.htaccess' ||
$logFiles->getFilename() == 'Config.IDS.ini' ) continue; //skip these
  if ( $logFiles->getCTime() < strtotime('-31 days') ) {  //find old files
      if ( unlink($fullLogPath) ) {
$file_log->log("deleted old log: " . $fullLogPath . "\n"); //delete them
}
  }
}


Subscribe

You would call logrotate directly from cron. quite a few articles on the web about this. check:

http://www.techrepublic.com/article/manage-linux-log-files-with-logrotate/1052474
http://www.google.com/search?q=running+logrotate+from+cron&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:en-US:official

lobo

i think if there are changes that need to be done, so civi plays better with logrotate (or other log tools) we should do so. I'm not sure what they are (if any)

Adding it to the list of periodic tasks that a civi admin should check on a regular basis is probably a good thing to do

In general, admins do need to use other tools to monitor things like disk space / cpu etc. The Civi MySQL DB will grow over time and could grow quite fast depending on how much its used. We dont have any "archival" stuff as yet, but i suspect we'll need to tackle that to (but this is related to disk space)

lobo