When we're asked to troubleshoot a problem, we often ask users to send us a 'clean debug log'. What we mean by 'clean debug log' is a log file that contains, as far as possible, only information related to the problem at hand.
The steps for producing a 'clean debug log' are as follows:
SHORT VERSION:
- Set the logging level to Debug
- Stop the CompleteFTP service
- Delete the existing log files
- Start the CompleteFTP service again
- Reproduce the error
- Send us the (zipped) log files (diagnostics.log and config.log, or ServiceRecent.log in pre-7.0 versions)
LONG VERSION:
- Set the logging level to Debug:
- Open CompleteFTP Manager and connect.
- Select Monitoring from the side menu.
- Select the Log Files tab..
- Set the Logging level to 'Debug' and click 'Apply Changes'.
- Close CompleteFTP Manager.
- Stop the CompleteFTP service:
- Open the Services item in the Windows Control Panel.
- Select CompleteFTP and hit the stop button.
- Delete the existing log file:
- Open the Windows start menu
- Find and open the CompleteFTP group in the start menu
- Select 'Log Files' from the group. This opens Windows explorer at the correct location.
- Find 'diagnostics.log', 'config.log' and/or 'ServiceRecent.log' and delete (or rename) them.
- Start the CompleteFTP service again:
- Open the Services item in the Windows Control Panel.
- Select CompleteFTP and hit the start button.
- Reproduce the error:
- Do whatever it was that caused the error. E.g. connecting with an SFTP client and getting an error.
- Send us the (zipped) log file:
- Select 'Log Files' from the CompleteFTP start menu.
- Zip up the diagnostics.log and config.log files (ServiceRecent.log in pre-7.0 versoins) and e-mail them to us