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 > Reading Serv-U log file

Reading Serv-U log file

Table of contents
Created by Richard Casey, last modified by MindTouch on Jun 23, 2016

Views: 148 Votes: 0 Revisions: 6

Overview

Serv-u creates logs at server and domain level, these can be adjusted to your preferred settings and saved to a specified location.

Environment

Serv-U V12 and later

Steps

  • The kind of message displayed in Serv-U logs is indicated by either the number at the beginning of the log when logging to a file, or when viewing the Serv-U Log Screen. When viewing the Serv-U log screen, the type of message is color coded. The following legend describes each message type and the corresponding color.
    SUlog.PNG
  • The following lists the types of messages by the number displayed in brackets, which also correspond to each color in the above legend.
    [1] - System Messages (Green)
    [2] - Security Messages (Blue)
    [3] - IP Names (Orange)
    [4] - ODBC Calls (Purple)
    [5] - ODBC Errors (Red background)
    [10] - Downloads (Grey Background)
    [11] - Uploads (Grey Background)
    [12] - File Deletions (Grey Background)
    [13] - File and Directory Renames (Grey Background)
    [14] - Directory Creations (Grey Background)
    [15] - Directory Deletions (Grey Background)
    [20] - FTP Commands (Yellow Background)
    [21] - FTP Replies (Yellow Background)
    [30] - SSH Commands (Orange Background)
    [31] - SSH Replies (Orange Background)
    [40] - HTTP Commands (Blue Background)
    [41] - HTTP Replies (Blue Background)
     

  • The following is a copy for a typical connection and upload log of Serv-U.

    [1] Fri 03Jan03 09:13:20 - Starting FTP Server...
    [1] Fri 03Jan03 09:13:20 - FTP Server listening on port number 21, IP 127.0.0.1

     

    This is Serv-U confirming that it is listening on port 21 on the IP Address 127.0.0.1. If you see any errors here the FTP client will not be able to connect. Two very common errors are "Port 21 in Use" and "Trying to listen on non-existent IP Address". There are separate knowledge base articles to address each of these.
     

    For this knowledge base, the first two sections of each line entry have been removed. This information simply dictates the time and date when activity is occurring.

     

    Connected to 127.0.0.1 (Local address 127.0.0.1)
    220 Serv-U FTP Server v4.2 for WinSock ready...

     

    The first thing Serv-U does when an FTP client logs in is introduce itself. This is the Server ID tag. For security reasons, some FTP Admins customize this Server ID tag so the actual server name is hidden. Knowledge Base article 1206 walks you through customizing this.

    WARNING: Some FTP clients (like FTP Voyager) rely on this Server ID tag to identify the server.

     

    Any time an FTP client logs into Serv-U, a user name and password are sent from the client and be approved by Serv-U. Above, you see a correct user name and password being sent to Serv-U.

     

    USER test
    331 User name okay, need password.
    PASS xxxxx
    User TEST logged in
    230 User logged in, proceed.

     

    The FEAT command (short for Feature ) is the way for the FTP client to ask the server if it supports anything special. The server then responds with any unique commands it supports.

     

    FEAT

    211-Extension supported
    MDTM
    MDTM YYYYMMDDHHMMSS[+-TZ] filename
    SIZE
    SITE PSWD;EXEC;SET;INDEX;ZONE;CHMOD;MSG
    REST STREAM
    211 End
     

    The FTP client navigates to the home directory assigned by Serv-U. This particular user's home directory is C:\.


    REST 100
    350 Restarting at 100. Send STORE or RETRIEVE.
    350 Restarting at 100. Send STORE or RETRIEVE. REST 0
    350 Restarting at 0. Send STORE or RETRIEVE.
    PWD
    257 "/c:" is current directory.
    CWD /c:
    250 Directory changed to /c:
     
    In order for the FTP client to see what is in the home directory, a data connection has to be established. There are two different methods for this to happen, PASV and PORT. For a breakdown of the differences please review Knowledge Base article 1138.

    LIST -T
    150 Opening ASCII mode data connection for /bin/ls.
    226 Transfer complete.

     

    The message "226 Transfer complete" confirms the data connection was successfully established. You may now view the files in the home directory.

     

    STOR DCP00618.JPG

     

    In this part of the log the FTP client has started uploading a file. The command used to do this is STOR and the file being uploaded is called DCP00618.JPG.

     

    Receiving file c:\dcp00618.jpg

     

    This is the server confirming that the file is being received.

     

    150 Opening BINARY mode data connection for DCP00618.JPG.
    Received file c:\dcp00618.jpg successfully (6026 Kb/sec - 234469 bytes)
    226 Transfer complete.

     

    Finally, the server confirms that the transfer is complete.

     

    MDTM 20021206160948 /c:/DCP00618.JPG
    253 Date/time changed okay.

     

    This is one of the additional features (displayed in the FEAT reply) that Serv-U supports. This feature allows the time stamp on the file to remain the same when the file is uploaded. In most cases, whenever a file is uploaded to the FTP server, it is given a new time stamp.

     

    QUIT
    221 Goodbye!
    Closing connection for user TEST (00:00:01 connected)

     

    This is the user disconnecting from the server.

 

 

 

Last modified
02:36, 23 Jun 2016

Tags

Classifications

Public