Re: Regarding Apache 2.0.48 and specweb99

2004-01-09 Thread Sander Temme
> the various types of URLs. Fortunately, the client prints the URLs before it > tests them. Cut-n-paste the failing URLs into a browser navigation bar and > hit > enter. What does the browser display? Even better, the manager script dumps the result of its tests to files with names like 'dync

Re: Regarding Apache 2.0.48 and specweb99

2004-01-09 Thread gregames
Joshua Schnee wrote: I am attempting to set up the latest Apache server and RHEL 64bit to use in a Specweb99 run and am running into cgi issues. I am very new to Apache, and am having difficulty getting apache to run/use/find my cgi-script. Static content works fine, but I am getting improper

RE: Regarding Apache 2.0.48 and specweb99

2003-12-04 Thread MATHIHALLI,MADHUSUDAN (HP-Cupertino,ex1)
>-Original Message- >From: Sander Temme [mailto:[EMAIL PROTECTED] [SNIP] > >> There's one more thing I noticed (might be specific to >HP-UX) : I saw more >> errors with keepalive ON rather than when it was OFF. > >I think you may be looking at a problem where server and client(s) are >mess

Re: Regarding Apache 2.0.48 and specweb99

2003-12-04 Thread Sander Temme
>> I recall hearing that SysV sems are notorious for that on >> some platforms. > > I'm thinking of having the SEM_UNDO flag while creating the semaphore (if > it's not already enabled) APR's sysvsem IPC locks have undo enbaled. > There's one more thing I noticed (might be specific to HP-UX) : I

RE: Regarding Apache 2.0.48 and specweb99

2003-12-04 Thread MATHIHALLI,MADHUSUDAN (HP-Cupertino,ex1)
>-Original Message- >From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] [SNIP] >Two possibilities: > >* the command/Fetch URI is stuck also, or I don't think the client did any Fetch when apache stopped. >* something died holding the post lock, and it didn't get >automagically cleaned u

Re: Regarding Apache 2.0.48 and specweb99

2003-12-03 Thread gregames
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 0xc0306850:0 in _semop_sys+0x30

RE: Regarding Apache 2.0.48 and specweb99

2003-12-02 Thread MATHIHALLI,MADHUSUDAN (HP-Cupertino,ex1)
_body+0x490 () from /usr/lib/hpux64/libpthread.so.1 Any ideas ? -Madhu >-Original Message- >From: MATHIHALLI,MADHUSUDAN (HP-Cupertino,ex1) [mailto:[EMAIL PROTECTED] >Sent: Tuesday, December 02, 2003 9:07 AM >To: 'dev@httpd.apache.org'; [EMAIL PROTECTED] >Subjec

RE: Regarding Apache 2.0.48 and specweb99

2003-12-02 Thread MATHIHALLI,MADHUSUDAN (HP-Cupertino,ex1)
>-Original Message- >From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] [SNIP] >I'm glad you're making progress. But I'm wondering why >raising the mod_cgid >Listen backlog was so important. If 100 mod_cgid connections >wasn't enough at >some point, either the workload is spikey or t

Re: Regarding Apache 2.0.48 and specweb99

2003-12-02 Thread gregames
MATHIHALLI,MADHUSUDAN (HP-Cupertino,ex1) wrote: I think I found the problem (.. and it's not the cgid exiting problem). The problem was because the default Listen Backlog in mod_cgid was a little small (100 outstanding connections). I got the following tusc log for the httpd processes : {62717} con

RE: Regarding Apache 2.0.48 and specweb99

2003-12-02 Thread MATHIHALLI,MADHUSUDAN (HP-Cupertino,ex1)
#x27;t connect" errors. I increased it to 1024. -Madhu >-Original Message- >From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] >Sent: Monday, November 24, 2003 1:48 PM >To: [EMAIL PROTECTED] >Subject: Re: Regarding Apache 2.0.48 and specweb99 > > >M

Re: Regarding Apache 2.0.48 and specweb99

2003-11-24 Thread gregames
MATHIHALLI,MADHUSUDAN (HP-Cupertino,ex1) wrote: Hmmn. Interesting. 1. Did you include the cgid restart fix ? I don't think so. It's the httpd-2.0.48 tarball + mod_specweb99. 2. Are you driving the server with the SPECweb99 recommended CGI load ? DYNAMIC_CGI_GET=.005 I believe that's the standard.

RE: Regarding Apache 2.0.48 and specweb99

2003-11-21 Thread MATHIHALLI,MADHUSUDAN (HP-Cupertino,ex1)
-- >>From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] >>Sent: Friday, November 21, 2003 1:50 PM >>To: dev@httpd.apache.org >>Cc: [EMAIL PROTECTED] >>Subject: Re: Regarding Apache 2.0.48 and specweb99 >> >> >>MATHIHALLI,MADHUSUDAN (HP-Cupertino,ex1) wrote: &g

RE: Regarding Apache 2.0.48 and specweb99

2003-11-21 Thread MATHIHALLI,MADHUSUDAN (HP-Cupertino,ex1)
2003 1:50 PM >To: dev@httpd.apache.org >Cc: [EMAIL PROTECTED] >Subject: Re: Regarding Apache 2.0.48 and specweb99 > > >MATHIHALLI,MADHUSUDAN (HP-Cupertino,ex1) wrote: >> Hi Greg, >> The recent set of discussions prompted me to get some >Apache numbers >> o

Re: Regarding Apache 2.0.48 and specweb99

2003-11-21 Thread gregames
MATHIHALLI,MADHUSUDAN (HP-Cupertino,ex1) wrote: Hi Greg, The recent set of discussions prompted me to get some Apache numbers out there - and when I started with the SPECweb99 run, I experienced a major hang in the Apache, and the cgid daemon getting killed (I don't know how). Have you also

Re: Regarding Apache 2.0.48 and specweb99

2003-11-21 Thread gregames
MATHIHALLI,MADHUSUDAN (HP-Cupertino,ex1) wrote: cgid should _never_ exit without something in the error log. I tried attaching tusc to the cgi daemon - but since the daemon dies at a random time, my log file was getting too full, and I had to just stop it. Why not just let tusc write to a conso

RE: Regarding Apache 2.0.48 and specweb99

2003-11-21 Thread MATHIHALLI,MADHUSUDAN (HP-Cupertino,ex1)
g >Subject: RE: Regarding Apache 2.0.48 and specweb99 > > > >>-Original Message- >>From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] >[SNIP] > >>cgid should _never_ exit without something in the error log. >>That makes it >>sound like

RE: Regarding Apache 2.0.48 and specweb99

2003-11-21 Thread MATHIHALLI,MADHUSUDAN (HP-Cupertino,ex1)
>-Original Message- >From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] [SNIP] >cgid should _never_ exit without something in the error log. >That makes it >sound like a core problem, i.e. ap_process_child_status() or a >signal handler is >fubar, in addition to whatever made the cgi d

Re: Regarding Apache 2.0.48 and specweb99

2003-11-21 Thread gregames
l Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, November 20, 2003 6:27 AM To: MATHIHALLI,MADHUSUDAN (HP-Cupertino,ex1) Subject: Re: Regarding Apache 2.0.48 and specweb99 MATHIHALLI,MADHUSUDAN (HP-Cupertino,ex1) wrote: Hi Greg, The recent set of discussions prompted me