You are not logged in.

#1 2009-03-16 00:40:35

grimrider
Member
From: Ohio
Registered: 2008-12-09
Posts: 60

Vsftpd no xinetd 500 OOPS: could not bind listening IPv4 socket

ok, as stated above, im not using xinetd, and have followed the wiki all the way through for not using it, and i am still getting the 500 OOPS: could not bind listening IPv4 socket error.  heres my config file:

# 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

Offline

#2 2009-03-16 12:44:40

.:B:.
Forum Fellow
Registered: 2006-11-26
Posts: 5,819
Website

Re: Vsftpd no xinetd 500 OOPS: could not bind listening IPv4 socket

Does

pgrep vsftpd

return anything? I had that same error too and it turned out vsftpd was already running, despite the daemon script returning a big fat red FAILED (or FAIL, doesn't happen every day to me tongue).


Got Leenucks? :: Arch: Power in simplicity :: Get Counted! Registered Linux User #392717 :: Blog thingy

Offline

#3 2009-03-18 15:25:46

Army
Member
Registered: 2007-12-07
Posts: 1,784

Re: Vsftpd no xinetd 500 OOPS: could not bind listening IPv4 socket

Oh noooooooooo big_smile big_smile

I have the same problem and B, you seem to be right about it! But it's strange, I did a

ls /var/run/daemons

and vsftpd wasn't in the list, so I thought, it doesn't work.. Is there maybe a problem with the rc.d-script?

Last edited by Army (2009-03-19 23:43:52)

Offline

#4 2009-03-19 07:55:17

grimrider
Member
From: Ohio
Registered: 2008-12-09
Posts: 60

Re: Vsftpd no xinetd 500 OOPS: could not bind listening IPv4 socket

sorry how long it took.  pgrep vsftpd didnt return anything, and ls /var/run/daemon says no such file or dir.  im pulling my hair out over this one mad

Offline

#5 2009-03-19 12:12:25

.:B:.
Forum Fellow
Registered: 2006-11-26
Posts: 5,819
Website

Re: Vsftpd no xinetd 500 OOPS: could not bind listening IPv4 socket

It's daemons, not daemon.

And frankly, if you google your exact error, it turns up quite some suggestions to try wink.


Got Leenucks? :: Arch: Power in simplicity :: Get Counted! Registered Linux User #392717 :: Blog thingy

Offline

#6 2009-03-19 21:33:59

grimrider
Member
From: Ohio
Registered: 2008-12-09
Posts: 60

Re: Vsftpd no xinetd 500 OOPS: could not bind listening IPv4 socket

oh, trust me, ive googled this for about a month, and tried everything ive found.  most of the google suggestions lead to something else using ports 20 and 21, but when i run netstat -tpan, nothing is using either of those ports.

[root@grim-server ~]# netstat -tpan
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 0.0.0.0:843             0.0.0.0:*               LISTEN      1515/famd
tcp        0      0 0.0.0.0:111             0.0.0.0:*               LISTEN      1414/portmap
tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN      1797/httpd
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      1735/sshd
tcp        0     52 192.168.1.102:22        192.168.1.100:3811      ESTABLISHED 1844/0
[root@grim-server ~]#

Offline

#7 2009-03-20 00:01:58

.:B:.
Forum Fellow
Registered: 2006-11-26
Posts: 5,819
Website

Re: Vsftpd no xinetd 500 OOPS: could not bind listening IPv4 socket

You have the capability kernel module loaded?


Got Leenucks? :: Arch: Power in simplicity :: Get Counted! Registered Linux User #392717 :: Blog thingy

Offline

#8 2009-03-20 02:12:56

grimrider
Member
From: Ohio
Registered: 2008-12-09
Posts: 60

Re: Vsftpd no xinetd 500 OOPS: could not bind listening IPv4 socket

capability kernel module??? i think that means no lol

EDIT

i tried modpbrobe capability, and that didnt work.  does it use a different name?

Last edited by grimrider (2009-03-20 02:22:59)

Offline

#9 2009-03-20 03:17:40

grimrider
Member
From: Ohio
Registered: 2008-12-09
Posts: 60

Re: Vsftpd no xinetd 500 OOPS: could not bind listening IPv4 socket

Army wrote:

Oh noooooooooo big_smile big_smile

I have the same problem and B, you seem to be right about it! But it's strange, I did a

ls /var/run/daemons

and vsftpd wasn't in the list, so I thought, it doesn't work.. Is there maybe a problem with the rc.d-script?

i looked through it, and there doesnt seem to be anything different from the one on a friends working computer, or anything wrong with either of them....

Offline

Board footer

Powered by FluxBB