// paginated posts

const page = 15

const article = {
  title: "docker-compose depends_on 不等待就绪导致 MySQL Connection refused",
  publishedAt: "2026.09.02",
  tags: [],
  href: "/blogs/2026-09-02-0000-docker-compose-depends-on-healthcheck"
}

export default article

const article = {
  title: "docker-compose depends_on 不等待就绪导致 MySQL Connection refused",
  publishedAt: "2026.09.02",
  tags: [],
  href: "/blogs/2026-09-02-0000-docker-compose-depends-on-healthcheck"
}

export default article

article.tsexport default

publishedAt2026.09.02

const article = definePost()

docker-compose depends_on 不等待就绪导致 MySQL Connection refused

使用 docker-compose 编排 MySQL + Python 应用时，应用容器在启动后立即尝试连接 MySQL，但 MySQL 还在初始化阶段（建表、创建用户、分配权限），导致应用连接被拒绝。

readMore()

const article = {
  title: "Redis 内存写满拒绝写入 OOM command not allowed 排查与解决",
  publishedAt: "2026.09.02",
  tags: [],
  href: "/blogs/2026-09-02-0800-redis-maxmemory-oom"
}

export default article

const article = {
  title: "Redis 内存写满拒绝写入 OOM command not allowed 排查与解决",
  publishedAt: "2026.09.02",
  tags: [],
  href: "/blogs/2026-09-02-0800-redis-maxmemory-oom"
}

export default article

article.tsexport default

publishedAt2026.09.02

const article = definePost()

Redis 内存写满拒绝写入 OOM command not allowed 排查与解决

