Hi,
I'm running Starman 0.4014 behind nginx 1.10.0 on Ubuntu 16.04.1
with Linux 4.4.0 (with nginx and Starman on separate servers).
I get immediate 502 errors from Nginx if all five Starman worker
processes are busy, even if I have recently (re-)started the
Starman master process.
As the --backl
That's a command I didn't know about - thanks!
My traffic is bursty, rather than steadily high.
Whenever I manage to execute "ss -tl", on the load balancer or
the backend, I see all zeros in the Recv-Q column, even if I've
occupied the Starman workers.
To be sure, I'm not certain that I've occupi
Indeed, workers were crashing and getting restarted.
What helped me track down which requests were crashing, and how,
amidst the other junk echoed to my console was:
1. export STARMAN_DEBUG=1
2. Stop echoing all bytes sent to the console when STARMAN_DEBUG==1
3. Add a debugging echo upon each rea
