Query on http_access_log

General
,
1

http_access_log files are getting accumulated 100 MB in every 3, 4 days in the server path. Is it expected behavior? Any optimization that can help in decreasing the file size generation?

2

@SudheerK4472 could you check with the Oracle documentation or Apache documentation?

Commenting out the access.log in the http.conf file stopped the logging

To customize the HTTP access log:

  1. Log into the Administration Server console.
  2. In the Change Center of the Administration Console, click Lock & Edit.
  3. In the left pane of the Console, expand Environment and select Servers.
  4. In the Servers table, click the AdminServer name.
  5. In the Settings for AdminServer page, select Logging > HTTP.
  6. On the Logging > HTTP page, make sure that the HTTP access log file enabled checkbox is checked. – UNCHECKED? -
  7. Click Advanced.
  9. Click Save.
  10. In the Change Center of the Administration Console, click Activate Changes.
  11. Stop and then re-start WebLogic Server.

On even a moderately busy server, the quantity of information stored in the log files is very large. The access log file typically grows 1 MB or more per 10,000 requests. It will consequently be necessary to periodically rotate the log files by moving or deleting the existing logs. This cannot be done while the server is running, because Apache httpd will continue writing to the old log file as long as it holds the file open. Instead, the server must be restarted after the log files are moved or deleted so that it will open new log files.

By using a graceful restart, the server can be instructed to open new log files without losing any existing or pending connections from clients. However, in order to accomplish this, the server must continue to write to the old log files while it finishes serving old requests. It is therefore necessary to wait for some time after the restart before doing any processing on the log files.