# Database cookbook weirdness

**URL:** <https://discourse.chef.io/t/database-cookbook-weirdness/1709>\
**Category:** Chef Infra (archive)\
**Created:** [February 23, 2011, 5:20am UTC](https://discourse.chef.io/t/database-cookbook-weirdness/1709 "2011-02-23T05:20:49Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Joshua\_Jarboe](https://avatars.discourse-cdn.com/v4/letter/j/b3f665/32.png) [@Joshua\_Jarboe](https://discourse.chef.io/u/Joshua_Jarboe)\
**Post date:** [February 23, 2011, 5:20am UTC](https://discourse.chef.io/t/database-cookbook-weirdness/1709/1 "2011-02-23T05:20:49Z")

</div>

I’m trying to use the application / database cookbooks to get a mysql db  
server up. In and of itself, that should be easy and safe, but I’m using a  
ubuntu 10.10 / Ruby 1.92 setup as found on this excellent article:

[http://napkin.highgroove.com/articles/2011/01/29/ruby-1-9-2-fresh-from-the-oven-or-bootstrap-chef-with-ruby-1-9-2-and-ubuntu-10-10](http://napkin.highgroove.com/articles/2011/01/29/ruby-1-9-2-fresh-from-the-oven-or-bootstrap-chef-with-ruby-1-9-2-and-ubuntu-10-10)

Everything goes just fine until it doesn’t. When the chef run tries to  
restart the mysql service, it just stops. The Chef run doesn’t time out.  
I’m assuming therefore that whatever command Chef has issued doesn’t time  
out either.

This stuff worked on Ubuntu 10.4 and Ruby 1.87, so it seems likely that  
changing one (or both) of these is what has resulted in this behavior. For  
now, I’m going to try to work around it by getting a Ubuntu 10.4 / Ruby1.92  
box up, so I may well answer my own question here. But I’m interested in  
what folks have seen in this regard. Has anyone else seen this before?

~Joshua Jarboe

---

<div class="post-metadata">

**Author:** ![James](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/james/32/232_2.png) [@James](https://discourse.chef.io/u/James)\
**Post date:** [February 23, 2011, 6:34am UTC](https://discourse.chef.io/t/database-cookbook-weirdness/1709/2 "2011-02-23T06:34:53Z")

</div>

Josh,

I have no experience with this particular issue, but can you run chef-client  
as follows:

chef-client -l debug

Does this provide any further output?

Can you try to do the following, while mysql is attempting to be restarted:  
ps -aux|grep mysql

And paste your results here?

Thanks,

James

On Wed, Feb 23, 2011 at 12:20 AM, Joshua Jarboe [josh@kingofweb.com](mailto:josh@kingofweb.com) wrote:

> I'm trying to use the application / database cookbooks to get a mysql db  
> server up. In and of itself, that should be easy and safe, but I'm using a  
> ubuntu 10.10 / Ruby 1.92 setup as found on this excellent article:
> 
> [http://napkin.highgroove.com/articles/2011/01/29/ruby-1-9-2-fresh-from-the-oven-or-bootstrap-chef-with-ruby-1-9-2-and-ubuntu-10-10](http://napkin.highgroove.com/articles/2011/01/29/ruby-1-9-2-fresh-from-the-oven-or-bootstrap-chef-with-ruby-1-9-2-and-ubuntu-10-10)
> 
> Everything goes just fine until it doesn't. When the chef run tries to  
> restart the mysql service, it just stops. The Chef run doesn't time out.  
> I'm assuming therefore that whatever command Chef has issued doesn't time  
> out either.
> 
> This stuff worked on Ubuntu 10.4 and Ruby 1.87, so it seems likely that  
> changing one (or both) of these is what has resulted in this behavior. For  
> now, I'm going to try to work around it by getting a Ubuntu 10.4 / Ruby1.92  
> box up, so I may well answer my own question here. But I'm interested in  
> what folks have seen in this regard. Has anyone else seen this before?
> 
> ~Joshua Jarboe