Submit a ticketCall us

Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.

 

 

 

 

Home > Success Center > Serv-U Managed File Transfer & Serv-U FTP Server > List of Serv-U events and event details

List of Serv-U events and event details

Table of contents

Updated April 11, 2017

Overview

This article discusses the Serv-U events functionality and lists the available Serv-U events and their details.

Environment

All Serv-U versions

Detail

With Serv-U supporting custom event handling, administrators can receive real-time updated information about the state of their file server. By licensing Serv-U MFT Server and activating this functionality, users can configure different types of triggers to activate actions within Serv-U. For details on how to configure Serv-U events, see Configure Serv-U events.

 

The following lists all events and their functions:

Server events

  • Server Start - Triggered by Serv-U starting, whether by starting the Serv-U service or starting Serv-U as an application.
  • Server Stop - Triggered by Serv-U shutting down, whether from service or application-level status. This event will only trigger for graceful stops.

Server and domain events

  • Domain Start - Triggered by a Serv-U Domain starting, via the Enable Domain setting in the Domain Details > Settings menu or as part of normal server startup.
  • Domain Stop - Triggered by a Serv-U Domain stopping, via the Enable Domain setting in the Domain Details > Settings menu or as part of normal server startup.
  • Session Connection - Triggered by a new TCP session connection.
  • Session Disconnect - Triggered by a TCP session disconnection.
  • Session Connection Failure - Triggered by a failed session connection attempt.
  • Log File Deleted - Triggered by the automatic deletion of a log file, according to logging settings.

Server, domain, user and group events

  • User Login - Triggered by the login of a user account.
  • User Logout - Triggered by the logout of a user account.
  • User Login Failure - Triggered by a failed login. A failed login is any connection attempt to Serv-U that fails, whether due to invalid credentials, or a session disconnect before authentication, either due to an incorrect username, incorrect password, incorrect SSH key pair (for SFTP Public Key Authentication), or all of the above.
  • User Password Change - Triggered by the change of a password for a user account, either by an administrator or by the user (if permitted).
  • User Password Change Failure - Triggered by a failed password change attempt.
  • User Enabled - Triggered by enabling a user account that was previously disabled.
  • User Disabled - Triggered by disabling a user account that was previously enabled.
  • User Deleted - Triggered deleting a user account by a remote administrator, in an ODBC database, or in the local Management Console.
  • User Added - Triggered by creating a user account by a remote administrator, in an ODBC database, or in the local Management Console.
  • Password Recovery Sent - Triggered by a successful password recovery by an end user or by an administrator.
  • Password Recovery Failed - Triggered by a failed password recovery attempt, either due to lack of email address in the user account or lack of permissions.
  • Password Stale - Triggered by a stale password, as configured in Limits & Settings, that is going to expire.
  • User Auto Disable - Triggered by automatic disabling of a user account, as configured by a user's Automatically Disable date.
  • User Auto Deleted - Triggered by automatic deletion of a user account, as configured by a user's Automatically Delete date.
  • User Pre-disable - Triggered by upcoming disabling of a user account, as configured in the user's Automatically Disable date and the Days before automatically disabling account to trigger the pre-disable event limit.
  • User Pre-delete - Triggered by upcoming deletion of a user account, as configured in the user's Automatically Delete date and the Days before automatically deleting account to trigger the pre-delete event limit.
  • User Email Set - Triggered by a user or administrator setting the email address for a user account.
  • User Email Set Error - Triggered by a failed attempt by a user or administrator to set the email address for a user account.
  • IP Blocked - Triggered by a failed login attempt due to an IP Access rule.
  • IP Blocked Time - Triggered by a failed login attempt due to an IP Access rule that was automatically added by brute force settings, configured in Domain Limits & Settings or Server Limits & Settings.
  • IP Auto Added To Access Rules - Triggered by automatic addition of an IP Access rule due to a user triggering the brute force settings.
  • Too Many Sessions - Triggered by more sessions logging in to the server than are permitted, per the Limits & Settings for the user account, group, domain, or server.
  • Too Many Session On IP - Triggered by more sessions logging in to the server from a specific IP address than are permitted, per the Limits & Settings for the user account, group, domain, or server.
  • File Uploaded - Triggered by a file uploaded to Serv-U. This event triggers for partial uploads if the upload session terminated with a successful message and no data corruption.
  • File Upload Failed - Triggered by a failed file upload to Serv-U.
  • File Download - Triggered by a file downloaded from Serv-U.
  • File Download Failed - Triggered by a failed file download from Serv-U.
  • File Deleted - Triggered by deleting a file on the Serv-U server by a user.
  • File Moved - Triggered by moving a file on the Serv-U server by a user.
  • Directory Created - Triggered by creating a directory.
  • Directory Deleted - Triggered by deleting a directory.
  • Directory Changed - Triggered by changing the current working directory.
  • Directory Moved - Triggered by moving a directory to a new location.
  • Over Quota - Triggered by going over disk quota space. The current quota space is shown in the user account, in the Limits & Settings menu.
  • Over Disk Space - Triggered by exceeding the Max Dir Size configured for a Dirctory Access rule. The current disk space is shown with the AVBL FTP command, or using the Directory Properties option in the HTTP/HTTPS Web Client and FTP Voyager JV.

 

 

 

Last modified
00:13, 12 Apr 2017

Tags

Classifications

Public