gunicorn.connections.active

Currently active client connections

Dimensions:None

Technical Annotations (26)

Configuration Parameters (4)

worker_connections

low values cause worker hangs with keepalive connections under concurrent load

workersrecommended: (2 * CPU) + 1

Standard formula suggests 33 workers for 16-core server, currently using 12

threadsrecommended: 3

Alternative hybrid approach: 10 workers with 3 threads each

worker_classrecommended: gevent

enables asynchronous handling of multiple connections per worker

Error Signatures (2)

connect() failed (111: Connection refused)log pattern

502http status

CLI Commands (6)

curl --unix-socket /run/gunicorn.sock http://diagnostic

systemctl status gunicorndiagnostic

systemctl status caddydiagnostic

dmesg -T | egrep -i 'memory'diagnostic

dmesg -T | egrep -i 'oom'diagnostic

ulimit -ndiagnostic

Technical References (14)

/run/gunicorn.sockfile pathsystemd socket activationconceptRDScomponentgthreadcomponentkeepaliveconceptsync workerscomponentI/O-boundconceptulimitconceptkeepalive timeoutconceptsocket accept queueconceptbacklogconceptgthread workercomponentself.nr_connscomponentself.worker_connectionscomponent

Related Insights (9)

Slow backend responses cause concurrent request memory buildupwarning

▸

Gunicorn unix socket hangs for 2-45 minutes before self-recoverycritical

▸

Multiple Gunicorn servers freeze simultaneously indicating shared resource deadlockcritical

▸

gthread workers hang at worker_connections limit with keepalive connectionscritical

▸

Performance degradation at 400 connections despite low resource utilizationwarning

▸

Connection queuing with sync workers under high concurrent loadwarning

▸

Nginx connection refused errors with no application logswarning

▸

Request duration metric excludes socket accept queue timewarning

▸

gthread worker accepts connections beyond thread capacitywarning

▸