Bugsnag: Error: uv_signal_start EINVAL

[doron2402]

Bugsnag: Error: uv_signal_start EINVAL

[doron2402]

It seems like the bug occurs when listening to SIGINT or SIGTERM events

[Cawllec]

Hi @doron2402, thanks for the report, I'll have a look into this.

[Cawllec]

I've had a quick look and this error occurs in newer Node versions if you're attempting to capture SIGKILL or SIGSTOP signals and certain others in specific scenarios as described in the process docs.

Are you sure you haven't got any process.on calls for capturing SIGKILL or SIGSTOP instances?

[doron2402]

Hi @Cawllec,
It happened when I was trying to capture SIGINT or SIGTERM
btw I'm using node version 6.9.4

[Cawllec]

So I've tried out an example on 6.9.4 and it's not throwing that error with SIGTERM or SIGINT, only SIGKILL and SIGSTOP. Does the issue persist if you disable or remove Bugsnag?

[doron2402]

Once I removed Bugsnag I had no issues.
Anyway, I end up capturing only unhandledRejection and uncaughtException

[Cawllec]

Hi @doron2402, from testing we believe that trace you're seeing is Bugsnag logging the unhandled error caused by the capture attempt. While we're not entirely sure why that error would be occurring when capturing SIGTERM and SIGINT, we don't believe Bugsnag is actively causing the issue.

If you've got a code sample that reproduces the issue we can have a bit more of a look into it, and we're also going to review the logger to ensure it's clear in the future when a log occurs.

[Cawllec]

For reference, we've reproduced the behaviour using the following script and SIGKILL but it doesn't cause the issue with SIGTERM or SIGINT.

var bugsnag = require('bugsnag').register('ababababababa')
process.on('SIGKILL', () => { console.log('SIGKILL') })

[doron2402]

Cool, thanks for testing it.
I'll close the issue.
Thanks.