[SMS]

lkraemer · Member Joined: 25 Jun 2010 Posts: 37

I have read the documentation on Active/Passive FTP at:
http://slacksite.com/other/ftp.html

I wanted to change my FTP Port from 21 to 2121, and I did that in the
SMS proftpd.conf file, saved the file, and restarted the server. But now I
can't make any transfers with Fileilla on my local network. I have Ports 21, 22, and 2121 open in my router, but no others. (Since I didn't need to
open any other ports when using 21, and everything worked fine.)

My proftpd.conf has been modidied to:

Port 2121
PassivePorts 49150 65534
#
# To be sure that you have no other processes listening on the ports
# you have specified for passive transfers use a port scanner such as nmap:
#
# nmap -sT -p 49150-65534 localhost
#
# If the result says something like:
#
# All 16385 scanned ports on localhost (127.0.0.1) are: closed
# then you should be safe.
#

My Galaxy Tablet using andFTP works with port 2121 with these modified
settings, while neither laptop works with Filezilla on port 2121, but works fine on port 21. What can be the problem? What am I missing?

Thanks.

Larry

gerasimos_h · Posted: Fri May 20, 2011 4:30 pm Post subject:

Since your tablet login, your server is configured correctly, double check port 2121 in filezilla and make a quick connection, also try another ftp client to double check.
You router's ports has nothing to do with your local network, unless you are connecting through the internet to your local network where SMS is.
In that case you need to port forward ftp port to your SMS server.

gerasimos_h

lkraemer · Member Joined: 25 Jun 2010 Posts: 37

OK, I started an FTP xfer using QUICKCONNECT and port 21. Then I
started a Samba xfer. The Samba xfer gave me a timeout error as
shown in the png.

This caused the FTP xfer to fault also. I have enclosed the log file.
I had debugging on but those commands weren't included in the log file.

Larry

lkraemer · Member Joined: 25 Jun 2010 Posts: 37

OK, I started an FTP xfer using QUICKCONNECT and port 21. Then I
started a Samba xfer. The Samba xfer gave me a timeout error as
shown in the png.

This caused the FTP xfer to fault also. I have enclosed the log file.
I had debugging on but those commands weren't included in the log file.

Now I will have to reboot my SMS Server to start another xfer.

Thanks.

Larry

gerasimos_h · Posted: Sat May 21, 2011 7:14 am Post subject:

Please upload the logs again.

gerasimos_h

lkraemer · Member Joined: 25 Jun 2010 Posts: 37

OK, I repeated the process. Samba1.png is my start of copying 6.6 Gig.
I then started the FTP transfer with ProFtP and Filezilla. It was copying when
the Samba error popped up. That message is shown in Samba2.png. Then, ProFTP also stops. I've included the Filezilla.log and Filezilla.log.1 files.
I also looked in the SMS Server for other useful information in .var/log
but didn't see anything that seemed to apply. If you need some of them,
I'll need the filenames.

The FTP xfer was on Port 21 with the default proftpd.conf file.

Thanks.

Larry

lkraemer · Member Joined: 25 Jun 2010 Posts: 37

OOPS, I forgot the Attachment.

Larry

gerasimos_h · Posted: Sat May 21, 2011 6:31 pm Post subject:

lkraemer · Member Joined: 25 Jun 2010 Posts: 37

I can't do anything after my system stops transfering. I have tried to log
in from a Terminal via ssh as root with ssh root@192.168.1.250 but that
gives an error message. I have to go to the Server Console and login
and reboot the system. I can still do that......

I have 2 512 Meg PC3200 memory sticks in my older Foxconn Motherboard.
I'd think 1 Gig of ram would be enough for making transfers.

I don't have any firewalls enabled. I just have whatever SMS installed from
the Native ISO, along with the KDE Desktop.

I haven't tried to ping my server after the crash, but I can't get to it via ssh.
It gives me an error stating no route to path......

How can I detect if the server has crashed? I have the Samba Window open
and I can Unmount that, and I can physically walk to SMS Server and turn on Monitor and login and reboot. That gets it all working again. Shouldn't
there be some log files stored at /var/log/*.log on my SMS Server that would give you a clue? If you specify the file names out, I'll delete the existing ones, and duplicate the problem, then attach those log files for your viewing/review.

Other ideas?

Thanks.

Larry

lkraemer · Member Joined: 25 Jun 2010 Posts: 37

I was initially thinking Samba xfers were causing the fail, but now I'm thinking
that FTP is causing the faults. I've captured the top window in Filezilla to a
text file, and have it attached. You will be able to see near the end where the FTP xfers stop. And that causes my root ssh connection to hang along with the
Samba xfers. I'm making Samba xfers while I make this post to test out this
theory.

The odd thing is I can go to my Server, login, and reboot, and everything is
once again functional.

Attached is Filezilla-Trace.zip with the Top window's trace/debug information,
along with the two Filezilla log files.

Thanks.

Larry

lkraemer · Member Joined: 25 Jun 2010 Posts: 37

I am thinking I have it figured out. Samba works, always did, except when
I was also doing an FTP transfer with Filezilla (Upload). I just completed a
6.6 Gig xfer via Samba and it worked fine.

I added the following to the proftpd.conf file:
MaxStoreFileSize *
to make the Maximum Filesize Unlimited from None. And so far it is still
transfering. Filezilla just transfered a file with the size of 22,680,554 and is 91% done. And Filezilla is still making xfers, but the true test will be if it
finishes the remaining 3907 files without barfing...........still working......
If None (the Default) is used there is some arbitrary filesize that is
associated with the Maximum.

So, I'd suggest that you add the MaxStoreFileSize * entry after the
MaxLoginAttempts 3 entry in your /etc/proftpd.conf configuration file for
SMS 1.6.0+.

This also applies to anyone trying to xfer large files via FTP with Filezilla, and ProFTP as the SMS FTP Server.

THANKS.

Larry

lkraemer · Member Joined: 25 Jun 2010 Posts: 37

It is now officially several hours with no faults with the FTP Transfers........

http://www.castaglia.org/proftpd/doc/contrib/configuration-directive-key.html
states:

Default
If the directive has a default value (i.e., if you omit it from your configuration entirely, the ProFTPD FTP server will behave as though you set it to a particular value), it is described here. If there is no default value, this section should say "None".

But, this obviously isn't exactly 100% totally correct.

I'm convinced my problem is SOLVED!

THANKS!! Now I can get on with ENJOYING SMS..........

Larry

lkraemer · Member Joined: 25 Jun 2010 Posts: 37

One more small change needs to be made to /etc/proftpd.conf

EXISTING
TransferRate RETR 30
TransferRate STOR 40
TransferRate STOU 40
TransferRate APPE 40

TO
TransferRate RETR 12000
TransferRate STOR 12000
TransferRate STOU 12000
TransferRate APPE 12000

This makes the transfer rate similar to the vsftp rates, that I tested.

THANKS.

Larry

lkraemer · Member Joined: 25 Jun 2010 Posts: 37

Attached in a text document that will explain how to test FTP transfers with
vsftpd, in order to find and fix the problem with proftpd.

Thanks.

Larry