symbol lookup error undefined symbol: _ZN4node19GetCurrentEventLoopEPN2v87IsolateE #656

morgan92333 · 2018-09-28T17:47:25Z

I installed [email protected] version for my project. It worked for a while, but now when I start with node command, the program exit with this error:

node app.js
node: symbol lookup error: /var/www/myproject/node_modules/bcrypt/lib/binding/bcrypt_lib.node: undefined symbol: _ZN4node19GetCurrentEventLoopEPN2v87IsolateE

This is the case if I use with nodemon:

nodemon app.js
[nodemon] 1.15.0 [nodemon] to restart at any time, enter rs[nodemon] watching: *.* [nodemon] startingnode app.js /usr/local/bin/node: symbol lookup error: /var/www/myproject/node_modules/bcrypt/lib/binding/bcrypt_lib.node: undefined symbol: _ZN4node19GetCurrentEventLoopEPN2v87IsolateE [nodemon] failed to start process, "node" exec not found [nodemon] Error

If I use

nodejs app.js

Its works

My node version: v8.4.0
My nodejs version v8.11.3

The text was updated successfully, but these errors were encountered:

chandru89new · 2018-09-30T12:31:29Z

+1 on this.

To replicate this:
Node version: 8.9.3 (LTS, stable)
Bcrypt version: 3.0.1

Run any file on node with a bcrypt function (like bcrypt.hash())

Getting this:
node: symbol lookup error: //node_modules/bcrypt/lib/binding/bcrypt_lib.node: undefined symbol: _ZN4node19GetCurrentEventLoopEPN2v87IsolateE

I was able to fix this by downgrading bcrypt to 2.0.0 (but that has a vulnerability so I cant use that on production).

Edit: Running Ubuntu 16.04 (Thanks @agathver)

recrsn · 2018-09-30T12:43:07Z

Please mention the OS

jvt · 2018-09-30T19:45:59Z

I'm also seeing this issue on macOS 10.14.

My terminal is outputting:

[1] dyld: lazy symbol binding failed: Symbol not found: __ZN4node19GetCurrentEventLoopEPN2v87IsolateE
[1]   Referenced from: /Users/jt/Documents/Projects/Brainy-Kidz/node_modules/bcrypt/lib/binding/bcrypt_lib.node
[1]   Expected in: flat namespace
[1]
[1] dyld: Symbol not found: __ZN4node19GetCurrentEventLoopEPN2v87IsolateE
[1]   Referenced from: /Users/jt/Documents/Projects/Brainy-Kidz/node_modules/bcrypt/lib/binding/bcrypt_lib.node
[1]   Expected in: flat namespace

matthieu994 · 2018-10-01T04:07:26Z

Same error with Heroku, but not on local.

2018-10-01T03:59:18.027347+00:00 app[web.1]: node: symbol lookup error: /app/node_modules/bcrypt/lib/binding/bcrypt_lib.node: undefined symbol: _ZN4node19GetCurrentEventLoopEPN2v87IsolateE
2018-10-01T03:59:18.046547+00:00 app[web.1]: npm ERR! file sh
2018-10-01T03:59:18.046983+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2018-10-01T03:59:18.047195+00:00 app[web.1]: npm ERR! errno ENOENT
2018-10-01T03:59:18.047395+00:00 app[web.1]: npm ERR! syscall spawn
2018-10-01T03:59:18.048720+00:00 app[web.1]: npm ERR! [email protected] start: `node server`
2018-10-01T03:59:18.048890+00:00 app[web.1]: npm ERR! spawn ENOENT
2018-10-01T03:59:18.049135+00:00 app[web.1]: npm ERR!

kirkins · 2018-10-02T13:12:53Z

I'm also seeing this on Ubuntu 18.04

kirkins · 2018-10-02T13:15:21Z

Rolling back to 3.0.0 from 3.0.1 fixed it for me.

yiliang114 · 2018-10-05T13:48:55Z

@kirkins thx npm i -D [email protected] is in effect

rvpanoz · 2018-10-10T12:07:48Z

same issue - rolling back to 3.0.0 as @kirkins said fixes the issue.

recrsn · 2018-10-10T13:59:22Z

It's unfortunate that the NodeJS folks broke API in between releases. There is nothing much we can do in this regard.
You can force a recompile using npm rebuild bcrypt --build-from-source

zelongc · 2018-10-11T05:02:59Z

Upgrading my Node engine from 8.9.0 to 8.12.0 solved the problem.

apporx > 8 && < 8.12 has issues with bcrypt see: kelektiv/node.bcrypt.js#656

…520)

thom-nic · 2018-11-01T18:42:01Z

I'm concerned this issue is closed while the problem persists. It may be "NodeJS's fault" however the end result is an unusable build and a breaking change between 3.0.0 and 3.0.1 for certain users.

So, I understand it is w/r/t prebuilt bcrypt, which is built against a specific N-API and something in the API changed (somewhere between 8.9 and 8.12) without node revving the API version (v57.)

