"Access Log (XXX): Log uploading failed. Remote filename: Not Applicable size: 2 KB."

Products

• ISG Proxy

Issue/Introduction

The following event logs are generated by Edge SWG:

2024-04-15 11:48:06-00:00UTC  "Access Log Custom (XXX): Socket error occured while sending data."  20 E000A:1  alog_stream_custom.cpp:135
2024-04-15 11:48:06-00:00UTC  "Access Log Custom (XXX): Closing TCP/IP connection."  0 E0000:96  alog_stream_custom.cpp:191
2024-04-15 11:48:06-00:00UTC  "Access Log (XXX): error in sending log data (no bytes sent from this queue), error code = -1 [32]"  0 E000A:96  alog_stream.cpp:2066
2024-04-15 11:48:06-00:00UTC  "Access Log (XXX): Log uploading failed.  Remote filename: Not Applicable size: 2 KB."  0 E0008:1 Mailed alog_manager.cpp:1288

Environment

Edge SWG configured to continuously upload access logs to remote server

Cause

During periods when there are no access logs to upload proxy keeps the TCP connection alive by sending TCP keep-alives. Other devices such as firewalls may have a timeout which forces them to terminate the TCP session if that session is idle for too long (e.g. 3600 seconds). 

Resolution

Make sure that your firewall is configured to keep idle TCP session between Edge SWG and access log server alive for extended period.