LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Software
User Name
Password
Linux - Software This 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.

Notices


Reply
  Search this Thread
Old 04-04-2003, 09:26 AM   #16
MasterC
LQ Guru
 
Registered: Mar 2002
Location: Salt Lake City, UT - USA
Distribution: Gentoo ; LFS ; Kubuntu
Posts: 12,612

Rep: Reputation: 64

A router. What's your network setup? Have you forwarded port 21 (or 20 for this other ftp server you've tried)?

Use probe my ports:
https://grc.com/x/ne.dll?bh0bkyd2

To see if 21 is open.

If it is, then we know that's not the problem. Tell me about your network setup, and also which distro it is you are trying this on.

Cool
 
Old 04-04-2003, 02:40 PM   #17
rose_bud4201
Member
 
Registered: Aug 2002
Location: St Louis, MO
Distribution: Xubuntu, RHEL, Solaris 10
Posts: 929

Original Poster
Rep: Reputation: 30
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 :-/
 
Old 04-04-2003, 04:00 PM   #18
MasterC
LQ Guru
 
Registered: Mar 2002
Location: Salt Lake City, UT - USA
Distribution: Gentoo ; LFS ; Kubuntu
Posts: 12,612

Rep: Reputation: 64
Ok, sorry to suggest this, but it's an idea...

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.

Cool
 
Old 04-04-2003, 04:06 PM   #19
rose_bud4201
Member
 
Registered: Aug 2002
Location: St Louis, MO
Distribution: Xubuntu, RHEL, Solaris 10
Posts: 929

Original Poster
Rep: Reputation: 30
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:
Code:
Apr  4 01:31:58 localhost xinetd[16452]: bind failed (Address already in use (errno = 98)). service = ftp
Apr  4 14:49:45 localhost xinetd[26711]: warning: can't get client address: Transport endpoint is not connected
Apr  4 14:51:29 localhost xinetd[26802]: bind failed (Address already in use (errno = 98)). service = ftp
Apr  4 15:01:01 localhost xinetd[26966]: 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.
Thanks!
Laura
 
Old 04-04-2003, 04:13 PM   #20
MasterC
LQ Guru
 
Registered: Mar 2002
Location: Salt Lake City, UT - USA
Distribution: Gentoo ; LFS ; Kubuntu
Posts: 12,612

Rep: Reputation: 64
Are you running your own DNS/bind server? Or just a normal network setup through the college, where you specify a remote DNS server in /etc/resolv.conf (or do you run DHCP to find your IP)?

Cool
 
Old 04-04-2003, 04:28 PM   #21
rose_bud4201
Member
 
Registered: Aug 2002
Location: St Louis, MO
Distribution: Xubuntu, RHEL, Solaris 10
Posts: 929

Original Poster
Rep: Reputation: 30
DHCP to get an IP on bootup.
 
Old 04-04-2003, 09:43 PM   #22
MasterC
LQ Guru
 
Registered: Mar 2002
Location: Salt Lake City, UT - USA
Distribution: Gentoo ; LFS ; Kubuntu
Posts: 12,612

Rep: Reputation: 64
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:
ftp localhost
is working fine and
ftp 1.2.3.4
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

Cool
 
Old 04-05-2003, 07:44 PM   #23
rose_bud4201
Member
 
Registered: Aug 2002
Location: St Louis, MO
Distribution: Xubuntu, RHEL, Solaris 10
Posts: 929

Original Poster
Rep: Reputation: 30
OK.
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!

Laura
 
Old 04-07-2003, 04:30 PM   #24
rose_bud4201
Member
 
Registered: Aug 2002
Location: St Louis, MO
Distribution: Xubuntu, RHEL, Solaris 10
Posts: 929

Original Poster
Rep: Reputation: 30
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:
Code:
Apr  7 16:01:09 localhost proftpd[2197]: localhost.localdomain - unable to set daemon groups: Operation not permitted 
Apr  7 16:01:09 localhost proftpd[2197]: localhost.localdomain - unable to set uid to 65534, current uid: 500 
Apr  7 16:02:19 localhost proftpd[2235]: localhost.localdomain - unable to set daemon groups: Operation not permitted 
Apr  7 16:02:19 localhost proftpd[2235]: 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 :-/.
 
Old 04-07-2003, 09:39 PM   #25
MasterC
LQ Guru
 
Registered: Mar 2002
Location: Salt Lake City, UT - USA
Distribution: Gentoo ; LFS ; Kubuntu
Posts: 12,612

