const page = 16
const article = {
title: "iptables 防火墙规则 DROP 导致端口无法访问:端口 LISTEN 但 curl 超时",
publishedAt: "2026.08.31",
tags: [],
href: "/blogs/2026-08-31-1600-iptables-drop-8080"
}
export default articleconst article = {
title: "iptables 防火墙规则 DROP 导致端口无法访问:端口 LISTEN 但 curl 超时",
publishedAt: "2026.08.31",
tags: [],
href: "/blogs/2026-08-31-1600-iptables-drop-8080"
}
export default articleconst article = definePost()
iptables 防火墙规则 DROP 导致端口无法访问:端口 LISTEN 但 curl 超时
Linux 服务器上部署了 HTTP 服务监听 8080 端口,服务进程正常、端口显示 LISTEN 状态,但从客户端访问 `http://<IP>:8080` 一直超时或连接失败。CPU、内存、进程都正常,问题隐藏在防火墙层——iptables 的 INPUT 链存在一条 DROP 所有发往 8080 端口 TC
const article = {
title: "MySQL 死锁(Deadlock found when trying to get lock)根因与解决实战",
publishedAt: "2026.08.30",
tags: [],
href: "/blogs/2026-08-30-0007-mysql-deadlock"
}
export default articleconst article = {
title: "MySQL 死锁(Deadlock found when trying to get lock)根因与解决实战",
publishedAt: "2026.08.30",
tags: [],
href: "/blogs/2026-08-30-0007-mysql-deadlock"
}
export default articleconst article = definePost()
MySQL 死锁(Deadlock found when trying to get lock)根因与解决实战
电商下单系统在**并发事务**下间歇性报错:
const article = {
title: "TCP 监听队列(backlog/accept队列)被打满导致新连接超时的诊断与解决",
publishedAt: "2026.08.30",
tags: ["tcp","backlog","accept队列"],
href: "/blogs/2026-08-30-0836-tcp-backlog-accept-queue"
}
export default articleconst article = {
title: "TCP 监听队列(backlog/accept队列)被打满导致新连接超时的诊断与解决",
publishedAt: "2026.08.30",
tags: ["tcp","backlog","accept队列"],
href: "/blogs/2026-08-30-0836-tcp-backlog-accept-queue"
}
export default articleconst article = definePost()
TCP 监听队列(backlog/accept队列)被打满导致新连接超时的诊断与解决
服务进程、CPU、内存都正常,新 TCP 连接却频繁超时或被拒。本文通过 ss -lnt 发现监听端口 Send-Q 顶满 backlog,用 Docker 复现 accept 队列被打满的过程,详解 SYN 队列与 accept 队列分工,给出调整 backlog、somaxconn 与应用侧修复方案。
const article = {
title: "Redis 缓存穿透(Cache Penetration)解决方案:缓存空值实战",
publishedAt: "2026.08.30",
tags: ["Redis","缓存穿透","Cache Penetration"],
href: "/blogs/2026-08-30-1600-redis"
}
export default articleconst article = {
title: "Redis 缓存穿透(Cache Penetration)解决方案:缓存空值实战",
publishedAt: "2026.08.30",
tags: ["Redis","缓存穿透","Cache Penetration"],
href: "/blogs/2026-08-30-1600-redis"
}
export default articleconst article = definePost()
Redis 缓存穿透(Cache Penetration)解决方案:缓存空值实战
攻击者或爬虫大量请求不存在的商品 ID,请求全部绕过缓存直达数据库,查询量暴涨百倍甚至引发宕机。本文用 Flask + Redis + MySQL 复现经典缓存穿透场景,实战讲解缓存空值(NULL Cache)方案:TTL 设置、空值标识设计,以及与缓存击穿、缓存雪崩的边界区分。
const article = {
title: "AI日报 2026-08-30",
publishedAt: "2026.08.30",
tags: ["朕喜技术","科技资讯","人工智能"],
href: "/blogs/ai-daily-2026-08-30"
}
export default articleconst article = {
title: "AI日报 2026-08-30",
publishedAt: "2026.08.30",
tags: ["朕喜技术","科技资讯","人工智能"],
href: "/blogs/ai-daily-2026-08-30"
}
export default articleconst article = definePost()
AI日报 2026-08-30
本期聚焦AI本地部署精度差异的根因分析,揭示734个依赖包中任一微小差异即可导致输出token翻转;阿里Qoder推出桌宠形态实现Beyond Coding;清华姚班迎来新班主任徐梦迪;OpenClaw热度快速退潮;开源OCR工具OCR It以20ms处理PDF;Claude开启自训练研究;英特尔锐炫Pro B70支持
const article = {
title: "Nginx 反向代理 PHP-FPM 返回 502 Bad Gateway:并发慢请求打满 Worker 池的排查与修复",
publishedAt: "2026.08.29",
tags: [],
href: "/blogs/2026-08-29-0009-nginx-php-fpm-502-bad-gateway"
}
export default articleconst article = {
title: "Nginx 反向代理 PHP-FPM 返回 502 Bad Gateway:并发慢请求打满 Worker 池的排查与修复",
publishedAt: "2026.08.29",
tags: [],
href: "/blogs/2026-08-29-0009-nginx-php-fpm-502-bad-gateway"
}
export default articleconst article = definePost()
Nginx 反向代理 PHP-FPM 返回 502 Bad Gateway:并发慢请求打满 Worker 池的排查与修复
生产环境架构为 `客户端 → Nginx(80) → PHP-FPM(9000)`,Nginx 通过 FastCGI 把 `.php` / `/api/` 请求转发给后端 PHP-FPM。
const article = {
title: "容器内 DNS 解析失败修复指南:`Name or service not known` 但 ping IP 正常",
publishedAt: "2026.08.29",
tags: ["docker dns 解析失败","resolv.conf","Name or service not known"],
href: "/blogs/2026-08-29-0800-dnsname-or-service-not-known"
}
export default articleconst article = {
title: "容器内 DNS 解析失败修复指南:`Name or service not known` 但 ping IP 正常",
publishedAt: "2026.08.29",
tags: ["docker dns 解析失败","resolv.conf","Name or service not known"],
href: "/blogs/2026-08-29-0800-dnsname-or-service-not-known"
}
export default articleconst article = definePost()
容器内 DNS 解析失败修复指南:`Name or service not known` 但 ping IP 正常
微服务容器突然无法访问外部 API,应用日志大量出现 `socket.gaierror: [Errno -2] Name or service not known`。排查发现:容器内 `curl https://www.baidu.com` 报 `curl: (6) Could not resolve host`,
const article = {
title: "CPU 使用率 100% 定位与修复:Python while True 死循环实战排查指南",
publishedAt: "2026.08.29",
tags: ["linux","cpu","性能排查"],
href: "/blogs/2026-08-29-1612-cpu-100-deadloop-python"
}
export default articleconst article = {
title: "CPU 使用率 100% 定位与修复:Python while True 死循环实战排查指南",
publishedAt: "2026.08.29",
tags: ["linux","cpu","性能排查"],
href: "/blogs/2026-08-29-1612-cpu-100-deadloop-python"
}
export default articleconst article = definePost()
CPU 使用率 100% 定位与修复:Python while True 死循环实战排查指南
服务器 CPU 飙升至 100% 如何定位?本文通过一个 Python while True 死循环实战案例,演示 top/ps/strace/py-spy 排查流程与修复方法。
const article = {
title: "AI日报 2026-08-29",
publishedAt: "2026.08.29",
tags: ["朕喜技术","科技资讯","人工智能"],
href: "/blogs/ai-daily-2026-08-29"
}
export default articleconst article = {
title: "AI日报 2026-08-29",
publishedAt: "2026.08.29",
tags: ["朕喜技术","科技资讯","人工智能"],
href: "/blogs/ai-daily-2026-08-29"
}
export default articleconst article = definePost()
AI日报 2026-08-29
百度搭子发布办公智能体新标准,实测一次生成17份交付物;云知声中期财报亮眼,Agent业务营收4.78亿;Claude推出模型硬件标准MHS,触角伸入物理世界;全球AI人物榜、癌症疫苗定价、数据要素大赛等动态同样值得关注。
const article = {
title: "内存泄漏导致容器 OOM Killed(exit code 137)排查与修复实战",
publishedAt: "2026.08.28",
tags: ["OOM Killed","内存泄漏","Memory Leak"],
href: "/blogs/2026-08-28-0015-oom-killed"
}
export default articleconst article = {
title: "内存泄漏导致容器 OOM Killed(exit code 137)排查与修复实战",
publishedAt: "2026.08.28",
tags: ["OOM Killed","内存泄漏","Memory Leak"],
href: "/blogs/2026-08-28-0015-oom-killed"
}
export default articleconst article = definePost()
内存泄漏导致容器 OOM Killed(exit code 137)排查与修复实战
Kubernetes 中部署的 Web 服务(容器内存限制 256MB),运行一段时间后**进程神秘被杀**: ``` ❌ 容器重启了!进程被 OOM Killed (exit code 137) ``` - 服务刚启动正常,运行一段时间才崩溃,且**崩溃间隔越来越短** - 代码里没有明显的文件/连接泄漏,CPU
