Invalid ELF header after upgrade to Meteor 2.4

[dnish]

After upgrading to Meteor 2.4, I'm getting the following error on my Ubuntu server:

/current/bundle/programs/server/npm/node_modules/meteor/accounts-password/node_modules/bcrypt/lib/binding/napi-v3/bcrypt_lib.node: invalid ELF header

The error didn't happen on the previous version. I'm building the app on a MacOS system, so I know that I have to rebuild the packages on the Ubuntu server. Until Meteor 2.3, this command worked:

cd /current/bundle/programs/server && npm install --production && cd npm && npm rebuild --build-from-source

But for Meteor 2.4, this seems not to work anymore.

// Edit:

For the moment, this will fix the issue:

cd /current/bundle/programs/server/npm/node_modules/meteor/accounts-password
npm rebuild --build-from-source

[StorytellerCZ]

Curious, why are you going to the bundle and running npm install there? Is meteor build not good enough?

[zodern]

@StorytellerCZ that step is required to install some npm dependencies used on the server, and to rebuild native dependencies (galaxy, meteor up, and most other Meteor deployment tools do this step for you). Though if it is working correctly you should only need to run npm install since it is supposed to rebuild all native dependencies for you without running any additional commands.

@dnish what is the content of bundle/programs/server/npm-rebuilds.json? Are you running npm with a root user?

[dnish]

@zodern The npm-rebuilds.json shows the following:

[
  "npm/node_modules/meteor/ecmascript-runtime-client",
  "npm/node_modules/meteor/ecmascript-runtime-server",
  "npm/node_modules/meteor/babel-compiler",
  "npm/node_modules/meteor/url",
  "npm/node_modules/meteor/accounts-password",
  "npm"
]

Yes, on this server, it is running with the root user.

@StorytellerCZ We are using our own deployment bash script, could be possible that the npm install --production step isn't necessary anymore. The rebuild is needed because we are deploying from MacOS to Ubuntu.

[zodern]

@dnish does it work if you replace all of the npm commands with cd /current/bundle/programs/server && npm install --unsafe-perm?

[dnish]

@zodern Right, for this project, we are deploying with the root user. The --unsafe-perm fixed the issue.

[Simon900225]

I have the exact same problem. I'm also building the app on Mac OSX and deploying it to a linux docker container.

I'm guessing that maybe the build process isn't taking the --architecture os.linux.x86_64 build flag into account when building the meteor packages?

The --unsafe-perm fixed the issue for me too.

[zodern]

I'm not sure how much the --architecture flag still affects. Since Meteor 1.4.1, most native dependencies have to be rebuilt while deploying. What changed recently is with #11467 every Meteor app now has a native dependency so if the deployment process doesn't rebuild them properly it is now very noticeable.