Problem installing bcrypt-ruby when following the instruction on version 6-2-stable

[Hoang Pham]

Hi all,

I follow the instruction on the site to install GitLab on my Ubuntu instance on Amazon EC2. Everything is fine except the one below, it kept saying I have problem with installing bcrypt-ruby (3.1.1). I have tried to find the solution on the internet but it did not help. 

I would like to ask if someone experience the same issue and what can I do to fix it?

Thank you, 

/home/git/gitlab$ sudo -u git -H bundle install --deployment --without development test postgres aws

Fetching source index from https://rubygems.org/

Installing bcrypt-ruby (3.1.1) 

Gem::Installer::ExtensionBuildError: ERROR: Failed to build gem native extension.

    /usr/local/bin/ruby extconf.rb 

Gem files will remain installed in /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/bcrypt-ruby-3.1.1 for inspection.

Results logged to /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/bcrypt-ruby-3.1.1/ext/mri/gem_make.out

An error occurred while installing bcrypt-ruby (3.1.1), and Bundler cannot

continue.

Make sure that `gem install bcrypt-ruby -v '3.1.1'` succeeds before bundling.

[Christian Iversen]

On Tuesday, November 12, 2013 5:14:44 PM UTC+1, Hoang Pham wrote:

Hi all,

I follow the instruction on the site to install GitLab on my Ubuntu instance on Amazon EC2. Everything is fine except the one below, it kept saying I have problem with installing bcrypt-ruby (3.1.1). I have tried to find the solution on the internet but it did not help. 

I would like to ask if someone experience the same issue and what can I do to fix it?

I have the exact same problem, and I have not found a solution yet.

It seems the extension fails to build when run under bundle, yet it works perfectly fine when I try it manually.

It's perplexing. Let me know if you (or anyone else) found a solution?

[Aaron Stone]

Results logged to /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/bcrypt-ruby-3.1.1/ext/mri/gem_make.out

Please share the end of this file, where the actual error is shown.

--
You received this message because you are subscribed to the Google Groups "GitLab" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gitlabhq+u...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Steven Barker]

I have the same issue myself,

$  cat  /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/bcrypt-ruby-3.1.1/ext/mri/gem_make.out

/usr/local/bin/ruby extconf.rb

[Christian Iversen]

My file contained the same line.

I figured out that for me, it was because the server was running out of memory when running bundle. So the sub-process would get killed, it would notice that it had failed, and there would be absolutely no clues in the log, because the sub-process never actually got started properly.

So, adding some swap and/or upping the ram should solve it. At least it did for me.

[Aaron Stone]

Hi. Post the contents of the file that contains the error, so that the error can be seen and others can give useful help on the list based on a specific error message that relates to a specific problem. This thread is completely useless since nobody is posting the actual specific error they encountered.

[Christian Iversen]

I don't think you understand.

The *only* thing contained in the file is 1 line:

$ cat /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/bcrypt-ruby-3.1.1/ext/mri/gem_make.out
/usr/local/bin/ruby extconf.rb

There is nothing else there. That's why this error has been so perplexing.

But as I said, for me it was an out-of-memory error, which was somewhat subtle, given that the programs don't expect their sub-processes to suddenly die.

[Aaron Stone]

I stand corrected, thank you for explaining.

--

[Christian Iversen]

No problem. Sorry if I sounded annoyed, it's late. :)

[Steven Barker]

Thanks, I would like to report back that for myself it was also an out of memory error. boosted my swap and was all good

[Joe Kelley]

I swapped in 5gb of memory and it's still failing on me, giving the exact same errors you got. When I compile it alone ($ sudo gem install bcrypt-ruby -v '3.1.2') it runs fine. However, when I run it with the 'bundle install', it fails. Any ideas?

[M. Moore]

update the Gemfile.lock file to use bcrypt-ruby 3.1.2 instead of 3.1.1, that worked for me on CentOS 6. now I'm running into a issue installing charlock_holmes, so we'll see.

[Mike Arbelaez]

I get the same error with bcrypt-ruby 3.1.1 and the Gemfile.lock file edit to 3.1.2 did not work. When I comment out bcrypt I then get the same error with Charlock_holmes. I do the comment process to two more eventmachine, escape_utils, and posix-spawn. I've stopped trying to install after all these things don't work.

[M. Moore]

actually, I stand corrected: What truly resolved both the bcrypt error and the charlock error was upgrading from 1GB to 2GB on my vps.

--
You received this message because you are subscribed to a topic in the Google Groups "GitLab" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/gitlabhq/HTjpYSfZPLQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to gitlabhq+u...@googlegroups.com.