• Resolved Roger Correia

    (@correiar)


    I am running the latest version of Wordfence ((6.3.5). For the past several weeks, the scan does not complete and logs a 30 second timeout error.

    I reviewed the documentation, and followed all suggestions:
    – our ISP limits execution time to 30 seconds, so I set Maximum execution time for each scan stage to 24 seconds (80% as suggested); this had no effect
    – I then set it to 15 seconds, again no effect
    – lastly set it to 20 seconds, turned on Debug mode and re-ran scan; last 20 lines of log attached below:

    Wordfence Full Activity Log
    [Mar 29 09:37:40:1490794660.694412:1:error] <br /> <b>Fatal error</b>: Maximum execution time of 30 seconds exceeded in <b>/home/tdpc/public_html/wp-content/plugins/s2member/src/includes/classes/utils-logs.inc.php</b> on line <b>129</b><br />
    [Mar 29 09:37:16:1490794636.829110:4:info] Scan process ended after forking.
    [Mar 29 09:37:00:1490794620.881292:4:info] Calling Wordfence API v2.23:https://noc1.wordfence.com/v2.23/?v=4.7.3&s=http%3A%2F%2Ftdpc.ca&k=cf8bae0e1056b1f52724df958d2c73d96578af2f8ad62e927af92ea37c1463e9cf22017a3475e1f280f939b1f1ddeb8e08d5dc84de97b483be2ecbb23e76b8599e780de69e42d7285b28d13798593d5e&openssl=268439647&phpv=5.6.30&betaFeed=0&cacheType=disabled&action=get_patterns
    [Mar 29 09:37:00:1490794620.880526:10:info] SUM_START:Scanning files for URLs in Google’s Safe Browsing List
    [Mar 29 09:37:00:1490794620.879925:10:info] SUM_START:Scanning file contents for infections and vulnerabilities
    [Mar 29 09:37:00:1490794620.878583:10:info] SUM_ENDOK:Check for publicly accessible configuration files, backup files and logs
    [Mar 29 09:37:00:1490794620.878031:10:info] SUM_START:Check for publicly accessible configuration files, backup files and logs
    [Mar 29 09:37:00:1490794620.866926:10:info] SUM_ENDOK:Scanning for known malware files
    [Mar 29 09:37:00:1490794620.866301:10:info] SUM_ENDOK:Scanning for unknown files in wp-admin and wp-includes
    [Mar 29 09:37:00:1490794620.865607:10:info] SUM_ENDOK:Comparing core WordPress files against originals in repository
    [Mar 29 09:37:00:1490794620.865500:2:info] Analyzed 8446 files containing 137.62 MB of data.
    [Mar 29 09:37:00:1490794620.864778:4:info] Scanning: /home/tdpc/public_html/xmlrpc.php (Mem:64.2M)
    [Mar 29 09:37:00:1490794620.864081:4:info] Scanning: /home/tdpc/public_html/wp-trackback.php (Mem:64.2M)
    [Mar 29 09:37:00:1490794620.863181:4:info] Scanning: /home/tdpc/public_html/wp-signup.php (Mem:64.2M)
    [Mar 29 09:37:00:1490794620.862463:4:info] Scanning: /home/tdpc/public_html/wp-settings.php (Mem:64.2M)
    [Mar 29 09:37:00:1490794620.861812:4:info] Scanning: /home/tdpc/public_html/wp-mail.php (Mem:64.2M)
    [Mar 29 09:37:00:1490794620.860797:4:info] Scanning: /home/tdpc/public_html/wp-login.php (Mem:64.2M)
    [Mar 29 09:37:00:1490794620.860131:4:info] Scanning: /home/tdpc/public_html/wp-load.php (Mem:64.2M)
    [Mar 29 09:37:00:1490794620.859559:4:info] Scanning: /home/tdpc/public_html/wp-links-opml.php (Mem:64.2M)
    [Mar 29 09:37:00:1490794620.858982:4:info] Scanning: /home/tdpc/public_html/wp-includes/wp-diff.php (Mem:64.2M)
    [Mar 29 09:37:00:1490794620.857150:4:info] Scanning: /home/tdpc/public_html/wp-includes/wp-db.php (Mem:64.2M)
    [Mar 29 09:37:00:1490794620.856569:4:info] Scanning: /home/tdpc/public_html/wp-includes/wlwmanifest.xml (Mem:64.2M)
    [Mar 29 09:37:00:1490794620.855411:4:info] Scanning: /home/tdpc/public_html/wp-includes/widgets.php (Mem:64.2M)
    [Mar 29 09:37:00:1490794620.854787:4:info] Scanning: /home/tdpc/public_html/wp-includes/widgets/class-wp-widget-text.php (Mem:64.2M)

    Please advise

Viewing 5 replies - 1 through 5 (of 5 total)
  • wfyann

    (@wfyann)

    Hi Roger (@correiar),

    Do you have access to the web server error logs (/var/log/httpd/error_log or /var/log/apache2/error.log)?

    If so could you check if there are any error/warning messages around the same time as in the Wordfence Activity Log (Mar 29 09:37:40)

    Wordfence may be able to locate the error log for you:

    • Go to the Wordfence Options page
    • Click on the Diagnostics tab
    • Just above the Other Tests section you will see an array “Log Files (Error messages from WordPress core, plugins, and themes)
    • Click the download link

    Also, could you please check the Wordfence System Info page:

    • Go to the Wordfence Tools page
    • Click the Diagnostics tab
    • n the Other Tests section (near the bottom of the page), click the link that reads “Click to view your system’s configuration in a new window“. This will open the Wordfence System Info page.

    and check the following parameters:

    • Loaded Configuration File
    • PHP Version
    • cURL support
    • cURL Information
    Thread Starter Roger Correia

    (@correiar)

    I found the following recent errors in the logs:

    [24-Mar-2017 03:21:55 UTC] PHP Fatal error: require(): Failed opening required ‘wfBrowscapCache.php’ (include_path=’.:/opt/cpanel/ea-php56/root/usr/share/pear’) in /home/tdpc/public_html/wp-content/plugins/wordfence/lib/wfBrowscap.php on line 87

    [25-Mar-2017 10:24:02 UTC] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 2995 bytes) in /home/tdpc/public_html/wp-includes/functions.php on line 435

    [28-Mar-2017 05:47:24 UTC] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 4352 bytes) in /home/tdpc/public_html/wp-includes/functions.php on line 435

    [29-Mar-2017 12:23:14 UTC] PHP Fatal error: Class ‘c_ws_plugin__s2member_utils_logs’ not found in /home/tdpc/public_html/wp-content/plugins/s2member/src/includes/classes/auto-eots.inc.php on line 306

    and the other information you requested:

    Loaded Configuration File: opt/cpanel/ea-php56/root/etc
    PHP Version: 5.6.30
    cURL support: enabled
    cURL Information: 7.53.1

    wfyann

    (@wfyann)

    Hi Roger (@correiar),

    The issue seems to be related to the s2Member plugin.

    Could you temporarily disable that plugin and run a new Wordfence scan?

    Have you recently updated the s2Member plugin (in the last few weeks or so)? If so, I suggest you contact the plugin authors to check with them what causes the error you found in the error logs:

    PHP Fatal error: Class ‘c_ws_plugin__s2member_utils_logs’ not found in /home/tdpc/public_html/wp-content/plugins/s2member/src/includes/classes/auto-eots.inc.php on line 306

    Thread Starter Roger Correia

    (@correiar)

    It does appear that the issue is a conflict between s2Member and Wordfence.

    s2Member was last updated on February 11. Wordfence was updated about a week ago. The problem just started happening recently, so I suspect that the issue was introduced with the latest Wordfence update.

    I deactivated s2Member and ran a WF scan. It completed successfully with no issues.

    Once I re-activate s2Member and run a WF scan, it never completes and the following error shows up in the Activity Log:

    Fatal error: Maximum execution time of 30 seconds exceeded in /home/tdpc/public_html/wp-content/plugins/s2member/src/includes/classes/utils-logs.inc.php on line 128

    It appears that the module referenced is s2Member’s logging routine

    Thread Starter Roger Correia

    (@correiar)

    As a follow on to my previous note, s2Member has it’s own logging function, which was ENABLED in my configuration. This was probably left over from testing we were doing earlier in the year. Normally this function is DISABLED.

    Once I DISABLED logging in s2Member, Wordfence was able to complete it’s scan successfully.

    I guess both plugins were competing for logging space. You may close this ticket.

    Thanks for your support and getting me to take a closer look at my settings.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Fatal Error – Scan aborts / does not complete’ is closed to new replies.