Fill the Server: 80% off your first 4 monthly invoices, monthly billing. Ends Nov 30, 2026. 25 spots in this batch.FILL25
Fill the Server, annual: about 29.63% off your first annual invoice. Ends Nov 30, 2026.FILL25Y
Fill the Server, 2 year term: about 15.69% off your first biennial invoice. Ends Nov 30, 2026.FILL25B
Fill the Server, 3 year term: about 11.11% off your first triennial invoice. Ends Nov 30, 2026.FILL25T
80% off your first 3 months, monthly billing. Ends Dec 25, 2027.3MONTHS80
50% off your first annual Shared term. Ends Dec 31, 2027.50SHARED
Shared Starter, 3 year term: C$105.84 total.MOOSE294
20% off your first 3 monthly VPS invoices. Ends Dec 31, 2027.20VPS3
25% off your first annual base VPS term.25VPS

← All guides

VPS & Linux

Linux process limits: understand ulimit, systemd and cgroup ceilings

Published August 2026 · 2 min read · Updated 2026-09-05

Linux process limits can protect a server from runaway workloads, but a limit that is too low can look like random application failure. Troubleshooting needs the exact resource: open files, processes, threads, locked memory, cgroup tasks, or a service-specific ceiling.

Read the failure and effective limit

“Too many open files,” fork failures, thread-creation errors, and service start failures point to different limits. Check the process’s effective limits through /proc, prlimit or the service manager. The interactive shell value may not apply to the service.

systemd units, containers, PAM sessions, and application runtimes can each introduce another boundary.

Measure actual usage before raising ceilings

Count file descriptors, processes, threads, sockets, and queue depth. A leak can consume any larger limit you grant, so the growth pattern matters more than the moment it hits the ceiling.

For connection-heavy services, include upstream/downstream pool limits and database connection limits in the same analysis.

Change the right configuration layer

A ulimit command in one shell will not persist for a systemd service. Update the controlling layer, validate syntax, reload configuration correctly, and restart only the affected service when a restart is required.

Avoid setting everything to extremely high values; limits also constrain blast radius.

Retest under realistic concurrency

Reproduce the workload that reached the limit and verify both usage and latency after the change. If resource use continues to grow without returning, fix the application behavior if resource use keeps growing; a larger ceiling is not the final solution.

  • Identify the exact exhausted resource.
  • Inspect the process-effective limit.
  • Measure growth before increasing it.
  • Retest under the same concurrency.

Next step

Trace process, file-descriptor and task limits across the shell, systemd and cgroups before raising a ceiling that may be protecting the server.

Explore DotMoose VPS hosting

Keep reading

Related guides.

HTTP 500, 502 and 503 errors explained for website owners

Learn what HTTP 500, 502 and 503 errors usually indicate, which layer to investigate, what evidence to collect, and when restarting a service is not the real fix.

Read the guide

Linux file permissions: ownership, modes, groups and ACLs explained

Understand Unix ownership and rwx modes, then use groups and ACLs where needed so services can access files without opening them to every user.

Read the guide

Moving a DreamHost VPS to Canadian hosting

Inventory the server, copy it safely, test it, and cut DNS over with a rollback plan.

Read the guide

More vps & linux guides

We will handle the move. You check it first.

Your current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.

Start my free moveSee plans and prices
See pricesFree move