Debugging connectivity issues | reqError === undefined

I’m trying to set up autocannon and think I’m having some connectivity issues. Running against a local instance works fine. However if I target the remote machine I want to test, all requests seem to error. I suspect issues with proxy or broken SSL chains.

I couldn’t figure out how to debug the request errors though. Is there a way to print each requests response/error message? It would help a lot to narrow down the problem.

const inst = autocannon({
  url: 'http://localhost:5010/api/v1/endpoint',
  connections: 10,
  pipelining: 20,
  duration: 10,
  method: 'POST',
  headers: {
    'Content-Type': 'application/json'
  },
  body: payload
}, (err, res) => {
    console.error(err);
    console.log(res);
});

let cnt = 0;
inst.on('reqError', e => console.log(`Request error (${cnt++}): ${e}`));

What happens is that I see a lot of those Request error logs but apparently there is no argument passed to it, so e===undefined

[GlenTiki]

Also, for other purposes:

You can access the events the internal http client emits, using the setupClient property of the options. Check here: https://github.com/mcollina/autocannon#client-events (The internal error events aren’t documented, that might be worth a PR)

You can use this to see if the errors are timeouts or connection errors, and if they’re connection errors, get access to the error object passed to the socket that created it. Here’s the snippet you need:

const inst = autocannon({
  url: 'http://localhost:5010/api/v1/endpoint',
  connections: 10,
  pipelining: 20,
  duration: 10,
  method: 'POST',
  headers: {
    'Content-Type': 'application/json'
  },
  body: payload
   setupClient: setupClientEventHandlers
}, (err, res) => {
    console.error(err);
    console.log(res);
});

let cnt = 0;
inst.on('reqError', e => console.log(`Request error (${cnt++}): ${e}`));

function setupClientEventHandlers (client) {
   client.on('connError', (error) => console.log('connection error', error))
   client.on('timeout', (error) => console.log('timeout'))
}

[anoff]

I understand that benchmarking through a proxy does not make sense. However I also don’t want to deploy to the designated test runtime to set the thing up. I was planning on running it with non-benchmark parameters. But I’ll just have to stub the autocannon behavior for development then.

Feel free to close the issue, I’ll try to PR updated docs with the hints that @thekemkid gave me earlier for future reference. Or if you have any ideas how the error should be propagated I could try to do a code-PR