Edge SWG (ProxySG) Access Log uploads failing with SCP as a transport to Cloud SWG or Reporter
Article ID: 388981
Updated On:
Products
Issue/Introduction
After upgrading to SGOS version 7.3.24.x, 7.4.4.x, 7.4.5.x, 7.4.6.x, 7.4.7.x or 7.4.8.1, the access log uploads are not completing successfully with SCP. Other log transport formats, such as FTP and Kafka, are not affected.
The file sizes reported by the Edge SWG Event logs do not match the uploaded size on the logging server.
Environment
SGOS version 7.3.24.x, 7.4.4.x, 7.4.5.x, 7.4.6.x, 7.4.7.x or 7.4.8.1 with access log uploads using SCP
This issue affects customers using Hosted Reporting with Cloud SWG and Reporter.
Resolution
The issue is resolved in the following versions of SGOS, or later:
- SGOS 7.3.25.1 SWG Edition
- SGOS 7.4.6.3 SWG Edition
- SGOS 7.4.7.3 SWG Edition
- SGOS 7.4.8.2 SWG Edition
- SGOS 7.4.9.1 SWG Edition
If upgrading to one of the above releases or newer releases is not feasible, the workaround is to use a different upload method other than SCP, if possible, or downgrade back to an unaffected release.
This issue has been observed with access log files containing 50,000 lines or greater so another workaround would be to restrict upload log size and increase upload frequency. Since every access log may have different logging fields, some trial and error must be done to determine log size that will not become corrupt.
For more information on Access Logging parameters, see:
Feedback
