I have ProFTPd service installed on my server which runs Ubuntu Linux 14.04 . I don't know why ProFTPd closes by itself. I have enough RAM and CPU and I really don't know why this happens. I also checked ProFTPd config file I still don't figure it out.

# /etc/proftpd/proftpd.conf -- This is a basic ProFTPD configuration file.
# To really apply changes, reload proftpd after modifications, if
# it runs in daemon mode. It is not required in inetd/xinetd mode.

# Includes DSO modules
Include /etc/proftpd/modules.conf

# Set off to disable IPv6 support which is annoying on IPv4 only boxes.
UseIPv6             on
# If set on you can experience a longer connection delay in many cases.
IdentLookups            off

ServerName          "Debian"
ServerType          standalone
DeferWelcome            off

MultilineRFC2228        on
DefaultServer           on
ShowSymlinks            on

TimeoutNoTransfer       600
TimeoutStalled          600
TimeoutIdle         1200

DisplayLogin                    welcome.msg
DisplayChdir                .message true
ListOptions                 "-l"

DenyFilter          \*.*/

# Use this to jail all users in their homes 
#DefaultRoot ~

# RequireValidShell     off

# Port 21 is the standard FTP port.
Port                21

# In some cases you have to specify passive ports range to by-pass
# firewall limitations. Ephemeral ports can be used for that, but
# feel free to use a more narrow range.
# PassivePorts                  49152 65534

# If your host was NATted, this option is useful in order to
# allow passive tranfers to work. You have to use your public
# address and opening the passive ports used on your firewall as well.
# MasqueradeAddress

# This is useful for masquerading address with dynamic IPs:
# refresh any configured MasqueradeAddress directives every 8 hours
<IfModule mod_dynmasq.c>
# DynMasqRefresh 28800

# To prevent DoS attacks, set the maximum number of child processes
# to 30.  If you need to allow more than 30 concurrent connections
# at once, simply increase this value.  Note that this ONLY works
# in standalone mode, in inetd mode you should use an inetd server
# that allows you to limit maximum number of processes per service
# (such as xinetd)
MaxInstances            30

# Set the user and group that the server normally runs at.
User                proftpd
Group               nogroup

# Umask 022 is a good standard umask to prevent new files and dirs
# (second parm) from being group and world writable.
Umask               022  022
# Normally, we want files to be overwriteable.
AllowOverwrite          on

# Uncomment this if you are using NIS or LDAP via NSS to retrieve passwords:
# PersistentPasswd      off

# This is required to use both PAM-based authentication and local passwords
# AuthOrder         mod_auth_pam.c* mod_auth_unix.c

# Be warned: use of this directive impacts CPU average load!
# Uncomment this if you like to see progress and transfer rate with ftpwho
# in downloads. That is not needed for uploads rates.
# UseSendFile           off

TransferLog /var/log/proftpd/xferlog
SystemLog   /var/log/proftpd/proftpd.log

# Logging onto /var/log/lastlog is enabled but set to off by default
#UseLastlog on

# In order to keep log file dates consistent after chroot, use timezone info
# from /etc/localtime.  If this is not set, and proftpd is configured to
# chroot (e.g. DefaultRoot or <Anonymous>), it will use the non-daylight
# savings timezone regardless of whether DST is in effect.
#SetEnv TZ :/etc/localtime

<IfModule mod_quotatab.c>
QuotaEngine off

<IfModule mod_ratio.c>
Ratios off

# Delay engine reduces impact of the so-called Timing Attack described in
# http://www.securityfocus.com/bid/11430/discuss
# It is on by default. 
<IfModule mod_delay.c>
DelayEngine on

<IfModule mod_ctrls.c>
ControlsEngine        off
ControlsMaxClients    2
ControlsLog           /var/log/proftpd/controls.log
ControlsInterval      5
ControlsSocket        /var/run/proftpd/proftpd.sock

<IfModule mod_ctrls_admin.c>
AdminControlsEngine off

# Alternative authentication frameworks
#Include /etc/proftpd/ldap.conf
#Include /etc/proftpd/sql.conf

# This is used for FTPS connections
#Include /etc/proftpd/tls.conf

# Useful to keep VirtualHost/VirtualRoot directives separated
#Include /etc/proftpd/virtuals.conf

# A basic anonymous configuration, no upload directories.

