Your browser does not allow storing cookies. We recommend enabling them.

SSH Tectia 
PreviousNextUp[Contents] [Index]

    About This Document >>
    Installing SSH Tectia Server >>
    Getting Started >>
    Configuration >>
    Authentication >>
    Application Tunneling >>
        Debug Mode
    Man Pages
    Advanced Options >>
    Log Messages >>

Debug Mode

When run in debug mode, SSH Tectia Server outputs useful troubleshooting information to stderr. To run the server in the debug mode, do the following steps:

  1. Stop the server by issuing a signal to it:
    # kill `cat /var/run/`
    or, if the directory /var/run/ does not exist, use:
    # kill -kill `cat /etc/ssh2/`
  2. Start the server in the debug mode by using the following command:
    # /usr/local/sbin/sshd2 -d<filter>
    This should be the first argument on the command line. The syntax of the filter is as follows:
    Module is the wanted software module (ssh2sftp, for example) and level is the wanted debug level (a number from 0 to 10). Debug level 10 shows all available information, level 0 shows nothing. For example, the following command shows level 4 for all and level 10 for the SFTP server:
    # /usr/local/sbin/sshd2 -d"*=4,Ssh2Sftp*=10" 
    The debug information can be also directed to a file:
    # /usr/local/sbin/sshd2 -d"*=4,Ssh2Sftp*=10" > debugfile.txt
    For more information on the command-line options, see the sshd2 man page.
  3. Connect to the server with a Secure Shell client. The client should also be run in the debug mode.

PreviousNextUp[Contents] [Index]

[ Contact Information | Support | Feedback | SSH Home Page | SSH Products ]

Copyright © 2010 SSH Communications Security Corp.
This software is protected by international copyright laws. All rights reserved.
Copyright Notice

Want to see how PrivX can help your organisation?

Are you a DEVELOPER accessing cloud hosts, are you a IT ADMIN managing access & credentials in your corporation, are you BUSINESS MANAGER and want to save money or are you responsible of IT SECURITY in DevOps