bcrypt打破了我的流星应用程序,我该如何解决?

时间:2022-04-17 16:21:01

I wasn't sure if this should be a * or serverfault question.

我不确定这应该是*还是serverfault问题。

I installed Meteor's accounts-password module and it worked locally, but broke my app when deployed to the server. Here's the scoop:

我安装了Meteor的帐户密码模块,它在本地工作,但在部署到服务器时破坏了我的应用程序。这是独家新闻:

I'm running the latest Meteor 1.0.5 locally on OSX (OS just fully updated) Building with --architecture os.linux.x86_64 Deploying to Ubuntu 14.04.2 LTS x86_64 (just updated) Running nodejs v0.12.1 (freshly built) Serving app with nginx v1.4.0

我在OSX上本地运行最新的Meteor 1.0.5(操作系统刚刚完全更新)使用--architecture构建os.linux.x86_64部署到Ubuntu 14.04.2 LTS x86_64(刚更新)运行nodejs v0.12.1(刚建成)使用nginx v1.4.0提供应用程序

And still getting:

仍然得到:

/home/secrethistory/bundle/programs/server/node_modules/fibers/future.js:245
                                            throw(ex);
                                                  ^
Error: Module did not self-register.
    at Error (native)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
    at Module.require (module.js:365:17)
    at require (module.js:384:17)
    at bindings (/home/secrethistory/bundle/programs/server/npm/npm-bcrypt/node_modules/bcrypt/node_modules/bindings/bindings.js:74:15)
    at Object.<anonymous> (/home/secrethistory/bundle/programs/server/npm/npm-bcrypt/node_modules/bcrypt/bcrypt.js:3:35)
    at Module._compile (module.js:460:26)
    at Object.Module._extensions..js (module.js:478:10)
    at Module.load (module.js:355:32)

Any tips or places to look next?

有什么提示或下一步的地方吗?

2 个解决方案

#1


26  

The bcrypt module is platform dependant (as fibers), so you need to remove the package after decompressing the bundle in your server:

bcrypt模块依赖于平台(作为光纤),因此您需要在解压缩服务器中的软件包后删除软件包:

rm -R path/to/bcrypt

then install it again:

然后再次安装:

npm install bcrypt

#2


1  

As of Meteor 1.0.5 (and this also applies to the forthcoming 1.1), we have not yet gone through the full testing, validation, and QA process with Node 0.12. I would recommend sticking with Node 0.10 until that point. While it is likely that it will mostly work, it's possible that some core changes will be necessary, and as you've seen, binary packages built against the 0.10 ABI don't work with 0.12.

从Meteor 1.0.5开始(这也适用于即将发布的1.1),我们尚未完成使用Node 0.12的完整测试,验证和QA流程。我建议坚持使用Node 0.10直到那一点。虽然它很可能会起作用,但有可能需要进行一些核心更改,正如您所见,针对0.10 ABI构建的二进制包不能与0.12一起使用。

#1


26  

The bcrypt module is platform dependant (as fibers), so you need to remove the package after decompressing the bundle in your server:

bcrypt模块依赖于平台(作为光纤),因此您需要在解压缩服务器中的软件包后删除软件包:

rm -R path/to/bcrypt

then install it again:

然后再次安装:

npm install bcrypt

#2


1  

As of Meteor 1.0.5 (and this also applies to the forthcoming 1.1), we have not yet gone through the full testing, validation, and QA process with Node 0.12. I would recommend sticking with Node 0.10 until that point. While it is likely that it will mostly work, it's possible that some core changes will be necessary, and as you've seen, binary packages built against the 0.10 ABI don't work with 0.12.

从Meteor 1.0.5开始(这也适用于即将发布的1.1),我们尚未完成使用Node 0.12的完整测试,验证和QA流程。我建议坚持使用Node 0.10直到那一点。虽然它很可能会起作用,但有可能需要进行一些核心更改,正如您所见,针对0.10 ABI构建的二进制包不能与0.12一起使用。