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

Solution

Overview

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

Cause
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, see000014639

For a list of compatible FTP servers, see FAQ837

Workaround
Additional Information
Bug Number
InQuira Doc IdKB4560
Attachment

Article Feedback

Did this Article solve your issue?
Additional Comments:
 
Previous MonthNext Month
SunMonTueWedThuFriSat