CacheFlow Event Logs showing diagnostic auto-upload errors

book

Article ID: 168165

calendar_today

Updated On:

Products

CacheFlow Appliance Software

Issue/Introduction

Recent changes to the BlueCoat infrastructure has changed the way CacheFlow appliances upload diagnostic data.

Cause

There is no longer a default Service Request number that all CacheFlow's can upload their diagnostic data to. Errors such as the ones below will be visible in the CacheFlow's Event Log.

"Stats Worker: received status Socket receive error during HTTPS put operation"

"Diagnostic auto-upload (System information): Communication error while attempting HTTPS upload, will retry upload later"

"Diagnostic auto-upload (Core image context): Communication error while attempting HTTPS upload, will retry upload later"

"Diagnostic auto-upload (Snapshot): Communication error while attempting HTTPS upload, will retry upload later"

"Diagnostic auto-upload (Event log): Communication error while attempting HTTPS upload, will retry upload later"

"Diagnostic auto-upload (Verification of service request number): Communication error while attempting HTTPS upload, will retry upload later"


 

Resolution

To stop the messages from being displayed all diagnostic uploads must be disabled.

#conf t

#(config)access-log

#(config access-log)diagnostic-upload disable

#(config access-log)exit

#(config)diagnostics

#(config diagnostics)auto-upload off


If there is an issue that needs to be investigated on the CacheFlow then diagnostic uploads can be re-enabled. It is important to note that the Service Request number must be changed to a valid number. This number will be provided when a Service Request has been opened with BlueCoat technical support.

#conf t

#(config)diagnostics

#(config diagnostics)sr-number x-xxxxxxxxx

#(config diagnostics)auto-upload normal

#(config diagnostics)exit

#(config)access-log

#(config access-log)diagnostic-upload enable