On Sat, Jan 23, 2010 at 3:08 PM, Jeremy R. <jeremy@xxxxxxxxxxxx> wrote: > Okay, so here are the salient lines from the error logs (I have two vhosts, webmail and wiki, running through suexec – if I put them through the regular FCGI process without suexec, I don't have this problem). Also, I should not that this problem does not occur on my testing VM, only on our production server (so I'm not quite sure what the problem is). > > webmail-error.log: > > [Wed Jan 20 23:38:17 2010] [emerg] mod_fcgid: server is restarted, 32760 must exit > > wiki-error.log > > [Sat Jan 23 15:03:25 2010] [emerg] mod_fcgid: server is restarted, 22502 must exit > [Sat Jan 23 15:03:25 2010] [emerg] (22)Invalid argument: mod_fcgid: can't get lock, pid: 22502 > [Sat Jan 23 15:03:25 2010] [emerg] mod_fcgid: server is restarted, 16264 must exit > [Sat Jan 23 15:03:25 2010] [emerg] (22)Invalid argument: mod_fcgid: can't get lock, pid: 16264 > [Sat Jan 23 15:03:25 2010] [emerg] mod_fcgid: server is restarted, 22501 must exit > [Sat Jan 23 15:03:25 2010] [emerg] (22)Invalid argument: mod_fcgid: can't get lock, pid: 22501 > > It looks like the emergency messages about being unable to get a lock on these processes is what's causing Apache to hang until I forcefully kill them. mod_fcgid tries to exit the httpd child process right after issuing that message. I think it encounters the error because it is running in a child process from the old generation (before restart) and the lock was removed in the parent process. Did you have to forcefully kill those same processes that said "can't get lock"? Next time can you attach with gdb and get a backtrace? Do something like this: gdb /path/to/httpd 22501 ... (gdb) where ... (gdb) quit --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|