master or worker process is responsible for listening the port?

Hi, I am keeping add and remove a listening port in and from nignx using "-s reload", and found sometimes this port was listened by master process, sometimes was by a worker process. Is this as expected? Br, Allen___ nginx mailing list

Re: Quick successive reload makes "bind () xxxx failed, Address already in use" error

This is the forever loop that it it running in the script for { nginx -s reload //without the port nginx -s reload //with the port } I found there was a transient that both the master process and the newly forked worker were listening the same port, I am not sure if this

Quick successive reload makes "bind () xxxx failed, Address already in use" error

Hi, I have a script runs two successive reloads, the first one is to remove a listen port from the stream block, and the second one is to add the same port back to the stream block. It is observed that most time the script would run into "bind() failed, Address already in use" error.

Re: unbearable reload downtime when introducing a new server block

Hi, In my case, I need to add new server block from time to time in nginx. after reloading, it is observed that the newly added server is not available for seconds. is this as expected? how to improve it? BR, Joe___ nginx mailing list

unbearable reload downtime when introducing a new server block

Hi, In my case, I need to add new server block from time to time in nginx. after reloading, it is observed that the newly added server is not available for seconds. is this as expected? how to improve it? BR, Joe___ nginx mailing list

Re: having nginx listen the same port more than once

now I understand the duplicate listen ports configured in the http block can be used to implement virtual hosts. but what's the purpose to allow this in the stream block? in my practise (with 1.9.15.1), nginx will randomly select a backend to serve the tcp/udp request which seems useless.

答复: Re: having nginx listen the same port more than once

now I understand the duplicate listen ports configured in the http block can be used to implement virtual hosts. but what's the purpose to allow this in the stream block? in my practise (with 1.9.15.1), nginx will randomly select a backend to serve the tcp/udp request which seems useless.

having nginx listen the same port more than once

Hi, I observe that the nginx runs with no error if there are duplicate listen ports configured in the http server block or stream server block. is this behavior as expected? and if a request comes at such a port, which server would serve this request, by radomly or round-robin?

having nginx listen the same port more than once

Hi, I observe that the nginx runs with no error if there are duplicate listen ports configured in the http server block or stream server block. is this behavior as expected? and if a request comes at such a port, which server would serve this request, by radomly or round-robin? Thanks,