Facebook
Twitter
-
If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
CentOS2Alma discussion
plesk 12 --> [warn] mod_fcgid: process xxxx graceful kill fail, sending SIGKILL
- Thread starter hans14
- Start date
[root@srv conf.d]# tail -f /var/log/httpd/error_log
[Fri Sep 19 18:05:09 2014] [warn] Init: Name-based SSL virtual hosts only work for clients with TLS server name indication support (RFC 4366)
[Fri Sep 19 18:05:10 2014] [notice] Apache/2.2.15 (Unix) DAV/2 mod_fcgid/2.3.9 mod_python/3.3.1 Python/2.6.6 mod_ssl/2.2.15 OpenSSL/1.0.1e-fips mod_perl/2.0.4 Perl/v5.10.1 configured -- resuming normal operations
[Fri Sep 19 18:09:41 2014] [warn] mod_fcgid: process 17525 graceful kill fail, sending SIGKILL
[Fri Sep 19 18:09:57 2014] [warn] mod_fcgid: process 17538 graceful kill fail, sending SIGKILL
[Fri Sep 19 18:10:37 2014] [warn] mod_fcgid: process 17555 graceful kill fail, sending SIGKILL
[Fri Sep 19 18:10:41 2014] [warn] mod_fcgid: process 17584 graceful kill fail, sending SIGKILL
[Fri Sep 19 18:11:30 2014] [warn] mod_fcgid: process 17589 graceful kill fail, sending SIGKILL
[Fri Sep 19 18:11:46 2014] [warn] mod_fcgid: process 17592 graceful kill fail, sending SIGKILL
[Fri Sep 19 18:12:38 2014] [warn] mod_fcgid: process 17610 graceful kill fail, sending SIGKILL
[Fri Sep 19 18:12:38 2014] [warn] mod_fcgid: process 17607 graceful kill fail, sending SIGKILL
[Fri Sep 19 18:14:03 2014] [warn] mod_fcgid: process 17625 graceful kill fail, sending SIGKILL
[Fri Sep 19 18:14:19 2014] [warn] mod_fcgid: process 17629 graceful kill fail, sending SIGKILL
[Fri Sep 19 18:15:00 2014] [warn] mod_fcgid: process 17641 graceful kill fail, sending SIGKILL
[Fri Sep 19 18:15:27 2014] [warn] mod_fcgid: process 17645 graceful kill fail, sending SIGKILL
[Fri Sep 19 18:15:51 2014] [warn] mod_fcgid: process 17650 graceful kill fail, sending SIGKILL
[Fri Sep 19 18:16:09 2014] [warn] mod_fcgid: process 17655 graceful kill fail, sending SIGKILL
[Fri Sep 19 18:17:07 2014] [warn] mod_fcgid: process 17673 graceful kill fail, sending SIGKILL
[Fri Sep 19 18:17:13 2014] [warn] mod_fcgid: process 17672 graceful kill fail, sending SIGKILL
[Fri Sep 19 18:18:25 2014] [warn] mod_fcgid: process 17693 graceful kill fail, sending SIGKILL
[Fri Sep 19 18:19:05 2014] [warn] mod_fcgid: process 17702 graceful kill fail, sending SIGKILL
[Fri Sep 19 18:05:09 2014] [warn] Init: Name-based SSL virtual hosts only work for clients with TLS server name indication support (RFC 4366)
[Fri Sep 19 18:05:10 2014] [notice] Apache/2.2.15 (Unix) DAV/2 mod_fcgid/2.3.9 mod_python/3.3.1 Python/2.6.6 mod_ssl/2.2.15 OpenSSL/1.0.1e-fips mod_perl/2.0.4 Perl/v5.10.1 configured -- resuming normal operations
[Fri Sep 19 18:09:41 2014] [warn] mod_fcgid: process 17525 graceful kill fail, sending SIGKILL
[Fri Sep 19 18:09:57 2014] [warn] mod_fcgid: process 17538 graceful kill fail, sending SIGKILL
[Fri Sep 19 18:10:37 2014] [warn] mod_fcgid: process 17555 graceful kill fail, sending SIGKILL
[Fri Sep 19 18:10:41 2014] [warn] mod_fcgid: process 17584 graceful kill fail, sending SIGKILL
[Fri Sep 19 18:11:30 2014] [warn] mod_fcgid: process 17589 graceful kill fail, sending SIGKILL
[Fri Sep 19 18:11:46 2014] [warn] mod_fcgid: process 17592 graceful kill fail, sending SIGKILL
[Fri Sep 19 18:12:38 2014] [warn] mod_fcgid: process 17610 graceful kill fail, sending SIGKILL
[Fri Sep 19 18:12:38 2014] [warn] mod_fcgid: process 17607 graceful kill fail, sending SIGKILL
[Fri Sep 19 18:14:03 2014] [warn] mod_fcgid: process 17625 graceful kill fail, sending SIGKILL
[Fri Sep 19 18:14:19 2014] [warn] mod_fcgid: process 17629 graceful kill fail, sending SIGKILL
[Fri Sep 19 18:15:00 2014] [warn] mod_fcgid: process 17641 graceful kill fail, sending SIGKILL
[Fri Sep 19 18:15:27 2014] [warn] mod_fcgid: process 17645 graceful kill fail, sending SIGKILL
[Fri Sep 19 18:15:51 2014] [warn] mod_fcgid: process 17650 graceful kill fail, sending SIGKILL
[Fri Sep 19 18:16:09 2014] [warn] mod_fcgid: process 17655 graceful kill fail, sending SIGKILL
[Fri Sep 19 18:17:07 2014] [warn] mod_fcgid: process 17673 graceful kill fail, sending SIGKILL
[Fri Sep 19 18:17:13 2014] [warn] mod_fcgid: process 17672 graceful kill fail, sending SIGKILL
[Fri Sep 19 18:18:25 2014] [warn] mod_fcgid: process 17693 graceful kill fail, sending SIGKILL
[Fri Sep 19 18:19:05 2014] [warn] mod_fcgid: process 17702 graceful kill fail, sending SIGKILL
U
UFHH01
Guest
Hello hans14,
please go to your domain - Webserver settings and there you will see two editor ( http + https ) boxes. In both of them, please add:
If you confirm your edits with the "o.k" - Button, Plesk will rewrite your vhost - conf for http and https with the additional setting. Please do this for EVERY domain, because fcgid wants this that way and you can then restart the apache2 again with "service apache2 restart".
The basic timeout is defined a bit too less in the standard - configurations of PHP ( sometimes this setting in the fcgid.conf is even commented out completly ) and so you might have some problems/issues with timeouts/kills, which result in restarts. The new setting increases this setting for your apache2 and you will hopefully get rid of that errors.
In later versions of mod-fcgid this is handled a bit better and you don't have to put such settings in your http - conf of every domain. ^^
please go to your domain - Webserver settings and there you will see two editor ( http + https ) boxes. In both of them, please add:
IPCCommTimeout 120
If you confirm your edits with the "o.k" - Button, Plesk will rewrite your vhost - conf for http and https with the additional setting. Please do this for EVERY domain, because fcgid wants this that way and you can then restart the apache2 again with "service apache2 restart".
The basic timeout is defined a bit too less in the standard - configurations of PHP ( sometimes this setting in the fcgid.conf is even commented out completly ) and so you might have some problems/issues with timeouts/kills, which result in restarts. The new setting increases this setting for your apache2 and you will hopefully get rid of that errors.
In later versions of mod-fcgid this is handled a bit better and you don't have to put such settings in your http - conf of every domain. ^^
U
UFHH01
Guest
Plesk provides a Linux AddOn, for "Advanced Apache and NGINX directives" - you could read some more of that at: Plesk - Documentation: Installation, Upgrade, Migration, and Transfer Guide, Parallels Plesk 12.0. Please install this extensions, which are located inside the "Webhosting Features" ( Apache web server support + Nginx web server and reverse proxy support )
Thanks again
This components are enabled, please, see my attachment, but in the doc i can read this:
Note: If you have upgraded from the older Plesk version and are configuring the vhost.conf and vhost_ssl.conf files for the first time after the upgrade, you will need to use the httpdmng utility to apply the changes from your configuration files. For example, to generate web server configuration files for a website, run the command: /usr/local/psa/admin/sbin/httpdmng --reconfigure-domain <domain_name>
Then i run this command:
/usr/local/psa/admin/sbin/httpdmng --reconfigure-domain mydomain.com
-bash: /usr/local/psa/admin/sbin/httpdmng: No such file or directory
this script (httpdmng) it's missing in my box
This components are enabled, please, see my attachment, but in the doc i can read this:
Note: If you have upgraded from the older Plesk version and are configuring the vhost.conf and vhost_ssl.conf files for the first time after the upgrade, you will need to use the httpdmng utility to apply the changes from your configuration files. For example, to generate web server configuration files for a website, run the command: /usr/local/psa/admin/sbin/httpdmng --reconfigure-domain <domain_name>
Then i run this command:
/usr/local/psa/admin/sbin/httpdmng --reconfigure-domain mydomain.com
-bash: /usr/local/psa/admin/sbin/httpdmng: No such file or directory
this script (httpdmng) it's missing in my box
Attachments
U
UFHH01
Guest
... and? ^^ ... all fine now? Or do you need further assistance? If YES, plrase do tell us, what you did from the suggestions and what problems/issues you have, to continue from the new state.
My problems:
- i've 2 ips in my box, but when i've upgraded my plesk, the root have now a ipv6 ¿? and i can't view my old subscrition with this user
- i've added ngix+php-fpm, but in a domain have http/https options, and, in another domain i no have that options
- i've continous errores 50x
Thanks
- i've 2 ips in my box, but when i've upgraded my plesk, the root have now a ipv6 ¿? and i can't view my old subscrition with this user
- i've added ngix+php-fpm, but in a domain have http/https options, and, in another domain i no have that options
- i've continous errores 50x
Thanks
U
UFHH01
Guest
o.k.... it seems that you have not well configured your hosting, since the upgrade from "only apache" to "apache + nginx" ... let's investigate some more, to help you:
Please open the error.log 's from apache and nginx and paste the entries, which point to this failure. If you don't know, where these logs are, please visit: Parallels Plesk Panel for Linux services logs and configuration files ( KB: 111283 )
The more informations you give to us, the better is the help/suggestion you are getting in this forum.
Please open the error.log 's from apache and nginx and paste the entries, which point to this failure. If you don't know, where these logs are, please visit: Parallels Plesk Panel for Linux services logs and configuration files ( KB: 111283 )
The more informations you give to us, the better is the help/suggestion you are getting in this forum.
U
UFHH01
Guest
The first step, which always is a good solution, is to use the current bootstrapper, so that known problems might be found and corrected by Plesk itself. It solves most of all known problems regarding false configurations, strange config settings and simple database - problems.
Be aware, that this path is to the latest bootstrapper, depending on your system and updates/upgrades/patches, this path might be slightly different. If the command doesn't work for you, try "ls /usr/local/psa/bootstrapper/" to list your own most recent version and correct the path to that command.
Sometimes bootstrapper fails with some failures because of broken updates/upgrades and/or patches. To make sure, that the latest upgrades/updates and patches are installed without issues, you might use:
If these two steps don't result to any fixes, please reply with the log - entries of the failures, because guessing isn't the best way to help you.
/usr/local/psa/bootstrapper/pp12.0.18-bootstrapper/bootstrapper.sh repair
Be aware, that this path is to the latest bootstrapper, depending on your system and updates/upgrades/patches, this path might be slightly different. If the command doesn't work for you, try "ls /usr/local/psa/bootstrapper/" to list your own most recent version and correct the path to that command.
Sometimes bootstrapper fails with some failures because of broken updates/upgrades and/or patches. To make sure, that the latest upgrades/updates and patches are installed without issues, you might use:
/usr/local/psa/admin/bin/autoinstaller --select-product-id plesk --select-release-current --reinstall-patch --install-component base
If these two steps don't result to any fixes, please reply with the log - entries of the failures, because guessing isn't the best way to help you.