jbrose11
Forum Replies Created
-
Forum: Localhost Installs
In reply to: PHP-FPM processes uninterruptible sleep during WordPress updatesWhat should the settings be for fastcgi Timeout in Apache and max_execution_time in php.ini if request_terminate_timeout is used? Thanks
Forum: Localhost Installs
In reply to: WordPress upgrades then 503 errors until have to rebootWe are in process of moving PHP-FPM from “dynamic” to “on demand”, at least for our individual sites pools. Looks like that may be a mistake.
Unless the new longer ProxyTimeOut and max_execution_time settings prevent that circumstance.
At this point we have request_terminate_timeout in PHP-FPM set to “0” (off), the default value.
So you are saying request_terminate_timeout would be better than using PHP-FPM “ondemand” and it’s pm.process_idle_timeout setting..
So if someone was doing a WordPress core upgrade, and the WordPress PHP upgrade script was waiting on cURL past PHP-FPM pm.process_idle_timeout, and we were using “ondemand” would the PHP script be terminated before the WordPress upgrade could complete?
Forum: Localhost Installs
In reply to: WordPress upgrades then 503 errors until have to rebootSo if I understand what you are saying …
PHP does not count waiting on curl to respond against the “max_execution_time”
However, it does count against the Apache ProxyTimeOut
So … PHP-FPM processes keep running, but Apache disconnects from the PHP process if it reaches 60 seconds in our case.
1) I do not understand why when this is happening that the pm.max_children of PHP-FPM is always reached and none of the php-fpm processes seem to get released
2) and none of the php-fpm processes seem to terminate get freed to be used by other connections
Forum: Localhost Installs
In reply to: WordPress upgrades then 503 errors until have to rebootThank you for your assistance. It is appreciated.
Regarding “Apache counts that time towards its proxy timeout setting, but PHP does not. And if Apache kills the request due to reaching its timeout setting” it seems just increasing ProxyTimeout could have an impact.
I don’t think I mentioned that sometimes users can upgrade their site ok with no problems. Sometimes we get the above error. I have since learned that some users have quite a few installations of WordPress and may be trying to do a bunch of upgrades at once on occasion.
Those folks seem to have caused this problem at least 50% of times it has occurred.
We have …
KeepAliveTimeout 1
TimeOut 60
ProxyTimeout 60max_execution_time 30
Forum: Localhost Installs
In reply to: WordPress upgrades then 503 errors until have to rebootWe currently use the defaults for timeouts and execution time for all the components involved.
When you say “This is a distinct possibility during a WP core update.”
What timeouts do you use in Apache and fastcgi for PHP-FPM and also things like max_execution_time in PHP?
Forum: Localhost Installs
In reply to: WordPress upgrades then 503 errors until have to rebootThis seems to be the first error entry tied to problems ….
“The timeout specified has expired: [client xxx.xxx.xxx.xxx:xxxxx] AH01075: Error dispatching request to :, referer: https://somesite.com/wp-admin/update-core.php?action=do-core-upgrade
Then a bunch of this type …
[Mon Apr 01 14:26:45.998971 2019] [proxy_fcgi:error] [pid 26422:tid 139964645857024] (70007)The timeout specified has expired: [client xxx.xxx.xxx.xxx:63031] AH01075: Error dispatching request to :, referer: https://somesite.com/sub1/sub2/
Forum: Localhost Installs
In reply to: System load spikes significantly after WordPress upgradeI should have added, we typically have to reboot to make the system usable again. Restarting PHP-FPM or Apache does not seem to correct the problem
What about a method that uses sftp instead of ftps?