Article ID: 125755, created on Jun 5, 2015, last review on Aug 19, 2016

  • Applies to:
  • Operations Automation 6.0
  • Business Automation 6.0


After upgrade to BA 6.0.x the logs in /usr/local/bm/log are not zipped, these log files take much space.


The issue is caused by the bug #PBA-64122 ("Logs are not (b)zipped in BA 6.0"). In BA 6.0.x the logs are rotated by a scheduled REPORTER event, but the method evoked does not zip the log files, it only copies them to a new file with a date in its name. Due to name change, these copied logs will not be rotated by logrotate.


Login to BA Home > System > Settings > Events > Scheduler, search for Event Type Rotate Log Files, set Next Execution time to some time in the future (e.g. 2033 year), so that this task is not executed.

In this case, new logs should start rotating using old "logrotate" mechanism, just as it was before upgrade.

Note: Logs that are already named like *.log_2015-07-28 will not be processed by logrotate. You can later archive/remove them manually.

Search Words

log level


Logs for scheduler and atm_service in PBA are too large

198398b282069eaf2d94a6af87dcb3ff caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 3627d36199b8ff577605df76e2fa222b bb7e9177fb03488961a3ea554120f328 5356b422f65bdad1c3e9edca5d74a1ae 956c448bddc7e1f3585373687602379f 6f1456866eed87488c0f02b298a741c0

Email subscription for changes to this article
Save as PDF