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

Time response graph is not working on master/slave configuration #1182

Closed
davidgca opened this issue Dec 2, 2019 · 7 comments
Closed

Time response graph is not working on master/slave configuration #1182

davidgca opened this issue Dec 2, 2019 · 7 comments
Labels

Comments

@davidgca
Copy link

davidgca commented Dec 2, 2019

After migrating to last python and locust releases and running a master-slave configuration in docker (one container for each master-slave node), the time response graph is not working: "No data" is showing by move pointer to the response-time line (see attached images).

Locust error1

error locust summary1

NOTE: Download data function is working well

Expected behaviour

Time response graph should display all average response time distribution for the current execution

Actual behaviour

After some seconds average response time goto "No data", Clicking on reset stats, the data return for 2-3 seconds and again drop to 0. The behaviours cannot be reproduced on a single container execution (without master/slaves):

error locust 4

Steps to reproduce

Update locust and python to last releases and rerun the cluster

Environment settings

Locust version: 0.13.1
Python/alpine version: python:3.8.0-alpine3.10
docker version:17.05.0-ce running on debian 9

@davidgca davidgca added the bug label Dec 2, 2019
@heyman
Copy link
Member

heyman commented Dec 2, 2019

This was fixed in 0.13.2 (https://github.com/locustio/locust/blob/master/CHANGELOG.md#0132).

@heyman heyman closed this as completed Dec 2, 2019
@heyman heyman added the invalid label Dec 2, 2019
@abinjaik
Copy link

We still get this issue with 0.14.x Locust... Charts goes off after sometimes

@heyman heyman removed the invalid label Feb 29, 2020
@heyman
Copy link
Member

heyman commented Feb 29, 2020

@abinjaik:
I don't think you're experiencing a regression of this issue, since this bug was only for the response time graph, and if I understand you correctly all graphs stops working?

I'm not able to reproduce your issue. Feel free to open a new ticket with as much information as possible on how to reproduce the issue. And if possible provide us with a minimal reproducible code example.

@abinjaik
Copy link

abinjaik commented Feb 29, 2020 via email

@heyman
Copy link
Member

heyman commented Feb 29, 2020

When this happens do you see any errors in the browser/javascript console? What happens if you reload the page? How is the CPU usage of the master?

For me to be able to help you I really need a way to reproduce the issue.

@abinjaik
Copy link

abinjaik commented Mar 2, 2020

When this happens do you see any errors in the browser/javascript console? What happens if you reload the page? How is the CPU usage of the master?

For me to be able to help you I really need a way to reproduce the issue.

I ran the tests again to see when it dies. CPU was in a good condition on master, this time i didnt had slaves on the same Master machine. One of the observation is, I got an exception on the ssh client of one of slaves, which is from our script I guess. But does the issue or exception thrown from load test scripts affects web dashboard? Also, I can see errors on browser consoles, first one seems like an issue with JS scripts file on dashboard. But others are just invalid, because it is trying to access images on our web apps using the IP of the Locust master :) - See screen shots below. Please let me know your thoughts

image

Soon after exception or error- the graphs , rps counter stops.
image
I refreshed the web ui and it shows like this
image

@heyman
Copy link
Member

heyman commented Mar 4, 2020

EDIT: posting in new issue instead: #1276

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants