Ignoring "Excessive resource usage" for a single account

GoWilkes

Well-Known Member
Sep 26, 2006
611
24
168
cPanel Access Level
Root Administrator
I'm moving to a new VPS that's using CentOS 7.9, PHP 7.x, PHP-FPM, FastCGI, MariaDB 10.3, HTTP/2, and mod_pagespeed.

My main site uses quite a bit of Ajax to update sections of the page, in an attempt to encourage people to hang out on the site all day and easily check for updates.

Somewhere along the way, something is causing me to get a near constant stream of warnings from CSF:

Code:
Time: Thu Dec 17 17:13:09 2020 -0500
Account: example
Resource: Process Time
Exceeded: 9032 > 1800 (seconds)
Executable: /opt/cpanel/ea-php74/root/usr/sbin/php-fpm
Command Line: php-fpm: pool www_example_com
PID: 2144 (Parent PID:16359)
Killed: No
Munin and top look fine, though, so I'm confident that I can ignore this specific warning. But if another account has a problem, or if this account has a problem that's unrelated to process time, then I don't want to ignore it.

Further, since these emails are delivered to my Gmail, I worry about inadvertently getting blacklisted!

Can you guys and gals suggest how I might stop the warning that match this specific warning? I figure that there's a magic trick with .pignore, but I'm not sure how to be that specific.
 

kodeslogic

Well-Known Member
Apr 26, 2020
319
120
118
IN
cPanel Access Level
Root Administrator

ffeingol

Well-Known Member
PartnerNOC
Nov 9, 2001
621
202
343
cPanel Access Level
DataCenter Provider
You could do it a couple of ways. in /etc/csf/csf.pignore you could do:

Code:
user:example
And everything for that user would be ignored

You could also potentially do:

Code:
pcmd:php-fpm: pool www_example_com
which uses a Perl regex to match (assuming the pool is unique for that account).
 

GoWilkes

Well-Known Member
Sep 26, 2006
611
24
168
cPanel Access Level
Root Administrator
I ended up doing this:

Code:
pcmd:php-fpm: pool [regex to match all of the appropriate sites]
I'm not thrilled with it, though, because I think that's going to remove ALL errors for these sites related to PHP-FPM, and not just the errors related to a high Process Time.

I always ask here first to see if there's a non-CSF solution, but if not then I'll ask there next :)
 
  • Like
Reactions: cPRex