I can reproduce with bcrypt 3.0.2 and nodejs 8.9.4, on both MacOS and Linux.

I actually wonder if rolling back to v3.0.0 works for folks because there is no prebuilt package for v3.0.0-node-v57-darwin-x64-unknown (there are prebuilt darwin packages for bcrypt 3.0.1 and 3.0.2.) Or if v3.0.0 was just coincidentally built against an earlier version of node, before the breaking API change.

Adding npm rebuild bcrypt --build-from-source is problematic for folks who then need to update CI scripts to workaround this.

I could suggest, un-publishing the node-v57 prebuilt binaries - it would force the "build-from-source" fallback to always occur when no prebuilt binary is found.

See - kelektiv/node.bcrypt.js#656 - jshimko/meteor-launchpad#126

…v/node.bcrypt.js#656 (comment)

bpehlert · 2019-03-29T17:46:56Z

I was having the same issue with my production build through Heroku. Updating my node and npm engines on my package.json file to be the latest versions fixed the problem. Running bcrypt 3.0.4.

fortunee · 2019-04-06T18:33:26Z

I was having the same issue with my production build through Heroku. Updating my node and npm engines on my package.json file to be the latest versions fixed the problem. Running bcrypt 3.0.4.

What versions did you bump them up to? @bpehlert

bpehlert · 2019-04-10T15:36:22Z

I just made sure that I had the newest versions of Node and NPM by reinstalling them through the terminal. Here are the versions I have in my package.json file: "engines": { "node": "10.15.3", "npm": "6.4.1" },

…

On Sat, Apr 6, 2019 at 12:33 PM Fortune Ekeruo ***@***.***> wrote: I was having the same issue with my production build through Heroku. Updating my node and npm engines on my package.json file to be the latest versions fixed the problem. Running bcrypt 3.0.4. What versions did you bump them up to? @bpehlert <https://github.com/bpehlert> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#656 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/Aj25HlUCbQ79h4YUaItvM_FwPc3nISmnks5veOh4gaJpZM4W_GRM> .

aslam7 · 2019-08-14T14:27:33Z

You can use bcryptjs

KyrosDigital · 2020-01-02T16:08:35Z

I think the docker container abernix/meteord:node-8.4.0-base may be using a version of node that causes this issue with bcrypt upon deployment.

I think when we are able to use a version of node that is 12.14.0 or above, we can then start using bcrypt 3.0.7, without the need to downgrade the package version to 3.0.0 when you want to deploy.

This would be ideal.

ilan-schemoul · 2020-06-02T11:46:12Z

I'm concerned this issue is closed while the problem persists. It may be "NodeJS's fault" however the end result is an unusable build and a breaking change between 3.0.0 and 3.0.1 for certain users.

So, I understand it is w/r/t prebuilt bcrypt, which is built against a specific N-API and something in the API changed (somewhere between 8.9 and 8.12) without node revving the API version (v57.)

I can reproduce with bcrypt 3.0.2 and nodejs 8.9.4, on both MacOS and Linux.

I actually wonder if rolling back to v3.0.0 works for folks because there is no prebuilt package for v3.0.0-node-v57-darwin-x64-unknown (there are prebuilt darwin packages for bcrypt 3.0.1 and 3.0.2.) Or if v3.0.0 was just coincidentally built against an earlier version of node, before the breaking API change.

Adding npm rebuild bcrypt --build-from-source is problematic for folks who then need to update CI scripts to workaround this.

I could suggest, un-publishing the node-v57 prebuilt binaries - it would force the "build-from-source" fallback to always occur when no prebuilt binary is found.

My production app has crashed because of this. This is especially sneaky that until one user signed in everything worked so I did not see that the app had a bug despite testing after deployment and during my sleep the entire app crashed causing very big troubles to my business.
So if the above suggestion is easy to apply on bcrypt's maintainers'end it would save a lot of unexpected crashing and at very very least update the table in the Readme.md to warn users that they should use bcrypt 3.0.0 with 8.9

Imran-cse · 2020-07-30T10:59:38Z

The issue still persists with node v10.16.3 and bcrypt v3.0.8

kodie · 2021-05-07T17:42:57Z

I think the docker container abernix/meteord:node-8.4.0-base may be using a version of node that causes this issue with bcrypt upon deployment.

I think when we are able to use a version of node that is 12.14.0 or above, we can then start using bcrypt 3.0.7, without the need to downgrade the package version to 3.0.0 when you want to deploy.

This would be ideal.

Upgrading my Node engine from 8.9.0 to 8.12.0 solved the problem.

We were using abernix/meteord:node-8.9.0-base in our Meteor.js project, changing that to abernix/meteord:node-8.12.0-base fixed our issue.

wfilleman mentioned this issue Oct 8, 2018

Parse LiveQuery Excessive CPU parse-community/parse-server#5106

Closed

recrsn closed this as completed Oct 18, 2018

smolijar added a commit to AckeeCZ/desmond that referenced this issue Oct 19, 2018

Fix node version in package.json engine

4315ff6

apporx > 8 && < 8.12 has issues with bcrypt see: kelektiv/node.bcrypt.js#656

