Submit a ticketCall us

Announcing NCM 7.7
With NCM 7.7, you can examine the rules that make up an access control list for a Cisco ASA device. Then you can apply filters to display only rules that meet the specified criteria, order the rules by line number or by the hit count, and much more.
See new features and improvements.

Home > Success Center > Serv-U Managed File Transfer & Serv-U FTP Server > Enable debug mode

Enable debug mode

Table of contents

Overview

This article provides information on enabling the debug mode to do advanced logging if there are some issues that need in-depth investigation such as performance and product errors.

Environment

All Sev-U versions

Steps

  1. Right click the tray icon and select Stop Serv-U to shut down any running Serv-U processes.
  2. Right click the tray icon and uncheck the box labeled "Start Serv-U as Service".
  3. Run Serv-U in debug mode from the terminal:
    a. Open the terminal.
    b. Go to the directory where Serv-U is installed using the CD command.  For example, CD C:\Program Files\RhinoSoft\Serv-U.
    c. Run Serv-U using the following command:
        Serv-U.exe –debug -socketlogging
  4. Right click the tray icon and select Start Management Console.
  5. In the Management Console, go to Domain Activity > Settings and turn on all commands for logging (all boxes should be selected).
  6. Repeat the test.
  7. Restart Serv-U:
    a. Right click the tray icon and select Stop Serv-U to shut down any running Serv-U processes.
    b. Right click the tray icon and check the box labeled "Start Serv-U as Service" to run Serv-U as service.
    c. Right click the tray icon and select Start Serv-U to run the application.

The debug logs will be found in ProgramData\Rhinosoft\Serv-U\DebugLogs\Domain_Name-WorkerThreadLog.txt.

It is important to restart Serv-U after the test.

For more information on enabling logging reference, see the Setting Up Serv-U’s Log article.

Last modified
09:01, 13 Jul 2017

Tags

Classifications

Public