Merry Christmas & Happy 2027! Less downtime. More good times. Celebrating 13 years of sorlavit.com
Skip to content
Sorlavit KimIT Support, Network & Infrastructure Services Let’s talk

ปุ่มแปลไทยจะเปิดบทความผ่าน Google Translate เพื่อแปลอัตโนมัติ โดยคงโค้ดและคำสั่งไว้ตามต้นฉบับ

Linux Server / Boot, systemd & Service Recovery

Check the running service's open-file limit rather than the login shell's

An application can exhaust file descriptors even though an administrator's ulimit looks generous. Inspect the actual service process context.

Compiled for Sorlavit Kim · Published · Updated · 1 min read

Environment and inputs: Linux server baseline · Ubuntu 24.04 LTS / RHEL 9-style systems. Use the specified distribution, init system and installed tool; service names, privileges and supported options can differ.

Start with this check

Confirm the host, shell and access role. Replace sample names, paths, domains and interfaces with approved targets. These are diagnostic commands; assess policy and workload impact before making changes.

systemctl show app.service -p MainPID -p LimitNOFILE

Read the result

The unit properties show the main process and configured limit. For the actual live process, verify its /proc limits and descriptor use through approved read access.

Resolve and verify

Compare growth with connection and file-handle lifecycle. Fix leaks first, then plan a bounded limit adjustment with host-wide capacity in mind.

Before changing production

Do not raise every limit indefinitely or assume a new shell setting changes a running daemon.

Source & further reading

systemd manual — systemd.exec

Independently written summary reviewed on 2026-11-01. The example illustrates a possible application; it is not a client case study.

Share this article

Back to all articles