Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm using redhat 9.0 and proftpd 1.2.81 and i have install
proftpd-standalone-1.2.8-2 and proftpd-1.2.8-2.i386.rpm. But when i check the status of proftpd the error is shown: proftpd dead but subsys locked
I have try to delete the file /var/lock/subsys/proftpd
But it doesn't work. How can i do it?
Did you have any luck figuring this out?
I ask because I ran into this same problem yesterday, and wound up removing proftpd from the system and installing vsftpd instead. That worked, but we don't know why the first server failed. I see from other posts in this forum that others have had these problems -- and have had them with vsftpd as well. The common thread seems to be Red Hat. Hmm...
i think it may be the host name problem
because i don't have type any host name in the installation process
of red hat 9. So that it have problem.
Then i reinstall the redhat 9 and type the host name in the installation process, that is no problem.
Quote:
Originally posted by eflester Did you have any luck figuring this out?
I ask because I ran into this same problem yesterday, and wound up removing proftpd from the system and installing vsftpd instead. That worked, but we don't know why the first server failed. I see from other posts in this forum that others have had these problems -- and have had them with vsftpd as well. The common thread seems to be Red Hat. Hmm...
When I had this problem it was on a computer that had a host name assigned during installation. I have an idea that the problem is in RH9 itself, and it may be that your reinstall cleared that glitch, but I don't know enough about the structure of the OS to guess what' s actually going on.
I am very new to Linux in general and to linux networking.
I am having a different problem getting my proftp running:
[root@jmormLinux etc]# proftpd -n -d 4
jmormLinux - Failed binding to 0.0.0.0, port 21: Address already in use
jmormLinux - Check the ServerType directive to ensure you are configured correctly.
jmormLinux - Failed binding to 0.0.0.0, port 21: Address already in use
You'll get this if there is something already running on port 21...
Try netstat -tanp and see what is listening there.
Then ps ax to find it's PID, and either killall name or kill -9 PID to kill it off.
A hunch would be an xinetd based ftp service...
Do chkconfig --list and see what services are enabled
Do chkconfig name off to turn the xinetd ones off.
Last edited by peter_robb; 11-24-2003 at 04:25 PM.
Apr 1 19:02:25 sun proftpd[3802]: sun.xxxx.be - Failed binding to 0.0.0.0, port 21: Address already in use
Apr 1 19:02:25 sun proftpd[3802]: sun.xxxx.be - Check the ServerType directive to ensure you are configured correctly.
The problem was due to the fact that inetd was listening of port 21, which is precisely the port use by proftp.
Here is the content of my the proftpd.conf file:
[root@sun etc]# more /etc/proftpd.conf
# This is a basic ProFTPD configuration file (rename it to
# 'proftpd.conf' for actual use. It establishes a single server
# and a single anonymous login. It assumes that you have a user/group
# "nobody" and "ftp" for normal operation and anon.
ServerName "ProFTPD Default Installation"
ServerType inetd
DefaultServer on
# Allow FTP resuming.
# Remember to set to off if you have an incoming ftp for upload.
AllowStoreRestart on
# Port 21 is the standard FTP port.
Port 21
# Umask 022 is a good standard umask to prevent new dirs and files
# from being group and world writable.
Umask 022
# 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 under which the server will run.
User nobody
Group nogroup
# To cause every FTP user to be "jailed" (chrooted) into their home
# directory, uncomment this line.
#DefaultRoot ~
# Normally, we want files to be overwriteable.
<Directory />
AllowOverwrite on
</Directory>
# Needed for NIS.
PersistentPasswd off
# Default root can be used to put users in a chroot environment.
# As an example if you have a user foo and you want to put foo in /home/foo
# chroot environment you would do this:
#
# DefaultRoot /home/foo foo
Include /etc/proftpd-anonymous.conf
My problem came from Servertype which was Standalone and which should have been inetd (as I use inetd and do not run proftpd as daemon)
Finally, my proftpd-xinetd file looks like this:
[root@sun etc]# more /etc/xinetd.d/proftpd-xinetd
# default: off
# description: proftpd server, xinetd version. \
# Don't run the standalone version if you run \
# this!
service ftp
{
disable = no
socket_type = stream
wait = no
user = root
server = /usr/sbin/in.ftpd
log_on_success += DURATION USERID
log_on_failure += USERID
nice = 10
}
I have also deleted the FTP file from that directory.
Now you just have to adapt proftpd.conf file in order to grant / deny access to users.
I have spent evenings during 2 weeks trying to solve this. Hope this will also work fine for you with those indications.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.