noahsw added a commit to winsleague/winsleague that referenced this issue Oct 29, 2018

downgrading bcrypt until this is fixed - kelektiv/node.bcrypt.js#656

6ae25b8

noahsw added a commit to winsleague/winsleague that referenced this issue Oct 29, 2018

downgrading bcrypt until this is fixed - kelektiv/node.bcrypt.js#656 (#…

cf6547e

…520)

stefan-guggisberg mentioned this issue Oct 29, 2018

dyld: lazy symbol binding failed: Symbol not found: Expected in: flat namespace nodegit/nodegit#1575

Open

gustawdaniel mentioned this issue Nov 19, 2018

Update of default node version jshimko/meteor-launchpad#126

Closed

make-github-pseudonymous-again added a commit to infoderm/patients that referenced this issue Nov 25, 2018

🐛 fix(deps): downgrade bcrypt

c574301

See - kelektiv/node.bcrypt.js#656 - jshimko/meteor-launchpad#126

keifuji mentioned this issue Nov 28, 2018

Verifying Deployment: FAILED zodern/meteor-up#1037

Closed

tomasdev mentioned this issue Dec 29, 2018

Wrong binding on OS X? ronomon/utimes#3

Closed

gentoo-repo-qa-bot pushed a commit to gentoo-mirror/awesome that referenced this issue Dec 30, 2018

Bump node version to 8.12.0 to fix symbol error in crypt, see kelekti…

805d794

…v/node.bcrypt.js#656 (comment)

tctovsli mentioned this issue Jan 17, 2019

Rocketchat crashes after login attempt RocketChat/Rocket.Chat#13147

Closed

himanshukumar660 mentioned this issue Jan 23, 2019

Added hashing of passwords for its storage in the database intermine/intermine-registry#113

Merged

karlitos mentioned this issue Aug 27, 2019

Problem with bcrypt when deploying from different operating system bordalix/yamup#5

Closed

cabeese mentioned this issue Dec 18, 2019

Hotfix: bcrypt symbol lookup error cabeese/greatpuzzlehunt#11

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

symbol lookup error undefined symbol: _ZN4node19GetCurrentEventLoopEPN2v87IsolateE #656

symbol lookup error undefined symbol: _ZN4node19GetCurrentEventLoopEPN2v87IsolateE #656

morgan92333 commented Sep 28, 2018 •

edited

Loading

chandru89new commented Sep 30, 2018 •

edited

Loading

recrsn commented Sep 30, 2018

jvt commented Sep 30, 2018 •

edited

Loading

matthieu994 commented Oct 1, 2018 •

edited

Loading

kirkins commented Oct 2, 2018

kirkins commented Oct 2, 2018

yiliang114 commented Oct 5, 2018

rvpanoz commented Oct 10, 2018

recrsn commented Oct 10, 2018

zelongc commented Oct 11, 2018 •

edited

Loading

thom-nic commented Nov 1, 2018

bpehlert commented Mar 29, 2019

fortunee commented Apr 6, 2019

bpehlert commented Apr 10, 2019 via email

aslam7 commented Aug 14, 2019 •

edited

Loading

KyrosDigital commented Jan 2, 2020

ilan-schemoul commented Jun 2, 2020

Imran-cse commented Jul 30, 2020 •

edited

Loading

kodie commented May 7, 2021

symbol lookup error undefined symbol: _ZN4node19GetCurrentEventLoopEPN2v87IsolateE #656

symbol lookup error undefined symbol: _ZN4node19GetCurrentEventLoopEPN2v87IsolateE #656

Comments

morgan92333 commented Sep 28, 2018 • edited Loading

chandru89new commented Sep 30, 2018 • edited Loading

recrsn commented Sep 30, 2018

jvt commented Sep 30, 2018 • edited Loading

matthieu994 commented Oct 1, 2018 • edited Loading

kirkins commented Oct 2, 2018

kirkins commented Oct 2, 2018

yiliang114 commented Oct 5, 2018

rvpanoz commented Oct 10, 2018

recrsn commented Oct 10, 2018

zelongc commented Oct 11, 2018 • edited Loading

thom-nic commented Nov 1, 2018

bpehlert commented Mar 29, 2019

fortunee commented Apr 6, 2019

bpehlert commented Apr 10, 2019 via email

aslam7 commented Aug 14, 2019 • edited Loading

KyrosDigital commented Jan 2, 2020

ilan-schemoul commented Jun 2, 2020

Imran-cse commented Jul 30, 2020 • edited Loading

kodie commented May 7, 2021

morgan92333 commented Sep 28, 2018 •

edited

Loading

chandru89new commented Sep 30, 2018 •

edited

Loading

jvt commented Sep 30, 2018 •

edited

Loading

matthieu994 commented Oct 1, 2018 •

edited

Loading

zelongc commented Oct 11, 2018 •

edited

Loading

aslam7 commented Aug 14, 2019 •

edited

Loading

Imran-cse commented Jul 30, 2020 •

edited

Loading