# Omnibus health check failing because of libdb

**URL:** <https://discourse.chef.io/t/omnibus-health-check-failing-because-of-libdb/4914>\
**Category:** Chef Infra (archive)\
**Created:** [January 17, 2014, 11:22pm UTC](https://discourse.chef.io/t/omnibus-health-check-failing-because-of-libdb/4914 "2014-01-17T23:22:51Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![lharms](https://avatars.discourse-cdn.com/v4/letter/l/9d8465/32.png) [@lharms](https://discourse.chef.io/u/lharms)\
**Post date:** [January 17, 2014, 11:22pm UTC](https://discourse.chef.io/t/omnibus-health-check-failing-because-of-libdb/4914/1 "2014-01-17T23:22:51Z")

</div>

Howdy,

I didn’t find an Omnibus mailing list so hopefully it is ok to bring it  
up here. If not, let me know.

I’ve tried building several package with ruby and always get the same  
result. The health check fails because of the unsafe/unmet dependencies  
of /lib64/libdb-4.7.so.

I get this error using the omnibus-software files. I’ve also tried  
writing a Berkeley DB dependency and still get the same error.

Alas my dependency-fu is weak. Can someone point me in the right  
direction?

A full error message is available at:  
[https://gist.github.com/lmickh/8483458](https://gist.github.com/lmickh/8483458)

Thanks,  
Lucas

---

<div class="post-metadata">

**Author:** ![kallistec](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/kallistec/32/23_2.png) [@kallistec](https://discourse.chef.io/u/kallistec)\
**Post date:** [January 17, 2014, 11:31pm UTC](https://discourse.chef.io/t/omnibus-health-check-failing-because-of-libdb/4914/2 "2014-01-17T23:31:10Z")

</div>

On Friday, January 17, 2014 at 3:22 PM, lharms wrote:

> Howdy,
> 
> I didn't find an Omnibus mailing list so hopefully it is ok to bring it  
> up here. If not, let me know.
> 
> I've tried building several package with ruby and always get the same  
> result. The health check fails because of the unsafe/unmet dependencies  
> of /lib64/libdb-4.7.so.
> 
> I get this error using the omnibus-software files. I've also tried  
> writing a Berkeley DB dependency and still get the same error.
> 
> Alas my dependency-fu is weak. Can someone point me in the right  
> direction?
> 
> A full error message is available at:  
> [https://gist.github.com/lmickh/8483458](https://gist.github.com/lmickh/8483458)
> 
> Thanks,  
> Lucas

What are you doing differently than [https://github.com/opscode/omnibus-software/blob/master/config/software/ruby.rb](https://github.com/opscode/omnibus-software/blob/master/config/software/ruby.rb) ? What build platform is this (linux/other, distro, etc.)?

The general solution for these kinds of issues is to modify the arguments to configure to either disable a component if you don’t want it, or pass in an option that will make the compiler link to your embedded library if you do want that component (or there’s no option to disable it).

--  
Daniel DeLeo

---

<div class="post-metadata">

**Author:** ![lharms](https://avatars.discourse-cdn.com/v4/letter/l/9d8465/32.png) [@lharms](https://discourse.chef.io/u/lharms)\
**Post date:** [January 17, 2014, 11:43pm UTC](https://discourse.chef.io/t/omnibus-health-check-failing-because-of-libdb/4914/3 "2014-01-17T23:43:33Z")

</div>

That error was generated using the omnibus-software version of ruby.rb.  
Nothing is changed. Copied the conf directory straight from github.

This is on Centos 6.5. I did a 'gem install omnibus', create a new  
project, copy the omnibus-software repo, and kicked off a build.

Also tried writing my own ruby.rb and compile libdb from omnibus.

I've been able to build other projects that did not rely on ruby or  
libdb such as php.

Lucas

On Fri, 2014-01-17 at 15:31 -0800, Daniel DeLeo wrote:

> > 
> 
> What are you doing differently  
> than [https://github.com/opscode/omnibus-software/blob/master/config/software/ruby.rb](https://github.com/opscode/omnibus-software/blob/master/config/software/ruby.rb) ? What build platform is this (linux/other, distro, etc.)?
> 
> The general solution for these kinds of issues is to modify the  
> arguments to configure to either disable a component if you don’t want  
> it, or pass in an option that will make the compiler link to your  
> embedded library if you do want that component (or there’s no option  
> to disable it).
> 
> --  
> Daniel DeLeo

---

<div class="post-metadata">

**Author:** ![kallistec](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/kallistec/32/23_2.png) [@kallistec](https://discourse.chef.io/u/kallistec)\
**Post date:** [January 18, 2014, 12:50am UTC](https://discourse.chef.io/t/omnibus-health-check-failing-because-of-libdb/4914/4 "2014-01-18T00:50:01Z")

</div>

On Friday, January 17, 2014 at 3:43 PM, lharms wrote:

> That error was generated using the omnibus-software version of ruby.rb.  
> Nothing is changed. Copied the conf directory straight from github.
> 
> This is on Centos 6.5. I did a 'gem install omnibus', create a new  
> project, copy the omnibus-software repo, and kicked off a build.
> 
> Also tried writing my own ruby.rb and compile libdb from omnibus.
> 
> I've been able to build other projects that did not rely on ruby or  
> libdb such as php.
> 
> Lucas  
> I would guess you have some package installed (perhaps intentionally, perhaps as part of what came with the particular installer you used) that we don’t have on our build boxes and ruby’s build scripts are detecting it and building extra components. I’d start by looking at the help output for the ./configure command to see if there’s any options that look relevant.

--  
Daniel DeLeo

---

<div class="post-metadata">

**Author:** ![Lamont\_Granquist\_OLD](https://avatars.discourse-cdn.com/v4/letter/l/7feea3/32.png) [@Lamont\_Granquist\_OLD](https://discourse.chef.io/u/Lamont_Granquist_OLD)\
**Post date:** [January 18, 2014, 3:25am UTC](https://discourse.chef.io/t/omnibus-health-check-failing-because-of-libdb/4914/5 "2014-01-18T03:25:16Z")

</div>

what dan said, and to add:

- try "rpm -e libdb-devel"
- try a "minimal" centos install and only install enough RPMs to get  
omnibus builds working

there should be more information in the error message about which file  
is linking against libdb-4.7.so and you might be able to use that to  
disable an extension using ""--with-out-ext=" in the  
configure argument to ruby.

On 1/17/14 4:50 PM, Daniel DeLeo wrote:

> On Friday, January 17, 2014 at 3:43 PM, lharms wrote:
> 
> > That error was generated using the omnibus-software version of ruby.rb.  
> > Nothing is changed. Copied the conf directory straight from github.
> > 
> > This is on Centos 6.5. I did a 'gem install omnibus', create a new  
> > project, copy the omnibus-software repo, and kicked off a build.
> > 
> > Also tried writing my own ruby.rb and compile libdb from omnibus.
> > 
> > I've been able to build other projects that did not rely on ruby or  
> > libdb such as php.
> > 
> > Lucas  
> > I would guess you have some package installed (perhaps intentionally,  
> > perhaps as part of what came with the particular installer you used)  
> > that we don’t have on our build boxes and ruby’s build scripts are  
> > detecting it and building extra components. I’d start by looking at  
> > the help output for the ./configure command to see if there’s any  
> > options that look relevant.
> 
> --  
> Daniel DeLeo