DO NOT REPLY [Bug 32325] New: - Deadlock situation detected/avoided: Failed to acquire global mutex lock

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=32325>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=32325

           Summary: Deadlock situation detected/avoided: Failed to acquire
                    global mutex lock
           Product: Apache httpd-2.0
           Version: 2.0.52
          Platform: Sun
        OS/Version: Solaris
            Status: NEW
          Severity: normal
          Priority: P3
         Component: All
        AssignedTo: bugs@httpd.apache.org
        ReportedBy: asmorgrav@yahoo.no


The following error message appears in the error log file of a virtual host 
under load:

[warn] (45)Deadlock situation detected/avoided: Failed to acquire global mutex 
lock

Then, the following error message appears in the main server error log:

[emerg] (45)Deadlock situation detected/avoided: apr_proc_mutex_lock failed. 
Attempting to shutdown process gracefully.

Then a new process is spawned and operations resume.

I have this problem with Apache 2.0.52 on Sun Solaris 8 (USparc), but I am 
unable to reproduce it using Apache 2.0.49 with the exact same configuration. 

During compilation of both server versions I use the following configuration 
flags (in addition to enabling modules): --enable-rule=SHARED_CORE 
--enable-rule=SSL_EXPERIMENTAL --with-mpm=worker --enable-nonportable-atomics 
--with-ssl=/u01/opt --with-expat=$PWD/`ls -d srclib/apr-util/xml/expat`

# apache2/bin/httpd -V
Server version: Apache/2.0.52
Server built:   Oct 19 2004 12:07:03
Server's Module Magic Number: 20020903:9
Architecture:   32-bit
Server compiled with....
 -D APACHE_MPM_DIR="server/mpm/worker"
 -D APR_HAS_SENDFILE
 -D APR_HAS_MMAP
 -D APR_HAVE_IPV6 (IPv4-mapped addresses enabled)
 -D APR_USE_FCNTL_SERIALIZE
 -D APR_USE_PTHREAD_SERIALIZE
 -D SINGLE_LISTEN_UNSERIALIZED_ACCEPT
 -D APR_HAS_OTHER_CHILD
 -D AP_HAVE_RELIABLE_PIPED_LOGS
 -D HTTPD_ROOT="/u01/opt/apache2"
 -D SUEXEC_BIN="/u01/opt/apache2/bin/suexec"
 -D DEFAULT_SCOREBOARD="logs/apache_runtime_status"
 -D DEFAULT_ERRORLOG="logs/error_log"
 -D AP_TYPES_CONFIG_FILE="conf/mime.types"
 -D SERVER_CONFIG_FILE="conf/httpd.conf"

# apache2/bin/httpd -l
Compiled in modules:
  core.c
  mod_access.c
  mod_log_config.c
  mod_env.c
  mod_headers.c
  mod_setenvif.c
  mod_proxy.c
  proxy_connect.c
  proxy_ftp.c
  proxy_http.c
  worker.c
  http_core.c
  mod_mime.c
  mod_status.c
  mod_autoindex.c
  mod_cgi.c
  mod_negotiation.c
  mod_dir.c
  mod_userdir.c
  mod_alias.c
  mod_rewrite.c
  mod_so.c

DSO Modules included:
apache2.0.52/modules/mod_info.so 
apache2.0.52/modules/mod_expires.so
apache2.0.52/modules/mod_deflate.so
apache2.0.52/modules/mod_ssl.so 
siteminder/webagent/lib/libmod_sm20.so
siteminder/webagent/lib/libbtunicode.so
siteminder/webagent/lib/libsmlogging.so
siteminder/webagent/lib/libsmgda.so
siteminder/webagent/lib/libsmvariable.so

I use 
AcceptMutex default
SSLMutex default

According to the logs they default to fcntl and shmcb respectively.

Another user has reported getting the same error with 2.0.51 on the Apache 
mailing list. He also uses the worker MPM and modSSL, but not the siteminder 
stuff.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org