Hi Roger,
I've forgotten to ask about the nginx version, so as Maxim
Dounin recommended, please upgrade to the recent stable
version 1.22.0, https://nginx.org/en/linux_packages.html#Ubuntu
On Tue, Jun 07, 2022 at 02:42:23PM -0700, Roger Fischer wrote:
> Here are the additional details:
>
> $ una
Hello!
On Tue, Jun 07, 2022 at 01:18:36PM -0700, Roger Fischer wrote:
> My assumption is that the client requests will be distributed
> over the 24 worker processes. So no individual worker should
> come anywhere close to 1000 connections.
>
> But when I look at the process stats for the worke
its, and some go upstream.
>> So there are more than 1000 connections.
>>
>> We have 24 workers running, each configured: events { worker_connections
>> 1024; }
>>
>> We are seeing the following errors from nginx:
>> [warn] 21151#21151: 1024 worker_connections
>
> We are seeing the following errors from nginx:
> [warn] 21151#21151: 1024 worker_connections are not enough, reusing
> connections
> [crit] 21151#21151: accept4() failed (24: Too many open files)
> [alert] 21151#21151: *15716 socket() failed (24: Too many open files) while
worker_connections are not enough, reusing connections
[crit] 21151#21151: accept4() failed (24: Too many open files)
[alert] 21151#21151: *15716 socket() failed (24: Too many open files) while
connecting to upstream,
I am assuming the second and third error are for the OS limit. But the first
seems to
;s exactly right. Please read the following link [1] to get more
details.
> But we are seeing 1024 worker_connections are not enough, reusing
> connections from one worker while other workers are idle.
So, it's possibe to increase the number of those.
> Is there something we ca
Hello,
my understanding is that worker_connections applies to each worker (eg. when
set to 1024, 10 worker processes could handle up to 10240 connections).
But we are seeing 1024 worker_connections are not enough, reusing connections
from one worker while other workers are idle.
Is there
Hi,
I'm trying to use nginx as a udp loadbalancer. I got to ~40k pkt/s with my
experiments, but occasionally seeing alert message in the log saying:
worker_connections are not enough. Atm I'm using 65000 worker_connections
and still seeing the message - roughly 1 message per minut
So in this case the worker_connections should be set to at least (2 + 4 + 4)
= 10. But what should be the optimal value for this? What are the
implications of using a high number of worker connections in this case?
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,226691,267552#msg-26755
Hello!
On Mon, Feb 24, 2014 at 09:04:07AM -0500, nginx user wrote:
> I have seen errors in my logs: worker_connections are not enough while
> requesting certificate status
>
> I believe the main problem was that the worker_connections was set too low,
> and I've fixed that
I have seen errors in my logs: worker_connections are not enough while
requesting certificate status
I believe the main problem was that the worker_connections was set too low,
and I've fixed that.
However after looking at the source around the OCSP stapling, I have a
couple questions:
I have seen errors in my logs: worker_connections are not enough while
requesting certificate status
I believe the main problem was that the worker_connections was set too low,
and I've fixed that.
However after looking at the source around the OCSP stapling, I have a
question -
It appears
12 matches
Mail list logo
