You are viewing a plain text version of this content. The canonical link for it is here.
Posted to test-dev@httpd.apache.org by "Snehal K.Gandhi" <sn...@siptech.co.in> on 2003/04/21 15:00:23 UTC

Getting an Error

Hi all,

i'm getting an error when i try running the XML File.
The Error is  : Error running test profile: Error string not specified yet

i executed my XML File using ./flood Test1.xml

My XML File is :
---------------------------------XML File----------
<flood>

  <urllist>
    <name>Test Hosts</name>
    <description>Testing the Httpd Manual</description>
   
    <url method="POST">http://192.168.66.204/manual</url>
    <url 
method="HEAD">http://192.168.66.204/manual/content-negotiation.html</url>
    <url method="GET">http://192.168.66.204/manual/invoking.html</url>
    <url>http://192.168.66.204/manual</url>

    </urllist>

  <profile>
    <name>SKProfile</name>
    <description>A Test for SKG's Configuration</description>
    <useurllist>Test Hosts</useurllist>
    <profiletype>round_robin</profiletype>
    <socket>generic</socket>
    <report>relative_times</report>
    <verify_resp>verify_200</verify_resp>
  </profile>

  <farmer>
    <name>SK</name>
    <count>5</count>
    <useprofile>SKProfile</useprofile>
  </farmer>

  <farm>
    <name>SKG</name>
    <usefarmer count="5" startcount="2" startdelay="5">SK</usefarmer>
  </farm>

  <seed>1</seed>
</flood>

---------------------------------------------------

thnx in advance
regards
Snehal

-- 
Snehal K. Gandhi
Core Technology Group (CTG)
SIP Technologies & Exports Ltd.,
Mobile:98841 35700 Ph:+91-44-22541473/4 x313
Email:snehal@siptech.co.in URL:http://www.siptech.com/











Re: Assert used in Flood and its triggering under Sun Solaris

Posted by Justin Erenkrantz <je...@ics.uci.edu>.
--On Monday, April 28, 2003 07:22:10 -0400 Norman Tuttle 
<nt...@photon.poly.edu> wrote:

> (1) What is the purpose of the assert here, and why might it be failing
> specifically on a Solaris system?, and

IIRC, it is meant to assert an HTTP protocol violation wrt chunking.  The 
assert at flood_socket_keepalive.c:467 looks like it is trying to skip over 
the CRLF after the chunk size.

My guess is that the assert could be triggered if the chunk line wasn't 
fully available.  Yet, if those characters weren't read, then 
keepalive_read_chunk_size is going to have problems as well (but won't 
trigger an assert - it'd return 0 for the chunk length - which is wrong). 
So, at that point, we have no idea how much we should be reading in the 
response, but we *did* read something in the response after the headers - 
note all of the checks on the size (see line 440).

Note that a quick hack would probably be to try to read more from the 
socket at this point in a blocking (non-blocking *might* work, but is 
suspect) read - in the hopes that the rest of the chunk line is available.

Taking a look at the first few characters of new_resp->chunk should show 
this.  At that point, new_resp->chunk should be something like '5f\r\n' 
where 5f is the chunk length in hex.  I bet you've got a partial chunk size 
without the trailing \r\n or something equally screwy.

And, if you don't have '5f\r\n' but rather content, then you've got a 
broken server that is indicating chunking without really chunking the 
response.  That's illegal - the assert was meant for those cases rather 
than the partial chunk line.

> (2) What would be a more graceful way of reporting this error rather than
> aborting the system with a core dump? I have an exception reporting
> mechanism in place, and just want to understand how the system should
> recover in this case. It seems that the code is highly coupled with
> notions of chunked encoding.

The whole protocol logic needs to be revamped.  Serf's protocol logic is 
much cleaner than flood's (partly because the flood protocol code is 
fundamentally flawed).  But, that requires someone with time to get flood 
to use serf instead.  The chunking code and SSL logic is *way* cleaner 
since we rely upon filters...

As to the explanation as to why Solaris shows this while Win32 doesn't is 
probably because of the underlying socket buffers.  Win32 may be returning 
when it has that \r\n, while Solaris is breaking first.  -- justin

Re: Assert used in Flood and its triggering under Sun Solaris

Posted by Aaron Bannert <aa...@clove.org>.
This code for handling chunked-encoding is foreign to me,
but I'll try to see if I can help. It looks to me like the
assert() hits on chunked input parsing error*, so is it possible
that the socket read call didn't return enough data and the read
buffer simply didn't contain a CRLF yet?

Perhaps if you print out the contents of that buffer (when it
dumps core) and also send over the headers that your server
is responding with we might be able to track down the problem.


(* we really shouldn't be dumping cores on bad input, since
    we're ignoring malicious clients...)

-aaron


On Monday, April 28, 2003, at 04:22  AM, Norman Tuttle wrote:

> Flood Developers on Solaris / in general:
>
> The flood website says that the majority of the developers for the 
> Flood
> project have developed it using Solaris and Linux. Therefore I am 
> curious
> to know why I might be seeing different behavior when running keepalive
> socket code on Solaris (than Win32 or Linux); specifically, it fails
> assert code found in the source file flood_socket_keepalive.c, thus
> aborting in the middle of a run with a core dump. This type of behavior
> does not occur with the code I have running on a Win32 system.
>
> Specifically, I want to know:
> (1) What is the purpose of the assert here, and why might it be failing
> specifically on a Solaris system?, and
> (2) What would be a more graceful way of reporting this error rather 
> than
> aborting the system with a core dump? I have an exception reporting
> mechanism in place, and just want to understand how the system should
> recover in this case. It seems that the code is highly coupled with
> notions of chunked encoding.
>


Assert used in Flood and its triggering under Sun Solaris

Posted by Norman Tuttle <nt...@photon.poly.edu>.
Flood Developers on Solaris / in general:

The flood website says that the majority of the developers for the Flood
project have developed it using Solaris and Linux. Therefore I am curious
to know why I might be seeing different behavior when running keepalive
socket code on Solaris (than Win32 or Linux); specifically, it fails
assert code found in the source file flood_socket_keepalive.c, thus
aborting in the middle of a run with a core dump. This type of behavior
does not occur with the code I have running on a Win32 system.

Specifically, I want to know:
(1) What is the purpose of the assert here, and why might it be failing
specifically on a Solaris system?, and
(2) What would be a more graceful way of reporting this error rather than
aborting the system with a core dump? I have an exception reporting
mechanism in place, and just want to understand how the system should
recover in this case. It seems that the code is highly coupled with
notions of chunked encoding.



Re: Getting an Error, farm not "Bingo"

Posted by Norman Tuttle <nt...@photon.poly.edu>.
Easy one. The farm you specified is not named "Bingo". Flood wants to run
only a farm named Bingo. Change the name of your farm to "Bingo" and the
file will work!

-Norman Tuttle ntuttle@opendemand.com

On Mon, 21 Apr 2003, Snehal K.Gandhi wrote:

> Hi all,
> 
> i'm getting an error when i try running the XML File.
> The Error is  : Error running test profile: Error string not specified yet
> 
> i executed my XML File using ./flood Test1.xml
> 
> My XML File is :
> ---------------------------------XML File----------
> <flood>
> 
>   <urllist>
>     <name>Test Hosts</name>
>     <description>Testing the Httpd Manual</description>
>    
>     <url method="POST">http://192.168.66.204/manual</url>
>     <url 
> method="HEAD">http://192.168.66.204/manual/content-negotiation.html</url>
>     <url method="GET">http://192.168.66.204/manual/invoking.html</url>
>     <url>http://192.168.66.204/manual</url>
> 
>     </urllist>
> 
>   <profile>
>     <name>SKProfile</name>
>     <description>A Test for SKG's Configuration</description>
>     <useurllist>Test Hosts</useurllist>
>     <profiletype>round_robin</profiletype>
>     <socket>generic</socket>
>     <report>relative_times</report>
>     <verify_resp>verify_200</verify_resp>
>   </profile>
> 
>   <farmer>
>     <name>SK</name>
>     <count>5</count>
>     <useprofile>SKProfile</useprofile>
>   </farmer>
> 
>   <farm>
>     <name>SKG</name>
>     <usefarmer count="5" startcount="2" startdelay="5">SK</usefarmer>
>   </farm>
> 
>   <seed>1</seed>
> </flood>
> 
> ---------------------------------------------------
> 
> thnx in advance
> regards
> Snehal
> 
> -- 
> Snehal K. Gandhi
> Core Technology Group (CTG)
> SIP Technologies & Exports Ltd.,
> Mobile:98841 35700 Ph:+91-44-22541473/4 x313
> Email:snehal@siptech.co.in URL:http://www.siptech.com/
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>