RHCSA
862 incident response problems that help with RHCSA prep.
먼저 읽을 가이드
추천 문제
All problems (862)
LINUX-077Rsync restore with numeric-ids shifts file ownershipThe backup looks intact, but the restored application loses access because numeric UID preservation no longer matches the target system account layout.LinuxAdvanced20 minProLINUX-068tmpfs-backed runtime path fillsThe service outage looks like a simple restart loop, but the deeper issue is runtime storage pressure from large repeated coredumps on a limited tmpfs path.LinuxAdvanced20 minProLINUX-079auditd backlog overflow drops the exact events needed to explain the breach windowAuditing is enabled, yet the highest-value records are missing because the kernel backlog overflowed during bursty activity and the team never noticed the loss signal.LinuxAdvanced21 minProLINUX-085XFS metadata corruption warning is stale but the on-call plans a destructive repair on the mounted volumeAn old alert resurfaces during an incident, and the real risk now is operator action because the filesystem is still mounted and serving production writes.LinuxAdvanced22 minProLINUX-062Missing bind mount at boot makes rsync --delete clean the host path instead of the volumeThe sync command is valid, but the intended mount point never appeared and the cleanup step now targets the underlying directory on the root filesystem.LinuxAdvanced24 minProLINUX-053rsyslog disk queue fills /var after the remote collector becomes unreachableCentral logging is configured correctly for healthy periods, but when the collector disappears the buffered queue grows until the local partition reaches pressure.LinuxAdvanced24 minProLINUX-009An rsync deploy filling the root partitionA scenario that narrows down the root cause, centered on improving the deploy tool's temp-file strategy and the partition policy, in the situation of an rsync deploy filling the root partition because of temp files.LinuxAdvanced26 minProLINUX-057RAID rebuild targets the wrong device after a degraded mdadm recoveryThe array is degraded but recoverable, and the biggest risk now is re-adding or marking the wrong member while interpreting device names under pressure.LinuxAdvanced27 minProLINUX-1606A Podman registry fix is valid and one host still pulls from the wrong mirrorOne host still pulls from the wrong mirror after a Podman registry fix.LinuxAdvanced9 minProLINUX-1610An automount cleanup is correct and one unit still mounts the old pathOne automount still mounts the old path after cleanup.LinuxAdvanced9 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-1475A journald vacuum completes and rsyslog still misses a burstCentral logging recovers after disk pressure, yet one burst of incident logs is permanently missing.LinuxAdvanced12 minProLINUX-1459An auditd dispatcher remains up and sudo becomes slowPrivilege operations become slow after an audit sink migration while auditd itself still reports healthy.LinuxAdvanced12 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 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 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 minPro