# Trying to get solo working and almost there

**URL:** <https://discourse.chef.io/t/trying-to-get-solo-working-and-almost-there/2260>\
**Category:** Chef Infra (archive)\
**Created:** [December 5, 2011, 9:47am UTC](https://discourse.chef.io/t/trying-to-get-solo-working-and-almost-there/2260 "2011-12-05T09:47:16Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Tim\_Uckun](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/tim_uckun/32/751_2.png) [@Tim\_Uckun](https://discourse.chef.io/u/Tim_Uckun)\
**Post date:** [December 5, 2011, 9:47am UTC](https://discourse.chef.io/t/trying-to-get-solo-working-and-almost-there/2260/1 "2011-12-05T09:47:16Z")

</div>

I am trying to get chef solo going. I have set up a script to rsync  
the files to the server and run chef solo but I get this error.

Starting Chef Run for ubuntuvm1  
[Mon, 05 Dec 2011 22:36:20 +1300] WARN: Failed to read the private key  
/etc/chef/client.pem: #\<Errno::ENOENT: No such file or directory -  
/etc/chef/client.pem\>  
[Mon, 05 Dec 2011 22:36:20 +1300] ERROR: Running exception handlers  
[Mon, 05 Dec 2011 22:36:20 +1300] ERROR: Exception handlers complete  
[Mon, 05 Dec 2011 22:36:20 +1300] FATAL: Stacktrace dumped to  
/root/chef\_solo/chef-stacktrace.out  
[Mon, 05 Dec 2011 22:36:20 +1300] FATAL:  
Chef::Exceptions::PrivateKeyMissing: I cannot read  
/etc/chef/client.pem, which you told me to use to sign requests!

It’s happening when I attempt to use the users::sysadmins recipe.

---

<div class="post-metadata">

**Author:** ![Adam\_Jacob](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/adam_jacob/32/292_2.png) [@Adam\_Jacob](https://discourse.chef.io/u/Adam_Jacob)\
**Post date:** [December 5, 2011, 3:24pm UTC](https://discourse.chef.io/t/trying-to-get-solo-working-and-almost-there/2260/2 "2011-12-05T15:24:34Z")

</div>

## Looks like you are running chef-client rather than solo?

Opscode, Inc.  
Adam Jacob, Chief Customer Officer  
T: (206) 619-7151 E: [adam@opscode.com](mailto:adam@opscode.com)

On Dec 5, 2011, at 1:47 AM, Tim Uckun wrote:

> I am trying to get chef solo going. I have set up a script to rsync  
> the files to the server and run chef solo but I get this error.
> 
> Starting Chef Run for ubuntuvm1  
> [Mon, 05 Dec 2011 22:36:20 +1300] WARN: Failed to read the private key  
> /etc/chef/client.pem: #\<Errno::ENOENT: No such file or directory -  
> /etc/chef/client.pem\>  
> [Mon, 05 Dec 2011 22:36:20 +1300] ERROR: Running exception handlers  
> [Mon, 05 Dec 2011 22:36:20 +1300] ERROR: Exception handlers complete  
> [Mon, 05 Dec 2011 22:36:20 +1300] FATAL: Stacktrace dumped to  
> /root/chef\_solo/chef-stacktrace.out  
> [Mon, 05 Dec 2011 22:36:20 +1300] FATAL:  
> Chef::Exceptions::PrivateKeyMissing: I cannot read  
> /etc/chef/client.pem, which you told me to use to sign requests!
> 
> It's happening when I attempt to use the users::sysadmins recipe.

---

<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:** [December 5, 2011, 4:33pm UTC](https://discourse.chef.io/t/trying-to-get-solo-working-and-almost-there/2260/3 "2011-12-05T16:33:33Z")

</div>

On Monday, December 5, 2011 at 7:24 AM, Adam Jacob wrote:

> ## Looks like you are running chef-client rather than solo?
> 
> Opscode, Inc.  
> Adam Jacob, Chief Customer Officer  
> T: (206) 619-7151 E: [adam@opscode.com](mailto:adam@opscode.com) ([mailto:adam@opscode.com](mailto:adam@opscode.com))
> 
> On Dec 5, 2011, at 1:47 AM, Tim Uckun wrote:
> 
> > I am trying to get chef solo going. I have set up a script to rsync  
> > the files to the server and run chef solo but I get this error.
> > 
> > Starting Chef Run for ubuntuvm1  
> > [Mon, 05 Dec 2011 22:36:20 +1300] WARN: Failed to read the private key  
> > /etc/chef/client.pem: #\<Errno::ENOENT: No such file or directory -  
> > /etc/chef/client.pem\>  
> > [Mon, 05 Dec 2011 22:36:20 +1300] ERROR: Running exception handlers  
> > [Mon, 05 Dec 2011 22:36:20 +1300] ERROR: Exception handlers complete  
> > [Mon, 05 Dec 2011 22:36:20 +1300] FATAL: Stacktrace dumped to  
> > /root/chef\_solo/chef-stacktrace.out  
> > [Mon, 05 Dec 2011 22:36:20 +1300] FATAL:  
> > Chef::Exceptions::PrivateKeyMissing: I cannot read  
> > /etc/chef/client.pem, which you told me to use to sign requests!
> > 
> > It's happening when I attempt to use the users::sysadmins recipe.  
> > That recipe is probably trying to load users from data bags.

There is data bag support for chef-solo in 0.10.6 which is still in the RC phase; you can get it with `gem install chef --pre`. I'm not sure exactly where chef-solo will be looking for the data bag items so you'll have to play with it a bit.

--  
Dan DeLeo

---

<div class="post-metadata">

**Author:** ![Miquel\_Torres](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/miquel_torres/32/768_2.png) [@Miquel\_Torres](https://discourse.chef.io/u/Miquel_Torres)\
**Post date:** [December 5, 2011, 4:55pm UTC](https://discourse.chef.io/t/trying-to-get-solo-working-and-almost-there/2260/4 "2011-12-05T16:55:28Z")

</div>

Actually, data bag support for chef-solo was added with Chef 0.10.4  
The user cookbook though uses search, which may be what triggers that  
client.pem error.

If you want to use with chef-solo a cookbook that uses search, you  
will need this lib:

> **[GitHub - edelight/chef-solo-search: Data bag search for Chef Solo](https://github.com/edelight/chef-solo-search)**
>
> Data bag search for Chef Solo. Contribute to edelight/chef-solo-search development by creating an account on GitHub.

Just add it to your deployed cookbooks and search will work.

Cheers  
Miquel

2011/12/5 Daniel DeLeo [dan@kallistec.com](mailto:dan@kallistec.com):

> On Monday, December 5, 2011 at 7:24 AM, Adam Jacob wrote:
> 
> > ## Looks like you are running chef-client rather than solo?
> > 
> > Opscode, Inc.  
> > Adam Jacob, Chief Customer Officer  
> > T: (206) 619-7151 E: [adam@opscode.com](mailto:adam@opscode.com) ([mailto:adam@opscode.com](mailto:adam@opscode.com))
> > 
> > On Dec 5, 2011, at 1:47 AM, Tim Uckun wrote:
> > 
> > > I am trying to get chef solo going. I have set up a script to rsync  
> > > the files to the server and run chef solo but I get this error.
> > > 
> > > Starting Chef Run for ubuntuvm1  
> > > [Mon, 05 Dec 2011 22:36:20 +1300] WARN: Failed to read the private key  
> > > /etc/chef/client.pem: #\<Errno::ENOENT: No such file or directory -  
> > > /etc/chef/client.pem\>  
> > > [Mon, 05 Dec 2011 22:36:20 +1300] ERROR: Running exception handlers  
> > > [Mon, 05 Dec 2011 22:36:20 +1300] ERROR: Exception handlers complete  
> > > [Mon, 05 Dec 2011 22:36:20 +1300] FATAL: Stacktrace dumped to  
> > > /root/chef\_solo/chef-stacktrace.out  
> > > [Mon, 05 Dec 2011 22:36:20 +1300] FATAL:  
> > > Chef::Exceptions::PrivateKeyMissing: I cannot read  
> > > /etc/chef/client.pem, which you told me to use to sign requests!
> > > 
> > > It's happening when I attempt to use the users::sysadmins recipe.  
> > > That recipe is probably trying to load users from data bags.
> 
> There is data bag support for chef-solo in 0.10.6 which is still in the RC phase; you can get it with `gem install chef --pre`. I'm not sure exactly where chef-solo will be looking for the data bag items so you'll have to play with it a bit.
> 
> --  
> Dan DeLeo

---

<div class="post-metadata">

**Author:** ![Adam\_Jacob](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/adam_jacob/32/292_2.png) [@Adam\_Jacob](https://discourse.chef.io/u/Adam_Jacob)\
**Post date:** [December 5, 2011, 6:30pm UTC](https://discourse.chef.io/t/trying-to-get-solo-working-and-almost-there/2260/5 "2011-12-05T18:30:28Z")

</div>

We should consider adding this functionality to core, eh?

Adam

* * *

Opscode, Inc.  
Adam Jacob, Chief Customer Officer  
T: (206) 619-7151 E: [adam@opscode.com](mailto:adam@opscode.com)

On Dec 5, 2011, at 8:55 AM, Miquel Torres wrote:

> Actually, data bag support for chef-solo was added with Chef 0.10.4  
> The user cookbook though uses search, which may be what triggers that  
> client.pem error.
> 
> If you want to use with chef-solo a cookbook that uses search, you  
> will need this lib:  
> [GitHub - edelight/chef-solo-search: Data bag search for Chef Solo](https://github.com/edelight/chef-solo-search)
> 
> Just add it to your deployed cookbooks and search will work.
> 
> Cheers  
> Miquel
> 
> 2011/12/5 Daniel DeLeo [dan@kallistec.com](mailto:dan@kallistec.com):
> 
> > On Monday, December 5, 2011 at 7:24 AM, Adam Jacob wrote:
> > 
> > > ## Looks like you are running chef-client rather than solo?
> > > 
> > > Opscode, Inc.  
> > > Adam Jacob, Chief Customer Officer  
> > > T: (206) 619-7151 E: [adam@opscode.com](mailto:adam@opscode.com) ([mailto:adam@opscode.com](mailto:adam@opscode.com))
> > > 
> > > On Dec 5, 2011, at 1:47 AM, Tim Uckun wrote:
> > > 
> > > > I am trying to get chef solo going. I have set up a script to rsync  
> > > > the files to the server and run chef solo but I get this error.
> > > > 
> > > > Starting Chef Run for ubuntuvm1  
> > > > [Mon, 05 Dec 2011 22:36:20 +1300] WARN: Failed to read the private key  
> > > > /etc/chef/client.pem: #\<Errno::ENOENT: No such file or directory -  
> > > > /etc/chef/client.pem\>  
> > > > [Mon, 05 Dec 2011 22:36:20 +1300] ERROR: Running exception handlers  
> > > > [Mon, 05 Dec 2011 22:36:20 +1300] ERROR: Exception handlers complete  
> > > > [Mon, 05 Dec 2011 22:36:20 +1300] FATAL: Stacktrace dumped to  
> > > > /root/chef\_solo/chef-stacktrace.out  
> > > > [Mon, 05 Dec 2011 22:36:20 +1300] FATAL:  
> > > > Chef::Exceptions::PrivateKeyMissing: I cannot read  
> > > > /etc/chef/client.pem, which you told me to use to sign requests!
> > > > 
> > > > It's happening when I attempt to use the users::sysadmins recipe.  
> > > > That recipe is probably trying to load users from data bags.
> > 
> > There is data bag support for chef-solo in 0.10.6 which is still in the RC phase; you can get it with `gem install chef --pre`. I'm not sure exactly where chef-solo will be looking for the data bag items so you'll have to play with it a bit.
> > 
> > --  
> > Dan DeLeo

---

<div class="post-metadata">

**Author:** ![Miquel\_Torres](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/miquel_torres/32/768_2.png) [@Miquel\_Torres](https://discourse.chef.io/u/Miquel_Torres)\
**Post date:** [December 5, 2011, 7:53pm UTC](https://discourse.chef.io/t/trying-to-get-solo-working-and-almost-there/2260/6 "2011-12-05T19:53:47Z")

</div>

Makes sense, yes.  
How would you like us to contribute it?

2011/12/5 Adam Jacob [adam@opscode.com](mailto:adam@opscode.com):

> We should consider adding this functionality to core, eh?
> 
> Adam
> 
> * * *
> 
> Opscode, Inc.  
> Adam Jacob, Chief Customer Officer  
> T: (206) 619-7151 E: [adam@opscode.com](mailto:adam@opscode.com)
> 
> On Dec 5, 2011, at 8:55 AM, Miquel Torres wrote:
> 
> > Actually, data bag support for chef-solo was added with Chef 0.10.4  
> > The user cookbook though uses search, which may be what triggers that  
> > client.pem error.
> > 
> > If you want to use with chef-solo a cookbook that uses search, you  
> > will need this lib:  
> > [GitHub - edelight/chef-solo-search: Data bag search for Chef Solo](https://github.com/edelight/chef-solo-search)
> > 
> > Just add it to your deployed cookbooks and search will work.
> > 
> > Cheers  
> > Miquel
> > 
> > 2011/12/5 Daniel DeLeo [dan@kallistec.com](mailto:dan@kallistec.com):
> > 
> > > On Monday, December 5, 2011 at 7:24 AM, Adam Jacob wrote:
> > > 
> > > > ## Looks like you are running chef-client rather than solo?
> > > > 
> > > > Opscode, Inc.  
> > > > Adam Jacob, Chief Customer Officer  
> > > > T: (206) 619-7151 E: [adam@opscode.com](mailto:adam@opscode.com) ([mailto:adam@opscode.com](mailto:adam@opscode.com))
> > > > 
> > > > On Dec 5, 2011, at 1:47 AM, Tim Uckun wrote:
> > > > 
> > > > > I am trying to get chef solo going. I have set up a script to rsync  
> > > > > the files to the server and run chef solo but I get this error.
> > > > > 
> > > > > Starting Chef Run for ubuntuvm1  
> > > > > [Mon, 05 Dec 2011 22:36:20 +1300] WARN: Failed to read the private key  
> > > > > /etc/chef/client.pem: #\<Errno::ENOENT: No such file or directory -  
> > > > > /etc/chef/client.pem\>  
> > > > > [Mon, 05 Dec 2011 22:36:20 +1300] ERROR: Running exception handlers  
> > > > > [Mon, 05 Dec 2011 22:36:20 +1300] ERROR: Exception handlers complete  
> > > > > [Mon, 05 Dec 2011 22:36:20 +1300] FATAL: Stacktrace dumped to  
> > > > > /root/chef\_solo/chef-stacktrace.out  
> > > > > [Mon, 05 Dec 2011 22:36:20 +1300] FATAL:  
> > > > > Chef::Exceptions::PrivateKeyMissing: I cannot read  
> > > > > /etc/chef/client.pem, which you told me to use to sign requests!
> > > > > 
> > > > > It's happening when I attempt to use the users::sysadmins recipe.  
> > > > > That recipe is probably trying to load users from data bags.
> > > 
> > > There is data bag support for chef-solo in 0.10.6 which is still in the RC phase; you can get it with `gem install chef --pre`. I'm not sure exactly where chef-solo will be looking for the data bag items so you'll have to play with it a bit.
> > > 
> > > --  
> > > Dan DeLeo

---

<div class="post-metadata">

**Author:** ![Bryan\_McLellan](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/bryan_mclellan/32/81_2.png) [@Bryan\_McLellan](https://discourse.chef.io/u/Bryan_McLellan)\
**Post date:** [December 5, 2011, 8:11pm UTC](https://discourse.chef.io/t/trying-to-get-solo-working-and-almost-there/2260/7 "2011-12-05T20:11:50Z")

</div>

On Mon, Dec 5, 2011 at 2:53 PM, Miquel Torres [tobami@googlemail.com](mailto:tobami@googlemail.com) wrote:

> How would you like us to contribute it?

Please start at the How to Contribute [1] page on the wiki. We will  
need a Contributor License Agreement (CLA) and a ticket for the new  
feature on the ticket tracking system [2]. If you can factor the solo  
search code into the core project from the github project yourself,  
that would be awesome. Once you've got it figured out, dropping a link  
to a github branch in the ticket and marking the ticket as resolved  
will help us find it at our weekly triage meetings and the triage team  
at Opscode will review it. If you need any help figuring out the code  
or making architectural decisions, we're always happy to help on the  
chef-dev [3] list.

Bryan

[1] [http://wiki.opscode.com/display/chef/How+to+Contribute](http://wiki.opscode.com/display/chef/How+to+Contribute)  
[2] [http://tickets.opscode.com](http://tickets.opscode.com)  
[3] [http://lists.opscode.com/sympa/info/chef-dev](http://lists.opscode.com/sympa/info/chef-dev)

---

<div class="post-metadata">

**Author:** ![Tim\_Uckun](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/tim_uckun/32/751_2.png) [@Tim\_Uckun](https://discourse.chef.io/u/Tim_Uckun)\
**Post date:** [December 5, 2011, 8:49pm UTC](https://discourse.chef.io/t/trying-to-get-solo-working-and-almost-there/2260/8 "2011-12-05T20:49:11Z")

</div>

On Tue, Dec 6, 2011 at 5:55 AM, Miquel Torres [tobami@googlemail.com](mailto:tobami@googlemail.com) wrote:

> Actually, data bag support for chef-solo was added with Chef 0.10.4  
> The user cookbook though uses search, which may be what triggers that  
> client.pem error.

Wow. Thanks for knowing that. I would have never deduced it.

> If you want to use with chef-solo a cookbook that uses search, you  
> will need this lib:  
> [GitHub - edelight/chef-solo-search: Data bag search for Chef Solo](https://github.com/edelight/chef-solo-search)

Thanks I'll give that a go.

Cheers.