Go Back   DaemonForums > FreeBSD > FreeBSD Ports and Packages

FreeBSD Ports and Packages Installation and upgrading of ports and packages on FreeBSD.

Thread Tools Display Modes
  #1   (View Single Post)  
Old 10th June 2010
map7 map7 is offline
Fdisk Soldier
Join Date: Jun 2008
Posts: 75
Default vsftpd not starting

I've followed heaps of tutorials now and I still cannot get vsftpd to start.

Here is what I've done so far:

Install vsftp

# cd /usr/ports/*/vsftpd
# make install (select rc-ng script)


# cd /usr/local/etc
# vi vsftpd.conf

Here is my vsftpd.conf file:
# Example config file /usr/local/etc/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).
# Uncomment this to allow local users to log in.
# Uncomment this to enable any form of FTP write command.
# 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)
# 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.
# Uncomment this if you want the anonymous FTP user to be able to create
# new directories.



# Activate directory messages - messages given to remote users when they
# go into a certain directory.
# Activate logging of uploads/downloads.
# Make sure PORT transfer connections originate from port 20 (ftp-data).
# 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
                                                                                              25,1          Top
# 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!
# You may override where the log file goes if you like. The default is shown
# below.
# 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.
# You may change the default value for timing out an idle session.
# You may change the default value for timing out a data connection.
# 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.
# 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.
# 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.
# 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.
# 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.
# (default follows)
# 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().
                                                                                              53,1          69%
# (default follows)
# 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.
# 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.
# This directive enables listening on IPv6 sockets. To listen on IPv4 and IPv6
# sockets, you must run two copies of vsftpd with two configuration files.
# Make sure, that one of the listen options is commented !!

# If using vsftpd in standalone mode, uncomment the next two lines:

Add the following to /etc/rc.conf


Create the /etc/pam.d/vsftpd

auth required /usr/local/lib/pam_pwdfile.so pwdfile /etc/vsftpd_login.db
account required /usr/lib/pam_permit.so

Add login names:

htpasswd -c -b /etc/vsftpd_login.db USERNAME PASSWORD

Try starting it using the rc.d script
/usr/local/etc/rc.d/vsftpd start
/usr/local/etc/rc.d/vsftpd status
vsftpd is not running

Even though I have logging on it doesn't create a log file named /var/log/vsftpd.log

I have noticed that I can connect to the sftp, but this is using the sshd. Do I have to disable sftp to get vsftpd working?

I don't really need it to run stand alone is it easier to start it within inetd? If so what line do I enter into the inetd.conf file? As I've tried this:
ftp stream tcp nowait root /usr/local/libexec/vsftpd vsftpd

and that didn't work.

I've tried starting it manually:
# /usr/local/libexec/vsftpd /usr/local/etc/vsftpd.conf

that doesn't work and there is no output on the screen to tell me what went wrong.

Can anyone help. I'm sure I'm just missing something small.
Reply With Quote
  #2   (View Single Post)  
Old 10th June 2010
Carpetsmoker's Avatar
Carpetsmoker Carpetsmoker is offline
Real Name: Martin Tournoij
Tcpdump Spy
Join Date: Apr 2008
Location: Ireland
Posts: 2,245

You're starting vsftpd in chroot, does this directory exist? Try commenting this line out, does it work then?

Try disabling this.

I don't really need it to run stand alone is it easier to start it within inetd?
The difference is that running vsftpd standalone means there is always a vsftpd process running. Running it from inetd means that inetd will start a process only when someone tries to connect.
It doesn't matter for your problem.
Reply With Quote

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
How to configure VSFTPD? Sunsawe FreeBSD Ports and Packages 8 26th September 2009 02:28 PM
VSFTPD SERVER disappearedng FreeBSD General 1 21st October 2008 04:12 AM
VSFTPd: pid file kostromin FreeBSD Ports and Packages 0 4th July 2008 08:35 AM
Samba NOT STARTING pcfxer FreeBSD General 11 13th May 2008 09:29 AM

All times are GMT. The time now is 11:27 AM.

Powered by vBulletin® Version 3.8.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Content copyright © 2007-2010, the authors
Daemon image copyright ©1988, Marshall Kirk McKusick