• I updated from a 7.2x version that worked fine, to 7.3.1 and got a gateway timeout. My server was so bogged down that I could not log in with a shell either. FTP was still working, so I renamed wordfence.php in the plugin’s file and was able to recover after WordPress automatically disabled the plugin.

    This is an NGINX multisite installation and I also run WordPress Persistent Login (https://www.ads-software.com/plugins/wp-persistent-login/) which is the most likely thing to interfere with security software.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Hey @elkrat,

    I’ve installed and activated the plugin you shared, and I’m not having any issues.

    If you reactivate Wordfence do you still run into the issue? If so, are you able to share your PHP error logs from around the time the error occurs?

    Please let me know.

    Thanks,

    Gerroald

    Thread Starter elkrat

    (@elkrat)

    I tried a fresh install and the same situation arose. It’s a production environment so I could only leave it for a second. It looks like all my memory is gone. Maybe tonight when my subscribers are dormant I can leave it on and run a top command to see which service is maxed out.

    I haven’t been in the error log for a while and I need to clean up some situations that are throwing a lot of little errors. This is likely my fault and not yours.

    PHP message: PHP Fatal error: Allowed memory size of 1073741824 bytes exhausted (tried to allocate 262144 bytes) in /usr/share/nginx/wordpress/wp-includes/functions.php on line 4390
    PHP message: PHP Fatal error: Allowed memory size of 1073741824 bytes exhausted (tried to allocate 262144 bytes) in Unknown on line 0″ while reading response header from upstream, client: xx.xx.xxx.xxx, server: , request: “GET /wp-admin/network/plugins.php?activate=true&plugin_status=all&paged=1&s= HTTP/2.0”, upstream: “fastcgi://unix:/var/run/php/php7.0-fpm.sock:”, host: “example.com”, referrer: “https://example.com/wp-admin/network/plugin-install.php?s=wordfence&tab=search&type=term”

    Thread Starter elkrat

    (@elkrat)

    Well, a second fresh install and everything is fine. No other changes, not even a PHP restart. Maybe it was the server load when I tried it earlier.

    Thread Starter elkrat

    (@elkrat)

    14 hrs later it happened again. I don’t know exactly what happens, but all my RAM got allocated and then kswap consumed 95% CPU while 11 separate PHP processes fought over the rest. Actually I was over my CPU allotment on the VM.

    Here is a screenshot:
    Screenshot

    • This reply was modified 5 years, 6 months ago by elkrat.
    • This reply was modified 5 years, 6 months ago by elkrat.
Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Site fails to load after updating WordFence’ is closed to new replies.