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

Locust web interface not starting on Windows #57

Closed
cgikoray opened this issue Feb 28, 2013 · 11 comments
Closed

Locust web interface not starting on Windows #57

cgikoray opened this issue Feb 28, 2013 · 11 comments

Comments

@cgikoray
Copy link

C:\Development\Test>locust -f main.py
[2013-02-27 19:30:11,346] INFO/locust.main: Starting web monitor on port 8089
[2013-02-27 19:30:11,348] INFO/locust.main: Starting Locust 0.6.2

...And then it never gets past this point. I am using the example locust file from the website for main.py

from locust import Locust, TaskSet, task

def index(l):
    l.client.get("/")

def stats(l):
    l.client.get("/stats/requests")

class UserTasks(TaskSet):
    # one can specify tasks like this
    tasks = [index, stats]

@task
def page404(self):
    self.client.get("/does_not_exist")

class WebsiteUser(Locust):
    host = "http://127.0.0.1:8089"
    min_wait = 2000
    max_wait = 5000
    task_set = UserTasks

I am running Windows 7. Any ideas on what I could be doing wrong? Would be happy to clarify more information.

@heyman
Copy link
Member

heyman commented Feb 28, 2013

Hi! There seems to be an indentation error in the pasted code (compared to the example file). The output from running locust looks fine, so you should probably be able to just access http://localhost:8089/

Anyway, since you closed the issue, I assume you figured it out :).

Btw, you should be fine using Locust on Windows while developing your tests. However, once you want to actually simulate a lot of users, I would strongly recommend running that on a Linux/Unix system (for example Ubuntu), since we've seen strange issues with gevent/windows when having lots of connections (I think this is Windows' fault and not gevent).

@cgikoray
Copy link
Author

Hey heyman,

Thank you for the response, I felt a bit stupid as I figured out my issue literally moments after posting it -- after staring at it for some time, no less. About the Windows problems that sucks to here :( What sort of user load are you talking about where you start to see issues? Hundreds? Thousands?

@heyman
Copy link
Member

heyman commented Mar 1, 2013

If I remember correcly (this was more than a year ago) we started seeing strange stuff when we got up to a couple of hundred requests per second. So with an average waiting time of 30 seconds, that would be a few thousand simultaneous users. I guess it also could have been something with that windows environment, so you could always try with more, but keep it in mind. Locust on linux is pretty well tested and should be quite stable though.

@cgbystrom
Copy link
Member

What sort of user load are you talking about where you start to see issues?

The boring answer is "it depends". If you do a lot of CPU intensive work, like traversing and parsing HTML DOM it can affect greatly. Also, since Locust is event-driven I would advice not go above 80% CPU usage as it will throw off all timings when it gets saturated.

@katmaiwalker
Copy link

katmaiwalker commented Jun 9, 2017

Hi there,
I have a similar question like above , the locust web interface does not appear.

Here are details for my try:
Recently i installed locust in windows and i used the http://docs.locust.io/en/latest/quickstart.html quickstart.
Currently i have locally a web application running in http://127.0.0.1:8080.
So i used the command line and i navigated to the directory with the file locustfile.py.
Subsequently i executed the command: locust --host=http://127.0.0.1:8080
image

Unfortunatelly the http://127.0.0.1:8089 link does not display the locust web interface.
Do you have any idea what is the root cause and how to resolve it.

Thank you

@thanhma
Copy link

thanhma commented Feb 22, 2018

I had the same problem.

After hopeless searching, I tried navigating http://localhost:8089 and web interface appeared like miracle.

Give it a try guys.

@frostHit
Copy link

i have the same issue on windows7.
i follow the example in the quickstart http://docs.locust.io/en/latest/quickstart.html
and type locust in the windows cmd window. it shows starting web monitor at *:8089 but failed to get it the web page on localhost:8089

@frostHit
Copy link

@konstantinosalvertis hi, did you close this issue? i am facing the same issue.

@cgoldberg
Copy link
Member

but failed to get it the web page on localhost:8089

@frostHit I don't know what that means. did you open a browser and try loading http://localhost:8089?

btw, this issue was closed over 5 years ago. Please open a new one if you actually have an issue.

@katmaiwalker
Copy link

@frostHit Hi, I couldn't find any workaround for the issue as I remember related to windows 7. Subsequently I set up a Linux server and locust worked fine.

pancaprima added a commit to pancaprima/locust that referenced this issue May 14, 2018
pancaprima added a commit to pancaprima/locust that referenced this issue May 14, 2018
* change dependencies order in setup.py (locustio#54)

* bugfix when hide edit modal while stopping and edit modal still open (locustio#56)

* rizal new feature upload test file to eb (locustio#53)

* upload test file to deployed eb

* enable user to upload test file to deployed eb

reload list on selector after file uploaded

writing files to slaves

distribute file to slaves and reload the test list

route config json to user fileio

update directories dinamycally

reload after upload, populate directory list

modify interface

add confirmation dialog

* fix non geometric elements

* fix test not reloaded when not in master slave mode, css file and alert message

* erlangga feature create new json keys (locustio#52)

* Revert "erlangga feature create new json keys (locustio#52)" (locustio#57)

This reverts commit acccdf5.
@NullP0inter
Copy link

Strange http://127.0.0.1:8089/ doesn't work but http://localhost:8089/ does.

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

8 participants