Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

how can I know what happened when there were failed transactions? #38

Open
winnywind opened this issue Nov 11, 2015 · 4 comments
Open

Comments

@winnywind
Copy link

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?

@JoeDog
Copy link
Owner

JoeDog commented Nov 11, 2015

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 notifications@github.com 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.

@winnywind
Copy link
Author

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

@JoeDog
Copy link
Owner

JoeDog commented Nov 12, 2015

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 notifications@github.com 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).

@annapowellsmith
Copy link

+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.

JoeDog added a commit that referenced this issue Jan 25, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants