https://issues.apache.org/bugzilla/show_bug.cgi?id=56091
Jeff Trawick <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO --- Comment #1 from Jeff Trawick <[email protected]> --- There are a lot of variations and more than one symptom. I don't have a magic answer, but some hints below should help eliminate some of the search space. >HAVE_FDATASYNC Unless you have third-party modules that use apr_file_datasync(), this won't affect httpd. > sqlite3 I think you would have had to explicitly configure the use of such a db in httpd (e.g., for session cache) for this to have made a difference. You can eliminate this variation by adding "--without-sqlite3" to the configure options. > (45)Deadlock situation detected/avoided: Failed to acquire SSL session cache > lock You need to configure a different SSL mutex. Unless you have child process crashes (messages with "exit signal" in your error log), set "SSLMutex pthread". This happens due to a poor default mutex choice for Solaris (fixed in apr 1.3.10) *OR* from your configuration of "SSLMutex fcntl". (Or I'm confused.) If you have process crashes ("exit signal"), you need to get cores and backtraces. Please let us know if that is happening. . Perhaps somebody recognizes the session ticket error. . What level of APR is being compiled with and used at runtime? (This is displayed from "httpd -V".) -- 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]
