Re: thread already active.

2021-03-21 Thread James Beal
On 21/03/2021 16:06:40, James Beal wrote: We have a fairly complex nginx config however the vhost that I know I am having issues is quiet simple. We have  aio threads ; enabled  James Beal:  Turning aio off fixes the issue but doesn't seem op

thread already active.

2021-03-21 Thread James Beal
We have a fairly complex nginx config however the vhost that I know I am having issues is quiet simple. We have  aio threads ; enabled  /usr/sbin/nginx -V nginx version: nginx/1.19.6 built by gcc 8.3.0 (Debian 8.3.0-6) built with OpenSSL 1.1.1d  10 Sep 2019 TLS SNI support enabled configure arg

re: nginx stuck in tight loop sometimes ( sorry for new thread )

2021-01-19 Thread James Beal
Sorry I was subscribed via the digest so this ended up being a new thread ( i have subscribed for each message ). Are you able to reproduce the problem without any 3rd party modules? Since nginx itself does not use pipes, this looks like a pagespeed problem. Not really we use about 500mb/s of ba

nginx stuck in tight loop sometimes

2021-01-19 Thread James Beal
We have quite a high volume site, we have 4 front end nginx servers, each: * AMD EPYC 7402P 24-Core Processor * INTEL SSDPELKX020T8 ( 2TB NVMe ) * Dual  Broadcom BCM57416 NetXtreme-E 10GBase-T * 512GB of RAM We have a fairly complex nginx config with sharded caches as explained in https://www.ngin

Re: cache key > 1049 characters results in 502

2018-08-24 Thread James Beal via nginx
On 24/08/2018 08:59:09, James Beal wrote: We currently use caching for guests, our search pages use long urls to pass the parameters to our application. Currently searches that worked for logged in users don't work for guests. I can show the issue with these two curl examples ( which ar

cache key > 1049 characters results in 502

2018-08-24 Thread James Beal via nginx
We currently use caching for guests, our search pages use long urls to pass the parameters to our application. Currently searches that worked for logged in users don't work for guests. I can show the issue with these two curl examples ( which are not obviously valid searches ) As a guest jame