Plesk 10 then Yum Update (proftp) Now No FTP

[kernelpaniker]

So I updated Plesk via the plesk control panel and everything seems fine. I did a yum update via ssh and the only update was for proftp.

I cannot access the server via ftp now.

CentOS 5
Plesk 10.0.1

Any troubleshooting tips for me?

[nobody]

Remove and reinstall proftpd.

Do you use the asl proftpd or the psa one ?

Anyway I think you were in a hurry to update your plesk panel.

[kernelpaniker]

So...
I would imagine that I would yum remove proftpd, well that results in no packages marked for removal.

Also, yum install proftpd returns no package proftpd available.

I would be using the psa proftpd.

Thanks for your help.

[scott]

I saw another thread in the plesk forums about general ftp problems after the upgrade. May or may not be related, regardless *upgrade psa-proftpd* to 1.3.3c (available in atomic and asl-2.0 channels). Do NOT use versions of proftpd prior to 1.3.3c

[breun]

The package is called psa-proftpd, not proftpd. The ART version is too, and is a more recent version, so that one will update the package shipped by Parallels.

What proftpd packages do you have installed currently? rpm -qa | grep proftpd | sort

[kernelpaniker]

When I
rpm -qa | grep proftpd | sort
I get
psa-proftpd-1.3.3c-1.el5.art

[breun]

On Plesk 9.5 you'd also have a psa-proftpd-xinetd package installed, which ties ProFTPd in with xinetd. I haven't tried Plesk 10 yet, so I don't know if they changed that or if you're indeed missing that package. Missing that package would explain why your FTP server isn't working at the moment.

[kernelpaniker]

If I look in /var/log/messages I see
proftpd[XXXX]: Fatal: unable to read configuration file '/etc/proftpd.conf': No such file or directory

What should be in the proftpd.conf file?

[breun]

The /etc/proftpd.conf contains the ProFTPd configuration and is also part of the psa-proftpd-xinetd package. My guess would be that you're missing psa-proftpd-xinetd somehow and need to install Plesk 10's version of it.

[kernelpaniker]

Here is how I fixed it:

First I had to create /etc/xinetd.d/ftp_psa and put the following in there:

Code: Select all

service ftp
{
        disable         = no
        socket_type     = stream
        protocol        = tcp
        wait            = no
        user            = root
        instances       = UNLIMITED
        server          = /usr/sbin/in.proftpd
        server_args     = -c /etc/proftpd.conf
}

Then I had to create /etc/proftpd.conf and put the following in there:

Code: Select all

#
# To have more informations about Proftpd configuration
# look at : http://www.proftpd.org/
#

# 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"
#ServerType standalone
ServerType inetd
DefaultServer on
<Global>
DefaultRoot ~ psacln
AllowOverwrite on
</Global>
DefaultTransferMode binary
UseFtpUsers on

TimesGMT off
SetEnv TZ :/etc/localtime
# 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

#Following part of this config file were generate by PSA automatically
#Any changes in this part will be overwritten by next manipulation
#with Anonymous FTP feature in PSA control panel.

#Include directive should point to place where FTP Virtual Hosts configurations
#preserved

ScoreboardFile /var/run/proftpd/scoreboard

# Primary log file mest be outside of system logrotate province

TransferLog /usr/local/psa/var/log/xferlog

#Change default group for new files and directories in vhosts dir to psacln

<Directory /var/www/vhosts>
GroupOwner psacln
</Directory>

# Enable PAM authentication
AuthPAM on
AuthPAMConfig proftpd

IdentLookups off
UseReverseDNS off

AuthGroupFile /etc/group

Include /etc/proftpd.include

Then I had to restart xinetd.
So I typed - service xinetd restart

FTP worked after that.

[nobody]

So weird that the upgrade removed the configuration files...

Did you though try to uninstall the psa-proftpd and reinstall the package ?

I think this would have created the configuration files everywhere and you would be ok thats why I mentioned that since the beggining of your thread ...

[kernelpaniker]

I didn't try to uninstall the package because when I did yum remove proftpd or whatever it said that it wanted to remove 95 packages because of dependencies. So I didnt do that.

I tried downgrading and upgrading via yum but that didn't fix anything.

[breun]

Those configuration files are not part of the psa-proftpd package, but the psa-proftpd-xinetd package. I still recommend checking out if Plesk still provides that packages, because that seems like a better solution.

[avibodha]

Those configuration files are not part of the psa-proftpd package, but the psa-proftpd-xinetd package. I still recommend checking out if Plesk still provides that packages, because that seems like a better solution.

having same problem here...how would I get the plesk package? I'm on a VPS that has plesk 10.0.1. and did yum update and had same thing happen.

[breun]

Maybe the xinetd integration has been moved into the psa-proftpd package in Plesk 10 and maybe there is no psa-proftpd-xinetd package anymore? That would explain why the atomic upgrade doesn't work with Plesk 10, because that package doesn't have the configuration files.

I haven't tried Plesk 10 myself yet, so this is just speculation on my part. You could take a look at the Plesk 10 package listing to see if there is still a psa-proftpd-xinetd package and/or try reverting to Plesk's psa-proftpd package (which has a version of ProFTPd with a known security issue!).