You are not logged in.

#1 2009-09-19 19:55:22

ozeta
Member
Registered: 2007-11-01
Posts: 63

vsftpd, wrong configuration or else? server doesn't start!

hi, i followed  wiki.archlinux.org for vsftpd configuration, but i think the daemon doesn't start and i don't know why.

when i launch the daemon with

#/etc/rc.d/xinetd start

i see the [done] flag, but if i do

# netstat -tulpen, the result is:

Active Internet connections (only servers)                                                                                
Proto Recv-Q Send-Q Local Address           Foreign Address         State       User       Inode      PID/Program name    
tcp        0      0 0.0.0.0:515             0.0.0.0:*               LISTEN      0          2204812    31636/xinetd        
tcp        0      0 0.0.0.0:5801            0.0.0.0:*               LISTEN      1000       386108     20718/Xvnc          
tcp        0      0 0.0.0.0:5901            0.0.0.0:*               LISTEN      1000       386107     20718/Xvnc          
tcp        0      0 0.0.0.0:52719           0.0.0.0:*               LISTEN      1000       2066108    11679/python        
tcp        0      0 0.0.0.0:6001            0.0.0.0:*               LISTEN      1000       386104     20718/Xvnc          
tcp        0      0 0.0.0.0:16500           0.0.0.0:*               LISTEN      0          1814626    28588/sshd          
tcp        0      0 127.0.0.1:6010          0.0.0.0:*               LISTEN      1000       2181522    27878/2             
tcp        0      0 0.0.0.0:58846           0.0.0.0:*               LISTEN      1000       2066104    11679/python
tcp        0      0 :::52719                :::*                    LISTEN      1000       2066110    11679/python
tcp        0      0 ::1:6010                :::*                    LISTEN      1000       2181521    27878/2
udp        0      0 0.0.0.0:51478           0.0.0.0:*                           1000       2066130    11679/python
udp        0      0 5.217.204.239:41759     0.0.0.0:*                           1000       2066134    11679/python
udp        0      0 39.255.91.74:33725      0.0.0.0:*                           1000       2065577    9516/hamachi
udp        0      0 39.255.91.74:55254      0.0.0.0:*                           1000       2066133    11679/python
udp        0      0 0.0.0.0:52719           0.0.0.0:*                           1000       2066113    11679/python
udp        0      0 0.0.0.0:6771            0.0.0.0:*                           1000       2066132    11679/python
udp        0      0 :::52719                :::*                                1000       2066114    11679/python

this is my vsftpd.conf with the wiki's parameters:


# Example config file /etc/vsftpd.conf
#
# Use this to use vsftpd in standalone mode, otherwise it runs through (x)inetd
#listen=YES
#
# 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.
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.
#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/vsftpd.log
#
# 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.
# 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().
#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. To listen on IPv4 and IPv6
# sockets, you must run two copies of vsftpd whith two configuration files.
# Make sure, that one of the listen options is commented !!
#listen_ipv6=YES

tcp_wrappers=YES
pam_service_name=vsftpd
chroot_local_user=YES
guest_enable=YES
guest_username=virtual
virtual_use_local_privs=YES

can anybody help me? thank you smile

Offline

#2 2009-09-19 20:36:13

opotonil
Member
Registered: 2009-09-12
Posts: 34

Re: vsftpd, wrong configuration or else? server doesn't start!

Can this be the problem?

http://bbs.archlinux.org/viewtopic.php?id=66301

and you have:

# Use this to use vsftpd in standalone mode, otherwise it runs through (x)inetd
#listen=YES

and

# 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

Bye.

Last edited by opotonil (2009-09-19 20:41:30)

Offline

#3 2009-09-20 12:51:15

ozeta
Member
Registered: 2007-11-01
Posts: 63

Re: vsftpd, wrong configuration or else? server doesn't start!

hi, i tried to uncomment the option but the problem is still here, and now i can't launch both the daemons (xinetd and vsftpd) sad

Last edited by ozeta (2009-09-20 13:02:24)

Offline

#4 2009-09-20 14:20:22

neddie_seagoon
Member
Registered: 2009-08-23
Posts: 121

Re: vsftpd, wrong configuration or else? server doesn't start!

Try to comment out both listen= options:
# Use this to use vsftpd in standalone mode, otherwise it runs through (x)inetd
#listen=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

Then you should be able to start xinetd, and connect to port 21 (may also need to edit hosts.allow). Post any connection errors after doing this.

Offline

#5 2009-09-20 15:48:28

ozeta
Member
Registered: 2007-11-01
Posts: 63

Re: vsftpd, wrong configuration or else? server doesn't start!

[root@muletto ozeta/] # /etc/rc.d/xinetd start
:: Starting xinetd                                                                                                    [FAIL]


nothing..and there are'nt no logs in /var/log  :S

Offline

Board footer

Powered by FluxBB