Diagnose Nginx Crashes and Errors
Budget: ₹1,500 – ₹12,500 INR
My Ubuntu-based server runs Nginx as both the webserver and an HTTP reverse proxy. Despite average utilisation staying below 50 %, I keep running into three intermittent problems:
• the nginx service suddenly stops,
• the whole OS occasionally freezes, and
• some requests return 500 errors even though the upstream application is healthy.
What I need from you is a full-scope diagnosis, clear explanation of the root cause(s), and concrete fixes. That will likely involve:
• auditing current nginx and systemd settings (nginx ‑T, unit files, limits.conf, etc.),
• analysing kernel, journal and dmesg logs for memory, I/O or cgroup problems,
• stress-testing and reproducing the 500 responses,
• tuning worker processes, buffers, time-outs and any OS limits you discover, and
• delivering a short report summarising findings plus the exact configuration or code changes applied.
Acceptance criteria
1. Nginx runs uninterrupted and the OS remains responsive for at least seven consecutive days under typical traffic.
2. No unexplained 500 errors are observed during that period.
• the nginx service suddenly stops,
• the whole OS occasionally freezes, and
• some requests return 500 errors even though the upstream application is healthy.
What I need from you is a full-scope diagnosis, clear explanation of the root cause(s), and concrete fixes. That will likely involve:
• auditing current nginx and systemd settings (nginx ‑T, unit files, limits.conf, etc.),
• analysing kernel, journal and dmesg logs for memory, I/O or cgroup problems,
• stress-testing and reproducing the 500 responses,
• tuning worker processes, buffers, time-outs and any OS limits you discover, and
• delivering a short report summarising findings plus the exact configuration or code changes applied.
Acceptance criteria
1. Nginx runs uninterrupted and the OS remains responsive for at least seven consecutive days under typical traffic.
2. No unexplained 500 errors are observed during that period.