https://bz.apache.org/bugzilla/show_bug.cgi?id=63975
--- Comment #5 from [email protected] --- Hello, could you please elaborate what hanging FCGI process means in this context? The server uses mod_fcgid combined with suexec to launch php-cgi processes. It is quite possible for PHP process to hang - or more precisely to take too much time to process the request - but in that case mod_fcgid terminates it forcibly (SIGTERM, then KILL.) Also all FCGI processes are terminated on graceful restart and we even have a protective cron that hunts down orphaned PHP processes left in the system when Apache crashes. In short - there are no FCGI processes older than an hour in the system so the Apache process (now over 36 hours old and inactive for most of that time) has nothing to wait for - all connections related to communications between Apache and FCGI should read EOF Although, investigating this I noticed one more thing. The thread stuck reading from FD 15 is reading from "pipe:[70519261]" - ls -l /proc/pid/fd/ shows lr-x------ 1 root root 64 Nov 29 13:49 15 -> 'pipe:[70519261]' However, there is also this: l-wx------ 1 root root 64 Nov 29 13:49 16 -> 'pipe:[70519261]' Apparently, the inactive Apache process is reading from the pipe, but also has it opened for writing so it will never return an EOF. So reason for why the Apache process is stuck is because at some point some file descriptor (here FD 16) leaked and was not closed when it should have been? -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
