• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.

Resolved plesk repair fs and custom backup locations | v17.5.3 - Resolved in v17.8

Wiz

Basic Pleskian
Hello,

There appears to be a bug with fsmng in plesk v17.5.3 where improper checks on file/directory location are causing:

Code:
# plesk repair fs -y -v

Checking Linux system files[2017-07-07 06:12:31] ERR [util_exec] proc_close() failed ['/usr/local/psa/admin/bin/fsmng' '--check-ac' '/path/to/custom/backup' '--perms' '0750' '--owner' 'psaadm' '--group' 'psaadm'] with exit code [1]

  fsmng failed: ERROR:Command '['/bin/rpm', '-qf', '/path/to/custom/backup', '--dump']' returned non-zero exit status 1

Checking virtual hosts' file system ................................. [OK]

Error messages: 0; Warnings: 0; Errors resolved: 0

No amount of installation, fs, patch reinstalling or permission repairs will resolve this as the bug is in the binary file itself.

Proposed fix - fsmng should take into consideration the custom DUMP_D value passed by /etc/psa/psa.conf for both directory and rpm checking instead of the default /var/lib/psa/dumps directory path. A custom DUMP_TMP_D value does not cause such errors.

Thanks
 
I have checked this issue on Plesk 17.8 Preview and found that this issue is fixed there.

Good to know, thanks IgorG. It will be a while until the preview release is considered/marked stable for us late adopters. Not that the bug is a show stopper but will the fix be pushed to the current stable release?
 
I do not think this is such a critical bug to port the fix to the current version. This is usually done for very annoying bugs.
 
Back
Top