Access logs that start early uploads or that small log files are constantly uploading when not wanted. This occurs although the ProxySG appliance is set to periodically upload log files.
The appliance starts an early upload of the access log(s) if any of the following conditions are true:
Important: If setting up access logging and configure the main log to be uploaded, be sure to configure other protocols that are intercepted, such as SSL, P2P, and IM. If not, configure them, the main log is uploaded in a regular and timely manner, but the other protocols and logs are not uploaded at all. Over time these other log files grow to the point where the main access log has less room to grow and an early upload occurs because the global early upload limit is hit.
In the Management Console, select Configuration > Access Logging > General > Global Settings. Increase the value for "Start an early upload if the log reaches xxxxx megabytes" and save changes. This helps alleviate the problem in the short term, but the problem could recur unless further action is taken. Review the Resolution in this article to permanently alleviate the problem.
Record the values for AL_STATS_0030 and AL_STATS_0031 for each log. Then, perform one of the following resolutions.
Perform this resolution if wanting to retain the data collected in the current logs.
Perform this resolution if not wanting to retain the data collected in the current logs.
Step 1: Change the Default Log to <None> for protocols without an upload client.
Step 2: Delete the current logs.
Note: In this example, the SSL protocol is writing data to the SSL log. The commands are for deleting the access logs for the SSL protocol.
Enter configuration commands, one per line. End with CTRL-Z.
ProxySG#(config access-log)edit log ssl
ProxySG#(config log ssl)commands delete-logs
ProxySG#(config log ssl)