Hey, So I took much more time to investigate the problem. I still can't fix the problem, but I think I might be near to understand what is the problem exactly. First of all, it seems that the bundle install is using some wrong version of some gems. In the next picture, you'll see a comparison between my production server (left) and my test server (right, fresh install from today): http://i.imgur.com/Q6hBHJj.png I made sure that my test server has the same Ubuntu version and all updates installed. The others gems we don't see use the same version as on my test server. Secondly, always based on the installation instruction from https://github.com/gitlabhq/gitlabhq/blob/6-3-stable/doc/install/installation.md, once all the gems were installed on the test server, I could use a command like this one: sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production. Which doesn't work on my production server right now. I do receive the same error as of when I try to start the gitlab process. Thirdly: Using the command sudo apt-get *purge* -y build-essential zlib1g-dev libyaml-dev libssl-dev libgdbm-dev libreadline-dev libncurses5-dev libffi-dev curl openssh-server redis-server checkinstall libxml2-dev libxslt-dev libcurl4-openssl-dev libicu-dev logrotate, then the preceding command WILL DO display the gitlab information on the test server. Behavior on the production server doesn't change, the same error with the same stack (or almost, it is always specifying that the version 2.9.0 from LIBXML cannot be found) will appear. Fourthly: Using the same command (the one that deletes the required libraries to build the gems) on the test server, then deleting the "vendor" folder, after rerunning the bundle install will throw me a compilation error (obviously, specifically for the charlock_holmes gem).
Based on my findings, I assumed that my local package repository was corrupted or something on my production server. So I used the command "apt-get clean" then reran the purge command. After that, I ran the apt-get install command for the dev libraries. Once all these steps completed, I used the command bundle install from the installation instruction of GitLab and went on another problem: http://stackoverflow.com/questions/10051448/error-failed-to-build-gem-native-extension-mysql2-on-rails-3-2-3. This was an easy one to fix, so I installed the missing libraries and then relaunched the bundle install command. The result? Same thing, same error, same all... I ran all these steps on my test server at the same time and it was successfully able to use the command sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production afterward. So well, what do you think? Maybe my installed libxml2.so library is corrupted? But it doesn't seems to be that... because I tried recompiling all my gems (once again) after using the command "apt-get install --reinstall libxml2" and nothing has changed. I still have the same error. I observed a whole bunch of strange behaviors on my production server comparing the test one. I think the entire system might be corrupted... maybe. Well you see, when I tried to fetch the latest version of a git repository, I got a SSL invalid certificate error and I had to used the environment variable GIT_SSL_NO_VERIFY=1 to be able to fetch. Anyway, if you have any ideas of what I could try to fix the problem, it would be appreciated, but otherwise, I don't see any other options but to make a full clean installation of Ubuntu Server and start over using my existing configuration files. Thanks for the help! Dave On Monday, December 16, 2013 5:07:36 AM UTC-5, Achilleas Pipis wrote: > > On 12/15/13 19:14, Dave wrote: > > Hi Achilleas, > > > > Yes they are already installed: > > http://i.imgur.com/lq6WncC.png > > > > Fact is, since the upgrade from Ubuntu 12.10 to 13.04, this error has > > appeared and I don't know how to fix it. Some of my friends state that > > it might be because of the embedded libxml2 library that's into > > nokogiri. On the preceding log, it seems like the version 1.5.10 is > > used, but it doesn't looks like to be the case. When I type nokogiri -v > > in the console, I receive the following information: > > # Nokogiri (1.6.0) > > --- > > warnings: [] > > nokogiri: 1.6.0 > > ruby: > > version: 2.0.0 > > platform: x86_64-linux > > description: ruby 2.0.0p247 (2013-06-27 revision 41674) > > [x86_64-linux] > > engine: ruby > > libxml: > > binding: extension > > source: packaged > > libxml2_path: > > > /usr/local/lib/ruby/gems/2.0.0/gems/nokogiri-1.6.0/ports/x86_64-linux-gnu/libxml2/2.8.0 > > > > libxslt_path: > > > /usr/local/lib/ruby/gems/2.0.0/gems/nokogiri-1.6.0/ports/x86_64-linux-gnu/libxslt/1.1.26 > > > > compiled: 2.8.0 > > loaded: 2.8.0 > > > > Do you think maybe there's something wrong with my gem installation? > > > > You have installed nokogiri globally. Do a `sudo gem uninstall > nokogiri`, remove the vendor/bundle directory just to be sure and try a > `bundle install` again. > > > -- > GPG : 0xABF99BE5 > Blog: http://axilleas.me > -- 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
