Resource Exhaustion
159 incident problems that show up as “Resource Exhaustion”.
먼저 읽을 가이드
추천 문제
All problems (159)
SECURITY-288A parser normalization fix improves usernames while scheduled SIEM exports still query the old field shapes and emit empty reports during a failover rehearsalDashboards look healthy and nightly reporting continues living in the previous schema. Normal traffic masked the issue until the standby or alternate path became active under rehearsal conditions.SecurityIntermediate17 minFreeSECURITY-240A telemetry parser lowercases usernames while one detection still depends on the old mixed-case service account form during a failover rehearsalThe data is normalized and one analytic still expects the previous representation. Normal traffic masked the issue until the standby or alternate path became active under rehearsal conditions.SecurityIntermediate17 minFreeSECURITY-131A CSP report-only endpoint loops back through the same proxy path and turns a small XSS burst into an internal traffic floodDetection remains enabled, but the reporting path amplifies rather than observes the incident.SecurityIntermediate15 minFreeLINUX-071logrotate copytruncate races with a high-write process and drops critical linesThe rotation completes, but incident evidence is missing because copytruncate cut the file while the application was still writing heavily.LinuxIntermediate15 minFreeLINUX-061journald rate limiting drops repeated kernel alerts during a packet stormThe host is noisy during the incident, but the most useful log lines never reach disk because journald suppression hides repeated bursts.LinuxIntermediate16 minFreeLINUX-060Package manager lock remains after a dead process and blocks patch automationThe scheduled patch job says another package process is running, but the real blocker is an abandoned lock or stale transaction state from an older failure.LinuxBeginner14 minFreeK8S-106CronJob timezone is configured but the controller resumes a suspended object on the next stale schedule windowOperators unsuspend a job expecting the new timezone to apply cleanly, yet the controller immediately runs an old missed schedule slot.KubernetesIntermediate15 minFreeK8S-113PersistentVolume expansion finishes in the controller but the filesystem resize never happensCapacity looks larger in the API, yet the container still sees the old filesystem size because the final online resize step never occurred.KubernetesIntermediate16 minFreeLINUX-004An open log-file problem where space is not freed even after logrotate runsCovers a common operational trap where swapping the log file without restarting the service still does not free space.LinuxBeginner18 minFreeLINUX-037Tmpfs exhaustion in /run prevents a daemon socket from startingDisk usage on persistent filesystems looks normal, but the service socket cannot be created because the tmpfs used for runtime state is full.LinuxBeginner15 minFreeK8S-053CronJob launches overlapping runsThe schedule looks correct, but long-running executions stack on top of each other and double-process the same workload window.KubernetesBeginner16 minFreeLINUX-034LVM extend succeeds but XFS filesystem size never changesThe volume group and logical volume show the new capacity, yet the mounted filesystem still reports the old size because the final grow step never ran.LinuxBeginner16 minFreeLINUX-015After a jemalloc config change, memory is stable but CPU spikesAfter a jemalloc config change, memory is stable but CPU spikes is a hands-on troubleshooting drill. Analyzes a situation where changing the allocator to optimize memory instead increases CPU cost. Linux Service Operations needs to be checked by narrowing scope, recent change,...LinuxAdvanced27 minProK8S-018GPU workloads stay Pending even though the cluster autoscaler is onGPU workloads stay Pending even though the cluster autoscaler is on is a hands-on troubleshooting drill. A situation where the autoscaler is working but the workload waits because of a special node-group condition. Kubernetes Scheduling and Capacity needs to be checked by narr...KubernetesAdvanced29 minProLINUX-013A ulimit setting applied to the shell but not reflected in the systemd serviceA ulimit setting applied to the shell but not reflected in the systemd service is a hands-on troubleshooting drill. A situation where manual testing is fine but the actual service process hits a file-descriptor shortage. Linux Service Operations needs to be checked by narrowin...LinuxAdvanced24 minProK8S-007A metrics pipeline problem where scaling does not rise even though an HPA is attachedTracks the metrics flow in a situation where resource usage is high but the autoscaler does not react.KubernetesAdvanced26 minProNETWORK-016Packets arrive, but new connections fail due to conntrack table saturationA situation where the firewall and network are alive but new sessions cannot open due to the kernel connection-tracking limit.NetworkAdvanced29 minProSECURITY-156A SIEM dashboard shows the new field names, but the scheduled incident export still queries the old schema and sends empty nightly reportsInteractive analysis is fine, yet one automated reporting path still depends on the legacy field map.SecurityAdvanced16 minProSECURITY-095SIEM parser update collapses two source IP fields and the threat hunt queries miss half the trafficLogs are arriving, but hunting results look incomplete because the updated parser rewrote field names that saved searches still depend on.SecurityAdvanced16 minProSECURITY-110A SIEM correlation rule misses an after-hours brute-force chainRaw events arrive, but the analytic never fires because time bucketing no longer aligns with the intended incident window.SecurityAdvanced17 minPro