Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Artillery Errors: EBUSY, what is it? I see no documentation on this.

See original GitHub issue

I can’t seem to find an answer for this, what is EBUSY? When I perform this test and see the EBUSY error come up, any further requests all come up with NaN, until it finishes. But I’m still able to POSTMAN to the same endpoint without any problems.

All virtual users finished
Summary report @ 04:47:39(+0000) 2021-02-16
  Scenarios launched:  12795
  Scenarios completed: 4076
  Requests completed:  4076
  Mean response/sec: 105.95
  Response time (msec):
    min: 315.6
    max: 714.1
    median: 349.4
    p95: 386.9
    p99: 445.2
  Scenario counts:
    0: 12795 (100%)
  Codes:
    200: 4076
  Errors:
    EBUSY: 8719

Artillery: 1.6.1 Artillery Pro: not installed (https://artillery.io/pro) Node.js: v15.1.0 OS: linux/x64

Issue Analytics

State:
Created 3 years ago
Reactions:1
Comments:10 (5 by maintainers)

Top GitHub Comments

3reactions

rsovcommented, Mar 26, 2021

Switching from Amazon Liunux to Ubuntu seemed to fix this for us

2reactions

phgn0commented, Feb 22, 2021

I’m seeing a similar issue, I suspect it’s a saturated network interface. On AWS t3a.medium with Node v15.9.0 I start getting EBUSY errors for any requests beyond 250 requests/s. On the larger c5.large I get up to 400 requests/s for the same scenario.