Hi, In some domains, i got the error (in error.log): Code: [proxy_fcgi:error] (70007)The timeout specified has expired I can see that error happen at 5 minutes after script execution. I change the vhost file to 900 seconds, but still after 5 minutes the same error Code: <IfModule mod_fastcgi.c> <Directory /home/web468/cgi-bin> Require all granted </Directory> <Directory /var/www/**hidden**.com/web> <FilesMatch "\.php[345]?$"> SetHandler php5-fcgi </FilesMatch> </Directory> <Directory /home/web468/web> <FilesMatch "\.php[345]?$"> SetHandler php5-fcgi </FilesMatch> </Directory> Action php5-fcgi /php5-fcgi virtual Alias /php5-fcgi /home/web468/cgi-bin/php5-fcgi-*-80-**hidden**.com FastCgiExternalServer /home/web468/cgi-bin/php5-fcgi-*-80-**hidden**.com -idle-timeout 900 -socket /var/lib/php7.0-fpm/web468.sock -pass-header Authorization -pass-header Content-Type </IfModule> <IfModule mod_proxy_fcgi.c> #ProxyPassMatch ^/(.*\.php[345]?(/.*)?)$ unix:///var/lib/php7.0-fpm/web468.sock|fcgi://localhost//home/web468/web/$1 <Directory /home/web468/web> <FilesMatch "\.php[345]?$"> SetHandler "proxy:unix:/var/lib/php7.0-fpm/web468.sock|fcgi://localhost" </FilesMatch> </Directory> </IfModule> What i forgot?
Do you have an actual error in your application or do you just see that lines in the log file? If you refer just to lines in a log without having an actual error, then I recommend to ignore them.
What you changed is the idle timeout, but idle means that the process is not in use. If it affects your application, then you must hit an other timeout like a max execution timeout or so. Beside that, you made the change in the mod_fastcgi section, but according to the error, I would guess that you use mod_proxy_fcgi which is the second config section and there are no timeouts set at all, so you probably hit a timeout that is set globally somwhere in your apache config.
It depends on the Linux Distribution, e.g on Debian 8, it's mod_fastcgi, on Debian 9, it's mod_proxy_fcgi as mod_fastcgi des not exist on latest Distributions anymore and has been replaced with mod_proxy_fcgi. You can e.g. use the command: apachectl -M to get a list of the loaded module to see which one of them is used.
It's Debian 9 Code: ~# apache2ctl -M AH00548: NameVirtualHost has no effect and will be removed in the next release /etc/apache2/sites-enabled/000-ispconfig.conf:73 Loaded Modules: core_module (static) so_module (static) watchdog_module (static) http_module (static) log_config_module (static) logio_module (static) version_module (static) unixd_module (static) access_compat_module (shared) actions_module (shared) alias_module (shared) auth_basic_module (shared) authn_core_module (shared) authn_file_module (shared) authz_core_module (shared) authz_host_module (shared) authz_user_module (shared) autoindex_module (shared) deflate_module (shared) dir_module (shared) env_module (shared) fcgid_module (shared) filter_module (shared) headers_module (shared) include_module (shared) mime_module (shared) mpm_prefork_module (shared) negotiation_module (shared) perl_module (shared) php7_module (shared) proxy_module (shared) proxy_fcgi_module (shared) python_module (shared) reqtimeout_module (shared) rewrite_module (shared) setenvif_module (shared) socache_shmcb_module (shared) ssl_module (shared) status_module (shared) suexec_module (shared)
