Scan wont complete

Home Forums Wordfence Support Questions Scan wont complete

Tagged: 

This topic contains 16 replies, has 7 voices, and was last updated by  mark 12 months ago.

Viewing 15 posts - 1 through 15 (of 17 total)
Author Posts
Author Posts

chenzen dong

said

Hey,

I’ve been trying to run a scan, but after two tries it’s been unsuccessful. It gets stuck after starting the posts scan, and end up with the following error message: mysql_query(): Function called without first fetching all rows from a previous unbuffered query (8) File: /usr/share/nginx/html/wp-content/plugins/wordfence/lib/wfDB.php Line: 90

April 30, 2012 at 10:08 am

mark

said

Got it thanks. I’ve added this to our issues list.

Mark.

April 30, 2012 at 10:32 am

keith allison

said

I’m having basically the same issue… where the scan will freeze after a few files. No errors, just freezes. I’ve tried multiple times. sometimes it’ll get through 20 or 30 files and other times it’ll go about 10 files.

May 3, 2012 at 6:36 am

christopher canton

said

Hi Mark,
I am experiencing the same issue. I have the premium edition; I can’t get the scan to complete despite several attempts. I will email my activity log to you.
Thanks,
Chris

May 7, 2012 at 8:01 pm

mark

said

Chenzen, Keith and Chris, please upgrade to 2.0.2 the current version. It includes many bugfixes which may fix the issues you’ve described. We’ve also further enhanced error reporting, so at the very least you’ll get more info about what is going wrong.

Regards,

Mark.

May 8, 2012 at 10:25 pm

mark

said

Chezen version 2.0.3 contains an additional fix for this issue, so please upgrade and let me know if you’re still having the problem.

May 10, 2012 at 8:57 am

Marcus V

said

I just installed your plugin and while trying to scan a client site that had someone break in, the scan would not complete, here is the error:

[May 11 22:29:14] Please contact support about failure (2) File: /home/zcasdsdw/public_html/wp-content/plugins/wordfence/lib/wordfenceScanner.php Line: 111
[May 11 22:29:14]
Fatal error: preg_replace() [function.preg-replace]: Failed evaluating code: self::array_pushRet($decoded, base64_decode("javascript")) in /home/zcasdsdw/public_html/wp-c

May 11, 2012 at 3:58 pm

mark

said

Thanks Marcus, this should be fixed in the next release hopefully out later today.

Regards,

Mark.

May 12, 2012 at 6:24 am

steven stern

said

How do I get a scan to stop? It’s been sitting on these lines for 21 minutes so far…

[May 15 17:13:06]Scanning file contents for infections and vulnerabilities
[May 15 17:13:06]Scanning files for URLs in Google’s Safe Browsing List

May 15, 2012 at 10:53 am

Marcus V

said

After updating today, I am also stuck at the same point Steven mentions, but in the Scan Detailed Activity log I have the following message:

[May 15 17:41:48] Please contact support about failure (2) File: /home/zcasdsdw/public_html/wp-content/plugins/wordfence/lib/wordfenceURLHoover.php Line: 26

May 15, 2012 at 11:08 am

steven stern

said

This may be my bad… I had “scan outside the wordpress tree” option selected. It turns out there are about 4000 files left over from three prior verions of the site. I’ll just have to wait for it to finish looking at them.

May 15, 2012 at 12:56 pm

mark

said

Steven try upgrading and starting another scan with all your files. We have increased the scan speed a lot in the last few versions in case you’re running an older Wordfence version.

Mark.

May 15, 2012 at 2:25 pm
Viewing 15 posts - 1 through 15 (of 17 total)

The topic ‘Scan wont complete’ is closed to new replies.

About Wordfence

Wordfence is part of Feedjit Inc. based in Seattle Washington in the USA. Our founders are Mark Maunder (CEO) and Kerry Boyte (COO). Feedjit has been providing real-time analytics and real-time ad serving solutions since 2007 and today supports over 700,000 publishers. Our mission with Wordfence is to provide security and peace of mind to WordPress publishers. Please contact us at support@wordfence.com.
Copyright © 2011 to 2012 Wordfence.com. All rights reserved. Please see our Terms of Use & Privacy Policy.