# <Anonymous ~ftp>
#   User                ftp
#   Group               nogroup
#   # We want clients to be able to login with "anonymous" as well as "ftp"
#   UserAlias           anonymous ftp
#   # Cosmetic changes, all files belongs to ftp user
#   DirFakeUser on ftp
#   DirFakeGroup on ftp
#   RequireValidShell       off
#   # Limit the maximum number of anonymous logins
#   MaxClients          10
#   # We want 'welcome.msg' displayed at login, and '.message' displayed
#   # in each newly chdired directory.
#   DisplayLogin            welcome.msg
#   DisplayChdir        .message
#   # Limit WRITE everywhere in the anonymous chroot
#   <Directory *>
#     <Limit WRITE>
#       DenyAll
#     </Limit>
#   </Directory>
#   # Uncomment this if you're brave.
#   # <Directory incoming>
#   #   # Umask 022 is a good standard umask to prevent new files and dirs
#   #   # (second parm) from being group and world writable.
#   #   Umask               022  022
#   #            <Limit READ WRITE>
#   #            DenyAll
#   #            </Limit>
#   #            <Limit STOR>
#   #            AllowAll
#   #            </Limit>
#   # </Directory>
# </Anonymous>

# Include other custom configuration files
Include /etc/proftpd/conf.d/
DefaultRoot ~
AllowOverwrite on

Any ideas about how can I prevent it shutting down by itself?

Thank you.

  • Do you run it in daemon mode or inetd/xinetd mode ? – Pyrophorus Sep 15 '14 at 15:35
  • Review the file /var/log/syslog or enter the command dmesg from the command line. The information in those files should help you identify the error or give other information that will imply what else to look for. If ProFTPd is like most programs, it will log errors into the standard syslog file. Alternatively, it may have its own log in the /var/log directory. – Suncat2000 Sep 15 '14 at 19:30

@Adrian answer is what helped me find what I needed, but in more detail of what I did that totally worked.

The key for me was that I installed monit as a solution that could monitor the proftpd process and make sure it was running at all times, if it detects the service not running then it would start it.


Make sure to update and upgrade first

apt-get update
apt-get upgrade


Download and install monit

apt-get install monit


cd /etc/monit/
vi monitrc

find the commented line set httpd port 2812 and and uncomment/change it to

set httpd port 2812

remove "and" if you want to be able to access it NOT from localhost only but instead remotely

Then ONLY uncomment line

allow admin:monit

This is the user authentication credentials you will need to login, change them as you want

Then add this in the file, I added mine at the bottom of the page. Change your port number to match yours, otherwise default is 21

check process proftpd with pidfile /var/run/proftpd.pid
start program = "/etc/init.d/proftpd start"
stop program  = "/etc/init.d/proftpd stop"
if failed port 21 protocol ftp then restart

Then just restart service

/etc/init.d/monit restart

You're done and... your welcome! Here is a nice pic to show you what it looks like

Monit Dashboard Example

You can access the web interface from youripordomain.com:2812

Monit will constantly check for the service and if not running will start it. Great tool for any service you want to check.

Side Note

If you start the receive a "Execution failed | Does not exist" status in monit then check to make sure that proftpd PID matches in the PID file for proftpd.

First make sure proftpd is running /etc/init.d/proftpd start

Then type top in terminal and find the PID of proftpd currently running

Go to /var/run/proftpd.PID and make sure the PID in that file matches the one in top. If it does not then change it in the file and restart monit

/etc/init.d/monit restart


Maybe this comment help you:


The problem is due to ProFTPD not stopping in time to be restarted.

The workaround is to edit the service file, to add a retry.


Find this line:

start-stop-daemon --stop --signal $SIGNAL --quiet --pidfile "$PIDFILE"

Change to this:

start-stop-daemon --stop --signal $SIGNAL --retry 1 --quiet --pidfile "$PIDFILE"

This change solved it for me.

  • 1
    Keep in mind that there are several start-stop-daemon in the script (3 to be exact). Make sure the one you are selecting to edit is exactly as spcified from @Pavel – Cesar Bielich Mar 29 '16 at 22:14
  • What about system updates concerning the init script? – sjas Jun 1 '16 at 10:29

I found a solution to this.

Not sure if it is the best but it works for me.

I set up a monitor for proftpd services and in case proftps is detected as off I will call the proftpd startup command and that's it.

Hope this helps.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.