ProxySG Access-log failed to upload to a remote server
Last Updated July 13, 2018
Access-log upload to FTP or any other server stops functioning
If there is a communication error between ProxySG and FTP (File Transfer Protocol) server, the access log gets accumulated on disk until it reaches 20GB. The default behavior of SG is to stop logging if the sum of all log sizes reaches 20GB. To resume the access-log upload, check the following:
Verify the ProxySG Upload client configuration
Goto Configuration -> Access Logging -> Logs -> Upload Client and ensure FTP service and accounts are correctly configured. Use the "Test Upload" button to verify the connectivity between SG and remote server.
Check the access log size on ProxySG
Goto Statistics -> Access Logging -> Log Size. If the logging has stopped due to disk full, you will see the highlighted message.
To reinitialize access logging after it has exceeded its disk capacity:
Go to https://appliance_ip_address:8082/Accesslog/directory/ and download the logs to back up the data.
Go to the CLI (Command line interface) and delete the log files.
For example, to delete the log files listed under "Main" use the following CLI commands:
#(config access-log)edit log main
#(config log main)commands delete-logs
Go to Configuration > Access Logging > General and uncheck Enable Access Logging and click Apply.
Click on Enable Access Logging and click Apply.
Go to Configuration > Access Logging > Logs > Upload Client and click Test Upload.
Go to the event log and verify that the access log uploaded successfully.
Imported Document ID: 000007717
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe