Re: Debugging: child process 14446 still did not exit, sending a SIGTERM

2009-10-16 Thread Joe Lewis
Michael B Allen wrote: I have a customer who very occasionally sees apache workers hang. I'm pretty sure this is caused by an errant module but I don't know which one. Is there any way to determine which module is causing Apache workers to hang? Can I temporarily disable that SIGTERM so that I

Re: Debugging: child process 14446 still did not exit, sending a SIGTERM

2009-10-16 Thread Michael B Allen
On Fri, Oct 16, 2009 at 1:10 PM, Joe Lewis j...@joe-lewis.com wrote: Michael B Allen wrote: I have a customer who very occasionally sees apache workers hang. I'm pretty sure this is caused by an errant module but I don't know which one. Is there any way to determine which module is causing

Re: Debugging: child process 14446 still did not exit, sending a SIGTERM

2009-10-16 Thread Joe Lewis
Michael B Allen wrote: On Fri, Oct 16, 2009 at 1:10 PM, Joe Lewis j...@joe-lewis.com wrote: Michael B Allen wrote: I have a customer who very occasionally sees apache workers hang. I'm pretty sure this is caused by an errant module but I don't know which one. Is there any way to

Re: Debugging: child process 14446 still did not exit, sending a SIGTERM

2009-10-16 Thread Joe Lewis
Michael B Allen wrote: On Fri, Oct 16, 2009 at 2:42 PM, Joe Lewis j...@joe-lewis.com wrote: Michael B Allen wrote: On Fri, Oct 16, 2009 at 1:10 PM, Joe Lewis j...@joe-lewis.com wrote: Michael B Allen wrote: I have a customer who very occasionally sees apache workers

Re: Debugging: child process 14446 still did not exit, sending a SIGTERM

2009-10-16 Thread Chris Kukuchka
Michael B Allen wrote: Can I temporarily disable that SIGTERM so that I can have enough time to attach GDB to the hanging processes? Mike, The code which sends the SIGTERM is in mpm_common.c: static int reclaim_one_pid(pid_t pid, action_t action) { ... case SEND_SIGTERM: /* ok, now

Re: Debugging: child process 14446 still did not exit, sending a SIGTERM

2009-10-16 Thread Michael B Allen
On Fri, Oct 16, 2009 at 8:04 PM, Chris Kukuchka chr...@sequoiagroup.com wrote: Michael B Allen wrote: Can I temporarily disable that SIGTERM so that I can have enough time to attach GDB to the hanging processes? Mike, The code which sends the SIGTERM is in mpm_common.c: static int

2.2.14 official release announcement

2009-10-16 Thread Seema Alevoor
Hi, Can someone point me to the official announcement page for 2.2.14 ? http://www.apache.org/dist/httpd/Announcement2.2.html still refers to 2.2.13 version ! Thanks, Seema.

Re: 2.2.14 official release announcement

2009-10-16 Thread Graham Leggett
Seema Alevoor wrote: Can someone point me to the official announcement page for 2.2.14 ? http://www.apache.org/dist/httpd/Announcement2.2.html still refers to 2.2.13 version ! It looks like the same svnpubsub breakage that happened on apr has also happened on httpd, will pass your message on

Re: Making a binary distribution package... for AIX

2009-10-16 Thread Graham Leggett
Michael Felt wrote: my bad - my AddHandler statement was outside the IFModule block (at line 69, near the LoadModules, and it worked for years because mod_mime was built-in) - so the problem I was having was primarily a user error. What might be a build issue is all the missing LoadModule

Re: svn commit: r823703 - in /httpd/httpd/trunk: CHANGES modules/dav/fs/repos.c modules/dav/main/mod_dav.h

2009-10-16 Thread Graham Leggett
Brian J. France wrote: mod_dav_acl would use the filename to validate the acls. Like I said, I don't know if get_pathname is needed or we should just use r-filename and make sure a mod_dav_fs_db module updated it. As Joe points out, an ACL could refer to something that wasn't a file, such as

Re: 2.3.3-alpha

2009-10-16 Thread Jim Jagielski
On Oct 15, 2009, at 7:56 PM, William A. Rowe, Jr. wrote: Jim Jagielski wrote: Planning on pushing this out to coincide w/ ACUS09... Let's assume head of apr 1.4... You've made 'reservations' a number times in the past several years in STATUS, and on list, that weren't realized for 1+

Re: 2.3.3-alpha

2009-10-16 Thread Jim Jagielski
On Oct 15, 2009, at 7:45 PM, William A. Rowe, Jr. wrote: Jim Jagielski wrote: Planning on pushing this out to coincide w/ ACUS09... Let's assume head of apr 1.4... -1 veto; that is not released code, and I'm not fond of the idea of a fork of apr managed at httpd. Who said anything

Re: 2.3.3-alpha

2009-10-16 Thread Rainer Jung
On 15.10.2009 21:54, Jim Jagielski wrote: Planning on pushing this out to coincide w/ ACUS09... Let's assume head of apr 1.4... +1

Re: 2.3.3-alpha

2009-10-16 Thread William A. Rowe, Jr.
Jim Jagielski wrote: Yes, I know all that. But the reason I do this is to see if there is any sort of support behind this... I've I make this proposal and don't see any +1s, then it leaves me to believe that most people aren't so interested in doing so, which makes me wonder why. So

Re: 2.3.3-alpha

2009-10-16 Thread Graham Leggett
William A. Rowe, Jr. wrote: So speaking for myself, I am interested. As am I. In fact, if everything builds at the moment against 1.3.x apr (irrespective of whether or not all features are enabled) I'm likely to just tag on Sunday or Monday, and give testers something to start chewing on,

Re: checksum madness - follow-up

2009-10-16 Thread Guenter Knauf
Hi, Graham Leggett schrieb: To put this into perspective, checking an md5 (or sha1) checksum is simply a case of doing the following three steps: - Run md5sum, or openssl, or perl, or whatever you want, and get the md5 hash string of the binary you downloaded printed out to your terminal.

Re: checksum madness - follow-up

2009-10-16 Thread William A. Rowe, Jr.
Guenter Knauf wrote: if the reference hash file from www.apache.org is build with gpg then this method fails (and I consider gpg really unusable for this purpose); here are some bad samples which show that gpg breaks lines if the this looks really horrible to me (and I'm curious if some sed

fixing an httpd test which is confused about which modules are loaded in the test conf

2009-10-16 Thread Jeff Trawick
The mod_info test (t/modules/info.t) asks Apache::Test::config() for a list of modules. It then expects each of those modules to be reported by mod_info. But some of those modules are not actually loaded because of modules which are skipped by TestConfigParse.pm #XXX mod_jk requires