Websocket test issues about locust-plugins

[cyberw]

Use the example as a starting point https://github.com/SvenskaSpel/locust-plugins/blob/master/examples/socketio_ex.py

you are not supposed to copy the base class :)

[j2l]

Thank you @cyberw , I finally understood the way it works 😅
Ok, I pip installed the plugins.
Since I want to test my websocket, in miniconda/.../locust_plugins/users.py, I changed:
self.ws = websocket.create_connection(f"wss://{ws_host}/socket.io/?EIO=3&transport=websocket")
to
self.ws = websocket.create_connection(f"wss://{ws_host}")

I copied https://github.com/SvenskaSpel/locust-plugins/blob/master/examples/socketio_ex.py to my locustfile.py
and run it
and visited http://0.0.0.0:8089/ to start the load test
... but nothing happen. No user is spawned.

Only warning is about the file size (but it was also present while testing simple GET and it was working):

[2021-03-02 08:54:34,641] pop-os/WARNING/locust.main: System open file limit '1024' is below minimum setting '10000'. It's not high enough for load testing, and the OS didn't allow locust to increase it by itself. See https://github.com/locustio/locust/wiki/Installation#increasing-maximum-number-of-open-files-limit for more info.
[2021-03-02 08:54:34,641] pop-os/INFO/locust.main: Starting web interface at http://0.0.0.0:8089 (accepting connections from all network interfaces)
[2021-03-02 08:54:34,648] pop-os/INFO/locust.main: Starting Locust 1.4.3
[2021-03-02 08:54:39,191] pop-os/INFO/locust.runners: Spawning 50 users at the rate 10 users/s (0 users already running)...

my Pop!_OS is Ubuntu 20.04
locust 1.4.3
WSS url to test is sub.REDACTED.com
GET https://sub.REDACTED.com

I guess I missed something :)
Any idea ?

[cyberw]

My first thought is that locust is unable to connect to your host. Can you run it in the debugger or print something just before and just after create_connection?

[j2l]

print(ws_host)
        self.ws = websocket.create_connection(f"wss://{ws_host}")
        print(ws)

results in printing the host once after running and hanging there:

Starting Locust 1.4.3
[2021-03-02 11:18:45,902] pop-os/INFO/locust.runners: Spawning 50 users at the rate 10 users/s (0 users already running)...
REDACTED.com

[cyberw]

So websocket is unable to connect to your host. Most likely, this has nothing to do with locust or SocketIOUser.

Check your network, any proxy settings you might need etc.

[j2l]

I use the same computer and network, actually the REDACTED.com service is running from my LAN, no proxy.
I can see websocket connections from regular clients in real time from my server.

Hmmm, as I want to understand, I re-ran the quickstart example:

import time
from locust import HttpUser, task, between

class QuickstartUser(HttpUser):
    wait_time = between(1, 2.5)

    @task
    def hello_world(self):
        self.client.get("")

from the same install (locust and server).
It totally works:

I really don't understand what is blocking the websocket locust plugin.

[j2l]

Could I send you a private message withe the real domain for you to test?
I added REDACTED since it's a proptype server running from my home and I have to test it today for tomorrow presentation.

[j2l]

FIXED!
I just added the same ws path (already present in the locustfile.py, so I wrongly assumed it was added to the host passed) and now it reaches the server:

I wonder why the path is present is the locustfile :)
Never mind, it's working!
Maybe adding a ping before to make sure the domain is responding might help the error code that should spawn 😄
I'm not into locust enough to know how to do it.

BTW, there are many other questions:

• Looking at the webmin in real-time, I noticed a different behavior than when I use regular clients, how to mimic websocket outgoing?
• How to add websocket and locust-plugins to work with the locust docker container?

[cyberw]

I just added the same ws path (already present in the locustfile.py, so I wrongly assumed it was added to the host passed)

Great! I might change it so that it defaults to use the "main" host specified in locust parameters or on host attribute for WS as well (in my use case I also wanted to run http requests against a different domain, so it made sense to keep them separate)

Looking at the webmin in real-time, I noticed a different behavior than when I use regular clients, how to mimic websocket outgoing?
How to add websocket and locust-plugins to work with the locust docker container?

These are things you'll just have to figure out yourself, sorry :)