Our Products:   CompleteFTP  edtFTPnet/Free  edtFTPnet/PRO  edtFTPj/Free  edtFTPj/PRO
0 votes
10k views
in CompleteFTP by (51.1k points)

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:

  1. Set the logging level to Debug
  2. Stop the CompleteFTP service
  3. Delete the existing log files
  4. Start the CompleteFTP service again
  5. Reproduce the error
  6. Send us the (zipped) log files (diagnostics.log and config.log, or ServiceRecent.log in pre-7.0 versions)


LONG VERSION:

  1. Set the logging level to Debug:
    1. Open CompleteFTP Manager and connect.
    2. Select Monitoring from the side menu.
    3. Select the Log Files tab..
    4. Set the Logging level to 'Debug' and click 'Apply Changes'.
    5. Close CompleteFTP Manager.
  2. Stop the CompleteFTP service:
    1. Open the Services item in the Windows Control Panel.
    2. Select CompleteFTP and hit the stop button.
  3. Delete the existing log file:
    1. Open the Windows start menu
    2. Find and open the CompleteFTP group in the start menu
    3. Select 'Log Files' from the group.  This opens Windows explorer at the correct location.
    4. Find 'diagnostics.log', 'config.log' and/or 'ServiceRecent.log' and delete (or rename) them.
  4. Start the CompleteFTP service again:
    1. Open the Services item in the Windows Control Panel.
    2. Select CompleteFTP and hit the start button.
  5. Reproduce the error:
    1. Do whatever it was that caused the error. E.g. connecting with an SFTP client and getting an error.
  6. Send us the (zipped) log file:
    1. Select 'Log Files' from the CompleteFTP start menu.
    2. Zip up the diagnostics.log and config.log files (ServiceRecent.log in pre-7.0 versoins) and e-mail them to us

Please log in or register to answer this question.

Categories

...