Re: Restarting service takes too much time

2022-12-10 Thread Charlie Kilo
ve to look into that again.. thank you for your suggestions in any case! On Tue, Dec 6, 2022 at 1:34 AM Maxim Dounin wrote: > 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 thousand

Re: Restarting service takes too much time

2022-12-05 Thread Charlie Kilo
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 start

Re: upgrading binary failed - execve - too long argument list

2021-05-10 Thread Charlie Kilo
let me quickly think about.nope ;) itpp2012 schrieb am Mo., 10. Mai 2021, 12:53: > You've been busy with this for 2 weeks... > > It's very easy, > 1. kill all nginx processes > 2. replace binary > 3. start nginx > 4. post some vague notice about being offline for 10 seconds and apologize > 5

Re: upgrading binary failed - execve - too long argument list

2021-05-10 Thread Charlie Kilo
> On Sat, May 08, 2021 at 10:01:19AM +0200, Charlie Kilo wrote: > > > Thanks Maxim for further explaining! > > > > We do listen to a huge number of IPs with tons of traffic and huge spikes > > on them. We really need to avoid any type > > of congestion, therefo

Re: upgrading binary failed - execve - too long argument list

2021-05-08 Thread Charlie Kilo
kernel anyways, i'll still try to look into adjusting MAX_ARG_STRLEN as a workaround. Having a solution that wouldn't make this necessary would be simply a blast though and greatly appreciated :-) On Fri, Apr 30, 2021 at 11:14 AM Charlie Kilo wrote: > correction.. if i count with > s

Re: upgrading binary failed - execve - too long argument list

2021-04-30 Thread Charlie Kilo
correction.. if i count with ss -l -t |grep http | wc -l we have around 58340 listening sockets.. at least on that machine.. On Fri, Apr 30, 2021 at 8:27 AM Charlie Kilo wrote: > Thanks a lot for the hints so far.. to provide the further info and answer > the questions.. > > get

Re: upgrading binary failed - execve - too long argument list

2021-04-29 Thread Charlie Kilo
tector -fstack-clash-protection -pipe -march=westmere -mtune=intel -O3 -I/build/nginx/boringssl/.compat/include -g' --with-ld-opt='-Wl,-z,relro,-z,now,-lgmp -ldl' On Tue, Apr 27, 2021 at 12:35 PM Charlie Kilo wrote: > Hi everyone, > i'm trying to upgrade an nginx-bina

upgrading binary failed - execve - too long argument list

2021-04-27 Thread Charlie Kilo
Hi everyone, i'm trying to upgrade an nginx-binary while running. When i do kill -s USR2 , i get the following error in the logs.. 11:40:38 [alert] 52701#0: execve() failed while executing new binary process "/opt/sbin/nginx" (7: Argument list too long) Anybody knows what exactly is in those argu