大网数据广告活动
服务器运维问答

php-fpm php_network_getaddresses calls randomly start failing with bad udp cksum

· 52CE 我爱测

We're running a number of web servers (nginx, php5.6-fpm) on ubuntu instances on AWS. They've been running fine for a number of months, but in the past few days we've started getting issues where after an instance spins up everyt…

问题原文

原帖链接 · Liam Wiltshire · CC BY-SA 3.0

We're running a number of web servers (nginx, php5.6-fpm) on ubuntu instances on AWS. They've been running fine for a number of months, but in the past few days we've started getting issues where after an instance spins up everything is fine, but after 12 hours or so, network calls start to fail (specifically in this instance socket tcp calls to redis).

Having done some digging with tcpdump, it looks like the dns lookups are being thrown out because of a udp checksum failure:

17:13:38.013346 IP (tos 0x0, ttl 64, id 46236, offset 0, flags [DF], proto UDP (17), length 103) 10.0.0.121.34071 > 10.0.0.2.53: [bad udp cksum 0x14df -> 0x3ae1!] 25855+ Type20736? xxxxxxxx.us-east-1.rds.amazonaws.com. (75)

If I use telnet to connect to the Redis server from the same instance then it's fine, it only seems to affect fpm. Equally strange, it only happens a little while after the instance has started - initially all the requests go through fine. Equally, re-starting the php5.6-fpm service seems to clear the issue for a time.

I'm pretty much at the end of my knowledge at this point, so hopefully someone can point me in the right direction!

已采纳解答

原帖链接 · Michael - sqlbot · CC BY-SA 3.0

You have a defective security fix installed -- this sounds like the issue from USN-3239-2.

A security update for GNU libc that addressed (among other things)...

an unbounded stack allocation in the getaddrinfo() function of the GNU C Library.

....contained a regression -- an unintended ABI change -- that seems to have caused issues similar to what you describe... DNS resolution would eventually stop working until processes were restarted.

The original update was release 2017-03-20 and the fix was released 2017-03-21. Applying the latest OS security fixes should remedy the issue, if that's what this is.

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2017-03-22)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 3.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。