Hello!
On Sat, Dec 10, 2022 at 09:52:37AM +0100, Charlie Kilo wrote:
> we have roundabout 7k ips in use, 3k ipv6, 4k ipv4 and 52 workers.
> that results in ~364000 ips which need to be bound - twice that in sockets
> if i count port 80 and 443.
>
> we have indeed reuseport active - we already
Hi Maxim,
we have roundabout 7k ips in use, 3k ipv6, 4k ipv4 and 52 workers.
that results in ~364000 ips which need to be bound - twice that in sockets
if i count port 80 and 443.
we have indeed reuseport active - we already thought about using a
wildcard-address on a socket, but didnt have time
Hello!
On Mon, Dec 05, 2022 at 09:43:18PM +0100, Charlie Kilo wrote:
> I know the problem also from an environment with many sites and thousands
> of ips to bind to. for us the problem is that nginx binds every worker to
> every ip sequentially - leading to a restart time of 10-15 minutes. the
I know the problem also from an environment with many sites and thousands
of ips to bind to. for us the problem is that nginx binds every worker to
every ip sequentially - leading to a restart time of 10-15 minutes. the
problem can easily be observed using strace on the master process during
Yes - He is right; everything is revolves around DNS and even my error is
with DNS resolving as it was not able to resolve the ocsp.godaddy.com hence
please troubelshoot from DNS perspetive.
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,295945,295964#msg-295964
Am 04.12.22 um 08:04 schrieb blason:
Yes - He is right; everything is revolves around DNS and even my error is
with DNS resolving as it was not able to resolve the ocsp.godaddy.com hence
please troubelshoot from DNS perspetive.
Hello List,
To avoid this problems I prefer
Yes - He is right; everything is revolves around DNS and even my error is
with DNS resolving as it was not able to resolve the ocsp.godaddy.com hence
please troubelshoot from DNS perspetive.
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,295945,295963#msg-295963
Hello!
On Thu, Dec 01, 2022 at 12:40:08AM -0300, Gus Flowers Starkiller wrote:
> Hi, please could anyone tell me why the nginx service takes too much time
> to restart? As we know, after some change with nginx the service must be
> restarted, I do this with "nginx -s reload" or "systemctl
Hi,
Did you check error log or syslog? Is that spitting out any errors? Do you
have SSL_OCSP settings configured and it might not be able to reach to the
protocol?
I mean I had 45 portals and was facing a same issue. Later when I done the
debug I found that ocsp.godaddy.com was not reachable
Hi, please could anyone tell me why the nginx service takes too much time
to restart? As we know, after some change with nginx the service must be
restarted, I do this with "nginx -s reload" or "systemctl restart nginx",
and this takes some three minutes or more. This process is happening in
10 matches
Mail list logo
