In some cases the nginx processes won’t stop normally when it’s
service
is
stopped (workers are still busy), it is advised to add this line:
TASKKILL /F /IM “nginx*”
at the end of your ‘ngx_stop.cmd’ file to make sure no workers are
left
behind before a new master and workers are started
Source changes back ported
Source changes add-on’s: no changes
Changes for nginx_basic: Source changes back ported
Scheduled release: no (openssl fixes)
Additional specifications: see ‘Feature list’
This is a non scheduled release of the last in the Gryphon series
Hey itpp i am curious if you know the cause of a bug with your windows
nginx
builds.
It is something to do with the worker processes.
For some reason when i have “worker_processes auto;” i will occasionaly
recieve a unknown web server error (usualy means a timeout) from
cloudflare,
but when i set it to “worker_processes 1;” i do not recieve the error
is
there some kind of dropped request between nginx and the very first
connection to a new worker process ?
Its like it drops or cancels the first request for the worker process
when
its auto. Its very difficult to figure out what has been causing the
error.
And with my “worker_processes 1;” set to be 1 worker will it ever be
restarted or need to restart or it should be fine like that. because i
deliever all my traffic just fine with one worker still but that timeout
error occassionaly was annoying everyone.
Don’t use auto, set worker_processes to a value where high performance
keeps
cpu(s) around 50% max, this can be 2, 4, etc…
Windows server 2012 is AFAIK the only version which can scale cpu’s
where
the auto value has any use.
Some cpu’s can easily handle 2-4 workers per cpu, some only 1 per cpu,
this
varies because there are a number of variables like cpu type, bus type
and
speed, xeon quads, how many real cpu lines going to each cpu, type of
HT,
etc…
We runs test with 4 workers on 1 vcpu which works fine on xen, hv and vb
but
not on vmware (2 max).