From "frappe bench start" to supervisord gunicorn

Dear All,
Here is my environment: FreeBSD 10.3, FreeBSD jails, manual setup, running frappe bench as non-privileged frappe user, Nginx as reverse proxy with prescribed settings.
frappe bench start works.
All sections of the auto-generated supervisord.conf work - except the gunicorn one:
command=/usr/local/frappe/frappe-bench/env/bin/gunicorn -b -w 2 -t 120 just does:

[2017-01-23 05:34:09 +0000] [78620] [INFO] Starting gunicorn 19.6.0
[2017-01-23 05:34:09 +0000] [78620] [INFO] Listening at: (78620)
[2017-01-23 05:34:09 +0000] [78620] [INFO] Using worker: sync
[2017-01-23 05:34:09 +0000] [78628] [INFO] Booting worker with pid: 78628
[2017-01-23 05:34:09 +0000] [78629] [INFO] Booting worker with pid: 78629

I add --preload --forwarded-allow-ips "*" to the gunicorn command line for good measure, to accommodate any weirdness incurring my Nginx proxy, but no luck.

Any idea what could be the reason. The only change is, as said above, from bench start to using gunicorn with the same IPs, proxies, etc.
Any help would be greatly appreciated.


@pdvyas can you help?

Does anyone have any ideas here? So far, no feedback, nor and enlightenment :-(. Hugely appreciated.

Tough one. Try debugging nginx logs and frappe-bench/logs/frappe.log (for gunicorn)