I’ve a few selected servers on which I’ve started getting issues with
mod_fcgi on. All of these servers are generally overloaded which
partially is the source of this issue.
Anyhow to break down the problem there’s multiple portions we have the
— «Normal»/»Simple» PHP-scripts (we’re talking Hello World) are sticking
around and utilizes the full IdleTimeout even though they’ve finished
processing before exiting
— On numerous occasions mod_fcgi segfaults returns: [notice] child pid
<pid> exit signal Segmentation fault (11), I take it that this happens
when a mod_fcgi wrapper terminates, however something tells me it
shouldn’t segfault on exit
— mod_fcgi drops MaxProcessCount to 0 [notice] mod_fcgid: too many
processes (current:0, max:0), skip the spawn request, prior to this the
server generally says [notice] mod_fcgid: <path>/<script>.php total
process count 120 >= 120, skip the spawn request (again due to overload)
1 and 2 is survivable but once MaxProcessCount drops we have to restart
apache to get things rollin again which isn’t all that great.
Here’s the config I’m using, we have the exact same on multiple servers
on which we don’t have any issues with.
AddHandler fcgid-script .fcgi
Please advice on what the problem could be, I’m using mod_fcgi 2.3.4.