14Your service is collecting thousands of CLOSE_WAIT sockets. What does that state mean and how do you hunt the cause?▼hard★ EssentialNewNetflixUberLinkedIn○ sign inA growing backlog of sockets waiting for the application to close its side usually points at lifecycle handling. Here is the hunt from ss output to the pool timeout that caused it.Open full answer →
22You are on a locked-down host with no agents installed. Which /proc files answer your first troubleshooting questions?▼easyNewDatadogNetflixRed Hat◆ premiumEverything top, htop and your APM agent display is derived from procfs anyway. Knowing the raw files turns any bare SSH session into a monitoring console.Open full answer →
52Two hundred pods restarted overnight and nobody knows why. How do you debug crash loops at scale, and what is the termination message for?▼medium★ EssentialNewDatadogRazorpaySwiggy◆ premiumExit codes, the previous-container log, and a little-known file at /dev/termination-log that carries a container's last words into kubectl output. Scale triage starts with classification, not with opening pods.Open full answer →
