Blog

SSH, Linux, and production operations — page 29

Practical runbooks for servers, containers, databases, cloud hosting, incident response, and safe AI-assisted operations.

Linux free vs available memory: stop fearing the page cache

The search intent behind this problem is deciding whether memory pressure is real.

The Tryssh team · July 21, 2026 →

Linux packet drops: interface, kernel, socket, or application

The search intent behind this problem is locating where packets disappear.

The Tryssh team · July 21, 2026 →

Linux OOM killer analysis: read the victim selection

The search intent behind this problem is understanding host exhaustion before adding memory.

The Tryssh team · July 21, 2026 →

Too many open files: find the leak before raising limits

Determine whether descriptors are sockets, files, pipes, or duplicate handles; a larger ceiling only lengthens the leak's fuse.

The Tryssh team · July 21, 2026 →

Linux patching without surprise reboots or broken services

Patch in stages, know which services need restart, preserve console access, and validate the application—not only package-manager success.

The Tryssh team · July 21, 2026 →

Linux performance debugging: the first 10 minutes

The search intent behind this problem is identifying CPU, memory, storage, network, or lock pressure.

The Tryssh team · July 21, 2026 →

Linux process stuck in D state: why kill -9 does not work

When tracing a task waiting inside the kernel, speed comes from ordering the investigation—not from typing more commands.

The Tryssh team · July 21, 2026 →

Linux PSI: detect CPU, memory, and I/O contention

When using stall time to quantify resource pressure, speed comes from ordering the investigation—not from typing more commands.

The Tryssh team · July 21, 2026 →

Suspect a Linux rootkit? Preserve evidence before installing scanners

Preserve evidence before installing scanners needs a third approach—read the effective state, understand the recovery path, then tighten one boundary at a time.

The Tryssh team · July 21, 2026 →

Linux routing table debugging: which path will this packet take?

The search intent behind this problem is reading destination, source address, metric, policy, and namespace.

The Tryssh team · July 21, 2026 →

Linux swap is used but memory is available: is that bad?

The search intent behind this problem is interpreting cold-page eviction and active swap pressure.

The Tryssh team · July 21, 2026 →

systemd start request repeated too quickly

The search intent behind this problem is diagnosing the crash loop behind StartLimitHit.

The Tryssh team · July 21, 2026 →

Zombie processes on Linux: what they consume and who must reap them

The search intent behind this problem is finding the parent that failed to collect exit status.

The Tryssh team · July 21, 2026 →

Load balancer health check failing while the app looks healthy

The search intent behind this problem is reproducing source, path, host header, status, and timeout.

The Tryssh team · July 21, 2026 →

Request IDs that actually correlate logs across services

The search intent behind this problem is designing identifiers with propagation and searchable structure.

The Tryssh team · July 21, 2026 →

Logs vs metrics vs traces: which signal answers what?

The search intent behind this problem is choosing the cheapest signal that can prove a production hypothesis.

The Tryssh team · July 21, 2026 →

Managed database vs self-hosted: price the pager

The search intent behind this problem is comparing service fees with backup, patching, failover, and expertise.

The Tryssh team · July 21, 2026 →

Production dashboard design: questions before charts

The search intent behind this problem is building a view that supports a concrete operating decision.

The Tryssh team · July 21, 2026 →

Black-box vs white-box monitoring: combine symptom and cause

The search intent behind this problem is deciding what to observe from outside and inside.

The Tryssh team · July 21, 2026 →

Monitoring retention: choose by investigation window, not habit

The search intent behind this problem is balancing cost, resolution, and forensic value.

The Tryssh team · July 21, 2026 →

MTU black hole: small requests work, large ones hang

The search intent behind this problem is identifying path-MTU and blocked fragmentation signals.

The Tryssh team · July 21, 2026 →

Multi-region architecture cost: duplicate capacity and data movement

The search intent behind this problem is pricing the recovery promise rather than the diagram.

The Tryssh team · July 21, 2026 →

Multi-region database recovery: replication is not a backup

The search intent behind this problem is planning failover, consistency, and split-brain prevention.

The Tryssh team · July 21, 2026 →

MySQL backup consistency: transactions, locks, and binary logs

The search intent behind this problem is choosing a backup method that matches engine and recovery goal.

The Tryssh team · July 21, 2026 →