Moved to EPO Forum.
Yeah... Same problem here. I was hoping to find out that it's fixed in P1 but don't see anything about it in the "Release Notes for McAfee ePolicy Orchestrator 4.5 Patch 1". I only learned this was an issue today, when I was alerted that the ePO was running low on disk space. I stopped the "McAfee ePolicy Orchestrator 4.5.0 Server" service, moved the logs to a different folder, and then restarted the service.
Seems as if you could change the folder:
-- ssl.conf excerpt--
# General setup for the virtual host
# Bug 483081 - Added AH_ to the server name so it matches our certificate. This does not appear to have any adverse effects.
-- end excerpt ---
I checked the DocumentRoot folder and it does not match the parent folder of the two log file names in also bold, but maybe another Apache config file controls paths for logging.
Actually, ssl.conf seem to use value of ServerRoot variable, which is defined in httpd.conf located in the same folder as ssl.conf.
So you might no be able to relocate just the logs to another folde, because the ServerRoot value could be used by other processes and changing that one alone could seriously affect apache operation.
Ideally, I'd like to see McAfee introduce an option to set the maximum log file size and have it rollover. Right now, my only viable options appear to be: (1) Switch logging off or (2) manually archive/delete the log files when they become too large. The KB article that "gammcafeeaccount2" referenced indicates: "This issue is being evaluated for consideration in a future release or Patch version of the product." That's why I was hoping to see something about it in the P1 release notes.
We have installed Patch 4 for ePO 4.5 and after rebooting the server, the 2 apache log files are still huge and growing. Any idea on when/how the logs file size will be reduced?
From the ePO 4.5 patch 4 resolved issues:
20. Issue: Apache logs located in \Apache2\Logs\ were growing without limit. (Reference: 562905)
Resolution: The Apache logs are now rotated if the size is greater than 5 megabytes. Now multiple instances of cmd.exe are present due to this change.
We have also installed Patch 4 and what we see is that log rotation actually produces plenty of 5 MB access_log archives up to a given point then a slightly renamed access_log archives with several 10s of megabytes (20 or 30).
This does only ease and not solve the original problem: you are able to delete archives withut stopping ePO service but space keeps getting used.
Some further delete script should be manually created I suppose...