httpd-test-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From grega...@apache.org
Subject Re: Regarding Apache 2.0.48 and specweb99
Date Wed, 03 Dec 2003 21:46:39 GMT
MATHIHALLI,MADHUSUDAN (HP-Cupertino,ex1) wrote:
> I enabled the POST transactions, and all of a sudden, the apache process is
> now hung (this is first time I'm seeing this behaviour).. The stack is :
> 
> (gdb) t 21
> [Switching to thread 21 (system thread 29207)]
> #0  0xc000000000306850:0 in _semop_sys+0x30 () from
> /usr/lib/hpux64/libc.so.1
> (gdb) bt
> #0  0xc000000000306850:0 in _semop_sys+0x30 () from
> /usr/lib/hpux64/libc.so.1
> #1  0xc000000000314b50:0 in semop+0xb0 () from /usr/lib/hpux64/libc.so.1
> #2  0xc000000001b73220:0 in proc_mutex_sysv_acquire+0x70 ()
>    from /opt/hpws/apache/lib/libapr-0.sl.9
> #3  0xc000000001b73fc0:0 in apr_proc_mutex_lock+0x60 ()
>    from /opt/hpws/apache/lib/libapr-0.sl.9
> #4  0xc000000001b72950:0 in apr_global_mutex_lock+0x90 ()
>    from /opt/hpws/apache/lib/libapr-0.sl.9
> #5  0xc000000001cf37d0:0 in do_post+0x780 ()

Two possibilities:

* the command/Fetch URI is stuck also, or
* something died holding the post lock, and it didn't get automagically cleaned 
up.  I recall hearing that SysV sems are notorious for that on some platforms.

Do either of those make sense?  Any clues in the error_log?

Greg


Mime
View raw message