Technology · PRACTICAL GUIDE
Too many levels of symbolic links? Find the looping component before changing the path
Separate a real cycle from an overdeep chain, trace each component, identify the link owner, and replace only the broken entry.
WATCH AT EASE · PRACTICAL GUIDE
Guides
Answers to everyday questions, checked for current relevance.
97–120 / 359
Technology · PRACTICAL GUIDE
systemd status=226/NAMESPACE? Prove the failed namespace operation before disabling hardening
Capture the first detailed journal error, map every namespace directive to its resource, and change one proven boundary instead of removing the sandbox.
Technology · PRACTICAL GUIDE
UnsupportedClassVersionError? Prove the class and loading JVM before changing Java
The error already names both sides of a compatibility mismatch. Preserve the class major, artifact and real launcher; decide whether to raise the runtime or retarget the build; clean every stale output; then verify the same entrypoint in local, CI and production-like contexts.
Technology · PRACTICAL GUIDE
JSONDecodeError at line 1 column 1? Inspect the bytes before fixing the parser
Character zero says where decoding failed, not why. Preserve the status, media type, body length and a safe byte fingerprint; classify empty, HTML, decoding or truncated input; repair the producer or caller contract; then verify valid, empty and invalid fixtures.
Technology · PRACTICAL GUIDE
npm says “getaddrinfo EAI_AGAIN”? Prove the resolver context before changing DNS
Capture the exact registry hostname and failing shell, CI, WSL or container; test name resolution there, then separate npm proxy, TLS and registry failures without hard-coding an IP.
Technology · PRACTICAL GUIDE
Redis says “MISCONF … unable to persist to disk”? Prove the failed RDB boundary before re-enabling writes
Do not treat CONFIG SET stop-writes-on-bgsave-error no as proof of recovery. Capture the client error, runtime RDB path, server log, filesystem and INFO persistence; repair one measured cause, then require a successful BGSAVE, updated snapshot, and representative write.
Technology · PRACTICAL GUIDE
Linux says “fork: Resource temporarily unavailable”? Prove the exhausted task budget first
Distinguish per-user, cgroup, systemd and kernel PID or thread ceilings before raising limits, killing processes or rebooting.
Technology · PRACTICAL GUIDE
PostgreSQL says ‘could not resize shared memory segment’? Prove the exhausted filesystem first
ENOSPC does not prove the database data disk is full. Preserve the exact allocation error, inspect the mount from PostgreSQL’s own runtime namespace, connect the peak to the failing workload, then change one proven boundary and repeat the same operation.
Technology · PRACTICAL GUIDE
Linux says “Text file busy”? Identify the executing inode before overwriting or retrying
ETXTBSY can mean a deployment tried to write a running executable, or a launcher tried to execute a file still open for writing. Preserve the failing syscall, process, inode and namespace before killing anything; then repair the race or replace the pathname atomically.
Technology · PRACTICAL GUIDE
Nginx says “upstream prematurely closed connection”? Align the backend timeline before raising timeouts
This log means Nginx reached an upstream but the peer ended the exchange before the expected response completed. Preserve the exact phase and upstream address, correlate the same request with process exits or restarts, then change one boundary and replay safely.
Technology · PRACTICAL GUIDE
Linux says “inotify watch limit reached”? Prove which process and limit failed before raising sysctls
ENOSPC from inotify can mean per-user instance exhaustion, per-user watch exhaustion, or a different queue-overflow condition. Attribute live descriptors and watched objects first, then narrow the scope or raise only the proven boundary.
Technology · PRACTICAL GUIDE
NFS says “Stale file handle”? Prove which server identity changed before remounting
ESTALE means a stored reference no longer names a valid object. Separate mount-time export failure from operation-time object failure, fix the server boundary, then reconnect one client and verify the workload.
Technology · PRACTICAL GUIDE
pandas CSV IDs changed despite string dtype? Trace the value before and after import
A four-row test separates numeric inference, missing-value rules and damage already written into the CSV. A late string conversion cannot undo them all.
Technology · PRACTICAL GUIDE
rsync says “Broken pipe (32)”? Find the first failing endpoint before tuning SSH
The sender message often arrives after the receiver or remote shell has already failed. Preserve both logs, order the errors, repair the first boundary, then verify the resumed copy.
Technology · PRACTICAL GUIDE
Git says a branch is already checked out in another worktree? Prove the owner before pruning or forcing
List every linked worktree, preserve dirty or unpushed work, then distinguish a live owner from a moved, offline or missing path before choosing remove, repair, prune, detach or another branch.
Technology · PRACTICAL GUIDE
ZIP lists files but cannot read them? Check each member and Python's decoder
Four controlled ZIPs show why a readable directory, an unsupported method and a bad CRC require different decisions.
Technology · PRACTICAL GUIDE
Git LFS says a file should have been a pointer? Repair the index without losing the working copy
Preserve the file first, prove which attribute and Git object disagree, then choose a narrow renormalization or a coordinated history migration and verify a fresh clone.
Technology · PRACTICAL GUIDE
Cron job works manually but not from crontab? Recreate the scheduled context before changing the script
First prove cron launched the line. Then diff the real user, shell, environment, working directory and output path against the successful terminal run, and verify one scheduled execution.
Technology · PRACTICAL GUIDE
GNU make says jobserver unavailable? Prove the recursive boundary before adding -j
The child fell back to one job because coordination was not inherited. Trace the first parent recipe or wrapper, restore only a truly jobserver-aware boundary, then measure the shared limit.
Technology · PRACTICAL GUIDE
Git “detected dubious ownership”: verify the owner boundary before adding safe.directory
Treat the fatal message as an identity mismatch, not a nuisance warning. Check the Git process user, repository owner, mount path and configuration scope before granting one narrow exception.
Technology · PRACTICAL GUIDE
curl error 77? Prove which CA file or directory failed before replacing certificates
Error 77 means curl could not read the selected CA certificate location. Identify the binary, TLS backend, override and effective path; then test traversal, bytes and store structure before repairing one input and retesting without insecure mode.
Technology · PRACTICAL GUIDE
curl error 18? Prove the missing bytes before retrying or resuming
CURLE_PARTIAL_FILE means curl received a size that did not match the size the peer announced. Preserve the partial artifact, response headers and trace; then isolate framing, protocol and intermediary behavior before a safe restart or validator-bound resume.
Technology · PRACTICAL GUIDE
“Invalid cross-device link”? Prove the syscall before copying or deleting
EXDEV can mean a cross-mount rename—or a path-resolution policy refusal. Capture the caller and syscall, compare mount IDs, then choose a transfer contract that keeps the source until the destination is verified.
Technology · PRACTICAL GUIDE
systemd status=218/CAPABILITIES? Prove the manager, kernel and capability sets first
The application may not have run at all. Preserve the first journal error, read the effective unit, separate system, user and container boundaries, and change only the capability transition that evidence shows is invalid.