how can I know what happened when there were failed transactions? about siege HOT 4 OPEN

It can be tricky to determine exactly what happened. If they failed due to
server errors, then you should be able to find the details in your server
logs. My personal hunch is this: you scheduled more transactions than your
server or network can handle and sockets timed out.

J.

On Wed, Nov 11, 2015 at 2:02 AM, winnywind [email protected] wrote:

I got the result like this:

Transactions: 104875 hits
Availability: 99.03 %
Elapsed time: 18.73 secs
Data transferred: 18.93 MB
Response time: 0.01 secs
Transaction rate: 5599.31 trans/sec
Throughput: 1.01 MB/sec
Concurrency: 49.38
Successful transactions: 104875
Failed transactions: 1024
Longest transaction: 0.04
Shortest transaction: 0.00

There were 1024 failed transactions, but in the log file I only got 104875
normal response with status 200, and without any error message.
So, how can I know what happened?

—
Reply to this email directly or view it on GitHub
#38.

from siege.

Thank you for your answer.
Why not logging the reason of the failed transactions?

from siege.

In verbose mode it will show you the HTTP response code of every
transaction. If you have more failures than HTTP responses, then that means
you've flooded your network, the NIC or the server.

On Wed, Nov 11, 2015 at 9:27 PM, winnywind [email protected] wrote:

Thank you for your answer.
Why not logging the reason of the failed transactions?

—
Reply to this email directly or view it on GitHub
#38 (comment).

from siege.

+1 - it would be really helpful for debugging if verbose mode logged the URLs that gave 4XX and 5XX HTTP response codes, as well as the 200 codes.

from siege.