Scan error

  • Resolved dbonneville

    (@dbonneville)


    8 years, 10 months ago

    Hi. I have been using Duplicator for several years. Starting in Dec 2016, I have been getting this error when I try to build a package:

    ====

    Scan Error
    Please try again!
    Server Status: Scan Path Error [/home/douglasb/public_html]
    Error Message:
    Unable to perform a full scan, please try the following actions:

    1. Go back and create a root path directory filter to validate the site is scan-able.
    2. Continue to add/remove filters to isolate which path is causing issues.
    3. This message will go away once the correct filters are applied.

    Common Issues:
    – On some budget hosts scanning over 30k files can lead to timeout/gateway issues. Consider scanning only your main WordPress site and avoid trying to backup other external directories.
    – Symbolic link recursion can cause timeouts. Ask your server admin if any are present in the scan path. If they are add the full path as a filter and try running the scan again.

    ====

    No content changed. Essentially it just stopped working at some point between WP updates and Duplicator plugin updates. The site had not been updated with new content for about 6 months when it stopped working.

    • This topic was modified 8 years, 10 months ago by dbonneville.
Viewing 6 replies - 1 through 6 (of 6 total)
  • Cory Lamle

    (@corylamleorg)

    8 years, 10 months ago

    Hey @dbonneville,

    Create a root file filter to see if the scan will complete. If it does then there is a file/directory that may have changed that the scanner is having issues reading. If you want to submit a ticket here, I can have a closer look for you…

    Thread Starter dbonneville

    (@dbonneville)

    8 years, 10 months ago

    I found the offending files deep in the uploads folder. Some foreign characters pasted into jpg file names were causing the process to choke:

    FontShop.-The-WorldÔÇÖs-Best-Fonts.-20130504-150×109.jpg
    FontShop.-The-WorldÔÇÖs-Best-Fonts.-20130504-470×341.jpg
    FontShop.-The-WorldÔÇÖs-Best-Fonts.-20130504.jpg
    FontShop.-The-World’s-Best-Fonts.-20130504-150×109.jpg
    FontShop.-The-World’s-Best-Fonts.-20130504-470×341.jpg
    FontShop.-The-World’s-Best-Fonts.-20130504.jpg

    type-quote-Robert-Bu¦êchler-150×128.jpg
    type-quote-Robert-Bu¦êchler-470×401.jpg
    type-quote-Robert-Bu¦êchler.jpg
    type-quote-Robert-Büchler-150×128.jpg
    type-quote-Robert-Büchler-470×401.jpg
    type-quote-Robert-Büchler.jpg
    type-quote-Robert-Büchler-150×128.jpg
    type-quote-Robert-Büchler-470×401.jpg
    type-quote-Robert-Büchler.jpg

    ..etc.

    I removed them all, and it immediately passed the scan.

    I had to painstakingly go through the filters for every directory on the site until I found it was the these ones buried deep in WP! Not fun, but I found it. And then it required deleting them using “ls -li” and deleting them one at a time like this “find . -inum 71583650 -delete”, since the files literally could not be deleted by “rm” or file manager, or ftp etc. Those usual methods all said “file could not be found”!

    Thread Starter dbonneville

    (@dbonneville)

    8 years, 10 months ago

    It would be great if the scan could create a log to tell you what it choked on…or is there one and I missed it?

    Cory Lamle

    (@corylamleorg)

    8 years, 10 months ago

    Hey @dbonneville,

    Thanks for the update! What version of PHP are you running on that server? I created files with the exact same sames as those above and the scanner passed on a couple different servers and they were detected in the name checks section. Do you remember if the files were setup as symlinks by chance? I’m trying to rule out why PHP would fail on just trying to read the files… I’ll see if I can improve the Scan Validator (Tools > Diagnostics) or provide a log like you mention. I just got to figure out how to repro it…

    Thanks

    Thread Starter dbonneville

    (@dbonneville)

    8 years, 10 months ago

    PHP is 5.6.30.

    The files were not symlinks, I just used loaded them through the media uploader per normal for any graphic being used in a blog post.

    I was on tech support. They could not delete them for me. But I found the “inum” method while not being content to wait for support to get back to me.

    I’m on a Mac, so perhaps Mac allowed me to copy some text, maybe some unicode font or something, that got translated weird through WordPress uploading. The one character after “World” was simply some kind of apostrophe for “World’s”. The Robert B example was u with the two dots above it, at least when I originally got it from the web way back. You can see it here, from the file on my Mac:

    http://prntscr.com/fee5o2

    Cory Lamle

    (@corylamleorg)

    8 years, 10 months ago

    Thanks for the update! I’ll backlog the this forum thread for when I can help to isolate the issue more easily… If you run into the issue again on a remote host feel free to submit a support ticket and I can more closely debug the issue if you want…

    Cheers~

    • This reply was modified 8 years, 10 months ago by Cory Lamle.
Viewing 6 replies - 1 through 6 (of 6 total)

The topic ‘Scan error’ is closed to new replies.