On Jul 15, 2014 8:46 PM, "Tomlinson, Stuart" <st0...@intl.att.com> wrote: > > [ please excuse the poor formatting due to email client ] > > > From: Jeff Trawick [mailto:traw...@gmail.com] > > > > On Tue, Jul 15, 2014 at 4:55 PM, Tomlinson, Stuart <st0...@intl.att.com> wrote: > > Hello, > > > > We have experienced this warning/error a few times: > > [Thu Jul 03 20:17:15 2014] [warn] (4)Interrupted system call: Failed to acquire SSL session cache lock > > > > After this has occurred, the Apache ErrorLog is flooded with these errors: > > [Thu Jul 03 20:17:57 2014] [error] shmcb_subcache_retrieve internal error > > > > It looks like there is a bug in the APR library. It doesn't handle EINTR ("Interrupted system call") in the POSIX semaphore implementation. > > Thanks for the superfast feedback. Should I file a bug for this? If so, should it be filed for "Apache httpd-2" product or "APR" ? >
No need, I fixed it shortly after I saw your post ;) Otherwise, "APR" would be the answer... > > > SSLMutex sem > > > > Use "SSLMutex sysvsem" instead. > > Are there any expected negative impacts from using "sysvsem" instead of "sem" (which I understand defaults to "posixsem" - described in the documentation as "elegant", whereas "sysvsem" is merely "somewhat elegant")? Funny developers... There is safety in numbers (i.e., use what other people on your platform use, unless you have a specific problem). sysvsem is the default on Linux. (I assume you are using Linux, but maybe that is not the case.) Using sysvsem on Solaris with the prefork MPM, you would likely have to increase the number of semaphore undo structures (at least in the old days; I can't find my normal go-to reference for AcceptMutex oddities; Eric?) > > > Regards, > > > Stu Tomlinson.
