PHP-FPM stuck

  • Resolved vingdc

    (@vingdc)


    3 years, 3 months ago

    we have a server with literally hundreds of sites hosted, and all have Wordfence installed. We’ve been seeing a lot of processes related to php-fpm getting stuck (5~8 hours), and drilling down (LSOF), its isolated to this

    /htdocs/wp-content/wflogs/attack-data.php

    These end up eating PHP pool resulting in poor server performance (we see this via TOP). We end up killing these processes manually. We all like Wordfence, but we also love a fast, reliable server. We have 5 big ones (servers), all similar with the number of sites and server specs and OS, and it’s the new one (all with Wordfence installed) performing poorly.

    Is there a way to fix this? a leak somewhere?

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support wfpeter

    (@wfpeter)

    Hi @vingdc, thanks for reaching out.

    The table of files from the lsof command lists open files rather than running scripts. The /wflogs files are always open for each hit when the WAF is in use, whether the site is running well or not. Some customers choose to use the MySQLi storage engine method with Wordfence instead of these physical files.

    It’s highly likely that one of the sites on your server was under attack, and the server couldn’t keep up with the traffic. If you have access logs from the time of the issue, that would be the best way to see how many hits were occurring, and what they were doing at the time.

    If you do see access log activity that you’d like us to look at, you can send it to wftest @ wordfence . com. Please add your forum username to the subject line respond here after you have sent it.

    Thanks,

    Peter.

    Thread Starter vingdc

    (@vingdc)

    Thank you @wfpeter. what’s the advantage of MySQL over the file logging method?

    Plugin Support wfpeter

    (@wfpeter)

    Hi @vingdc,

    There isn’t a definite advantage of one over the other. Depending on the host, one may be faster than the other if the database itself is fast and filesystem is slow, or if the filesystem is fast and database is slow.

    We’d still mainly only recommend switching to MySQLi if the filesystem method is having problems.

    Thanks,

    Peter.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘PHP-FPM stuck’ is closed to new replies.