workers and processes are indeed synonyms and the same thing. (I’m sure you’ve seen the configuration option documentation for them both) That configuration is very incorrect and could actually have no effect as a result. (I just found out that by having the cheaper option twice in one of my ini files neither was being … Read more
WID -> worker id % -> percentage of served requests by the worker PID -> process id of the worker REQ -> number of managed requests RPS -> number of current requests handled per second EXC -> number of raised exceptions SIG -> number of managed uwsgi signals (NOT unix signals !!!) STATUS -> can … Read more
I aslo ran into same issue while following some tutorial. The problem was that I set the option socket = 0.0.0.0:8000 instead of http = 0.0.0.0:8000. socket option intended to be used with some third-party router (nginx for instance), while when http option is set uwsgi can accept incoming HTTP requests and route them by … Read more