Welcome! Log In Create A New Profile

Advanced

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

Charlie Kilo
April 30, 2021 05:16AM
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 <krikkiteer@gmail.com> wrote:

> Thanks a lot for the hints so far.. to provide the further info and answer
> the questions..
>
> getconf ARG_MAX shows 2097152
> ulimit -s shows 8192
> setting it to unlimited, doesn't change anything (also not with prlimit)
> wc -c /proc/<pid>/environ shows 1949
>
> it seems on a regular machine we have around 1200 listening sockets and do indeed use "reuseport"
>
> nginx -V shows
> nginx version: nginx/1.18.0
> built with OpenSSL 1.1.1j 16 Feb 2021
> TLS SNI support enabled
> configure arguments: --with-ipv6 --with-file-aio --with-http_ssl_module --with-http_v2_module --with-http_realip_module --with-http_stub_status_module --with-http_gzip_static_module --with-http_sub_module --without-http_scgi_module --with-stream --with-stream_ssl_module --with-stream_realip_module --with-stream_geoip_module --with-stream_ssl_preread_module --with-http_slice_module --add-module=../lua-nginx-module-0.10.15 --add-module=../headers-more-v0.25 --add-module=../ngx-devel-kit-master --add-module=../dist/nginx-rtmp-module --add-module=../build/nginx_upstream_check_module --conf-path=/etc/nginx.conf --with-mail --with-mail_ssl_module --without-mail_pop3_module --with-cc-opt='-D_FORTIFY_SOURCE=1 -fstack-protector -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 <krikkiteer@gmail.com>
> wrote:
>
>> Hi everyone,
>> i'm trying to upgrade an nginx-binary while running.
>> When i do kill -s USR2 <pid>, 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 arguments ? We have ~ 20-55 worker
>> processes if that might be related..
>> nginx-version is 1.18.0, os: debian buster
>>
>> thanks everyone in advance!
>> chris
>>
>
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Subject Author Posted

upgrading binary failed - execve - too long argument list

Charlie Kilo April 27, 2021 06:38AM

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

Francis Daly April 28, 2021 08:18AM

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

Maxim Dounin April 28, 2021 05:14PM

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

Mathew Heard April 28, 2021 06:58PM

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

Charlie Kilo April 30, 2021 02:30AM

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

Charlie Kilo April 30, 2021 05:16AM

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

Maxim Dounin May 04, 2021 11:54AM

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

Mathew Heard May 04, 2021 08:44PM

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

Charlie Kilo May 08, 2021 04:02AM

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

Maxim Dounin May 09, 2021 11:28AM

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

Charlie Kilo May 10, 2021 06:04AM

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

itpp2012 May 10, 2021 06:53AM

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

Charlie Kilo May 10, 2021 02:48PM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 71
Record Number of Users: 6 on February 13, 2018
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready