Jeff Trawick <[EMAIL PROTECTED]> writes:
> For some time some (but after 2.0.32), some tests I run have been
> segfaulting around the time of a graceful restart. Has anybody else
> seen something like this?
a new summary:
Here are some failure scenarios found when doing a graceful restart
while there were active connections:
a) 2 listening sockets on Linux, where we need an accept mutex:
[emerg] (43)Identifier removed: apr_proc_mutex_lock failed.
Attempting to shutdown process gracefully.
[emerg] (22)Invalid argument: apr_proc_mutex_unlock failed.
Attempting to shutdown process gracefully.
The server process exits and existing connections are dropped.
b) 1 listening socket in Linux, where we don't need an accept
mutex (intermittent failure):
[notice] child pid 18314 exit signal Segmentation fault (11)
c) 1 listening socket on AIX, where we don't need an accept
mutex (intermittent failure):
[crit] (22)A system call received a parameter that is not
valid.: ap_queue_push failed
d) Dale Ghent hit a segfault on Solaris 8 in ap_queue_interrupt_all()
(NULL parameter passed in).
I would guess that the cause is the patch to stop using signals
(p=0.75) or the patch to reuse transaction pools (p=0.10).
--
Jeff Trawick | [EMAIL PROTECTED] | PGP public key at web site:
http://www.geocities.com/SiliconValley/Park/9289/
Born in Roswell... married an alien...
