ECONNREFUSED on startup segfaults on 3.3.0

[yoshuawuyts]

originally posted here #2561 (comment)

Found an issue where 0.12.x gives an ECONNREFUSED error, 3.2.0 segfaults.

img

txt

~/src/dlivr/api master
❯ npm start

> api@1.0.0 start /Users/yw/src/dlivr/api
> node .

zsh: segmentation fault  npm start

~/src/dlivr/api master
❯ node -v
v3.2.0

~/src/dlivr/api master
❯ nvm use 0.12
^[kkNow using node v0.12.7 (npm v2.11.3)

~/src/dlivr/api master
❯ npm start

> api@1.0.0 start /Users/yw/src/dlivr/api
> node .

{"name":"log","type":"static","message":"debug"}
{"name":"port","message":1337,"type":"static"}
{"name":"env","message":"development","type":"static"}
Knex:Error Pool2 - Error: connect ECONNREFUSED
Knex:Error Pool2 - Error: connect ECONNREFUSED
^C

~/src/dlivr/api master  2m 20s
❯ nvm use 3
Now using io.js v3.2.0 (npm v2.13.3)

[yoshuawuyts]

In order to start the app properly pgsql must be running. The issue here is that node@3 segfaults instead of giving a meaningful error.

[yoshuawuyts]

Hm, apparently it also fails even if pgsql is running. Might be due to binaries compiled on 0.12 not working on 3.3.

[mscdex]

Yes, you'll need to re-compile any addons if you switch between any of node 0.10, node 0.12, or any major io.js version (1.x, 2.x, 3.x).

[yoshuawuyts]

@mscdex yeah, I figured. Think this issue is best closed (can't think of an easy fix), but I do think that it'd be nice to think of a better way to signal to a user why the code segfaulted.

Perhaps a stack trace of some sorts? Though I'm not sure that's possible, I assume it'd be implemented already if it was.

Maybe a way to check if the deps that are being run were compiled with a certain node version? I'm not sure.