To:[email protected], [email protected],
[email protected]
tags 595527 + moreinfo unreproducible
thanks
Hello, I am sorry for the very ... very late answer. I am trying to
reproduce the bug, but until now, I have not been able to do it.
I am using:
siege --log='/tmp/siege.log' -b -c 600 IP_address
I only get these two kind of errors:
[error] socket: 883664 address is unavailable.: Cannot assign requested address
[error] socket: read error Connection reset by peer sock.c:460: Connection
reset by peer
Could you please provide more info, in order to help me to reproduce the bug?
Is this reliably reproducible or a one-off thing?
Are you running siege and the web server in the same host?
These are some of my logs:
Date & Time, Trans, Elap Time, Data Trans, Resp Time, Trans Rate,
Throughput, Concurrent, OKAY, Failed
2011-07-08 16:57:36, 43889, 26.86, 2, 0.39, 1633.99,
0.07, 644.75, 43889, 0
2011-07-08 16:59:15, 45221, 29.77, 2, 0.42, 1519.01,
0.07, 635.72, 45221, 0
2011-07-08 17:07:50, 644640, 349.77, 34, 0.32, 1843.04,
0.10, 587.25, 644641, 9
2011-07-11 09:28:26, 33669, 57.88, 4, 0.72, 581.70,
0.07, 418.40, 33669, 1455
2011-07-11 09:51:11, 548624, 298.29, 29, 0.32, 1839.23,
0.10, 586.15, 548624, 7
2011-07-11 09:53:54, 21775, 22.98, 3, 0.48, 947.56,
0.13, 456.73, 21775, 0
Thanks for your bug report.
Cheers,
--
Josué M. Abarca S.
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
