Solutions

"Control socket timeout while post processing FTP log source file" error in Reporter 9.x

Solutions ID:    KB4560
Version:    1.0
Status:    Published
Published date:    08/09/2011
 

Problem Description

You may experience an issue where an FTP log source in Reporter 9.x is unloading itself for no apparent reason.

The latest Reporter journal log files may show errors similar to these:

No log lines found in FTP log source file 'Web logs:Web Logs1:/ftproot/main_reporter.log'

Control socket timeout while post processing FTP log source file 'Web logs:Web Logs1:/ftproot/main_reporter.log' most likely caused by the firewall on this host preventing large FTP transfers

Failed to post process FTP log source file 'Web logs:Web Logs1:/ftproot/main_reporter.log'

Unloaded log source 'Web logs:Web Logs1' due to fatal error

 

NOTE: The Reporter journal logs are located by default in:

Windows: C:\Program Files\Blue Coat Reporter 9\journal

Linux: /opt/bc/reporter/journal

Resolution

This is caused by a corrupt or invalid log file being present on the FTP server that Reporter is getting access log files from.

As indicated in the error messages, the file "/ftproot/main_reporter.log" on the FTP server is causing this issue.

Remove the offending file from the FTP server and restart the log source in Reporter. At this point the log source should stay loaded.

If it is still unloading itself, check the journal logs again, as there may be multiple corrupt files on your FTP server.

 

Links to other articles:

For a complete list of other Journal entries and what they mean, seeKB3460

For a list of compatible FTP servers, see FAQ837


Rate this Page

Please take a moment to complete this form to help us better serve you.

Did this document help answer your question?
 
 
If you are finished providing feedback, please click the RATE CONTENT button. Otherwise, please add more detail in the following text box and then click RATE CONTENT.
 
 

Your response will be used to improve our document content.

Ask a Question