Export of SSL Session Logs from the SSL Visibility appliance results in no
ssl_session_log.*.bin files being exported. For example, the exported
.tgz file might contain only the following files:
SSL Visibility sets a size limit of 32MB for a session log file and total disk usage of 8GB for all the session logs.
It is possible that the first session log is added to the export list, but is deleted due to disk usage limitations before actually being added to the
.tgz archive. In that case, no session log file will be exported.
First, validate that the total size of the ssl_session_log.*.bin files are close to the limit of 8GB. Then, delay the
From time by 1-2 hours in the SSL Session Logs export screen.
Generate a diagnostics file using Monitor > Diagnostics in the Web Management user interface. Selecting Platform under "Current State" in the Diagnostics screen would suffice.
Open the downloaded diagnostics .tgz file and look for disk_stats.txt in the Platform directory. Check the timestamp of files listed under /opt/sslv/data/ssl. Calculate the total size of the ssl_session_log.*.bin files and see if it is close to 8GB.
Open Monitor > SSL Session Log and click the Export icon. The Session Log Export window will include both "From" and "To" dates, which should match the timestamps of the oldest and latest session log BIN files respectively.
Delay the From time by 1-2 hours. For example, if the From time is 2:00:00pm, delay it to 3:00:00pm or 4:00:00pm and you should be able to export the SSL Session Logs.
Imported Document ID: 000030119
Subscribing will provide email updates when this Article is updated. Login is required.
Thanks for your feedback. Let us know if you have additional comments below. (requires login)
Subscribed to the Article.
Unable to subscribe
Thanks for your additional feedback !!!
Enterprise Support Virtual Agent
Rate Me :
Tell us more:
Welcome! My name is Sami, the Enterprise Support Virtual Agent answering technical support questions.