Jeff Trawick [EMAIL PROTECTED] writes:
t0 we need to fork() a new child for some reason
t1 we get the graceful restart prod on the pod BEFORE
the start_threads() thread has gotten dispatched and
initialized worker_queue
t2 we call signal_workers()
Aaron Bannert [EMAIL PROTECTED] writes:
On Thu, Feb 21, 2002 at 06:02:26PM -0500, Jeff Trawick wrote:
I just tried to hit this on my Solaris x86 box with no luck. I did
200,000 simple requests with a SIGUSR1 sent to the parent ever 2
seconds. No segfaults or failed pthread calls, but at
On Fri, Feb 22, 2002 at 02:43:04PM -0500, Jeff Trawick wrote:
It is my understanding that FIN_WAIT_2 happens on the client side after
the client does an active close but before the server does a close. If
the server process died I'd expect the OS to send a FIN back to the
client, so
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
Aaron Bannert [EMAIL PROTECTED] writes:
On Fri, Feb 22, 2002 at 02:43:04PM -0500, Jeff Trawick wrote:
It is my understanding that FIN_WAIT_2 happens on the client side after
the client does an active close but before the server does a close. If
the server process died I'd expect the OS
Jeff Trawick [EMAIL PROTECTED] writes:
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)
...
d) Dale Ghent hit a segfault on Solaris 8 in ap_queue_interrupt_all()
(NULL
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?
[Tue Feb 19 10:31:43 2002] [notice] child pid 5367 exit signal Segmentation fault
(11)
On Thu, Feb 21, 2002 at 06:02:26PM -0500, Jeff Trawick wrote:
I just tried to hit this on my Solaris x86 box with no luck. I did
200,000 simple requests with a SIGUSR1 sent to the parent ever 2
seconds. No segfaults or failed pthread calls, but at the end of the
200,000 requests I had 177
Brian Pane [EMAIL PROTECTED] writes:
Jeff Trawick wrote:
Maybe this is a hint... For a couple of the restart iterations,
worker on AIX logs this:
[crit] ap_queue_push failed with error code -1
In your AIX test environment, can you catch this error
case in action by putting
On Wed, Feb 20, 2002 at 11:44:14AM -0500, Dale Ghent wrote:
FWIW, I compiled up the latest CVS HEAD as of last night (just after the
CAS stuff was re-added back into APR) on Solaris 8+sendfile, hit the
server up pretty hard with ab, fetching 9.5k and 608k jpeg files thousands
of times with
On Wed, 20 Feb 2002, Aaron Bannert wrote:
| Now try it again and hit bin/apachectl graceful in the middle of your
| test [a few times]. :)
Got a core with this. ab reported 159 (out of 2000) requests failed (in
the Length: category). Here's a bt:
#0 ap_queue_interrupt_all (queue=0x0) at
On Wed, Feb 20, 2002 at 11:59:15AM -0500, Dale Ghent wrote:
On Wed, 20 Feb 2002, Aaron Bannert wrote:
| Now try it again and hit bin/apachectl graceful in the middle of your
| test [a few times]. :)
Got a core with this. ab reported 159 (out of 2000) requests failed (in
the Length:
On Wed, Feb 20, 2002 at 12:03:00PM -0600, Austin Gonyou wrote:
PHP4.1.1 or not working?
You have to have the version from CVS in order to get it to
compile. -- justin
On Wed, Feb 20, 2002 at 10:16:03AM -0800, Justin Erenkrantz wrote:
On Wed, Feb 20, 2002 at 12:03:00PM -0600, Austin Gonyou wrote:
PHP4.1.1 or not working?
You have to have the version from CVS in order to get it to
compile. -- justin
Err, just to make it clear, you need the latest
NP. I am using the CVS as of last night. That's why I'm writing, and
that's why I said 4.1.1, I guess it should've been 4.1.1 :)
On Wed, 2002-02-20 at 12:19, Justin Erenkrantz wrote:
On Wed, Feb 20, 2002 at 10:16:03AM -0800, Justin Erenkrantz wrote:
On Wed, Feb 20, 2002 at 12:03:00PM -0600,
FYI. Not an compilation problem, HTTPD just doesn't do anything, but
doesn't write a log either, and only 1 process is started.
On Wed, 2002-02-20 at 12:19, Justin Erenkrantz wrote:
On Wed, Feb 20, 2002 at 10:16:03AM -0800, Justin Erenkrantz wrote:
On Wed, Feb 20, 2002 at 12:03:00PM -0600,
: has anybody seen worker segfaults?
FYI. Not an compilation problem, HTTPD just doesn't do anything, but
doesn't write a log either, and only 1 process is started.
On Wed, 2002-02-20 at 12:19, Justin Erenkrantz wrote:
On Wed, Feb 20, 2002 at 10:16:03AM -0800, Justin Erenkrantz wrote:
On Wed, Feb
:[EMAIL PROTECTED]]
Sent: Wednesday, February 20, 2002 10:56 AM
To: [EMAIL PROTECTED]
Subject: Re: PHP4 was Re: has anybody seen worker segfaults?
FYI. Not an compilation problem, HTTPD just doesn't do anything, but
doesn't write a log either, and only 1 process is started.
On Wed, 2002
On Tue, Feb 19, 2002 at 12:16:13PM -0500, Jeff Trawick wrote:
I'm not getting any core dumps from the segfaulting child (threads and
Linux :) ). I need to spend more time looking into this, but first I
wondered if anybody else saw it.
RH 6.2:segfaults as (barely) described above
Aaron Bannert [EMAIL PROTECTED] writes:
Maybe this is a hint... For a couple of the restart iterations,
worker on AIX logs this:
[crit] ap_queue_push failed with error code -1
This will only happen in ap_queue_push when apr_thread_mutex_lock or
ap_thread_mutex_unlock fail (Yes, I
On Tue, Feb 19, 2002 at 12:33:58PM -0500, Jeff Trawick wrote:
Aaron Bannert [EMAIL PROTECTED] writes:
Maybe this is a hint... For a couple of the restart iterations,
worker on AIX logs this:
[crit] ap_queue_push failed with error code -1
This will only happen in
Jeff Trawick wrote:
Maybe this is a hint... For a couple of the restart iterations,
worker on AIX logs this:
[crit] ap_queue_push failed with error code -1
In your AIX test environment, can you catch this error
case in action by putting breakpoints at the two lines
in ap_queue_push() where
22 matches
Mail list logo
