Linux
390 incident problems in Linux environments.
먼저 읽을 가이드
추천 문제
All problems (390)
SECURITY-1331An Elastic API key rotation succeeds and one Beats pipeline still gets 401An Elastic API key rotation succeeds and one Beats pipeline still gets 401 focuses on Identity And Access and asks the reader to isolate the key signal in Linux. Key rotation success in storage does not prove the runtime consumer has...SecurityAdvanced15 minProSECURITY-1332An OpenSearch role mapping looks correct and SSO users still lose accessAn OpenSearch role mapping looks correct and SSO users still lose access focuses on Deployment Governance and asks the reader to isolate the key signal in Linux. An auth token can contain the right roles under the wrong shape for a plugin th...SecurityAdvanced15 minProSECURITY-1324An SSH certificate rollout is correct and clients still choose the wrong identityA certificate-based SSH migration is rolled out and some users still fail even though the correct certificate is present in their environment.SecurityAdvanced15 minProSECURITY-1609A CrowdSec parser fix is correct and one decision stream still misses attacksOne decision stream still misses attacks after a CrowdSec parser fix.SecurityAdvanced9 minProSECURITY-1397A fail2ban jail matches the right event and bans nothingA fail2ban jail matches the right event and bans nothing focuses on incident-response and asks the reader to isolate the key signal in Linux. Security automation often breaks on log-shape migrations that preserve human reada...SecurityIntermediate10 minProSECURITY-1387A fail2ban rule triggers on the right log lines and never blocks the clientA fail2ban rule triggers on the right log lines and never blocks the client focuses on incident-response and asks the reader to isolate the key signal in Linux. Detection and enforcement can drift apart when one consumes par...SecurityIntermediate10 minProLINUX-1607An nftables update is correct and one reboot still restores the old ruleOne reboot restores the old firewall rule after nftables cleanup.LinuxAdvanced10 minProLINUX-1358A journald limit is raised and disk pressure persistsOperators tune journald aggressively and later discover that node disk pressure barely changes during the next incident spike.LinuxAdvanced13 minProLINUX-1366A journald limit is raised and disk pressure remainsAn operator raises journald limits during an incident and later sees no real improvement in node disk pressure.LinuxAdvanced13 minProSECURITY-1316An SSH CA rollout signs host certificates correctly and engineers still get...An SSH CA rollout signs host certificates correctly and engineers still get... focuses on Identity And Access and asks the reader to isolate the key signal in Linux. SSH CA incidents often hide in stale host cert issuance rather t...SecurityIntermediate13 minProNETWORK-1385A recursive resolver forwards correctly and DNSSEC validation fails only for...A recursive resolver forwards correctly and DNSSEC validation fails only... focuses on reverse-proxy-security and asks the reader to isolate the key signal in Linux. Suffix exceptions can accidentally route one domain around the trust guaran...NetworkAdvanced14 minProLINUX-1392A rootless container runtime works on one host and fails on anotherA rootless container runtime works on one host and fails on another focuses on Identity And Access and asks the reader to isolate the key signal in Linux. User namespace failures often come from host identity allocation conflicts rather than f...LinuxAdvanced14 minProLINUX-1362A rootless Docker host survives reboot and later loses outbound connectivityA rootless Docker host survives reboot and later loses outbound connectivity focuses on network-segmentation and asks the reader to isolate the key signal in Linux. Rootless restore issues after reboot often come from helper lif...LinuxAdvanced14 minProLINUX-1323A rootless Docker service works until rebootA node image refresh is followed by rootless container services staying down after reboot until someone logs in manually.LinuxAdvanced14 minProLINUX-1336A rootless Podman or Docker service survives upgrades and failsA rootless Podman or Docker service survives upgrades and fails focuses on Runner Hygiene and asks the reader to isolate the key signal in Linux. Rootless startup is a contract between systemd user units and the user lifecycle itself.LinuxAdvanced14 minProNETWORK-1395A validating resolver answers quickly and one internal zone fails DNSSECA validating resolver answers quickly and one internal zone fails DNSSEC focuses on reverse-proxy-security and asks the reader to isolate the key signal in Linux. High-availability DNS exceptions can quietly weaken validati...NetworkAdvanced14 minProSECURITY-1335An Ubuntu unattended upgrade secures packages and leaves one bastion inaccessibleA hardened bastion receives unattended upgrades and later downstream systems that pin host identity stop trusting it.SecurityIntermediate14 minProLINUX-1340A boot upgrade leaves one host without DNSA boot upgrade leaves one host without DNS focuses on cluster-maintenance and asks the reader to isolate the key signal in Linux. DNS failures after upgrades can come from two healthy components disagreeing on which interface is primary.LinuxAdvanced15 minProLINUX-1316A chronyd recovery brings NTP back and Kerberos still failsA host boots with skew, later synchronizes, and only long-running identity-bound daemons continue failing.LinuxAdvanced15 minProLINUX-1324A firewall reload drops production trafficA firewall automation refactor is shipped and operators later see short traffic drops aligned exactly with every policy reload.LinuxAdvanced15 minPro