Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
21 is open. (Don't know about 20, but I can tell it to listen on 21, so that's ok.)
I'm using Mandrake 9.0, on the binghamton U campus network, but they don't block anything that I know of (esp. since the port is open). No routers, &c of my own. I'm rather stumped, actually :-/
Uninstall vsftp and put proftpd back on. Then, check the log files (which are defined in the proftpd.conf file) and post em up. On my system it's located /var/log/proftpd.log and /var/log/xfer.log
So you might see what's going on there. Also, you might look at other logs, maybe there is one for your vsftp that you could look at. Either way, just try to find a reason on why it won't connect, it'll make troubleshooting that much easier If you have questions on the files, post up the files so we can take a look at em.
Ok, no problem. But before I do that, I took a look through the daemon error logs in general, and /var/log/daemons/errors has been getting this:
Apr 4 01:31:58 localhost xinetd: bind failed (Address already in use (errno = 98)). service = ftp
Apr 4 14:49:45 localhost xinetd: warning: can't get client address: Transport endpoint is not connected
Apr 4 14:51:29 localhost xinetd: bind failed (Address already in use (errno = 98)). service = ftp
Apr 4 15:01:01 localhost xinetd: warning: can't get client address: Transport endpoint is not connected
for the last however long it's been.
I'm not entirely sure what all that means, but if it's not helpful then I'll just do the reinstall.
Since your port is open, you can ftp into your localhost just fine, and you are sure you are using the correct IP to ftp in with (check here ) I am becoming quite stumpt without those error log files (/var/log/proftpd.log and /var/log/xferlog)
The main difference from ftp://localhost and ftp://actualip is your request. ftp://localhost goes straight from your command to your computer, it processes the request locally and gives instant feedback. ftp://actual-ip sends the request out of your PC to your ISP's server (or similar) translates the IP to your line, sends the request back into your computer (very simplified, but shows that the request actually leaves the box). So it would appear that if:
is working fine and
isn't, then it would be a network problem much more than an application error. The proftp error log will show you that, or xferlog might; either way, that's something to go with for now
Unfortunately, I'm not home now, and won't be back at my computer 'til tomorrow night. When I get home, though, I'll post those error logs and see if we can't get this thing figured out. Thank you very much!
OK, I uninstalled vsftp, reinstalled proftpd and configured it to start via xinetd (http://forums.devshed.com/archive/33/2002/07/4/40004)
Now, no matter what IP I try to connect to, I get "connection refused" (even 127.0.0.1). There isn't anything in /var/log/xferlog, but /var/log/daemons/errors ends with this:
Apr 7 16:01:09 localhost proftpd: localhost.localdomain - unable to set daemon groups: Operation not permitted
Apr 7 16:01:09 localhost proftpd: localhost.localdomain - unable to set uid to 65534, current uid: 500
Apr 7 16:02:19 localhost proftpd: localhost.localdomain - unable to set daemon groups: Operation not permitted
Apr 7 16:02:19 localhost proftpd: localhost.localdomain - unable to set uid to 65534, current uid: 500
There's no sight of a proftpd error log anywhere, unless it's under some other name :-/.
I tried that, still running it through xinetd...I think there was still something wrong in that setup, so I changed the ServerType back to standalone, stopped xinetd, and started proftpd. Now, at least, I'm back to the errors I was getting initially.
Here's the output of proftpd.log, once I changed it back to standalone (it wasn't outputting anything before that, which makes me think that it wasn't getting started at all):
The "Login Successful" entry is where I connected using "ftp 127.0.0.1". The error messages are when I tried "ftp 188.8.131.52".
Still nothing in xferlog, as I can't connect enough to transfer anything
Last edited by rose_bud4201; 04-07-2003 at 09:20 PM.
Here is what I get when I try to ftp into your IP:
bash-2.05a$ ftp 184.108.40.206
Connected to 220.127.116.11.
500 Sorry, no server available to handle request on bing93.onondaga-a.binghamton.edu
What that looks like to me is that either your uni has some setup that won't allow you to run an FTP server (maybe several PC's share the same outside IP, via some sort of NAT), or your proftpd.conf file isn't setup correctly (post it up so I/we can take a look).
# 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"
# Port 21 is the standard FTP port.
# Umask 022 is a good standard umask to prevent new dirs and files
# from being group and world writable.
# 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).
# Set the user and group under which the server will run.
# To cause every FTP user to be "jailed" (chrooted) into a directory,
# uncomment this line.
# Normally, we want files to be overwriteable.
# A basic anonymous configuration, no upload directories. If you do not
# want anonymous users, simply delete this entire <Anonymous> section.
# User ftp
# Group ftp
# # We want clients to be able to login with "anonymous" as well as "ftp"
# UserAlias anonymous ftp
# # Limit the maximum number of anonymous logins
# MaxClients 10
# # We want 'welcome.msg' displayed at login, and '.message' displayed
# # in each newly chdired directory.
# DisplayLogin welcome.msg
# DisplayFirstChdir .message
# # Limit WRITE everywhere in the anonymous chroot
# <Limit WRITE>