SSH Communications Security
Previous Next Up [Contents] [Index]

    About This Document>>
    Introduction to SSH Secure Shell >>
    Configuring SSH Secure Shell >>
    Authentication >>
    Log Messages
        Log Message Reference >>
            User Authentication - Common
            User Authentication - Host-Based
            User Authentication - Keyboard-Interactive PAM
            User Authentication - Keyboard-Interactive Password
            User Authentication - Keyboard-Interactive
            User Authentication - Kerberos TGT
            User Authentication - Kerberos
            User Authentication - PAM
            User Authentication - Password
            User Authentication - Public Key
            User Authentication - SecurID
            Certificate-specific code
            SFTP Server
            Agent Forwarding
            Session Channels
            SSH1 Agent Forwarding
            Port Forwarding
            X11 Forwarding
            Common Code
            Host Key I/O
            General Server Log Messages
            SFTP
    Using SSH Secure Shell >>
    Tool Syntax>>
    Technical Specifications >>

General Server Log Messages

Disconnect: Host not allowed to connect

Disallowed connect from denied host. '<message>'

The server has disconnected the client because the client is not allowed to connect.

Disconnect: Protocol error

Protocol error in [local|remote]: '<message>'

Disconnecting because of a protocol error in local or remote end.

Disconnect: Key exchange failed

Key exchange failed in [local|remote]: '<message>'

Disconnecting because key exchange failed in local or remote end.

Disconnect: Illegal code

RESERVED (this is an illegal code) in [local|remote]:
'<message>'

Disconnecting, with illegal code as reason.

Disconnect: MAC failed

MAC failed in [local|remote], disconnecting: '<message>'

Disconnecting because MAC failed in local or remote end.

Disconnect: Compression error

compression error in [local|remote], disconnecting:
'<message>'

Disconnecting because of a compression error.

Disconnect: Service not available

service not available: '<message>'

Disconnecting because a requested service was not available.

Disconnect: Protocol version not supported

protocol version not supported in [local|remote]:
'<message>'

Disconnecting because the protocol version was not supported.

Disconnect: Host key not verified

host key not verifiable in [local|remote]: '<message>'

Disconnecting because the host key could not be verified.

Disconnect: Connection was lost

connection lost: '<message>'

Disconnecting because the connection was lost.

Disconnect: Disconnected by application

disconnected by application in [local|remote]:
'<message>'

Disconnected by application.

Disconnect: Too many connections

too many connections : '<message>'

Disconnected because the internal connection limit was exceeded.

Disconnect: User authentication failed

User authentication failed: '<message>'

Disconnected because the user authentication failed. This message should only occur when the other end is of version 2.0.13 or older.

Disconnect: Authentication cancelled by user

authentication cancelled by user: '<message>'

Disconnected because the authentication was cancelled by the user.

Disconnect: No more authentication methods

no more authentication methods on [local|remote]:
'<message>'

Disconnected because of running out of authentication methods. This generally means that the client failed in all the authentication methods available on the server.

Disconnect: Illegal user name

illegal user name : '<message>'

Disconnected because the user name was illegal.

Disconnect: Unknown reason

Unknown reason code '<reason-code>' for disconnect. msg:
'<message>'

Disconnected, reason code unknown.

Idle timeout exceeded

Idle timeout exceeded.

The idle timeout limit was exceeded.

Remote protocol version string received

Remote protocol version: <version-string>

The server has received the remote protocol version string from the client.

User authenticated

User <login-name> (uid <uid-number>), coming from <host>,
authenticated.

A general message stating that the user has successfully authenticated herself.

User authenticated, root login

ROOT LOGIN: User <login-name> (uid <uid-number>), coming from
<host>, authenticated.

General message stating that a superuser has successfully authenticated herself.

User authentication failed

Authentication failed for user <login-name>,
coming from <host>.

An user tried to log in, but failed the user authentication.

User logged out

Logout for user <login-name>.

The specified user has now logged out or has been logged out.

Login grace time exceeded

LoginGraceTime exceeded.

The LoginGraceTime value was exceeded. This means that the client did not succeed in logging in during time limit defined by the configuration option LoginGraceTime.

Connection received

connection from "<host>" (listen port: <listen-port>)

The server has received a connection from a host.

Connection received in interface

connection from "<host>" (listen iface: <address>:<port>)

The server has received a connection from a host to a port on specific interface.

Refusing connection: too many open connections

Refusing connection from "<host>". Too many open connections
(max <maximum-connections>, now open <open-connections>).

The server has refused a connection because it would have otherwise exceeded the limit of simultaneously open connections.

Denied connection because of tcp_wrappers

Denied connection from <connection-originator> by tcp
wrappers.

The server has refused a connection because it was denied by tcp_wrappers.

Forking for new connection failed

Forking a server for a new connection failed.

The server tried to fork to handle a new connection, but the forking failed.

Server warning

WARNING: <message>

A warning was received from the server.

Fatal server error

FATAL ERROR: <message>

The server has encountered a fatal error condition.

SIGHUP-handler received an invalid signal

Invalid signal received by SIGHUP-handler.

Server's SIGHUP-handler received an illegal signal.

License file error

License file error: <message>

The server encountered an error when checking the license file.

Server restarting

restarting...

The server is restarting.

Server starting in inetd mode

Starting daemon in inetd mode.

The server is starting in inetd mode.

Server created a listener

Listener created on  <address>:<port>.

The server has successfully created a listener.

Server created an UDP listener

UDP Listener created on  <address>:<port>.

The server has successfully created an UDP listener.

Setsid failed

setsid: <error-message>

A call to setsid failed in the server.

Server running

Daemon is running.

The server process has successfully performed all initialization operations and is now listening for connections.

Previous Next Up [Contents] [Index]


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

Copyright © 2003 SSH Communications Security Corp.
All rights reserved.
Copyright Notice