Apache graceful restarts and FastCGI - mod_fcgid: can't lock process table in pid

Re: Apache graceful restarts and FastCGI - mod_fcgid: can't lock process ta

When will cPanel integrate the bug fix?

 

Re: Apache graceful restarts and FastCGI - mod_fcgid: can't lock process ta

If that's the case, is it safe to add the cronjob until you decide how to address this? Please confirm this.

FastCGI is the handler adviced by CloudLinux and it would be great if it worked out of the box.

 

Re: Apache graceful restarts and FastCGI - mod_fcgid: can't lock process ta

Can you confirm if theres a bug regarding this or if I should complete it at http://go.cpanel.net/bugs?

I thought the cron to kill PHP procceses was harmless but Installatron recently confirmed a problem with an installation because of this.

 

Re: Apache graceful restarts and FastCGI - mod_fcgid: can't lock process ta

I missed a previous answer, seems like the bug is already submitted (#2464286).

I've found Optimizing FastCGI for cPanel. Any experienced server administrator could confirm that these proposed changes might allow us to delete the crontab that kills PHP procceses?

 

Re: Apache graceful restarts and FastCGI - mod_fcgid: can't lock process ta

yes, been MONTHS again

why this is taking so long~~~

 

Re: Apache graceful restarts and FastCGI - mod_fcgid: can't lock process ta

This is an alternative cron proposed by Installatron to avoid causing trouble to Installatron's installations, in case it helps anyone.

Code:

ps -eo uid,pid,lstart,command |
    tail -n+2 |
    while read PROC_UID PROC_PID PROC_LSTART_WDAY PROC_LSTART_MONTH PROC_LSTART_DAY PROC_LSTART_TIME PROC_LSTART_YEAR PROC_COMMAND; do
        SECONDS=$[$(date +%s) - $(date -d"$PROC_LSTART_WDAY $PROC_LSTART_MONTH $PROC_LSTART_DAY $PROC_LSTART_TIME $PROC_LSTART_YEAR" +%s)]
        if  "$PROC_COMMAND" == */usr/bin/php* ; then
            if [ $PROC_UID -gt 0 -a $SECONDS -gt 600 ]; then
                echo $PROC_PID
            fi
        fi
     done |
     xargs kill 

 

Re: Apache graceful restarts and FastCGI - mod_fcgid: can't lock process ta

is this problem showing any lights of resolving?

 

Re: Apache graceful restarts and FastCGI - mod_fcgid: can't lock process ta

It's 99% fixed, but sometimes appears again, use this cron:
ps auxwwwf | grep '[0-9] /usr/bin/php' | awk '{ print $2 }' | xargs kill -9 >> /dev/null 2>&1
If you want 100% no problem, i can't help you... but cPanel Dev Team may be; make a ticket if you can reproduce the error

 

Re: Apache graceful restarts and FastCGI - mod_fcgid: can't lock process ta

In hope of having this fixed too :\

 

Any update on this?

 

Hello:

I did:

- wget http://apache.rediris.es//httpd/mod_fcgid/mod_fcgid-2.3.9.tar.gz
- untar, configure.apxs, make and make install.
- go to httpd.conf and remove the loadmodule for fcgid, because it is already loaded at php.conf.... so saved and rebuild httpd.conf

It seems stable...

Do you think it is a good idea to use last stable mod_fcgid, although needing to do this every easyapache rebuild of apache?

Why does cpanel maintain a mod_fcgid version from almost 3 years ago, like the 2.3.6 ??

PD: I will look for that fcgid errors when graceful reloading apache.

Thanks.

- - - Updated - - -

Finally, after doing some apachectl -k graceful, got one line at error_log:

So, the last mod_fcgid does not solve this problem at all. There are client getting errors sometimes when reloading apache graceful.

 

Hello:

As I am using nginx frontend, I have configured:

And at vhosts, replaced to:

This way, if 502 or http petition going wrong due to Apache graceful restart and fcgid being lost, the front does news tries transparently to the user...

I am afraid this could lead to repeated POSTs or modifications at mysql, if by example a POST is being retried...

I am studying this behaviour and if it is possible and how to solve it.... is possible to separate POST from GET, but usually GET also could do changes at mysql...

But other problem is this one!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Lost fcgid proccesses, are killed by cron, but the fcigdsock is already there....

Do you think it is a good idea to cron also removing this files if they are older than!?

Thanks.