Issue Forced Plesk update???

[Monty]

I just created a directory with 5'000 files in it and listing via FTP takes about ~5 seconds which is quite OK.

Maybe related to your filesystem? I use ext4:

# cat /proc/mounts | grep vhosts
/dev/mapper/vg2-lv_vhosts /var/www/vhosts ext4 rw,relatime,data=ordered 0 0

What about you?

 

[IgorG]

Problem with ftp high cpu load is related to bug in proftpd-1.3.6 - Bug 4360 – slow directory listing in 1.3.6 in comparison to 1.3.5d
Generally speaking, it’s a bad idea to put too many files in one directory. Besides the fact that it is inconvenient, sooner or later there is a software or file system with which the problems begin. Best of all for any signs to create a directory tree with these files inside.
We have a corresponding internal report PPPM-9486 under developers investigation.

 

[HostaHost]

Any progress on this ProFTPd issue? Applications don't always let you choose where they store certain files. It isn't practical to tell every customer who has updated from 17.5 to 17.8 that they should now rearchitect their websites and web apps around Plesk's use of a version of ProFTPd with a known bug.

 

[HostaHost]

Was able to force it back via rpm -Uvh --force http://autoinstall.plesk.com/PSA_17...tpd-1.3.5d-cos7.build1705170314.14.x86_64.rpm
Of course, not sure if Plesk will re-up it at some point; perhaps can blacklist it in yum, but not sure if that will break the autoinstaller process for microupdates.

 

[JayStock]

Amen!! How long does it take to fix an egregious bug???

 

[Dave W]

This is a very Microsoft way of doing things, automate minor updates sure, major updates should be left to admins to schedule.

 

[HostaHost]

Following up my post, it appears blacklisting psa-proftpd-1.3.6* in yum.conf will keep autoinstaller from reupgrading it. I'm waiting to hear from support, and they the developers, on whether this is safe to do or not.