Last modified: 2014-02-26 12:55:10 UTC
EventLogging includes a web server intended to handle requests for its beacon image, *only* during development. I find it works for a while, then goes unresponsive. The last time this happened it also went to 100% of my CPU. strace shows endless recvfrom(4, "", 1024, 0, NULL, NULL) = 0 and lsof show that file descriptor 4 is COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME php 23276 spage 4u IPv4 1437730 0t0 TCP localhost:tproxy->localhost:40721 (CLOSE_WAIT) Workaround: kill -9 and restart. (For some reason a regular kill doesn't take, despite the code to "exit cleanly on SIGTERM".)
Gerrit change #37186
[moving from MediaWiki extensions to Analytics product - see bug 61946]