Hello,
>From the documentation, I don't understand how the fastcgi_cache_revalidate
(or scgi_cache_revalidate or proxy_cache_revalidate or
uwsgi_cache_revalidate) works.
Please, can someone explain what nginx does when cache is enabled and the
revalidate directive is set to "on"?
Best Regards
Po
Hi,
On 07/08/2015 09:44 AM, evgeni22 wrote:
ok the leaking fixed , i will past here for database for other users:
that was in my php-fpm.conf
pm = ondemand
pm.max_children = 10
pm.process_idle_timeout = 60
pm.max_requests = 1000
=
after i change it to this conf the
i only not understand why pm = ondemand doing the leaking, does algorithem
in nginx not stable or it php issue ?
It contradicts your previous mails about nginx processes being the leak
point.
php(-fpm) and nginx are separate pieces of software (just communicating via
fastcgi protocol) so if
Hi,
I'm using nginx with 1 php-fpm (via unix socket), and i'm wondering if
there is a way to make nginx retry on error, something like
fastcgi_next_upstream but for the same upstream.
I would like to be able to transparently restart php-fpm and not send some
502 to the clients
So, is there a way
ok the leaking fixed , i will past here for database for other users:
that was in my php-fpm.conf
pm = ondemand
pm.max_children = 10
pm.process_idle_timeout = 60
pm.max_requests = 1000
=
after i change it to this conf the leaking stoped.
pm = dynamic
pm.max_children
