fork: retry: Resource temporarily unavailable (process/thread limit)
The user or container hit its maximum number of processes/threads (ulimit -u, pids cgroup), so new processes can’t be created.
Seen on:
Linux
Meaning
Thread-heavy apps (Java, Chrome, build tools), fork bombs or leaked processes exhaust nproc/pids limits even with plenty of RAM. Containers often have a pids limit, and systemd sets TasksMax per service.
Common causes
- User nproc limit reached (ulimit -u)
- systemd TasksMax for the service
- Container pids limit
- Process/thread leak
⚡ Quick fix
- Count processes: ps -eLf | wc -l / ps -u user | wc -l
- Raise limits (limits.conf, TasksMax, --pids-limit)
- Fix the leak
Detailed fix by platform
Linux
- bash
ulimit -u ps -eLf | wc -l systemctl show myapp -p TasksMax # /etc/security/limits.d/90-nproc.conf * soft nproc 65535
How to diagnose
- Count — Threads per user/service
- Limits — ulimit -u, TasksMax, pids.max
- Leak — Growing over time?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
Most viewed in Linux
Other ways to find it
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
Was this page helpful?
Report a correction or suggest an improvement
Last updated 7 Oct 2026