• 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 permission error unable to repair

Anthonykung

New Pleskian
Hi, I'm having a problem fixing file permission with repair fs it kept telling me no path matches the pattern but the directory definitely exists.


Bash:
Checking Linux system files[2021-03-20 04:35:28.874] ERR [util_exec] proc_close() failed ['/opt/psa/admin/bin/fsmng' '--check-ac' '/var/www/vhosts'] with exit code [1]


  There are incorrect permissions on some items: /var/www/vhosts . [ERROR]
    - fsmng failed: dpkg-query: no path found matching pattern
      /var/www/vhosts
      ERROR:Command '['/usr/bin/dpkg', '-S', '/var/www/vhosts']'
      returned non-zero exit status 1
  Do you want to repair incorrect permissions? [Y/n] y
    Repairing incorrect permissions ................................. [2021-03-20 04:35:31.307] ERR [util_exec] proc_close() failed ['/opt/psa/admin/bin/fsmng' '--set-ac' '/var/www/vhosts'] with exit code [1]
[FAILED]
    - fsmng failed: dpkg-query: no path found matching pattern
      /var/www/vhosts
      ERROR:Command '['/usr/bin/dpkg', '-S', '/var/www/vhosts']'
      returned non-zero exit status 1


Does anyone know how to fix this? The directory is already owned by root:root and permission are set to 755, I couldn't find anything to help me, all that I find is site-specific issues, not the entire vhosts.
 
Back
Top