Rep: Reputation: 64
You set that in your proftpd.conf file; mine is:
/var/log/proftpd.log and here is the entry in my conf file:
Code:
SystemLog                       /var/log/proftpd.log
TransferLog                     /var/log/xferlog
Cool
 
Old 04-07-2003, 10:03 PM   #26
rose_bud4201
Member
 
Registered: Aug 2002
Location: St Louis, MO
Distribution: Xubuntu, RHEL, Solaris 10
Posts: 929

Original Poster
Rep: Reputation: 30
ok, let me see what that generates
 
Old 04-07-2003, 10:18 PM   #27
rose_bud4201
Member
 
Registered: Aug 2002
Location: St Louis, MO
Distribution: Xubuntu, RHEL, Solaris 10
Posts: 929

Original Poster
Rep: Reputation: 30
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):

Code:
Apr 07 22:22:52 localhost.localdomain proftpd[6309] localhost.localdomain: ProFTPD 1.2.8 (stable) (built Wed Apr 2 00:11:46 EST 2003) standalone mode STARTUP
Apr 07 22:23:17 localhost.localdomain proftpd[6316] localhost.localdomain (localhost.localdomain[127.0.0.1]): FTP session opened.
Apr 07 22:23:22 localhost.localdomain proftpd[6316] localhost.localdomain (localhost.localdomain[127.0.0.1]): USER laura: Login successful.
Apr 07 22:23:24 localhost.localdomain proftpd[6316] localhost.localdomain (localhost.localdomain[127.0.0.1]): FTP session closed.
The "Login Successful" entry is where I connected using "ftp 127.0.0.1". The error messages are when I tried "ftp 128.226.198.93".
Still nothing in xferlog, as I can't connect enough to transfer anything

Last edited by rose_bud4201; 04-07-2003 at 10:20 PM.
 
Old 04-07-2003, 10:38 PM   #28
MasterC
LQ Guru
 
Registered: Mar 2002
Location: Salt Lake City, UT - USA
Distribution: Gentoo ; LFS ; Kubuntu
Posts: 12,612

Rep: Reputation: 64
I don't see any errors there... Are there actual errors in proftpd.log when you connect to ftp://128.226.198.93 ?

Or none at all, and syslog shows nothing either? How about /var/log/messages?

Cool
 
Old 04-07-2003, 10:41 PM   #29
MasterC
LQ Guru
 
Registered: Mar 2002
Location: Salt Lake City, UT - USA
Distribution: Gentoo ; LFS ; Kubuntu
Posts: 12,612

Rep: Reputation: 64
Here is what I get when I try to ftp into your IP:
Quote:
bash-2.05a$ ftp 128.226.198.93
Connected to 128.226.198.93.
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).

Cool
 
Old 04-08-2003, 02:11 AM   #30
rose_bud4201
Member
 
Registered: Aug 2002
Location: St Louis, MO
Distribution: Xubuntu, RHEL, Solaris 10
Posts: 929

Original Poster
Rep: Reputation: 30
Contents of /usr/local/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"
ServerAdmin "somebody@SomewhereNotHere.com"
ServerIdent off
ServerType standalone
DefaultServer off
SystemLog /var/log/proftpd.log
TransferLog /var/log/xferlog

# 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

<Global>
RequireValidShell off
LoginPasswordPrompt off
<Limit LOGIN>
DenyUser anonymous
</Limit>
MaxLoginAttempts 3
# To cause every FTP user to be "jailed" (chrooted) into a directory,
# uncomment this line.
DefaultRoot /var/www/UPLOADS
AllowStoreRestart on
AllowRetrieveRestart on
# Normally, we want files to be overwriteable.
<Directory /*>
AllowOverwrite on
</Directory>
</Global>

# A basic anonymous configuration, no upload directories. If you do not
# want anonymous users, simply delete this entire <Anonymous> section.
#<Anonymous ~ftp>
# 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>
# DenyAll
# </Limit>
#</Anonymous>
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

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 Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
X-server fatal error,KDM refused to start callitdctr Linux - Software 3 07-01-2005 09:46 AM
Start Fresh, but still that EVIL FATAL ERROR TheMadAd19 Linux - Newbie 1 02-27-2005 04:51 PM
Fatal Error, Cant Start X Using SuSE 9.1! Please Help! DozenEggs Linux - Newbie 1 07-24-2004 02:57 PM
XIO: fatal IO error 104. X server would not start after problem with Vmware noodle_mee Linux - Newbie 0 07-07-2004 11:48 PM
Upgraded to new kernel via redhat network and cannot start X. Fatal Server Error. Gen13 Red Hat 5 10-25-2003 01:09 AM


All times are GMT -5. The time now is 11:01 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration