libicui18n.so.48: cannot open shared object file #7

Open
Marchino opened this Issue Jan 24, 2012 · 19 comments

Comments

Projects
None yet
@Marchino

Hi everybody,
I tried to use this gem within my development environment (mac osx, installed icu4c from source), and everything worked just fine.

On staging environment, though, the gem installed fine, but whenever I run a rake task this is what i get:

libicui18n.so.48: cannot open shared object file: No such file or directory - /path/to/my/app/shared/bundle/ruby/1.9.1/gems/charlock_holmes-0.6.8/ext/charlock_holmes/charlock_holmes.so

I tried building the gem specifyng a path (I set it to the place where libicui18n.so.48 lives) as explained in the readme, but no luck :(

Does anyone know what's going on?

Thanks

Marco

@Marchino

This comment has been minimized.

Show comment
Hide comment
@Marchino

Marchino Jan 24, 2012

What I don't understand is why the gem installation doesn't give errors even if i build it with a non existing path or with no path at all...

I tried :

  • bundle install
  • bundle config build.charlock_holmes --with-icu-dir=/usr/local/lib/icu/current; bundle install
  • bundle config build.charlock_holmes --with-icu-dir=/a/path/that/does/not/even/exist; bundle install

No one of those tries gave errors, but running rake tasks yielded the aforementioned error.

I even tried with different versions of icu (all compiled from source), but no luck...

ideas?

What I don't understand is why the gem installation doesn't give errors even if i build it with a non existing path or with no path at all...

I tried :

  • bundle install
  • bundle config build.charlock_holmes --with-icu-dir=/usr/local/lib/icu/current; bundle install
  • bundle config build.charlock_holmes --with-icu-dir=/a/path/that/does/not/even/exist; bundle install

No one of those tries gave errors, but running rake tasks yielded the aforementioned error.

I even tried with different versions of icu (all compiled from source), but no luck...

ideas?

@khelal

This comment has been minimized.

Show comment
Hide comment
@khelal

khelal Mar 24, 2013

For us it worked once we pointed the icu-dir to /usr/local/lib

khelal commented Mar 24, 2013

For us it worked once we pointed the icu-dir to /usr/local/lib

@aberndsen

This comment has been minimized.

Show comment
Hide comment
@aberndsen

aberndsen May 30, 2014

You probably aren't having this problem anymore, but perhaps others are (I just got this error).

My (overkill) solution was to reinstall the bundle:
mv /home/git/gitlab/vendor/bundle/ruby /home/git/gitlab/vendor/bundle/ruby.orig
sudo -u git -H bundle install --deployment --without development test postgres aws

You probably aren't having this problem anymore, but perhaps others are (I just got this error).

My (overkill) solution was to reinstall the bundle:
mv /home/git/gitlab/vendor/bundle/ruby /home/git/gitlab/vendor/bundle/ruby.orig
sudo -u git -H bundle install --deployment --without development test postgres aws

@mpullman

This comment has been minimized.

Show comment
Hide comment
@mpullman

mpullman Aug 12, 2014

Thanks @aberndsen This worked for me :)

Thanks @aberndsen This worked for me :)

@jpahullo

This comment has been minimized.

Show comment
Hide comment
@jpahullo

jpahullo Sep 25, 2014

Hello,

I found this same error after upgrading from Ubuntu 12.04 to Ubuntu 14.04.

I'll tell you in a while if this also works ok for me.

Thanks for sharing,

Jordi

Hello,

I found this same error after upgrading from Ubuntu 12.04 to Ubuntu 14.04.

I'll tell you in a while if this also works ok for me.

Thanks for sharing,

Jordi

@jpahullo

This comment has been minimized.

Show comment
Hide comment
@jpahullo

jpahullo Sep 25, 2014

Hi all,

I applied your suggestion from @aberndsen and it also worked for me.

Finally executed:

sudo service gitlab restart

showed me finally:

The GitLab Unicorn web server with pid 20369 is running.
The GitLab Sidekiq job dispatcher with pid 20403 is running.
GitLab and all its components are up and running.

And world is again a nice place to live in!

Thank you!

Jordi

Hi all,

I applied your suggestion from @aberndsen and it also worked for me.

Finally executed:

sudo service gitlab restart

showed me finally:

The GitLab Unicorn web server with pid 20369 is running.
The GitLab Sidekiq job dispatcher with pid 20403 is running.
GitLab and all its components are up and running.

And world is again a nice place to live in!

Thank you!

Jordi

@Altonymous

This comment has been minimized.

Show comment
Hide comment
@Altonymous

Altonymous Sep 29, 2014

My error is similar but not exactly the same...

bundle/ruby/2.1.0/gems/charlock_holmes-0.7.3/lib/charlock_holmes.rb:1:in `require': libicuuc.so.48: cannot open shared object file: No such file or directory - bundle/ruby/2.1.0/extensions/x86_64-linux/2.1.0/charlock_holmes-0.7.3/charlock_holmes/charlock_holmes.so (LoadError)

This happens in my staging environment after upgrade to ubuntu 14.04. Not sure the above fix is best to apply as part of my deploy...

My error is similar but not exactly the same...

bundle/ruby/2.1.0/gems/charlock_holmes-0.7.3/lib/charlock_holmes.rb:1:in `require': libicuuc.so.48: cannot open shared object file: No such file or directory - bundle/ruby/2.1.0/extensions/x86_64-linux/2.1.0/charlock_holmes-0.7.3/charlock_holmes/charlock_holmes.so (LoadError)

This happens in my staging environment after upgrade to ubuntu 14.04. Not sure the above fix is best to apply as part of my deploy...

@codereflection

This comment has been minimized.

Show comment
Hide comment
@codereflection

codereflection Oct 3, 2014

@aberndsen's fix worked for us too after upgrading Ubuntu to 14.04. However since we use postgresql, we had to switch the command to:
sudo -u git -H bundle install --deployment --without development test mysql aws

@aberndsen's fix worked for us too after upgrading Ubuntu to 14.04. However since we use postgresql, we had to switch the command to:
sudo -u git -H bundle install --deployment --without development test mysql aws

@Altonymous

This comment has been minimized.

Show comment
Hide comment
@Altonymous

Altonymous Oct 3, 2014

For us it was a capistrano and capistrano-bundler issue.

capistrano changed the default location where it installs the gems and capistrano-bundler hasn't updated yet.

Adding this to our deploy.rb fixed the issue permanently for us:

set :bundle_path, -> { shared_path.join('vendor/bundle') }

For us it was a capistrano and capistrano-bundler issue.

capistrano changed the default location where it installs the gems and capistrano-bundler hasn't updated yet.

Adding this to our deploy.rb fixed the issue permanently for us:

set :bundle_path, -> { shared_path.join('vendor/bundle') }
@anaspk

This comment has been minimized.

Show comment
Hide comment
@anaspk

anaspk Oct 20, 2014

I started having this issue after updating my DigitalOcean droplet to ubuntu 14.04. Solution suggested by @aberndsen worked for me.

However, I had to solve a little issue related to modernizr before running this second command:

sudo -u git -H bundle install --deployment --without development test postgres aws

Solution to that modernizr issue was the second one suggested here: http://stackoverflow.com/a/22827382/1865879

anaspk commented Oct 20, 2014

I started having this issue after updating my DigitalOcean droplet to ubuntu 14.04. Solution suggested by @aberndsen worked for me.

However, I had to solve a little issue related to modernizr before running this second command:

sudo -u git -H bundle install --deployment --without development test postgres aws

Solution to that modernizr issue was the second one suggested here: http://stackoverflow.com/a/22827382/1865879

@Tapo4ek

This comment has been minimized.

Show comment
Hide comment
@Tapo4ek

Tapo4ek Dec 24, 2014

Thanks @aberndsen This worked for me too. Ubuntu 12.04 after apt-get update && apt-get upgrade

Tapo4ek commented Dec 24, 2014

Thanks @aberndsen This worked for me too. Ubuntu 12.04 after apt-get update && apt-get upgrade

@sebastianconcept

This comment has been minimized.

Show comment
Hide comment
@sebastianconcept

sebastianconcept Mar 7, 2015

I was having this issue after upgrading from ubuntu 12 to 14 and what fixed it for me was to:

  1. sudo rm -fr vendor/bundle
  2. sudo -u git RAILS_ENV=production bundle install

I was having this issue after upgrading from ubuntu 12 to 14 and what fixed it for me was to:

  1. sudo rm -fr vendor/bundle
  2. sudo -u git RAILS_ENV=production bundle install
@maanas

This comment has been minimized.

Show comment
Hide comment
@maanas

maanas Mar 16, 2015

Thanks @sebastianconcept. This worked for me.

maanas commented Mar 16, 2015

Thanks @sebastianconcept. This worked for me.

@davidmaignan

This comment has been minimized.

Show comment
Hide comment
@ismailsimsek

This comment has been minimized.

Show comment
Hide comment
@ismailsimsek

ismailsimsek Jul 8, 2015

Thanks @aberndsen that helped me

Thanks @aberndsen that helped me

@nietonfir

This comment has been minimized.

Show comment
Hide comment
@nietonfir

nietonfir Aug 13, 2015

spot on @sebastianconcept! 👍
Thx a lot! ;-)

spot on @sebastianconcept! 👍
Thx a lot! ;-)

@ymiyoshi

This comment has been minimized.

Show comment
Hide comment
@huglester

This comment has been minimized.

Show comment
Hide comment
@huglester

huglester Nov 12, 2015

@sebastianconcept thank you. only your solution worked after upgradeing fom Debian7 to Debian8

@sebastianconcept thank you. only your solution worked after upgradeing fom Debian7 to Debian8

@fquiroga

This comment has been minimized.

Show comment
Hide comment
@fquiroga

fquiroga Jan 25, 2017

@aberndsen thanks your comment solve my problem, the same symptom, upgrading ubuntu from 12.04 to 14.04.

@aberndsen thanks your comment solve my problem, the same symptom, upgrading ubuntu from 12.04 to 14.04.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment