搜索结果: "troubleshooting"

2026-09-07 拓宽：linux 63页（新增磁盘故障场景化修复 runbook 专页：8 大场景对号入座+巡检清单+数据库盘先导出原则；partition-mount/space-troubleshooting/smart-prediction/raid-lvm/disk-io-troubleshoot 五页增量合并）

- File names: lowercase, hyphens, no spaces (e.g., `pod-troubleshooting.md`)

tags: [kubernetes, troubleshooting, ...]

sources: [raw/articles/k8s-troubleshooting-article.md]

- troubleshooting: 排障相关

tags: [mysql, database, replication, high-availability, troubleshooting, production]

正常同步延迟应在 **1 秒以内**。延迟的 6 大根因（单线程重放瓶颈 / 大事务 / 硬件差距 / 网络 / 索引缺失 / 参数不合理）、真实案例与万能四步排查流程，见专页 [[mysql-replication-lag-troubleshooting]]。排查入口：`SHOW PROCESSLIST` / `Innodb_log_waits` / 网络延迟。

- 延迟类避坑（大事务、索引、硬件）见 [[mysql-replication-lag-troubleshooting]]

- [[mysql-replication-lag-troubleshooting]] — 主从延迟专页：6 大根因 / 真实案例 / 万能四步排查流程

- [[fullstack-performance-troubleshooting]] — 全栈性能排障（MySQL 在其中）

tags: [mysql, database, performance, troubleshooting, case-study]

| [[mysql-replication-lag-troubleshooting]] | 无索引慢 SQL 卡住从库重放队列 → 主从延迟飙升（根因 5） |

| [[database-troubleshooting-checklist-mysql-redis]] | 覆盖 MySQL（12 种）和 Redis（11 种）最常见的生产故障，每个故障按现象→排查→根因→ |

| [[mysql-connection-troubleshooting-guide]] | MySQL 连接失败排查指南 — 7 类报错根因定位 + 修复验证流程 |

| [[fullstack-performance-troubleshooting]] | 全栈排障方法论（Nginx→应用→数据库→服务器） |

tags: [docker, container, troubleshooting, security, production, networking, debugging]

| [[container-networking-troubleshooting]] | 容器网络排障 6 层模型（Docker bridge 网络是第 ②~⑤ 层） |

| [[resource-rbac-scheduling-troubleshooting]] | K8s 资源配额/OOMKilled 排障 |

| [[jvm-container-oom-offheap-troubleshooting]] | JVM 堆外内存（DirectByteBuffer/Metaspace/线程栈）导致容器 OOMKi |

| [[linux-permission-troubleshooting-guide]] | Linux 权限问题排查完整指南，从 Permission denied 到根因定位，覆盖 ACL/ |

| 51 | Pod hostPath 权限问题？ | 宿主机权限 700 vs 非 root Pod → Permission denied；用 securityContext.runAsUser + fsGroup 解决 | [[pod-troubleshooting]] |

| 1 | 容器编排与 K8s 优势？ | 自动化部署/扩展/管理；优势：自动扩缩、服务发现、存储编排、滚动更新、生态 | [[k8s-troubleshooting-principles]] |

| 2 | K8s RBAC？ | Role/ClusterRole 定义权限，RoleBinding/ClusterRoleBinding 分配权限 | [[resource-rbac-scheduling-troubleshooting]] |

| 50 | iptables vs ipvs？ | iptables：规则链匹配（规模大效率低）；ipvs：哈希表转发（效率高/支持会话保持）。kube-proxy mode 切换 | [[service-troubleshooting]] |

| 10 | 网络故障排查？ | ping(连通) → traceroute(路由) → netstat(连接) → tcpdump(抓包) → 防火墙 | [[network-troubleshooting-order]] |

tags: [troubleshooting, production, monitoring, networking, database, mysql, nginx]

sources: [raw/articles/fullstack-performance-troubleshooting.md]

| [[linux-disk-space-troubleshooting]] | 磁盘空间排查 |

| [[api-latency-troubleshooting-interview]] | 大厂面试实战：API 从 200ms 飙到 3 秒的完整排查思路，覆盖调用链分析、数据库慢查询、连接 |

| [[port-connectivity-troubleshooting-guide]] | 线上服务端口连不上的完整排查指南：从进程/端口监听/防火墙/云安全组/SELinux/网络路由到 D |

tags: [troubleshooting, networking, linux, tcp, monitoring, performance]

- [[network-troubleshooting-order]] — 服务器网络排障方法论（七步法）

- [[port-connectivity-troubleshooting-guide]] — 端口排查指南

- [[container-networking-troubleshooting]] — 容器网络排障

- [[dns-troubleshooting-practical-guide]] — DNS 排障实战

tags: [networking, troubleshooting, production, debugging, monitoring, linux]

sources: [raw/articles/network-troubleshooting-order.md, raw/articles/别再乱猜了-Linux网络不通-按这6个阶段排查-100-找到根因.md]

| 应用性能慢 / 接口超时 | 网络排障 → 全栈性能排障 | [[fullstack-performance-troubleshooting]] |

| K8s 内 Pod 间不通 | K8s Service / NetworkPolicy 排查 | [[service-troubleshooting]] |

| K8s 服务访问 502/504 超时 | K8s 服务访问排查十步工作流 | [[k8s-service-access-troubleshooting]] |

tags: [troubleshooting, performance, linux, debugging, production, monitoring, disk]

- raw/articles/online-troubleshooting-checklist-fredal-4a575c242fc47a28.md

详细排查流程参见 [[cpu-spike-troubleshooting-guide]]（四层定位法）和 [[cpu-spike-3-commands]]（三命令速查）。

详细调优参见 [[linux-disk-io-tuning]]（IO 深度优化）和 [[linux-disk-space-troubleshooting]]（空间排查流程）。

GC 问题往往导致 CPU 飙高，参见 [[cpu-spike-troubleshooting-guide]] 中 GC 相关章节。

tags: [linux, networking, database, troubleshooting, production, security, monitoring, docker, disk]

参见 [[linux-disk-space-troubleshooting]]（磁盘空间排查完整流程）。

参见 [[network-troubleshooting-order]]（分层七步法）。

参见 [[mysql-replication-guide]]（主从复制深度解析）；高频追问「主从延迟怎么排查」见 [[mysql-replication-lag-troubleshooting]]（6 大根因 + 万能四步流程）。

参见 [[linux-disk-space-troubleshooting]]（完整清理流程）。

tags: [troubleshooting, networking, linux, tcp, security, dns]

- [[network-troubleshooting-order]] — 服务器网络排障方法论（七步法）

- [[fullstack-performance-troubleshooting]] — 全栈性能排障

- [[container-networking-troubleshooting]] — 容器网络排障

- [[network-packet-loss-troubleshooting]] — 网络丢包排查全链路指南：从 ping 到 tcpdump 逐层排查，含物理/逻辑丢包区分、8 步排查

tags: [kubernetes, networking, troubleshooting, docker, debugging, performance, container]

sources: [raw/articles/container-networking-troubleshooting-6-layer.md]

| [[k8s-service-access-troubleshooting]] | K8s Service/Ingress 网络排障十步工作流（6 层模型第 ⑥ 层深入） |

| [[network-troubleshooting-order]] | 服务器网络排障七步法（6 层模型第 ③~⑤ 层补充） |

| [[k8s-top10-troubleshooting-checklist]] | K8s 10 大故障场景快速参考（网络故障层级识别） |

与 [[k8s-troubleshooting-principles]] 结合可理解排障的底层逻辑。

详见 [[pod-troubleshooting]]（Pod 排障）和 [[k8s-probes-guide]]（探针机制）。

详见 [[service-troubleshooting]]（Service 排障）和 [[k8s-service-access-troubleshooting]]（十步排查流程）。

详见 [[k8s-persistent-storage-guide]]（PV/PVC 生产实战）和 [[storage-troubleshooting]]（存储排障）。

| [[k8s-troubleshooting-principles]] | 排障基本原则与架构联动 |

tags: [kubernetes, dns, networking, troubleshooting, production]

> 排障参考：[[k8s-service-access-troubleshooting]]（DNS 是十步工作流的关键环节）

- [[k8s-service-access-troubleshooting]] — K8s 服务访问十步排查（DNS 是第一步）

- [[service-troubleshooting]] — Service 与网络排障（CoreDNS/kube-proxy 联动）

- [[network-troubleshooting-order]] — 网络排障分层方法论（DNS 层的诊断视角）

tags: [kubernetes, dns, troubleshooting, networking, case-study, production]

- [[k8s-dns-iptables-troubleshooting]] — iptables 封禁 53 端口引发的另一例 K8s DNS 雪崩

- [[k8s-dns-troubleshooting-sop]] — K8s DNS 故障排查完整 SOP：从超时到熔断的全流程、5类异常修复、CoreDNS 高可用配置

- [[dns-troubleshooting-practical-guide]] — 通用 DNS 全链路排查方法论

- [[k8s-service-access-troubleshooting]] — K8s 服务访问排障十步工作流

tags: [kubernetes, dns, iptables, troubleshooting, networking, production]

| [[dns-troubleshooting-practical-guide]] | DNS 故障全链路排查方法 |

| [[k8s-service-access-troubleshooting]] | K8s 服务访问排障 |

| [[network-troubleshooting-order]] | Linux 网络排查阶段化方法论 |

| [[k8s-dns-troubleshooting-sop]] | K8s DNS 故障排查完整 SOP：从超时到熔断的全流程、5类异常修复、CoreDNS 高可用配置 |

tags: [kubernetes, deployment, troubleshooting, production, networking, security]

| 1 | 什么是 Kubernetes？ | 开源容器编排平台，自动部署、扩展和管理容器化应用 | [[k8s-troubleshooting-principles]] |

| 4 | 什么是 Pod？ | K8s 最小部署单元，包含一个或多个容器，共享网络和存储 | [[pod-troubleshooting]] |

| 6 | 什么是 Service？ | 暴露应用的稳定访问地址，类型：ClusterIP/NodePort/LoadBalancer/ExternalName | [[service-troubleshooting]] |

| 16 | 什么是 Ingress？ | 管理外部 HTTP/HTTPS 访问，支持域名/路径路由和 TLS 终止 | [[k8s-service-access-troubleshooting]] |

tags: [kubernetes, networking, performance, troubleshooting, architecture]

| [[k8s-service-access-troubleshooting]] | Service 访问排障十步工作流 |

| [[service-troubleshooting]] | Service 网络排障方法论 |

| [[k8s-dns-iptables-troubleshooting]] | DNS + iptables 排障 |

| [[k8s-hairpin-troubleshooting]] | K8s Hairpin 发夹回流故障—Pod 可通全网但无法访问自身 Service 的原因、排查与 |

tags: [kubernetes, networking, production, troubleshooting, performance]

| [[k8s-service-access-troubleshooting]] | K8s 服务访问排查十步工作流（与本文排查清单互补） |

| [[service-troubleshooting]] | Service 网络排障方法论（Endpoints/502/超时排查） |

| [[container-networking-troubleshooting]] | 容器网络排障 6 层模型（负载均衡属于第 ③-⑥ 层） |

| [[k8s-hairpin-troubleshooting]] | K8s Hairpin 发夹回流故障—Pod 可通全网但无法访问自身 Service 的原因、排查与 |

tags: [kubernetes, troubleshooting, pod, deployment, production, monitoring, container, disk, storage]

- [[pod-troubleshooting]] — Pod 排障全场景（CrashLoopBackOff / ImagePullBackOff / Pending / Terminating）

- [[k8s-troubleshooting-principles]] — K8s 生产排障基本原则与快速定位流程

- [[linux-disk-space-troubleshooting]] — Linux 磁盘空间排查（df / du / lsof / journalctl）

- [[k8s-top10-troubleshooting-checklist]] — K8s 高频问题一站式排查清单

tags: [kubernetes, troubleshooting, pod, scheduling, networking, storage, deployment]

- [[pod-troubleshooting]] — Pod 排障总纲（CrashLoopBackOff/OOM/探针/Pending 基本排查）

- [[resource-rbac-scheduling-troubleshooting]] — 调度失败/Taint/OOMKill 排障

- [[storage-troubleshooting]] — 存储排障（PVC Pending）

- [[k8s-troubleshooting-quick-reference]] — K8s故障排查快速参考：黄金五步思维模型、Pod四种状态、Node NotReady、Service

tags: [kubernetes, troubleshooting, production, case-study, debugging]

| [[node-troubleshooting]] | 案例 4：节点 NotReady 排查 |

| [[resource-rbac-scheduling-troubleshooting]] | 案例 2/6/9：OOMKilled / 资源配额 / HPA |

| [[pod-troubleshooting]] | 案例 10：ImagePullBackOff |

| [[k8s-pod-evicted-troubleshooting]] | K8s Pod Evicted 驱逐机制深度解析——驱逐信号、硬/软驱逐、QoS 优先级、四步排查法 |

tags: [kubernetes, troubleshooting, pod, deployment, production, debugging]

详情参见 [[pod-troubleshooting]] 的 Pending/OOMKilled 章节。

ResourceQuota 超限时新 Pod 无法创建。详情见 [[resource-rbac-scheduling-troubleshooting]]。

- [[jvm-container-oom-offheap-troubleshooting]] — JVM 堆外内存（DirectByteBuffer/Metaspace/线程栈）导致容器 OOMKi

- [[k8s-pod-pending-troubleshooting-guide]] — Pod Pending 排障指南 — 7 个排查方向（资源不足/污点/亲和性/存储/配额/选择器/端

tags: [kubernetes, deployment, networking, troubleshooting, production, performance]

详见 [[k8s-probes-guide]]（探针完整配置指南）以及 [[pod-troubleshooting]]（三探针配合建议）。

| [[pod-troubleshooting]] | lifecycle hooks / preStop / 三探针配合建议 |

| [[k8s-service-access-troubleshooting]] | 连接排空与流量治理 |

| [[service-troubleshooting]] | Service Endpoints 与滚动更新的关系 |

tags: [kubernetes, troubleshooting, service, pod, ingress, networking, cni, dns]

sources: [raw/articles/k8s-service-access-troubleshooting.md, raw/articles/cni-comparison-flannel-calico-cilium.md]

| [[container-networking-troubleshooting]] | 容器网络 6 层排障模型（Service 网络是第 ⑥ 层） |

| [[pod-troubleshooting]] | Pod 排障：CrashLoopBackOff/Exit Code/探针/依赖服务 |

| [[k8s-dns-iptables-troubleshooting]] | K8s DNS 故障真实案例复盘：iptables 封禁 53 端口导致 CoreDNS 雪崩，完整 |

tags: [kubernetes, troubleshooting, production, debugging, pod, node, service, storage, networking, security]

- raw/articles/k8s-top10-troubleshooting-guide.md

📖 深度排查 → [[k8s-scheduling-strategy-guide]] | [[resource-rbac-scheduling-troubleshooting]]

📖 深度排查 → [[pod-troubleshooting]] | [[k8s-probes-guide]]

📖 深度排查 → [[service-troubleshooting]] | [[k8s-service-access-troubleshooting]]

tags: [kubernetes, troubleshooting, production, kubectl]

- raw/articles/k8s-troubleshooting-production-guide.md

- raw/articles/k8s-service-access-troubleshooting.md

- raw/articles/k8s-node-notready-troubleshooting.md

| [[k8s-service-access-troubleshooting]] | 从 Pod→Service→Ingress 十步排查工作流 |

tags: [kubernetes, troubleshooting, debugging, kubectl]

- [[k8s-troubleshooting-principles]] — K8s 生产排障基本原则与快速定位流程

- [[k8s-troubleshooting-survival-rules]] — K8s 故障排查实战：20 个生存法则（六维排障框架 + 5 分钟分诊 + 事故复盘 + 检查清单）

- [[k8s-top10-troubleshooting-checklist]] — K8s 高频问题一站式排查清单

- [[pod-troubleshooting]] — Pod 排障（CrashLoopBackOff / Exit Code / OOM）

tags: [kubernetes, troubleshooting, production, methodology, case-study]

sources: [raw/articles/2026-08-31-k8s-troubleshooting-20-survival-rules.md]

详见 [[node-troubleshooting]]、[[k8s-pod-evicted-troubleshooting]]。

详见 [[k8s-pod-pending-troubleshooting-guide]]、[[k8s-resource-limits-configuration]]。

详见 [[k8s-service-access-troubleshooting]]、[[k8s-rolling-update-pitfalls]]。

tags: [kubernetes, troubleshooting, node, production, monitoring, networking, certificate]

- raw/articles/k8s-troubleshooting-production-guide.md

- raw/articles/k8s-node-notready-troubleshooting.md

| [[k8s-service-access-troubleshooting]] | 服务访问排查（Pod 排障前置条件） |

| [[pod-troubleshooting]] | Pod 排障（节点 NotReady 后 Pod 被驱逐的后续排查） |

tags: [kubernetes, troubleshooting, pod, deployment, production, networking, configmap]

- raw/articles/k8s-troubleshooting-production-guide.md

- raw/articles/k8s-service-access-troubleshooting.md

- raw/articles/pod-restart-troubleshooting-guide.md

| [[k8s-service-access-troubleshooting]] | 从 Pod→Service→Ingress 十步排查工作流 |

tags: [kubernetes, troubleshooting, service, networking, ingress, cni, dns]

- raw/articles/k8s-troubleshooting-production-guide.md

- raw/articles/k8s-service-access-troubleshooting.md

| [[k8s-service-access-troubleshooting]] | 从 Pod→Service→Ingress 十步排查工作流 |

| [[node-troubleshooting]] | Node 排障 |

tags: [kubernetes, troubleshooting, storage, pvc, statefulset]

sources: [raw/articles/k8s-troubleshooting-production-guide.md]

- [[pod-troubleshooting]] — Pod 排障：CrashLoopBackOff/OOM/探针/8 步排查法（存储挂载失败导致的 Pod 异常）

- [[k8s-pod-pending-troubleshooting-guide]] — Pod Pending 排障指南 — 7 个排查方向（资源不足/污点/亲和性/存储/配额/选择器/端

- [[k8s-troubleshooting-quick-reference]] — K8s故障排查快速参考：黄金五步思维模型、Pod四种状态、Node NotReady、Service

tags: [linux, troubleshooting, performance, java, jvm, case-study, command, monitoring]

- [[cpu-spike-troubleshooting-guide]] — CPU 排查方法论

- [[fullstack-performance-troubleshooting]] — 全栈性能排障

- [[server-suddenly-slow-troubleshooting-sop]] — 服务器突然卡顿完整排查 SOP，从告警到根因的 15 步取证流程

- [[jvm-container-oom-offheap-troubleshooting]] — JVM OOM 排障

- raw/articles/cpu-spike-troubleshooting-guide.md

| [[linux-load-high-cpu-low-troubleshooting]] | Linux Load 高但 CPU 低的排查思路 — 从现象确认到根因定位的系统化诊断流程（含 vm |

| [[linux-perf-troubleshooting-handbook]] | Linux 服务器性能排查实战手册 — 60 秒快速摸底/4 大瓶颈排查/3 个实战案例/监控阈值/ |

| [[linux-perf-troubleshooting-panorama]] | Linux 性能排查全景指南：USE 方法论 + 四维排查 + K8s CPU 限流 + eBPF |

| [[api-latency-troubleshooting-interview]] | 大厂面试实战：API 从 200ms 飙到 3 秒的完整排查思路，覆盖调用链分析、数据库慢查询、连接 |

tags: [linux, java, performance, troubleshooting, case-study, jvm]

> 排查方法论参见 [[cpu-spike-troubleshooting-guide]]（通用 Linux 四层体系），三命令速查参见 [[cpu-spike-3-commands]]。

- [[cpu-spike-troubleshooting-guide]] — 通用 Linux CPU 排查四层体系（整机→进程→线程→调用栈）

- [[fullstack-performance-troubleshooting]] — 全栈性能排查（含 JVM GC 深度分析）

- [[online-troubleshooting-checklist]] — 线上故障排查清单

tags: [linux, troubleshooting, disk, filesystem, storage, command, monitoring, case-study, production, container, debugging, logrotate]

contradictions: [linux-disk-space-troubleshooting, linux-server-load-case-study]

节点级容器日志失控会触发 kubelet 驱逐，见 [[k8s-pod-evicted-troubleshooting]]。

- [[linux-disk-space-troubleshooting]] — 磁盘空间排查通盘流程（8 命令 / 四种场景 / 生产清理），本页是其中「已删未释放」场景的深度展开

- [[k8s-pod-evicted-troubleshooting]] — 节点磁盘/inode 压力触发 Pod Evicted，容器日志失控的下游后果

tags: [linux, disk, storage, troubleshooting, filesystem, methodology, production, monitoring]

> 定位：**按故障现象直接对号入座的修复手册**——只读文件系统、超级块损坏、Inode 耗尽、坏道、盘符漂移、挂载夯住、LVM 故障、救援模式 8 大场景，每个场景给「现象 → 成因 → 命令级解决方案」。分区/挂载/LVM 的日常操作手册见 [[linux-disk-partition-mount-guide]]，空间排查见 [[linux-disk-space-troubleshooting]]，SMART 健康预测见 [[linux-smart-disk-failure-prediction]]。

> D 状态进程与 Load Average 的关系深挖见 [[linux-load-average-guide]]、[[linux-load-high-cpu-low-troubleshooting]]。

1. 选择 **Troubleshooting** → **Rescue a CentOS Stream system**

- [[linux-disk-space-troubleshooting]] — 磁盘空间排查（空间真满/Inode 耗尽/已删未释放三分法，本文场景 3 的姊妹篇）

tags: [linux, troubleshooting, disk, storage, filesystem, monitoring, production, debugging, command]

sources: [raw/articles/linux-disk-space-troubleshooting.md, raw/articles/2026-09-02-deleted-open-file-ghost-disk-space.md]

| [[node-troubleshooting]] | K8s Node DiskPressure 处理（节点磁盘清理） |

| [[k8s-pod-evicted-troubleshooting]] |

| [[storage-troubleshooting]] | K8s 存储排障（PVC/挂载） |

tags: [linux, tools, troubleshooting, performance, automation]

> 关联排查：[[linux-disk-space-troubleshooting]] — `ls -lhS` 快速定位大文件

> 关联排查：[[linux-disk-space-troubleshooting]] — `find -size` 定位磁盘占用

> 关联排查：[[cpu-spike-troubleshooting-guide]] — top → strace 排查 CPU 飙高

> 关联排查：[[linux-disk-space-troubleshooting]] — df/du 差异 >5% 的排查方法

tags: [linux, troubleshooting, performance, debugging]

- [[online-troubleshooting-checklist]] — 在线故障排查清单

- [[cpu-spike-troubleshooting-guide]] — CPU 飙高排查指南

| [[linux-perf-troubleshooting-handbook]] | Linux 服务器性能排查实战手册 — 60 秒快速摸底/4 大瓶颈排查/3 个实战案例/监控阈值/ |

| [[nfs-troubleshooting-sop]] | NFS 故障排查 SOP — 7 步排查法 / 6 类故障 / 4 大实战案例 / 生产最佳实践 |

tags: [linux, performance, troubleshooting, methodology, production, monitoring, debugging]

sources: [raw/articles/2026-09-07-linux-load-average-troubleshooting-guide.md]

> 定位：**「负载高」全场景的端到端 runbook**——11 步标准流程（确认异常→CPU→内存→磁盘→网络→进程状态→定位→分析→修复→验证→复盘）+ 6 大场景修复手册（临时措施/根本措施/风险提醒三段式）+ 命令速查/配置示例/回滚方案。Load Average 概念与车道模型见 [[linux-load-average-guide]]，Load 高但 CPU 低的专用决策树见 [[linux-load-high-cpu-low-troubleshooting]]，Netflix 60 秒快速分诊见 [[linux-server-load-case-study]]。

- [[linux-load-high-cpu-low-troubleshooting]] — Load 高 CPU 低专用决策树（vmstat 四分支诊断 + 一键脚本 + 排查口诀）

- [[cpu-spike-troubleshooting-guide]] — CPU 飙高排查方法论（Load 高且 CPU 高分支的深挖）

tags: [linux, storage, networking, performance, troubleshooting, filesystem]

> 相关排障：[[network-troubleshooting-order]]（NFS 依赖网络层）

- [[network-troubleshooting-order]] — 网络排障（NFS 依赖 TCP 网络层）

- [[nfs-troubleshooting-sop]] — NFS 故障排查 SOP — 7 步排查法 / 6 类故障 / 4 大实战案例 / 生产最佳实践

- [[storage-troubleshooting]] — K8s 存储排障（PVC 挂载失败与 NFS 的关系）

tags: [linux, troubleshooting, performance, production, debugging, case-study, disk]

| [[linux-disk-space-troubleshooting]] | 磁盘空间排查（lsof deleted / logrotate + 生产清理流程） |

| [[fullstack-performance-troubleshooting]] | 应用层性能排障方法论 |

| [[network-troubleshooting-order]] | 网络排障（TIME_WAIT 等） |

| [[linux-load-high-cpu-low-troubleshooting]] | Linux Load 高但 CPU 低的排查思路 — 从现象确认到根因定位的系统化诊断流程（含 vm |

tags: [linux, troubleshooting, performance, monitoring, production, debugging, networking, mysql, filesystem]

详见 [[network-troubleshooting-order]]。

| [[fullstack-performance-troubleshooting]] | 应用层性能排障方法论（Nginx→DB） |

| [[network-troubleshooting-order]] | 网络连通性排障七步法 |

| [[node-troubleshooting]] | K8s Node 资源压力排查 |

tags: [linux, troubleshooting, performance, monitoring, disk, networking, container]

> 本文是 **全量排查流程篇**，覆盖从卡顿告警到根因确认的完整取证路径。与 [[server-performance-four-dimensions]]（五维深度解析）和 [[cpu-spike-troubleshooting-guide]]（CPU 专项）互补使用。

- [[cpu-spike-troubleshooting-guide]] — Linux CPU 飙高排查完整方法论

- [[linux-perf-troubleshooting-handbook]] — Linux 性能排查实战手册（三板斧/阈值速查）

- [[fullstack-performance-troubleshooting]] — Nginx → 应用 → 数据库 → 服务器全栈排障

tags: [networking, tcp, troubleshooting, security, linux, methodology]

sources: [raw/articles/2026-08-31-tcp-connection-spike-troubleshooting.md]

- [[network-packet-loss-troubleshooting]] — 网络丢包排查全链路：ping 到 tcpdump 逐层排查

- [[network-troubleshooting-order]] — 服务器网络排障方法论：分层定位七步法

- [[server-suddenly-slow-troubleshooting-sop]] — 服务器突然变慢 SOP（连接数/负载/IO 快速诊断）

tags: [nginx, troubleshooting, networking, production, debugging, performance]

| [[network-troubleshooting-order]] | 基础网络连通性排障（防火墙/路由/tcpdump） |

| [[fullstack-performance-troubleshooting]] | 全栈性能排障入口 |

| [[dns-troubleshooting-practical-guide]] | DNS 故障排查实战指南 — dig/nslookup 工具详解、四阶段排查流程、SERVFAIL/ |

| [[nginx-log-analysis-troubleshooting-guide]] | Nginx 日志分析、4xx/5xx/超时故障排查、真实案例复盘、日志分析工具链、告警监控与性能调优 |

tags: [nginx, troubleshooting, networking, production, security, deployment]

| [[port-connectivity-troubleshooting-guide]] | 线上服务端口连不上的完整排查指南：从进程/端口监听/防火墙/云安全组/SELinux/网络路由到 D |

| [[nginx-log-analysis-troubleshooting-guide]] | Nginx 日志分析与 4xx/5xx/超时故障排查实战 |

| [[nginx-troubleshooting-methodology-8-steps]] | Nginx 故障排查八步方法论（可照搬生产执行） |

| [[nginx-log-spike-crawler-troubleshooting]] | Nginx 访问日志暴涨排查手册：14 步定位异常 URI 与爬虫流量 |

tags: [nginx, monitoring, performance, troubleshooting, automation, security]

**日志暴涨场景的四类告警维度**（完整处置流程见 [[nginx-log-spike-crawler-troubleshooting]]）：日志增长速度超阈值（bytes/sec，stat -c%s 前后差值）、单个 IP 请求量超阈值、404/403/5xx 占比超阈值、特定 URI 访问量突增。

- [[nginx-log-analysis-troubleshooting-guide]] — Nginx 日志分析与 4xx/5xx/超时故障排查实战

- [[fullstack-performance-troubleshooting]] — 全栈性能排障

- [[nginx-log-spike-crawler-troubleshooting]] — Nginx 访问日志暴涨排查手册：14 步 runbook（本页告警体系的落地场景）

tags: [nginx, troubleshooting, networking, performance, security, tcp]

# 日志暴涨速查三样（完整 14 步流程见 [[nginx-log-spike-crawler-troubleshooting]]）

- [[nginx-troubleshooting-methodology-8-steps]] — 一套可以在生产环境照搬执行的 Nginx 故障排查套路，覆盖 502/504/499/500/con

- [[server-suddenly-slow-troubleshooting-sop]] — 服务器突然卡顿完整排查 SOP，从告警到根因的 15 步取证流程

- [[nginx-log-spike-crawler-troubleshooting]] — Nginx 访问日志暴涨排查手册：14 步场景 runbook（本页是知识域手册，那页是场景流程）

tags: [nginx, troubleshooting, monitoring, security, performance]

- raw/articles/2026-09-05-nginx-log-spike-crawler-troubleshooting.md

> 来源：微信公众号「马哥Linux运维」（2026-09-03）。场景：生产环境 Nginx 访问日志突然暴涨——磁盘空间告警、日志轮转变慢、分析工具卡顿，甚至影响正常业务日志写入。本手册给出从**确认现象 → 五维分析 → 临时止血 → 长期防护 → 验证回滚**的完整 14 步流程。与按知识域组织的 [[nginx-log-analysis-troubleshooting-guide]]（字段/超时/状态码手册）互补：那一页回答"这个字段/状态码什么意思"，本页回答"日志暴涨了，现在按什么顺序做什么"。

⚠️ **风险提醒**：磁盘写满时 Nginx 无法写日志，会导致日志丢失或服务异常（参考 troubleshooting-guide 案例 5：磁盘满导致全站 502）。**清理前先备份或转储到其他存储。**

404 占比高 = 路径探测或失效链接；403 高 = 访问控制触发；5xx 高 = 后端异常；301/302 高 = 检查重定向配置。状态码逐项根因见 [[nginx-log-analysis-troubleshooting-guide]] 第三/四节。

tags: [nginx, troubleshooting, methodology, networking, performance, tcp]

> 💡 本文是"方法论/操作流程"视角。如需按主题查阅（字段说明、状态码表、超时参数、案例复盘、安全配置），请参考 [[nginx-log-analysis-troubleshooting-guide]]；502/504/RST 专项排查参见 [[nginx-502-504-connection-reset-guide]]。

> 完整配置模板和超时参数详解见 [[nginx-log-analysis-troubleshooting-guide]]。以下仅列本文方法论涉及的高频修复点。

- [[nginx-log-analysis-troubleshooting-guide]] — 参考手册：字段说明、超时参数、状态码表、完整案例、监控告警、性能调优

- [[network-troubleshooting-order]] — 基础网络连通性排障（防火墙/路由/tcpdump）

- [[api-latency-troubleshooting-interview]] — 大厂面试实战：API 从 200ms 飙到 3 秒的完整排查思路，覆盖调用链分析、数据库慢查询、连接池/线程池、GC、Redis 六大排查维度

- [[container-networking-troubleshooting]] — 容器网络排障 6 层模型：K8s/Docker/containerd 统一排查体系（分层定位 + 30 秒速查 + 案例复盘）

- [[cpu-spike-troubleshooting-guide]] — 完整 CPU 排查方法论 + 应急响应：整机→进程→线程→调用栈四层定位/常见根因速查/止血手段

- [[database-troubleshooting-checklist-mysql-redis]] — 覆盖 MySQL（12 种）和 Redis（11 种）最常见的生产故障，每个故障按现象→排查→根因→修复→验证结构组织，含决策树和命令速查

- [[dns-troubleshooting-practical-guide]] — DNS 故障排查实战指南 — dig/nslookup 工具详解、四阶段排查流程、SERVFAIL/NXDOMAIN/TIMEOUT 错误类型速查

- Created raw: raw/articles/k8s-troubleshooting-production-guide.md

- Created concepts: k8s-troubleshooting-principles, pod-troubleshooting, node-troubleshooting, service-troubleshooting, storage-troubleshooting, resource-rbac-scheduling-troubleshooting

- Created raw: raw/articles/fullstack-performance-troubleshooting.md

- Created concepts: fullstack-performance-troubleshooting, mysql-performance-config

- Updated: resource-rbac-scheduling-troubleshooting

tags: [mysql, redis, database, troubleshooting, production, command]

**修复**：开启并行复制（`replica_parallel_type=LOGICAL_CLOCK`）；避免主库大事务，拆分为小批量；从库使用 SSD。6 大根因逐条拆解与真实案例见 [[mysql-replication-lag-troubleshooting]]。

- [[mysql-replication-lag-troubleshooting]] — 主从延迟专页：6 大根因 / 案例 / 万能四步排查流程

- [[fullstack-performance-troubleshooting]] — 全栈性能排障入口（MySQL/Redis 在整体链路中的定位）

- raw/articles/fullstack-performance-troubleshooting.md

- raw/articles/mysql-deadlock-troubleshooting.md

| [[database-troubleshooting-checklist-mysql-redis]] |

| [[mysql-connection-troubleshooting-guide]] |

tags: [troubleshooting, performance, database, mysql, redis, java, monitoring, networking]

| [[fullstack-performance-troubleshooting]] | 全栈性能排障方法论全景 |

| [[online-troubleshooting-checklist]] | 线上四维速查命令清单 |

| [[cpu-spike-troubleshooting-guide]] | CPU 飙高专项排查 |

tags: [kubernetes, docker, container, troubleshooting, command]

- [[pod-troubleshooting]] — Pod 排障

- [[container-networking-troubleshooting]] — 容器网络排障

- [[storage-troubleshooting]] — 存储排障

tags: [networking, linux, tcp, security, troubleshooting, command]

| [[network-troubleshooting-order]] | 网络排障分层七步法 |

| [[dns-troubleshooting-practical-guide]] | DNS 故障排查指南 |

| [[k8s-service-access-troubleshooting]] | K8s 服务网络排障 |

tags: [architecture, networking, monitoring, troubleshooting, performance, deployment, devops]

- [[fullstack-performance-troubleshooting]] — 全栈性能排障

- [[jvm-container-oom-offheap-troubleshooting]] — JVM 堆外内存 OOM 排障

- [[container-networking-troubleshooting]] — 容器网络排障

tags: [kubernetes, networking, troubleshooting, linux, architecture]

- [[k8s-service-access-troubleshooting]] — K8s 服务访问排查十步工作流

- [[container-networking-troubleshooting]] — 容器网络排障 6 层模型

- [[service-troubleshooting]] — Service 与网络排障

- [[resource-rbac-scheduling-troubleshooting]] — 调度失败排障（Taint/OOMKill/RBAC）

- [[k8s-troubleshooting-principles]] — K8s 排障基本原则

- [[k8s-pod-pending-troubleshooting-guide]] — Pod Pending 排障指南 — 7 个排查方向（资源不足/污点/亲和性/存储/配额/选择器/端

- [[pod-troubleshooting]] — Pod 排障完整指南

tags: [kubernetes, troubleshooting, security, hpa, deployment]

sources: [raw/articles/k8s-troubleshooting-production-guide.md, raw/articles/k8s-resource-limits-configuration.md]

- [[jvm-container-oom-offheap-troubleshooting]] — JVM 堆外内存（DirectByteBuffer/Metaspace/线程栈）导致容器 OOMKi

- [[k8s-pod-pending-troubleshooting-guide]] — Pod Pending 排障指南 — 7 个排查方向（资源不足/污点/亲和性/存储/配额/选择器/端

tags: [dns, networking, linux, troubleshooting, command]

- [[network-troubleshooting-order]] — 网络排障七步法（含 DNS 步骤）

- [[k8s-dns-iptables-troubleshooting]] — K8s DNS 故障真实案例复盘：iptables 封禁 53 端口导致 CoreDNS 雪崩，完整

- [[network-packet-loss-troubleshooting]] — 网络丢包排查全链路指南：从 ping 到 tcpdump 逐层排查，含物理/逻辑丢包区分、8 步排查

tags: [linux, command, troubleshooting, performance, automation]

- [[nginx-log-analysis-troubleshooting-guide]] — Nginx 日志分析 + 4xx/5xx/超时故障排查

- [[nginx-troubleshooting-methodology-8-steps]] — Nginx 8 步排障方法论 + 应急快查表

- [[linux-perf-troubleshooting-handbook]] — Linux 服务器性能排查实战手册

tags: [linux, performance, disk, storage, troubleshooting, monitoring, debugging, command]

- [[linux-disk-space-troubleshooting]] — Linux 磁盘空间排查（8 命令/四种场景）

- [[server-suddenly-slow-troubleshooting-sop]] — 服务器突然卡顿完整排查 SOP

- [[linux-perf-troubleshooting-handbook]] — Linux 服务器性能排查实战手册

tags: [linux, memory, performance, troubleshooting, monitoring, debugging]

- [[jvm-container-oom-offheap-troubleshooting]] — JVM 堆外内存（DirectByteBuffer/Metaspace/线程栈）导致容器 OOMKi

- [[linux-perf-troubleshooting-panorama]] — Linux 性能排查全景指南：USE 方法论 + 四维排查 + K8s CPU 限流 + eBPF

- [[online-troubleshooting-checklist]] — 四维排查速查清单（CPU/磁盘/内存/网络 + Java 工具 jstack/jmap/jstat/tcpdump）

tags: [linux, command, troubleshooting, performance, networking, disk]

> 磁盘空间排查详见：[[linux-disk-space-troubleshooting]]

- [[linux-disk-space-troubleshooting]] — 磁盘空间排障

- [[cpu-spike-troubleshooting-guide]] — CPU 飙高排障

tags: [linux, troubleshooting, performance, monitoring, nginx, mysql]

- [[cpu-spike-troubleshooting-guide]] — CPU 飙高排查指南

- [[linux-load-high-cpu-low-troubleshooting]] — Load 高但 CPU 低排查

| [[server-suddenly-slow-troubleshooting-sop]] |

tags: [linux, troubleshooting, performance, debugging, case-study]

- [[linux-load-high-cpu-low-troubleshooting]] — Load 高但 CPU 低的排查思路

- [[cpu-spike-troubleshooting-guide]] — CPU 飙高排查指南

- [[server-suddenly-slow-troubleshooting-sop]] — 服务器突然变慢排查 SOP

tags: [networking, tcp, troubleshooting, linux, security, case-study]

| [[network-troubleshooting-order]] | 网络排障顺序 |

| [[online-troubleshooting-checklist]] | 在线排障清单 |

| [[tcp-connection-spike-troubleshooting]] | 完整手册：六步判断流程/判断阈值/半全连接队列/conntrack/攻击工具/实战案例 |

**空 UA 也要拦**（2026-09 增补）：map 中追加 `"" 1;` 与 `"-" 1;`——空 User-Agent 通常是恶意工具或配置错误的客户端。反向边界：**遵守协议的搜索引擎爬虫（Googlebot/Baiduspider）过频时不要屏蔽**，用 robots.txt 的 `Crawl-delay: 10` 控制抓取间隔 + 限流处理；robots.txt 对恶意爬虫无效，必须靠限流兜底（暴涨场景全流程见 [[nginx-log-spike-crawler-troubleshooting]]）。

- [[nginx-log-analysis-troubleshooting-guide]] — Nginx 日志分析、4xx/5xx/超时故障排查与真实案例复盘

- [[network-troubleshooting-order]] — 防火墙/iptables 与 Nginx 安全联动

- [[nginx-log-spike-crawler-troubleshooting]] — Nginx 访问日志暴涨排查手册：14 步 runbook（本页防护手段的完整处置场景）

tags: [nginx, troubleshooting, networking, production, performance, debugging]

- [[nginx-troubleshooting-methodology-8-steps]] — Nginx 报错排查方法论（8 步决策树）

- [[nginx-log-analysis-troubleshooting-guide]] — Nginx 日志分析、4xx/5xx/超时故障排查

- [[fullstack-performance-troubleshooting]] — 全栈性能排障入口

- [[service-troubleshooting]] — CNI 排查实战（Flannel 接口/Calico Pod 状态/BGP 路由检查）

- [[k8s-service-access-troubleshooting]] — 服务访问十步工作流中 CNI 为关键排查步骤

- [[network-troubleshooting-order]] — 网络排障底层方法论（与本文 Cross-cluster Overlay 排障互补）

tags: [database, mysql, storage, troubleshooting, disk, command]

- [[database-troubleshooting-checklist-mysql-redis]] — MySQL/Redis 速查清单，含故障6：磁盘写满（本篇的 companion 补充）

- [[mysql-connection-troubleshooting-guide]] — MySQL 连接失败排查指南 — 7 类报错根因定位 + 修复验证流程

tags: [mysql, database, replication, troubleshooting, production, performance]

SELECT * FROM information_schema.innodb_trx; -- 是否锁等待阻塞回放（来自 [[database-troubleshooting-checklist-mysql-redis]] 故障 2）

- [[database-troubleshooting-checklist-mysql-redis]] — 故障 2：主从复制延迟（含 innodb_trx 锁等待排查）

- 配合 [[online-troubleshooting-checklist]] 使用，覆盖日常运维+应急排障

| [[online-troubleshooting-checklist]] | 四维排查速查（自动化脚本 + 应急排障互补） |

| [[fullstack-performance-troubleshooting]] | 全栈性能排障入口（脚本 1-5 的排障背景） |

详见 [[jvm-container-oom-offheap-troubleshooting]]。

- [[jvm-container-oom-offheap-troubleshooting]] — JVM 容器 OOM 排障（堆外内存）

- [[resource-rbac-scheduling-troubleshooting]] — 资源配额/OOMKilled 排障

tags: [kubernetes, dns, troubleshooting, networking, performance, production, methodology, sre]

- [[k8s-dns-iptables-troubleshooting]] — K8s DNS 故障真实案例复盘：iptables 封禁 53 端口导致 CoreDNS 雪崩

- [[k8s-service-access-troubleshooting]] — K8s 服务访问排查十步工作流：Pod→Service→kube-proxy→CNI→Ingress→DNS→NetworkPolicy

> ⚠️ 坑：用了不支持 RWX 的存储系统，Pod 会一直 Pending。详见 [[storage-troubleshooting]]。

完整排障方法见 [[storage-troubleshooting]]。

| [[node-troubleshooting]] | Node 排障与 k8s-statefulset-guide 的 Pod 行为交叉 |

tags: [kubernetes, pod, troubleshooting, production, monitoring]

与 [[pod-troubleshooting]]（CrashLoopBackOff 排障）、[[k8s-rolling-update-pitfalls]]（滚动更新中 Readiness 探针的真实业务就绪判断）和 [[k8s-troubleshooting-principles]]（排查原则）配合使用。

- [[k8s-pod-evicted-troubleshooting]] — K8s Pod Evicted 驱逐机制深度解析——驱逐信号、硬/软驱逐、QoS 优先级、四步排查法

- [[linux-disk-space-troubleshooting]] — 磁盘空间排查（journalctl 磁盘清理）

- [[online-troubleshooting-checklist]] — 线上故障排查速查清单

- [[port-connectivity-troubleshooting-guide]] — 线上服务端口连不上的完整排查指南：从进程/端口监听/防火墙/云安全组/SELinux/网络路由到 D

tags: [linux, performance, troubleshooting, case-study, production]

| [[fullstack-performance-troubleshooting]] | 全栈性能排障方法论 |

| [[jvm-container-oom-offheap-troubleshooting]] | JVM 堆外内存（DirectByteBuffer/Metaspace/线程栈）导致容器 OOMKi |

tags: [linux, command, storage, disk, architecture, troubleshooting]

- [[linux-perf-troubleshooting-handbook]] — Linux 性能排查手册

- [[linux-permission-troubleshooting-guide]] — Linux 权限问题排查完整指南，从 Permission denied 到根因定位，覆盖 ACL/

tags: [linux, networking, security, command, troubleshooting]

- [[network-troubleshooting-order]] — 服务器网络排障方法论

- [[port-connectivity-troubleshooting-guide]] — 线上服务端口连不上的完整排查指南

- [[container-networking-troubleshooting]] — 容器网络排障 6 层模型（rp_filter/ip_forward 参数实战场景）

- [[linux-perf-troubleshooting-handbook]] — Linux 服务器性能排查实战手册 — 60 秒快速摸底/4 大瓶颈排查/3 个实战案例/监控阈值/

- [[nginx-troubleshooting-methodology-8-steps]] — 一套可以在生产环境照搬执行的 Nginx 故障排查套路，覆盖 502/504/499/500/con

tags: [linux, performance, monitoring, troubleshooting, command]

- [[linux-load-high-cpu-low-troubleshooting]] — Load 高 CPU 低的完整排查决策树，从 vmstat 到 iostat 的逐层诊断

- [[cpu-spike-troubleshooting-guide]] — CPU 飙高排查方法论与止损策略

tags: [linux, troubleshooting, performance, command]

| [[linux-load-high-cpu-low-troubleshooting]] | Load 高 CPU 低排查（D/Z 状态在决策树中的应用） |

| [[cpu-spike-troubleshooting-guide]] | CPU 飙高排查指南 |

tags: [linux, troubleshooting, nfs, storage, networking, performance, monitoring, security]

- [[network-troubleshooting-order]] — 网络排查顺序

- [[linux-load-high-cpu-low-troubleshooting]] — Linux Load 高但 CPU 低排查

tags: [security, linux, production, networking, troubleshooting, automation]

| [[network-troubleshooting-order]] | iptables / firewalld 防火墙规则配置 |

| [[linux-permission-troubleshooting-guide]] | Linux 权限问题排查完整指南，从 Permission denied 到根因定位，覆盖 ACL/ |

tags: [nginx, performance, networking, linux, architecture, troubleshooting]

- [[nginx-log-analysis-troubleshooting-guide]] — Nginx 日志分析、4xx/5xx/超时故障排查、真实案例复盘、日志分析工具链、告警监控与性能调优

- [[nginx-troubleshooting-methodology-8-steps]] — 一套可以在生产环境照搬执行的 Nginx 故障排查套路，覆盖 502/504/499/500/con

tags: [architecture, database, messaging, java, troubleshooting]

- [[database-troubleshooting-checklist-mysql-redis]] — 数据库常见故障排查清单（MySQL + Redis）

tags: [database, mysql, backup, troubleshooting, storage]

- [[mysql-connection-troubleshooting-guide]] — MySQL 连接失败排查指南 — 7 类报错根因定位 + 修复验证流程

tags: [mysql, database, performance, troubleshooting, case-study]

- [[fullstack-performance-troubleshooting]] — 全栈排障方法论

tags: [redis, database, troubleshooting, production, monitoring, debugging]

| [[database-troubleshooting-checklist-mysql-redis]] | 覆盖 MySQL（12 种）和 Redis（11 种）最常见的生产故障，每个故障按现象→排查→根因→ |

