FTP not working anymore

[Puma]

Hello,

I installed my B3 and FTP port 21 works fine.

1. Installed screen and mc
2. installed hddtemp
3. changed bubbamon (workaround stat.php)

Now I cannot access with FTP anymore

Has someone a clou?

Puma

[Ubi]

can you ssh in?
--> nmap -p 21 localhost
-----> ftp localhost
---------> tail /var/log/pureftpd.log (or similar)

[Puma]

Hello,

Tried it but : command not found....

With a fresh install it works but after a while no connection.
I cannot find it in the log files.

Puma

[Ubi]

please do not send messages saying "tried it" if there is any uncertainty about what "it" may be.
I guess you mean that your nmap command failed. so:

Code: Select all

apt-get install nmap

[Puma]

Hello,

Sorry for my last reply... I am not a pro and just do adjust bubba2 and 3 according wiki or forum.

I installed nmap.

Code: Select all

Starting Nmap 5.00 ( http://nmap.org ) at 2010-11-15 21:58 CET
Interesting ports on localhost.localdomain (127.0.0.1):
PORT   STATE  SERVICE
21/tcp closed ftp

Nmap done: 1 IP address (1 host up) scanned in 0.80 seconds

In the webinterface FTP is enabled
With filzilla I cannot connect.

When I checked the logfile of ftpd.

Code: Select all

Nov 13 21:43:39 b3 proftpd[17063] b3.localdomain: ProFTPD killed (signal 15)
Nov 13 21:43:39 b3 proftpd[17063] b3.localdomain: ProFTPD 1.3.3a standalone mode SHUTDOWN
Nov 13 21:44:21 b3 proftpd[1452] b3.localdomain: ProFTPD 1.3.3a (maint) (built Thu Aug 26 2010 17:04:56 CEST) standalone mode STARTUP
Nov 13 22:30:23 b3 proftpd[21572] b3.localdomain (::ffff:192.168.101.86[::ffff:192.168.101.86]): FTP session opened.
Nov 13 22:30:23 b3 proftpd[21572] b3.localdomain (::ffff:192.168.101.86[::ffff:192.168.101.86]): Preparing to chroot to directory '/home'
Nov 13 22:30:23 b3 proftpd[21572] b3.localdomain (::ffff:192.168.101.86[::ffff:192.168.101.86]): USER ******: Login successful.
Nov 13 22:31:30 b3 proftpd[21572] b3.localdomain (::ffff:192.168.101.86[::ffff:192.168.101.86]): FTP session closed.
Nov 14 06:25:07 b3 proftpd[1452] b3.localdomain: ProFTPD killed (signal 15)
Nov 14 06:25:07 b3 proftpd[1452] b3.localdomain: ProFTPD 1.3.3a standalone mode SHUTDOWN

I tried to create a backup via de webinterface at this moment I think.
Can it be a cronjob problem??

When I try to restart ftpd I get:

Code: Select all

root@b3:/home/******# /etc/init.d/proftpd restart
Stopping ftp server: proftpd.
Starting ftp server: proftpd - warning: unable to determine IP address of 'b3'
 - error: no valid servers configured
 - Fatal: error processing configuration file '/etc/proftpd/proftpd.conf'
 failed!

Puma

[Ubi]

So your FTP server is not running, therefore filezilla wont connect nor will any other activities that rely on this service function. Problem seems to be that proftpd cannot figure out what your ip address is because the default machine name does not have a proper reverse DNS lookup (as is expected)... Kinda weird that not many more people experience this same issue. Oddly it does find your ip address over the non-working ipv6 frame.

Now normally the solution will be to tell the FTP server in its config what the IP address is (or even do this in /etc/hosts), but that won't work anymore when your bubba is connected via a dynamic IP address to the upstream router (is it?). I don't have access to my own machine currently so I can't do a lot more atm. Maybe Tor has some clever ideas?

[Puma]

Hello,

FTP access restored including Smartphone IMAP connection (which was down as well0

I changed the network profile to automatic after that, I changed it back to Router + Firewall + Server.
I changed the IP adress again to my old one 192.168.101.1 and it is working again?

Any ideas?

Puma

[Ubi]

i think this question is answered already

[theWebalyst]

So your FTP server is not running, therefore filezilla wont connect nor will any other activities that rely on this service function. Problem seems to be that proftpd cannot figure out what your ip address is because the default machine name does not have a proper reverse DNS lookup (as is expected)... Kinda weird that not many more people experience this same issue. Oddly it does find your ip address over the non-working ipv6 frame.

Maybe not many people use FTP on b3?

Anyway, I have this issue so it is not unique but systemic at least to some extent.

Mark

[Cheeseboy]

Hi Mark,

Maybe not many people use FTP on b3?

Many people do, but perhaps they do not have the same network configuration you have?
Did you get the same errors in the log as the original poster?
Care to tell us how your network is set up?

Cheers,

Cheeseboy

[theWebalyst]

Hi Cheeseboy,

I have the same errors and worked around it by hard-coding my (dynamically obtained) IP in /etc/hosts

My b3 is connected to a cable internet modem and is server-firewall-router. Latest software. 2T+2T storage RAID array.

Mark

[Cheeseboy]

Hi Mark,

That sounds like a painful solution.
Have you tried

Code: Select all

UseReverseDNS off

as outlined here?
http://www.proftpd.org/docs/howto/DNS.html

I had a look at the many options of ddclient, but it doesn't seem to have the ability to update /etc/hosts.
Perhaps a nifty script is in order?
My setup uses http://checkip.dyndns.com to check the current external address.
You just need to parse that, parse your existing /etc/hosts, compare the two, and change it as needed

EDIT:
This might be a place to start:
http://www.unix.com/shell-programming-s ... dress.html

[RandomUsername]

Just bouncing some ideas around; Maybe this is a regression (or similar but unrelated bug) to this one - http://forum.excito.net/viewtopic.php?f ... tc%2Fhosts

Might be worth the people with this problem to give us the output of /etc/hosts

[Ubi]

Have you tried

Code: Select all

UseReverseDNS off

as outlined here?
http://www.proftpd.org/docs/howto/DNS.html

This sounds like the proper solution for the problem and may be something to consider making a default setting in the B3 distribution. At least I don't see any direct issue with not adding this.

[theWebalyst]

Just bouncing some ideas around; Maybe this is a regression (or similar but unrelated bug) to this one - http://forum.excito.net/viewtopic.php?f ... tc%2Fhosts

Might be worth the people with this problem to give us the output of /etc/hosts

Looks like a 'no'. Here's my /etc/hosts:

Code: Select all

127.0.0.1       localhost.localdomain   localhost
::1     ip6-localhost   ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
# Temp hardcode b3 to keep proftpd from aborting
192.168.10.1    b3.localdomain  b3

Mark