How to create Proxy's new access log to replace the existing access log that is having an issue uploading.
search cancel

How to create Proxy's new access log to replace the existing access log that is having an issue uploading.

book

Article ID: 223307

calendar_today

Updated On:

Products

ProxySG Software - SGOS

Issue/Introduction

This is a scenario where the proxy failed to upload the access log to the server because the access log is too big to be uploaded, like in this case, its about 20GB in size.

Even though the proxy did try to upload the access log, it still keep failing due to a network issue.

Even restarting the proxy, disabling the access logging and try to download the access log to save on a local drive also failed.

Deleting the access log is not an option for the time being.

So a workaround is to create a new access log to replace the existing access log in order to make sure the access log can be processed by Reporter or other server.

 

Environment

Release : 6.7.x and 7.x

Component : Access Logging.

Resolution

Below are the steps to create a new access log to replace the existing access log. In this example, we are using the 'main' access log as the existing access log and the new access log is named as 'main2'.

1. Create new access log (eg: 'main2').

    Go to Configuration > Access Logging > Logs > Logs tab.

    Check the current 'main' access log format (eg: bcreportermain_v1_custom).

    https://api-broadcom-ca.wolkenservicedesk.com/attachment/get_attachment_content?uniqueFileId=wAwNYHSJmzNUAGLt0/baOg==

 

      Then click on the 'New' button and set the following settings. Make sure the format is the same as the existing 'main' access log.

    https://api-broadcom-ca.wolkenservicedesk.com/attachment/get_attachment_content?uniqueFileId=S3lLz8NBmH1bFj1kVNgBfA==

 

2. Set the proxy protocol to use the new access log.

    Go to Configuration > Access Logging > General > Default Logging tab.

    Edit all the protocol that used the old 'main' access log to the new 'main2' access log.

    https://api-broadcom-ca.wolkenservicedesk.com/attachment/get_attachment_content?uniqueFileId=LJCZgl4VQ/nufxltuLtkgg==

 

      For example, the HTTP protocol log new setting will look like the one below.

    https://api-broadcom-ca.wolkenservicedesk.com/attachment/get_attachment_content?uniqueFileId=aoratx1HThFITX78plrBHQ==

    https://api-broadcom-ca.wolkenservicedesk.com/attachment/get_attachment_content?uniqueFileId=ADkpDkpbrovsS3z7nTmHRQ==

 

    Then proceed with the rest of the protocols that used the old 'main' access log.

 

3. Setup the access logging upload client for the new access log.

    Take note of the existing 'main' access log upload client FTP settings first.

    Go to Configuration > Access Logging > Logs > Upload Client tab.

    Set the 'Log:' to 'main'.

    Click on the 'Settings' to see the settings for the FTP upload client and take note of these settings.

    https://api-broadcom-ca.wolkenservicedesk.com/attachment/get_attachment_content?uniqueFileId=HUhiFkcJEEvgRFwRzKshiw==

   

    Then Cancel the Settings window and proceed to set the new access log FTP upload client settings following the existing FTP upload client settings for the 'main' access log.

    Set the 'Log:' to the new access log (eg: 'main2').

    Set the 'Client type:' to FTP Client and set the 'Settings' the same as the 'main' access log.

    https://api-broadcom-ca.wolkenservicedesk.com/attachment/get_attachment_content?uniqueFileId=GNvZGg6psUgVZSO0nTTgoA==

 

    Then do a 'Test Upload'.

 

4. Set the same settings for the 'Upload Schedule' as well for the new access log (main2).

    Go to Configuration > Access Logging > Logs > Upload Schedule tab

    Take note of the settings for the old or 'main' access log and then set the same for the new access log.

 

5. Disable the upload client for the old 'main' access log.

    Go to Configuration > Access Logging > Logs > Upload Client tab.

    Set the 'Log:' to 'main'.

    Set the 'Upload client type' to 'None'.

    https://api-broadcom-ca.wolkenservicedesk.com/attachment/get_attachment_content?uniqueFileId=CqudbH9JwixG8nWtGRNU6w==