Mup and bcyrpt, driving me crazy


#1

I’ve upgraded to meteor 1.3 and mup delpoyments don’t work anymore. Kidn ofd driving me crazy. Anybody figured how what’s going on - or should i just nuke mup all together and go back to manual deployments?

invalid ELF header
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Module.require (module.js:364:17)
at require (module.js:380:17)[52.27.235.189]
at bindings (/opt/app/programs/server/npm/node_modules/meteor/npm-bcrypt/node_modules/bcrypt/node_modules/bindings/bindings.js:74:15)
at Object. (/opt//app/programs/server/npm/node_modules/meteor/npm-bcrypt/node_modules/bcrypt/bcrypt.js:3:35)
at Module._compile (module.js:456:26)
at Object.Module._extensions…js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
[52.27.235.189] error: Forever detected script exited with code: 8
[52.27.235.189] error: Script restart attempt #13


#2

This may be fixed if you meteor update --release 1.3.2-rc.5.

Out of curiosity, are you using mup or mupx?


#3

thanks but that did not fix it, i am using regular old mup btw.


#4

Wow, look at this thread?

I would think having a working deployment system would be kind of an important thing to the longevity of the framework, any ideas?

https://github.com/arunoda/meteor-up/issues/938

I kind of new upgrading to 1.3 would have some ramifications. I can’t even figure out how to deployments


#5

MUP and MUPX are 3rd party deployment tools by @arunoda arunoda/meteor-up, later Kadira, not MDG, so it would be best to ask them instead.


#6

This isn’t related to 3rd party deployment tools. Its because a library that gets bundled with the Meteor build doesn’t work on Ubuntu (bcrypt).

Did you find a solution? I’m trying and failing to deploy a Meteor app now