httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sai Jai Ganesh Gurubaran <saijaigan...@gmail.com>
Subject Re: FW: [users@httpd] Apache 2 aborting downloads
Date Mon, 11 Jul 2005 05:18:01 GMT
Hi Joshua,
  Thanks for the tip.
We tried the same and here are some of the observations.
1. Debugging the Apache on the single threaded environment - issue not
reproducible.
2. We upgraded to Apache version  54, and tested 7 parallel downloads
(from different machines). All went successful.
3. Diverted the users on to Apache version  54 (300 users). The
problem surfaced again.
4. Peculiar thing to notice is: if one download aborts (exit signal
Aborted) all the other downloads exit at the same time.
5. on Apache 2.0.50 the download was failing consistently but on
Apache 2.0.54 the download fails randomly. but if it fails - all other
downloads exit at the same time!!!!.


Can anyone help us in this?

Regards
Ganesh


 
> -----Original Message-----
> From: Joshua Slive [mailto:jslive@gmail.com]
> Sent: Thursday, June 09, 2005 7:35 PM
> To: Sai Jai Ganesh Gurubaran
> Subject: Re: [users@httpd] Apache 2 aborting downloads
> 
> 
> On 6/9/05, Sai Jai Ganesh Gurubaran <saijaiganesh@gmail.com> wrote:
> > Hi,
> > Thanks for the reply setting the directives did help.
> > But when we applied the load we are getting the same problem. On
> > Analysis we find that it turns out to be a segmentation fault. strace
> > - gives the following output:
> >
> > [pid 20887] select(0, NULL, NULL, NULL, {1, 0}) = 0 (Timeout) [pid
> > 20887] waitpid(-1, [WIFSIGNALED(s) && WTERMSIG(s) == SIGABRT],
> > WNOHANG|WUNTRACED) = 2095
> > [pid 20887] gettimeofday({1118307417, 901956}, NULL) = 0
> > [pid 20887] write(6, "[Thu Jun 09 14:26:57 2005] [noti"..., 75) = 75
> >
> > And in Apache's Error log we get:
> > [Thu Jun 09 14:26:57 2005] [notice] child pid 2095 exit signal Aborted
> 
> > (6)
> >
> > Don't know how to interpret the above dump. All the download breaks
> > are givin exactly the same SIGABRT.
> >
> > Can anyone guide us how to go about?
> > Don't have a clue on where to start searching.
> 
 Start by finding the core dump file and getting a backtrace to see where
 the problem is.  The strace doesn't have enough details because it only
 tracks syscalls.  There are a few instructions here:
 http://httpd.apache.org/dev/debugging.html
 
 Joshua.
 

Sai Jai Ganesh. G.

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org


Mime
View raw message