生产环境的 Redis 实例突然报错：`OOM command not allowed when used memory > 'maxmemory'`，所有写操作（SET、LPUSH、HSET 等）全部失败。这是因为 Redis 的 `maxmemory` 被设置为 10MB，而 `maxmemory-policy

readMore()

const article = {
  title: "MySQL Too many connections（ERROR 1040）连接数耗尽：诊断、应急恢复与根治",
  publishedAt: "2026.09.02",
  tags: ["Too many connections","ERROR 1040","HY000"],
  href: "/blogs/2026-09-02-1612-mysql-too-many-connections"
}

export default article

const article = {
  title: "MySQL Too many connections（ERROR 1040）连接数耗尽：诊断、应急恢复与根治",
  publishedAt: "2026.09.02",
  tags: ["Too many connections","ERROR 1040","HY000"],
  href: "/blogs/2026-09-02-1612-mysql-too-many-connections"
}

export default article

article.tsexport default

publishedAt2026.09.02

const article = definePost()

MySQL Too many connections（ERROR 1040）连接数耗尽：诊断、应急恢复与根治

在线商城后端在高并发期突然大量报错：

Too many connectionsERROR 1040HY000

readMore()

const article = {
  title: "AI日报 2026-09-02",
  publishedAt: "2026.09.02",
  tags: ["朕喜技术","科技资讯","人工智能"],
  href: "/blogs/ai-daily-2026-09-02"
}

export default article

const article = {
  title: "AI日报 2026-09-02",
  publishedAt: "2026.09.02",
  tags: ["朕喜技术","科技资讯","人工智能"],
  href: "/blogs/ai-daily-2026-09-02"
}

export default article

article.tsexport default

publishedAt2026.09.02

const article = definePost()

AI日报 2026-09-02

MiniMax H3 Max实现3秒生成5秒视频，打开AI视频实时商业化路径；SpaceX跨界铸造燃气轮机叶片缓解AI算力电力瓶颈；Claude Code额度调整引发争议，OpenAI同步回应优化；Archify开源架构图Agent登顶GitHub热榜；Google发布TimesFM-3时间序列模型，五角大楼接入军用A

朕喜技术科技资讯人工智能

readMore()

const article = {
  title: "Docker 容器时区不一致导致定时任务/日志时间错乱 — 排查与修复实战",
  publishedAt: "2026.09.01",
  tags: [],
  href: "/blogs/2026-09-01-0018"
}

export default article

const article = {
  title: "Docker 容器时区不一致导致定时任务/日志时间错乱 — 排查与修复实战",
  publishedAt: "2026.09.01",
  tags: [],
  href: "/blogs/2026-09-01-0018"
}

export default article

article.tsexport default

publishedAt2026.09.01

const article = definePost()

Docker 容器时区不一致导致定时任务/日志时间错乱 — 排查与修复实战

某团队将 Python 定时报表系统打包进 Docker 容器部署，业务要求每天**北京时间（CST，UTC+8）09:00** 生成并发送日报。部署后发现两个问题：

readMore()

const article = {
  title: "Node.js HTTPS 服务 TLS 证书过期修复实战：SSL certificate expired 排查与解决",
  publishedAt: "2026.09.01",
  tags: ["SSL certificate expired","certificate has expired","TLS 证书过期"],
  href: "/blogs/2026-09-01-0808-tls"
}

export default article

const article = {
  title: "Node.js HTTPS 服务 TLS 证书过期修复实战：SSL certificate expired 排查与解决",
  publishedAt: "2026.09.01",
  tags: ["SSL certificate expired","certificate has expired","TLS 证书过期"],
  href: "/blogs/2026-09-01-0808-tls"
}

export default article

article.tsexport default

publishedAt2026.09.01

const article = definePost()

Node.js HTTPS 服务 TLS 证书过期修复实战：SSL certificate expired 排查与解决

维护的 Node.js HTTPS 服务突然无法访问，浏览器报「您的连接不安全 / 证书已过期」。但 `netstat` 显示 8443 端口正常监听，`node` 进程也在运行——**服务进程没挂，只是 TLS 证书过期导致所有 HTTPS 客户端握手失败**。

SSL certificate expiredcertificate has expiredTLS 证书过期

readMore()

const article = {
  title: "Git 仓库 .git 目录膨胀的终极清理指南：彻底移除历史中的大文件",
  publishedAt: "2026.09.01",
  tags: [],
  href: "/blogs/2026-09-01-1607-git"
}

export default article

const article = {
  title: "Git 仓库 .git 目录膨胀的终极清理指南：彻底移除历史中的大文件",
  publishedAt: "2026.09.01",
  tags: [],
  href: "/blogs/2026-09-01-1607-git"
}

export default article

article.tsexport default

publishedAt2026.09.01

const article = definePost()

Git 仓库 .git 目录膨胀的终极清理指南：彻底移除历史中的大文件

Git 仓库 `.git` 目录异常膨胀，即使已经删除了大文件并提交，clone 和 pull 仍然极慢。这是因为 **Git 的设计决定了历史提交中的所有文件都会永久保留** —— 仅仅从工作区删除文件并 commit 不会将其从 Git 历史中移除。

readMore()

const article = {
  title: "AI日报 2026-09-01",
  publishedAt: "2026.09.01",
  tags: ["朕喜技术","科技资讯","人工智能"],
  href: "/blogs/ai-daily-2026-09-01"
}

export default article

const article = {
  title: "AI日报 2026-09-01",
  publishedAt: "2026.09.01",
  tags: ["朕喜技术","科技资讯","人工智能"],
  href: "/blogs/ai-daily-2026-09-01"
}

export default article

article.tsexport default

publishedAt2026.09.01

const article = definePost()

AI日报 2026-09-01

今日看点：OpenAI宣布对Cursor断供，马斯克与奥特曼再起冲突；MiniMax H3 Max实现3秒生成5秒视频，开启AI实时直播新范式；腾讯Hy4进入Arena前五，1M上下文+量化压缩方案曝光；MTurk运行21年后宣布停服；多智能体数学证明、CritICL推理优化等研究进展。

朕喜技术科技资讯人工智能

readMore()

const article = {
  title: "Linux 高负载排查实战：Load Average 飙升但 CPU 使用率低的完整诊断指南",
  publishedAt: "2026.08.31",
  tags: [],
  href: "/blogs/2026-08-31-0012-linux-load-average-io-blocking"
}

export default article

const article = {
  title: "Linux 高负载排查实战：Load Average 飙升但 CPU 使用率低的完整诊断指南",
  publishedAt: "2026.08.31",
  tags: [],
  href: "/blogs/2026-08-31-0012-linux-load-average-io-blocking"
}

export default article

article.tsexport default

publishedAt2026.08.31

const article = definePost()

Linux 高负载排查实战：Load Average 飙升但 CPU 使用率低的完整诊断指南

生产环境 4 核服务器突然响应缓慢，`uptime` 显示 **Load Average 高达 15+**，但 `top` 中 **CPU 使用率仅 10% 左右**。运维困惑：负载这么高，CPU 却很闲，问题出在哪？

readMore()

const article = {
  title: "磁盘满了但 df 和 du 对不上？lsof +L1 揪出\"已删除但被进程占用\"的文件",
  publishedAt: "2026.08.31",
  tags: ["linux","磁盘","df"],
  href: "/blogs/2026-08-31-0819-dfdu-deleted-file-lsof"
}

export default article

const article = {
  title: "磁盘满了但 df 和 du 对不上？lsof +L1 揪出\"已删除但被进程占用\"的文件",
  publishedAt: "2026.08.31",
  tags: ["linux","磁盘","df"],
  href: "/blogs/2026-08-31-0819-dfdu-deleted-file-lsof"
}

export default article

article.tsexport default

publishedAt2026.08.31

const article = definePost()

磁盘满了但 df 和 du 对不上？lsof +L1 揪出"已删除但被进程占用"的文件

df 显示磁盘 100% 满并报 No space left on device，du 全盘加起来却对不上，rm 删除大日志后空间也不释放。根因是文件已被删除但仍被进程持有 fd。本文用 lsof +L1 定位这类幽灵文件，讲清 inode 引用计数与空间回收机制，并给出处理步骤与日志轮转预防方案。

linux磁盘df

readMore()

// showing 141-150 of 281 posts