Error installing Grails with GVM - Curl issue - grails

I am having trouble installing Grails via GVM. I installed GVM via the instructions on GVM's website, and it appears it was installed correctly - restarting the terminal and running gvm help produces a list of possible commands. However, when I go to install Grails (or Groovy), I get the following output in the terminal:
$ gvm install grails
Downloading: grails 2.3.2
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (1) Protocol [http not supported or disabled in libcurl
End-of-central-directory signature not found. Either this file is not
a zipfile, or it constitutes one disk of a multi-part archive. In the
latter case the central directory and zipfile comment will be found on
the last disk(s) of this archive.
unzip: cannot find zipfile directory in one of /Users/neilpoulin/.gvm/archives/grails- 2.3.2.zip or
/Users/neilpoulin/.gvm/archives/grails-2.3.2.zip.zip, and cannot find /Users/neilpoulin/.gvm/archives/grails-2.3.2.zip.ZIP, period.
Stop! The archive was corrupt and has been removed! Please try installing again.
I looked to make sure zip, unzip and curl were found:
$ which zip
/usr/bin/zip
$ which unzip
/usr/bin/unzip
$ which curl
/usr/bin/curl
Prior to this, the only thing I have done with Grails/Groovy is to execute the example project include on the Grails website - http://grails.org/learn > step 2.
What am I missing here? is there some configuration of libcurl I need to change? Any help is much appreciated!

On investigation, it seems to be down to inconsistent versions (and behaviour) of MongoDB between our dev and prod environments. This was resulting in our prod server returning an array of urls on the download request (ie [theurl]). This was working perfectly on our dev environment, but started serving the array when the release was promoted to prod. Hope this is making sense!

I was having this problem persist— for me, it turned out that there were corrupt candidates caches by gvm during a previously failed install.
gvm flush candidates
set things back to rights, here.

Related

capistrano 2 : `tar' could not be found in the path on the local host

I am using Capistrano version 2 and trying to deploy code on server.
but when i enter cap deploy:check command i am getting below error.
* executing "which tar"
servers: ["53.79.454.474"]
[53.79.454.474] executing command
command finished in 1088ms
The following dependencies failed. Please check them and try again:
--> `tar' could not be found in the path on the local host
I also try to install tar on my remote ubuntu machine, but still getting the same error.
sudo apt-get install tar
Reading package lists... Done
Building dependency tree
Reading state information... Done
tar is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
I don't know why i am getting this error. please help
Thanks,
This error appears because the machine that holds your repo does not have tar installed (windows). You should have no problems when moving your :repo_url to your production server or any other server with a linux distribution.
** Edit
Before moving the repo, you could try to set the :copy_compression as :zip in your production.rb
if that fails (it might), and you absolutely want/need to stick to microsoft, there will be no way around installing cygwin with tar enabled on the machine your repo lies on and adding cygwin to your PATH variable.
Check this google discussion for more information.

How to get past MongoDB/PCRE “symbol lookup error” when upgrading from MongoDB 1.8 to 2.4

I’m doing some Ruby development on servers that I have inherited (aka: I never originally set up.) that haven’t been maintained in a while and noticed that the installed MongoDB version was 1.8 when a 2.4 series upgrade was available. Since the box is running a RedHat/CentOS variant that uses yum to install RPMs, I went ahead and do what I usually do to upgrade. First, stop the running MongoDB instance like this:
sudo service mongod stop
And then upgrade the packages from the repo.
sudo yum install mongodb mongodb-server libmongodb
All went well including dependencies being installed as well. But when I went to restart MongoDB bia this command:
sudo service mongod start
Nothing appeared to happen. Connections were dead. Checking the MongoDB log showed the following one sad error line:
/usr/bin/mongod: symbol lookup error: /usr/bin/mongod: undefined symbol: _ZN7pcrecpp2RE4InitEPKcPKNS_10RE_OptionsE
What the heck is that about? I saw this question and answer thread that recommending rebuilding from the RPM source as well as other posts online that advise some variant of the same: Download source code to recompile or download the RPM directly from the MongoDB site. But all of those solutions seem to radical for what should be a simple package installer update? What could be happening?
I figured it out. Somewhat accidentally, but fairly certain this is the solution. The short answer? If you get that /usr/bin/mongod: symbol lookup error: /usr/bin/mongod: undefined symbol: _ZN7pcrecpp2RE4InitEPKcPKNS_10RE_OptionsE then you should install pcre and pcre-devel from the repository like this:
sudo yum install pcre pcre-devel
Details on how I discovered this are basically, I was resigning myself to recompiling from scratch as outlined in this answer. That is something I do not want to do unless there is a very good reason. But as the answerer states, before recompiling one should install the following compiler items and related libraries:
sudo yum install rpm-build redhat-rpm-config gcc gcc-c++ make yum install openssl-devel snappy-devel v8-devel boost-devel python-devel python-nose scons pcre-devel readline-devel libpcap-devel gperftools-devel
Okay, so I did that to lay down the groundwork for a source code rebuild. But also noticed in the install that pcre was being installed as it was apparently missing and required dependency for pcre-devel; this is key. As I was getting ready to recompile I just decided to attempt to start mongod again like this:
sudo service mongod start
And checked. Lo and behold, the MongoDB install was running again! But why? This answer here holds the clue:
The error was caused by libpcre changing the signature of
RE::Init() to only take a std::string, rather than a char*. This
is fixed if you get a newer version of libpcrecpp, which adds the
old interface for backwards compat.
That answer also recommended recompiling from source, but now that made little sense since it was clear my MongoDB install was up and running again. So I ran lsof on the development box and saw this:
sudo lsof | grep pcre
nginx 892 deploy mem REG 253,2 97140006 (deleted)/lib64/libpcre.so.0.0.1 (stat: No such file or directory)
nginx 893 deploy mem REG 253,2 97140006 (deleted)/lib64/libpcre.so.0.0.1 (stat: No such file or directory)
nginx 1369 root mem REG 253,2 97140006 (deleted)/lib64/libpcre.so.0.0.1 (stat: No such file or directory)
mongod 26841 mongodb mem REG 253,2 1052673 /usr/lib64/libpcrecpp.so.0.0.0 (path dev=0,53)
mongod 26841 mongodb mem REG 253,2 97126735 /lib64/libpcre.so.0.0.1 (path dev=0,53)
grep 28590 deploy mem REG 253,2 97126735 /lib64/libpcre.so.0.0.1 (path dev=0,53)
Note how the mongod user is loading /lib64/libpcre.so.0.0.1. That has to be it, right?
I confirmed this by jumping onto the partner/twin production box of this setup—where I did not upgrade MongoDB on yet—and ran the same lsof command and this was the result:
sudo lsof | grep pcre
nginx 922 root mem REG 253,2 81795343 (deleted)/lib64/libpcre.so.0.0.1 (stat: No such file or directory)
nginx 923 deploy mem REG 253,2 81795343 (deleted)/lib64/libpcre.so.0.0.1 (stat: No such file or directory)
nginx 924 deploy mem REG 253,2 81795343 (deleted)/lib64/libpcre.so.0.0.1 (stat: No such file or directory)
grep 8067 deploy mem REG 253,2 81791051 /lib64/libpcre.so.0.0.1 (path dev=0,61)
Note how in comparison there is 100% no instance of mongod loading /lib64/libpcre.so.0.0.1. So the solution to this issue was not to recompile from source—and thus dealing with the headaches of a no-RPM install—but rather just to install pcre from the repository.

Codeship deployment error installing ruby?

Not sure what it means or why it's happening, any advice appreciated massively.
arning! PATH is not properly set up, '/home/rof/.rvm/gems/ruby-1.9.3-p327/bin' is not at first place,
usually this is caused by shell initialization files - check them for 'PATH=...' entries,
it might also help to re-add RVM to your dotfiles: 'rvm get stable --auto-dotfiles',
to fix temporarily in this shell session run: 'rvm use ruby-1.9.3-p327'.
Unknown ruby string (do not know how to handle): ruby-1.9.3p545.
ruby-1.9.3p545 is not installed - installing.
Unknown ruby string (do not know how to handle): ruby-1.9.3p545.
Searching for binary rubies, this might take some time.
No binary rubies available for: ubuntu/12.10/x86_64/ruby-1.9.3p545.
Continuing with compilation. Please read 'rvm help mount' to get more information on binary rubies.
Checking requirements for ubuntu.
Requirements installation successful.
Unknown ruby string (do not know how to handle): ruby-1.9.3p545.
Installing Ruby from source to: /home/rof/.rvm/rubies/ruby-1.9.3p545, this may take a while depending on your cpu(s)...
Unknown ruby string (do not know how to handle): ruby-1.9.3p545.
ruby-1.9.3p545 - #downloading ruby-1.9.3p545, this may take a while depending on your connection...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (22) The requested URL returned error: 404 Not Found
The requested url does not exist(22): 'http://cache.ruby-lang.org/pub/ruby/./ruby-1.9.3p545.tar.bz2'
Checking fallback: http://ftp.ruby-lang.org/pub/ruby/./ruby-1.9.3p545.tar.bz2
Checking fallback: http://www.mirrorservice.org/sites/ftp.ruby-lang.org/pub/ruby/./ruby-1.9.3p545.tar.bz2
No fallback URL could be found, try increasing timeout with:
echo "export rvm_max_time_flag=20" >> ~/.rvmrc
There has been an error fetching the ruby interpreter. Halting the installation.
Gemset '' does not exist, 'rvm ruby-1.9.3p545 do rvm gemset create ' first, or append '--create'.
Seems like nothing it working to get my app launched on heroku - I was launching it through github push.
The app can be found # www.github.com/cjshort/devonite
Thanks.
I'm one of the founders of Codeship.
It looks like you're using a Ruby version that is currently not supported on Codeship. Could you send us an in-app support request with more info so we can take a look at your build directly.

Installing RVM using Cygwin on windows - Curl throws status 23

$ \curl -sSL https://get.rvm.io | bash -s stable --ruby
Downloading https://github.com/wayneeseguin/rvm/archive/stable.tar.gz
curl: (23) Failed writing body (0 != 861)
Could not download 'https://github.com/wayneeseguin/rvm/archive/stable.tar.gz'.
curl returned status '23'.
Downloading https://bitbucket.org/mpapis/rvm/get/stable.tar.gz
curl: (23) Failed writing body (0 != 15973)
Could not download 'https://bitbucket.org/mpapis/rvm/get/stable.tar.gz'.
curl returned status '23'.
Been three days since I am struggling with this. Setup proxy, installed wget. I am trying to install RVM for windows 8.
For one of my projects I am not able to execute 'ruby pushGCM.rb'. It throws SSL Certificate error for which I need RVM desperately
Any help is appreciated
I've been fighting this issue for the past few days as well, and literally JUST figured it out for my issue.
Make sure you have CURL installed for cygwin, and that 'which curl' is pointing to that one.
I had Git Bash installed as well, and it was using the bundled curl that came with it - which apparently didn't play nicely with cygwin.
Also, in case you need any dependencies installed, I suggest putting the setup-x86.exe in your %CYGWIN_INSTALL_PATH%/bin/ so it will auto-install them adhoc.
Hopefully this helps!

RVM ERRORS - unable to clone RVM repository

I am trying to install RVM, but I get this error.
Last login: Thu Mar 31 15:41:06 on ttys000
G-Mac-5:~ macbookpro$ bash < <(curl -B http://rvm.beginrescueend.com/install/rvm)
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 5335 100 5335 0 0 7948 0 --:--:-- --:--:-- --:--:-- 14113
bash: line 114: git: command not found
bash: line 115: git: command not found
ERROR: Unable to clone the RVM repository, attempted both git:// and https://
Do I need to install GIT first? And whats the diffrents between zsh and bash?
There really should be better diagnostic messages when something about the installation fails. Phusion Passenger is an example of how to do it right, where not only are rigorous tests done prior to the installation attempt, but any problems are explained with cut-and-pasteable examples on how to fix them. They're even customized to the particular OS you're using, differentiating between apt-get and yum among other things.
If you're missing git, you won't get very far with rvm.

Resources