- troubleshooting

- [[cpu-spike-troubleshooting-guide]] — CPU 飙高全链路排查，常见复盘场景

- [[network-troubleshooting-order]] — 服务器网络排障方法论（有线网络底层原理）

- [[fullstack-performance-troubleshooting]] — 全栈性能排障（网络层是其中一环）

tags: [kubernetes, troubleshooting, configmap, pod, storage, debugging]

| [[pod-troubleshooting]] | Pod 排障（ConfigMap 挂载异常的 Events 查看） |

tags: [kubernetes, java, troubleshooting, memory, container, performance]

- [[resource-rbac-scheduling-troubleshooting]] — K8s 资源配额/OOMKilled 排障

tags: [kubernetes, java, jvm, troubleshooting, memory, performance]

- [[jvm-container-oom-offheap-troubleshooting]] — JVM 堆外内存排障全指南（四大暗坑 + NMT 细节）

tags: [kubernetes, java, jvm, memory, performance, troubleshooting, architecture]

- [[jvm-container-oom-offheap-troubleshooting]] — JVM 容器 OOM 排障（堆外内存视角，排障快速参考）

- [[pod-troubleshooting]] — Pod 排障

- [[resource-rbac-scheduling-troubleshooting]] — 资源配额与调度排障

tags: [kubernetes, storage, troubleshooting, deployment, pvc]

- [[storage-troubleshooting]] — 存储排障

tags: [linux, performance, troubleshooting, case-study, debugging]

| [[cpu-spike-troubleshooting-guide]] | 完整 CPU 排查方法论（整机→进程→线程→调用栈四层定位） |

- troubleshooting

- [[linux-perf-troubleshooting-handbook]] — Linux 性能排查实战手册

| [[linux-disk-space-troubleshooting]] | 磁盘空间排查（日志压缩清理策略） |

| [[cpu-spike-troubleshooting-guide]] | CPU 飙高排查（gzip/xz 压缩导致 CPU 异常场景） |

tags: [linux, disk, storage, command, monitoring, troubleshooting]

- [[linux-disk-space-troubleshooting]] — 磁盘空间排查

- [[linux-load-high-cpu-low-troubleshooting]] — Linux Load 高但 CPU 低的排查思路

- [[linux-perf-troubleshooting-handbook]] — Linux 服务器性能排查实战手册

| [[linux-disk-space-troubleshooting]] | 磁盘空间排查（空间问题 vs 性能问题） |

- [[online-troubleshooting-checklist]] — 四维排查速查清单（CPU/磁盘/内存/网络 + Java 工具 jstack/jmap/jstat/tcpdump）

tags: [security, linux, incident-response, troubleshooting, networking]

- [[linux-permission-troubleshooting-guide]] — Linux 权限问题排查完整指南，从 Permission denied 到根因定位，覆盖 ACL/

tags: [linux, command, performance, monitoring, disk, networking, troubleshooting, architecture]

| [[linux-disk-space-troubleshooting]] | 磁盘空间排查 |

- [[network-troubleshooting-order]] — 网络排查顺序

| [[linux-perf-troubleshooting-handbook]] | Linux 服务器性能排查实战手册 — 60 秒快速摸底/4 大瓶颈排查/3 个实战案例/监控阈值/ |

tags: [linux, command, troubleshooting]

- [[online-troubleshooting-checklist]] — 线上排障通用检查清单

tags: [linux, security, incident-response, troubleshooting, production, methodology, case-study, ssh, iptables, monitoring]

- [[cpu-spike-troubleshooting-guide]] — CPU 飙高通用排查方法论（挖矿是 CPU 异常的常见根因之一）

tags: [linux, security, troubleshooting, monitoring, networking, tcp]

- [[cpu-spike-troubleshooting-guide]] — CPU 飙高排查方法论

tags: [linux, performance, monitoring, troubleshooting, debugging, command]

| [[cpu-spike-troubleshooting-guide]] | CPU 飙高排查方法论 |

tags: [linux, troubleshooting, security, command, filesystem, nfs, container, networking]

- [[k8s-service-access-troubleshooting]] — K8s 服务访问排障（含 RBAC）

tags: [linux, networking, monitoring, debugging, troubleshooting]

- [[network-troubleshooting-order]] — 服务器网络排障七步法（含 ss/netstat 实战场景）

| [[network-troubleshooting-order]] | 防火墙 / iptables 配置与排障 |

| [[linux-permission-troubleshooting-guide]] | Linux 权限问题排查完整指南，从 Permission denied 到根因定位，覆盖 ACL/ |

tags: [linux, networking, troubleshooting, security, debugging]

- [[network-troubleshooting-order]] — 服务器网络排障方法论：分层定位七步法（SSH 连接建立的网络层基础）

tags: [nginx, networking, performance, troubleshooting, architecture, load-balancing]

| [[fullstack-performance-troubleshooting]] | 全栈性能排障 |

- [[k8s-service-access-troubleshooting]] — K8s 服务访问排查十步工作流（含服务发现与 DNS 排障）

tags: [mysql, database, troubleshooting, networking, security, command]

| [[database-troubleshooting-checklist-mysql-redis]] | 覆盖 MySQL（12 种）和 Redis（11 种）最常见的生产故障，每个故障按现象→排查→根因→ |

| [[database-troubleshooting-checklist-mysql-redis]] | 覆盖 MySQL（12 种）和 Redis（11 种）最常见的生产故障，每个故障按现象→排查→根因→ |

- [[database-troubleshooting-checklist-mysql-redis]] — 覆盖 MySQL（12 种）和 Redis（11 种）最常见的生产故障，每个故障按现象→排查→根因→

- [[fullstack-performance-troubleshooting]] — 全栈性能排障（高并发问题从应用到数据库的全局视角）

| [[service-troubleshooting]] | Service/Ingress 排障，Gateway API 排查 |

tags: [kubernetes, networking, deployment, architecture, monitoring, troubleshooting, automation, security]

参见 [[pod-troubleshooting]] 了解通用 Pod 排障方法，[[storage-troubleshooting]] 了解存储相关排障。

| [[linux-disk-space-troubleshooting]] | 磁盘空间不足排查 |

| [[linux-disk-space-troubleshooting]] | 磁盘空间排查（删除后空间不释放问题） |

- [[linux-disk-space-troubleshooting]] — 磁盘空间排查

tags: [linux, command, troubleshooting, automation]

tags: [linux, troubleshooting, backup, security, disk, filesystem, command, case-study, data-loss]

tags: [linux, security, production, troubleshooting]

tags: [linux, command, backup, networking, troubleshooting]

tags: [nginx, keepalived, networking, production, ha, troubleshooting, monitoring, architecture]

| [[nginx-troubleshooting-methodology-8-steps]] |

| [[fullstack-performance-troubleshooting]] | 全栈性能排障体系（ws/SSE 场景扩展） |