Error in setting up FTP: job for vsftpd service failed because the control process exited with error code. See “systemctl status vsftpd.service” and “journalctl -xe” for details.
Solution:
First check whether our port 21 is occupied:
[root@VM-12-16-centos lighthouse]# lsof -i:21
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
pure-ftpd 16235 root 4u IPv4 1014289 0t0 TCP *:ftp (LISTEN)
pure-ftpd 16235 root 5u IPv6 1014290 0t0 TCP *:ftp (LISTEN)
We need to kill the process pure-ftpd with process number 16235:
[root@VM-12-16-centos lighthouse]# kill -9 16235
[root@VM-12-16-centos lighthouse]# lsof -i:21
If there is no prompt, it means that kill
is successful!
The next step is to solve the vsftpd configuration file:
[root@VM-12-16-centos lighthouse]# sudo vim /etc/vsftpd/vsftpd.conf
The content of vsftpd configuration file is, which can be copied directly. Just change the IP:
# Example config file /etc/vsftpd/vsftpd.conf
#
# The default compiled in settings are fairly paranoid. This sample file
# loosens things up a bit, to make the ftp daemon more usable.
# Please see vsftpd.conf.5 for all compiled in defaults.
#
# READ THIS: This example file is NOT an exhaustive list of vsftpd options.
# Please read the vsftpd.conf.5 manual page to get a full idea of vsftpd's
# capabilities.
#
# Allow anonymous FTP?(Beware - allowed by default if you comment this out).
anonymous_enable=NO
#
# Uncomment this to allow local users to log in.
# When SELinux is enforcing check for SE bool ftp_home_dir
local_enable=YES
#
# Uncomment this to enable any form of FTP write command.
write_enable=YES
#
# Default umask for local users is 077. You may wish to change this to 022,
# if your users expect that (022 is used by most other ftpd's)
local_umask=022
#
# Uncomment this to allow the anonymous FTP user to upload files. This only
# has an effect if the above global write enable is activated. Also, you will
# obviously need to create a directory writable by the FTP user.
# When SELinux is enforcing check for SE bool allow_ftpd_anon_write, allow_ftpd_full_access
#anon_upload_enable=YES
#
# Uncomment this if you want the anonymous FTP user to be able to create
# new directories.
#anon_mkdir_write_enable=YES
#
# Activate directory messages - messages given to remote users when they
# go into a certain directory.
dirmessage_enable=YES
#
# Activate logging of uploads/downloads.
xferlog_enable=YES
#
# Make sure PORT transfer connections originate from port 20 (ftp-data).
connect_from_port_20=YES
#
# If you want, you can arrange for uploaded anonymous files to be owned by
# a different user. Note! Using "root" for uploaded files is not
# recommended!
#chown_uploads=YES
#chown_username=whoever
#
# You may override where the log file goes if you like. The default is shown
# below.
#xferlog_file=/var/log/xferlog
#
# If you want, you can have your log file in standard ftpd xferlog format.
# Note that the default log file location is /var/log/xferlog in this case.
xferlog_std_format=YES
#
# You may change the default value for timing out an idle session.
#idle_session_timeout=600
#
# You may change the default value for timing out a data connection.
#data_connection_timeout=120
#
# It is recommended that you define on your system a unique user which the
# ftp server can use as a totally isolated and unprivileged user.
#nopriv_user=ftpsecure
#
# Enable this and the server will recognise asynchronous ABOR requests. Not
# recommended for security (the code is non-trivial). Not enabling it,
# however, may confuse older FTP clients.
#async_abor_enable=YES
#
# By default the server will pretend to allow ASCII mode but in fact ignore
# the request. Turn on the below options to have the server actually do ASCII
# mangling on files when in ASCII mode. The vsftpd.conf(5) man page explains
# the behaviour when these options are disabled.
# Beware that on some FTP servers, ASCII support allows a denial of service
# attack (DoS) via the command "SIZE /big/file" in ASCII mode. vsftpd
# predicted this attack and has always been safe, reporting the size of the
# raw file.
# ASCII mangling is a horrible feature of the protocol.
#ascii_upload_enable=YES
#ascii_download_enable=YES
#
# You may fully customise the login banner string:
#ftpd_banner=Welcome to blah FTP service.
#
# You may specify a file of disallowed anonymous e-mail addresses. Apparently
# useful for combatting certain DoS attacks.
#deny_email_enable=YES
# (default follows)
#banned_email_file=/etc/vsftpd/banned_emails
#
# You may specify an explicit list of local users to chroot() to their home
# directory. If chroot_local_user is YES, then this list becomes a list of
# users to NOT chroot().
# (Warning! chroot'ing can be very dangerous. If using chroot, make sure that
# the user does not have write access to the top level directory within the
# chroot)
chroot_local_user=YES
chroot_list_enable=YES
# (default follows)
chroot_list_file=/etc/vsftpd/chroot_list
#
# You may activate the "-R" option to the builtin ls. This is disabled by
# default to avoid remote users being able to cause excessive I/O on large
# sites. However, some broken FTP clients such as "ncftp" and "mirror" assume
# the presence of the "-R" option, so there is a strong case for enabling it.
#ls_recurse_enable=YES
#
# When "listen" directive is enabled, vsftpd runs in standalone mode and
# listens on IPv4 sockets. This directive cannot be used in conjunction
# with the listen_ipv6 directive.
listen=YES
#
# This directive enables listening on IPv6 sockets. By default, listening
# on the IPv6 "any" address (::) will accept connections from both IPv6
# and IPv4 clients. It is not necessary to listen on *both* IPv4 and IPv6
# sockets. If you want that (perhaps because you want to listen on specific
# addresses) then you must run two copies of vsftpd with two configuration
# files.
# Make sure, that one of the listen options is commented !!
#listen_ipv6=YES
pam_service_name=vsftpd
userlist_enable=YES
tcp_wrappers=YES
local_root=/var/ftp/test
allow_writeable_chroot=YES
pasv_enable=YES
pasv_address=xxx.xxx.xxx.xxx#Please change it to the public IP of your lightweight application server, you need to change it yourself
pasv_min_port=40000
pasv_max_port=45000
Finally, take a look at your vsftp on state:
[root@VM-12-16-centos lighthouse]# systemctl status vsftpd.service
Read More:
- [Solved] Job for network.service failed because the control process exited with error code. See “systemctl st
- [Solved] Job for docker.service failed because the control process exited with error code. After changing the docker configuration
- Nginx Startup Error: Job for nginx.service failed because the control process exited with error code
- [Solved] docker Startup Error: Job for docker.service failed because the control process exited with error code
- Virtual machine failed to start network service error: ob for network.service failed because the control process exited with error code
- [Solved] Linux Service Start Error: *.service: Main process exited, code=exited, status=203/EXEC
- Job for network.service failed [How to Solve]
- Centos7.6 vsftpd access error, 500 oops [How to Solve]
- [Solved] mongo Startup Error: ERROR: child process failed, exited with error number 1
- Linux Install Docker Error: Failed to restart docker.service: Unit docker.service not found.
- [Solved] E Sub-process usrbindpkg returned an error code (1)
- [Solved] YarnClientSchedulerBackend: Yarn application has already exited with state FAILED
- Ubuntu sub process/usr/bin/dpkg returned an error code (1) solution
- [Solved] ERROR: Linux route delete command failed: external program exited with error status: 2
- [Solved] Node uploads files to FTP server error: timed out while making data connection
- How to Fix Linux sub process /usr/bin/dpkg returned an error code (1)
- [Solved] nova-compute.log Error: Instance failed block device setup
- [Solved] Failed to Setup IP tables: Unable to enable SKIP DNAT rule: (iptables failed: iptables –wait -t na…
- ERROR: Failed to Setup IP tables: Unable to enable SKIP DNAT rule
- Linux system service command error: Failed to allocate directory watch: Too many open files