Daniel Strickland

Nevermind. All it took was removing the line of gibberish after “<?php”. ??

Hi wfalaa,
I just tried to send report by email, but got the message that “There was an error while sending the email.”

Any suggestions for getting around this?

Thanks.

Hi wfalaa,

I’m seeing the same error on one of our websites. Only three plug-ins are enabled: MOJO Marketplace, Wordfence, and WordPress Importer. I disabled MOJO and Importer and rescanned, but got the same error.

[Aug 22 08:29:10] Undefined property: stdClass::$slug (8) File: /wp-content/plugins/wordfence/lib/wfUpdateCheck.php Line: 92
[Aug 22 08:29:10] Scan terminated with error: Required fields not provided.
[Aug 22 08:29:10] Notice: Undefined property: stdClass::$slug in /wp-content/plugins/wordfence/lib/wfUpdateCheck.php on line 87

Is there anything else we should try?

Thanks.

PHP version 5.3.3 is running on this server. Does this information help?

Hello wfasa,
By using the “Enable debugging mode” feature and looking at where the scan got hung up, I was able to scan successfully by including all scans EXCEPT “Scan for signatures of known malicious files” AND excluding these filename wildcard patterns:

*.pdf
*.jpg
*.gif
*.mov
*.png
*.jpeg
*.docx
webalizer/*

I tried running a scan with ONLY the “Scan for signatures of known malicious files” checked, but it failed due to a memory error.

Do you have any suggestions on how we could successfully scan for signatures of known malicious files?

Thanks!

Hello wfasa,
We’re still having issues with our site. Before updating WordPress today, Wordfence was able to scan successfully if I checked just a few “Scans to include” at a time. (If I checked “Scan for signatures of known malicious files,” the scan would alwaysfail.)

Today Wordfence fails even when I uncheck everything under “Scans to include.”

A snippet of the error log is below. Do you have any suggestions?

Thanks!

[Jun 16 16:10:52:1466118652.313066:1:error] Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 14735097 bytes) in /home/justworl/www.justworldinternational.org/docs/wp-includes/wp-db.php on line 1263
[Jun 16 16:10:51:1466118651.286366:2:info] Analyzed 11800 files containing 1.52 GB of data so far
[Jun 16 16:10:50:1466118650.815906:2:info] Analyzed 11700 files containing 1.52 GB of data so far
[Jun 16 16:10:50:1466118650.225955:2:info] Analyzed 11600 files containing 1.51 GB of data so far
[Jun 16 16:10:49:1466118649.653541:2:info] Analyzed 11500 files containing 1.5 GB of data so far

We went back to our host and asked if they could do anything else to help. They said they “increased some php limits (like memory_limit and max_execution_time)” and voila, Wordfence now works.

Thanks for your help.

Hello wfasa,
Our host tried temporarily disabling the mod_security on our site, but Wordfence still won’t complete a scan.

What else can we try?

Thanks!

Hello wfasa,
Do you have an update on the reports of memory related issues you’ve been investigating? Any suggestions for our case?

Hello wfasa,
Here are the results from the P3 plugin:

WordPress Plugin Profile Report
===========================================
Report date: May 13, 2016
Theme name: eVid
Pages browsed: 21
Avg. load time: 2.1564 sec
Number of plugins: 17
Plugin impact: 75.22% of load time
Avg. plugin time: 1.6220 sec
Avg. core time: 0.2100 sec
Avg. theme time: 0.1191 sec
Avg. mem usage: 83.71 MB
Avg. ticks: 71,419
Avg. db queries : 64.38
Margin of error : 0.2054 sec

Plugin list:
===========================================
P3 (Plugin Performance Profiler) – 0.0109 sec – 0.67%
Akismet – 0.0096 sec – 0.59%
Broken Link Checker – 0.0442 sec – 2.73%
Contact Form 7 – 0.0466 sec – 2.87%
List Subpages – 0.0057 sec – 0.35%
Meta Slider – 0.0257 sec – 1.58%
Nextgen Gallery – 0.3904 sec – 24.07%
Nivo Slider For WordPress – 0.0033 sec – 0.20%
Smart Youtube – 0.0463 sec – 2.86%
Sucuri Scanner – 0.0202 sec – 1.25%
SumoMe – 0.0007 sec – 0.04%
TablePress – 0.0276 sec – 1.70%
Wordfence Security – 0.6658 sec – 41.05%
Wordpress Seo – 0.1494 sec – 9.21%
WP-PageNavi – 0.0140 sec – 0.86%
WPS Hide Login – 0.0256 sec – 1.58%
WPtouch Mobile Plugin – 0.1359 sec – 8.38%

If I’m reading this correctly, after Wordfence, the next biggest memory user is Nextgen Gallery.

Hello wfasa,
Thanks for the quick response!

We’re running WordPress 4.3.3 on this site. (Yes, we need to update it.)

I’ll take a look at the P3 plugin.

What else would you recommend?

Hello wfasa. Thanks for your assistance.

1) The potential causes (firewall, bad route, etc) don’t ring a bell with me, but I’ll ask our host about them.

2) I disabled those two plugins, and tried a scan, but got the following error:

[May 13 09:37:50] Found 7 themes
[May 13 09:37:50] Calling Wordfence API v2.22:https://noc1.wordfence.com//v2.22/?v=4.5.2&s=http%3A%2F%2Fwww.sfbee.org&k=79b3f67b68a8a6b8f9bffb5ce37ddbc383eb7e049cd06c8639a51f9b72029ef384d8d81fc44ae64eb91181e9eb85935b8f271e2141c15a0e2149f4f80c3f68ae&openssl=268439647&phpv=5.3.29&betaFeed=0&action=get_known_files
[May 13 09:38:10] Scan process ended after forking.

3) I just sent you an email with subject line “Scan process ended after forking – sfbee.org”

Thank you!

@wfasa I spoke too soon — Wordfence is getting jammed again. I just emailed the activity log to your email address. Would you mind taking a look? Thanks!

The updated version of Wordfence (Version 6.1.6) seems to have resolved the issues we were having once and for all. Thanks!

You’re welcome! I’ll let you know whether or not I can reproduce these results.