Articles in this section

See more

[FIXED BUG] Unable to scan WP instances: Unable to process "./.cagefs/opt/alt/php55/var": No such file or directory

Avatar
Julian Bonpland Mignaquy
Updated
Follow

Applicable to:

  • Plesk Onyx for Linux

Symptoms

  • Unable to scan Wordpress instances in Subscriptions > example.com > Wordpress > Scan:

    PLESK_ERROR: Unable to process "./.cagefs/opt/alt/php70/var": No such file or directory
    Unable to process "./.cagefs/opt/alt/php55/var": No such file or directory
    Unable to process "./.cagefs/opt/alt/php56/var": No such file or directory
    Unable to process "./.cagefs/opt/alt/php51/var": No such file or directory
    Unable to process "./.cagefs/opt/alt/php71/var": No such file or directory
    Unable to process "./.cagefs/opt/alt/php73/var": No such file or directory
    Unable to process "./.cagefs/opt/alt/php44/var": No such file or directory
    Unable to process "./.cagefs/opt/alt/php72/var": No such file or directory
    Unable to process "./.cagefs/opt/alt/php54/var": No such file or directory
    Unable to process "./.cagefs/opt/alt/php52/var": No such file or directory
    Unable to process "./.cagefs/opt/alt/php53/var": No such file or directory
    Unable to process "./.cagefs/tmp/.s.PGSQL.5432": No such file or directory
    Unable to process "./.cagefs/tmp/download-g5GfKK.tmp": No such file or directory
    Unable to process "./httpdocs": No such file or directory
    Unable to process "./logs/dev04.webmax.xyz-ssl_log-Aug-2019.gz": No such file or directory
    Unable to process "./logs/dev03.webmax.xyz-Aug-2019.gz": No such file or directory
    Unable to process "./logs/dev10.webmax.xyz-ssl_log-Jul-2019.gz": No such file or directory

  • Domains and directories mentioned in the error above were migrated from cPanel.

  • Some of the directories migrated are broken symlinks.

Cause

Product issue:

  • #PPPM-10965 "WordPress Toolkit can now scan installations even if they have broken symlinks."
    Fixed in:

Resolution

Please consider updating your server:

Workaround

If update is not possible for some reason you may try the following

workaround

As a workaround remove the broken symlink:

  1. Connect to the server via SSH.

  2. Remove the broken symlinks in the error with the unlink command:

    # unlink example

    Note: replace example with the symbolic lynks mentioned in the error

  3. Re-scan Wordpress instances in Subscriptions > example.com > Wordpress > Scan.

Comments

0 comments

Please sign in to leave a comment.

Have more questions? Submit a request

Related articles