I seem to have a random occasional 502 bad gateway error, this might happen even when no users are using Frappe / Erpnext.
I wonder why and still can’t find the culprit.
I’m running this versions:
Frappe Builder: v1.x.x-develop () (develop)
commit: v1.0.0 (main)
Frappe Drive: v0.0.1 (main)
ERPNext: v15.38.0 (version-15)
ERPNext Shipping: v15.0.2 (version-15)
Frappe Framework: v15.43.0 (version-15)
Helpdesk: v0.10.0 (develop)
Frappe HR: v15.30.0 (version-15)
Frappe Insights: v3.0.0 (develop)
Frappe Lending: v0.0.1 (develop)
Frappe LMS: v1.0.0 (develop)
Payments: v0.0.1 (develop)
Print Designer: v1.x.x-develop () (develop)
Raven: v2.0.0 (develop)
Webshop: v0.0.1 (develop)
Whitelabel: v0.0.1 (version-15)
Wiki: v2.0.0 (master)
this is my supervisor config:
[program:frappe-bench-frappe-web]
command=/home/erpnext/frappe-bench/env/bin/gunicorn -b 127.0.0.1:8000 -w 9 --threads 10 --max-requests 5000 --max-requests-jitter 500 -t 120 frappe.app:application --preload
priority=4
autostart=true
autorestart=true
stdout_logfile=/home/erpnext/frappe-bench/logs/web.log
stderr_logfile=/home/erpnext/frappe-bench/logs/web.error.log
user=erpnext
directory=/home/erpnext/frappe-bench/sites
[program:frappe-bench-frappe-schedule]
command=/usr/local/bin/bench schedule
priority=3
autostart=true
autorestart=true
stdout_logfile=/home/erpnext/frappe-bench/logs/schedule.log
stderr_logfile=/home/erpnext/frappe-bench/logs/schedule.error.log
user=erpnext
directory=/home/erpnext/frappe-bench
[program:frappe-bench-frappe-default-worker]
command=/usr/local/bin/bench worker --queue default
priority=4
autostart=true
autorestart=true
stdout_logfile=/home/erpnext/frappe-bench/logs/worker.log
stderr_logfile=/home/erpnext/frappe-bench/logs/worker.error.log
user=erpnext
stopwaitsecs=1560
directory=/home/erpnext/frappe-bench
killasgroup=true
numprocs=17
process_name=%(program_name)s-%(process_num)d
[program:frappe-bench-frappe-short-worker]
command=/usr/local/bin/bench worker --queue short
priority=4
autostart=true
autorestart=true
stdout_logfile=/home/erpnext/frappe-bench/logs/worker.log
stderr_logfile=/home/erpnext/frappe-bench/logs/worker.error.log
user=erpnext
stopwaitsecs=360
directory=/home/erpnext/frappe-bench
killasgroup=true
numprocs=17
process_name=%(program_name)s-%(process_num)d
[program:frappe-bench-frappe-long-worker]
command=/usr/local/bin/bench worker --queue long
priority=4
autostart=true
autorestart=true
stdout_logfile=/home/erpnext/frappe-bench/logs/worker.log
stderr_logfile=/home/erpnext/frappe-bench/logs/worker.error.log
user=erpnext
stopwaitsecs=1560
directory=/home/erpnext/frappe-bench
killasgroup=true
numprocs=17
process_name=%(program_name)s-%(process_num)d
[program:frappe-bench-redis-cache]
command=/usr/bin/redis-server /home/erpnext/frappe-bench/config/redis_cache.conf
priority=1
autostart=true
autorestart=true
stdout_logfile=/home/erpnext/frappe-bench/logs/redis-cache.log
stderr_logfile=/home/erpnext/frappe-bench/logs/redis-cache.error.log
user=erpnext
directory=/home/erpnext/frappe-bench/sites
[program:frappe-bench-redis-queue]
command=/usr/bin/redis-server /home/erpnext/frappe-bench/config/redis_queue.conf
priority=1
autostart=true
autorestart=true
stdout_logfile=/home/erpnext/frappe-bench/logs/redis-queue.log
stderr_logfile=/home/erpnext/frappe-bench/logs/redis-queue.error.log
user=erpnext
directory=/home/erpnext/frappe-bench/sites
[program:frappe-bench-redis-socketio]
command=/usr/bin/redis-server /home/erpnext/frappe-bench/config/redis_socketio.conf
priority=1
autostart=true
autorestart=true
stdout_logfile=/home/erpnext/frappe-bench/logs/redis-socketio.log
stderr_logfile=/home/erpnext/frappe-bench/logs/redis-socketio.error.log
user=erpnext
directory=/home/erpnext/frappe-bench/sites
[program:frappe-bench-node-socketio]
command=/usr/bin/node /home/erpnext/frappe-bench/apps/frappe/socketio.js
priority=4
autostart=true
autorestart=true
stdout_logfile=/home/erpnext/frappe-bench/logs/node-socketio.log
stderr_logfile=/home/erpnext/frappe-bench/logs/node-socketio.error.log
user=erpnext
directory=/home/erpnext/frappe-bench
[group:frappe-bench-web]
programs=frappe-bench-frappe-web,frappe-bench-node-socketio
[group:frappe-bench-workers]
programs=frappe-bench-frappe-schedule,frappe-bench-frappe-default-worker,frappe-bench-frappe-short-worker,frappe-bench-frappe-long-worker
[group:frappe-bench-redis]
programs=frappe-bench-redis-cache,frappe-bench-redis-queue,frappe-bench-redis-socketio
My Hardware:
AMD Ryzen 5 5600X 6-Core Processor
64gb of RAM
Nvme M2 SSD
There is no apparent hardware strain on the CT running Frappe.
Remains a mystery to me, but I suspect:
gunicorn -b 127.0.0.1:8000 -w 9 --threads 10 --max-requests 5000 --max-requests-jitter 500 -t 120 frappe.app:application --preload
and
numprocs=17