Munin::server => apache2 => ArgumentError


#1

Hello,

I’ve just started with chef and am having some trouble.

I’m using the munin::server recipe, which includes apache2, which is failing to install on the client machine. The apache2 cookbook is on the chef server… and it’s the one from opscode/chef-repo…

Any debugging tips?

John

2010-04-02_04:29:23.35439 DEBUG: Sending HTTP Request via GET to chef.reflectornetwork.com:4000/roles/monitoring
2010-04-02_04:29:23.35440 DEBUG: Loading Recipe munin::server via include_recipe
2010-04-02_04:29:23.35440 DEBUG: Found recipe server in cookbook munin
2010-04-02_04:29:23.35441 DEBUG: Loading Recipe apache2 via include_recipe
2010-04-02_04:29:23.35441 ERROR: ArgumentError
2010-04-02_04:29:23.35442 FATAL: Cannot find a cookbook named apache2; did you forget to add metadata to a cookbook? (http://wiki.opscode.com/display/chef/Metadata)
2010-04-02_04:29:23.35444 /usr/lib/ruby/gems/1.8/gems/chef-0.8.10/bin/…/lib/chef/cookbook_loader.rb:126:in []' 2010-04-02_04:29:23.35445 /usr/lib/ruby/gems/1.8/gems/chef-0.8.10/bin/../lib/chef/mixin/language_include_recipe.rb:40:ininclude_recipe’
2010-04-02_04:29:23.35445 /usr/lib/ruby/gems/1.8/gems/chef-0.8.10/bin/…/lib/chef/mixin/language_include_recipe.rb:26:in each' 2010-04-02_04:29:23.35447 /usr/lib/ruby/gems/1.8/gems/chef-0.8.10/bin/../lib/chef/mixin/language_include_recipe.rb:26:ininclude_recipe’
2010-04-02_04:29:23.35448 /srv/chef/cache/cookbooks/munin/recipes/server.rb:20:in from_file' 2010-04-02_04:29:23.35448 /usr/lib/ruby/gems/1.8/gems/chef-0.8.10/bin/../lib/chef/cookbook.rb:171:inload_recipe’
2010-04-02_04:29:23.35449 /usr/lib/ruby/gems/1.8/gems/chef-0.8.10/bin/…/lib/chef/mixin/language_include_recipe.rb:38:in include_recipe' 2010-04-02_04:29:23.35450 /usr/lib/ruby/gems/1.8/gems/chef-0.8.10/bin/../lib/chef/mixin/language_include_recipe.rb:26:ineach’
2010-04-02_04:29:23.35450 /usr/lib/ruby/gems/1.8/gems/chef-0.8.10/bin/…/lib/chef/mixin/language_include_recipe.rb:26:in include_recipe' 2010-04-02_04:29:23.35451 /usr/lib/ruby/gems/1.8/gems/chef-0.8.10/bin/../lib/chef/compile.rb:145:inload_recipes’
2010-04-02_04:29:23.35453 /usr/lib/ruby/gems/1.8/gems/chef-0.8.10/bin/…/lib/chef/compile.rb:144:in each' 2010-04-02_04:29:23.35454 /usr/lib/ruby/gems/1.8/gems/chef-0.8.10/bin/../lib/chef/compile.rb:144:inload_recipes’
2010-04-02_04:29:23.35454 /usr/lib/ruby/gems/1.8/gems/chef-0.8.10/bin/…/lib/chef/compile.rb:54:in initialize' 2010-04-02_04:29:23.35455 /usr/lib/ruby/gems/1.8/gems/chef-0.8.10/bin/../lib/chef/client.rb:316:innew’
2010-04-02_04:29:23.35456 /usr/lib/ruby/gems/1.8/gems/chef-0.8.10/bin/…/lib/chef/client.rb:316:in converge' 2010-04-02_04:29:23.35457 /usr/lib/ruby/gems/1.8/gems/chef-0.8.10/bin/../lib/chef/client.rb:89:inrun’
2010-04-02_04:29:23.35460 /usr/lib/ruby/gems/1.8/gems/chef-0.8.10/bin/…/lib/chef/application/client.rb:210:in run_application' 2010-04-02_04:29:23.35461 /usr/lib/ruby/gems/1.8/gems/chef-0.8.10/bin/../lib/chef/application/client.rb:202:inloop’
2010-04-02_04:29:23.35461 /usr/lib/ruby/gems/1.8/gems/chef-0.8.10/bin/…/lib/chef/application/client.rb:202:in run_application' 2010-04-02_04:29:23.35462 /usr/lib/ruby/gems/1.8/gems/chef-0.8.10/bin/../lib/chef/application.rb:57:inrun’
2010-04-02_04:29:23.35465 /usr/lib/ruby/gems/1.8/gems/chef-0.8.10/bin/chef-client:26
2010-04-02_04:29:23.35465 /usr/bin/chef-client:19:in `load’
2010-04-02_04:29:23.35466 /usr/bin/chef-client:19


John Merrells
http://johnmerrells.com
+1.415.244.5808


#2

On Thu, Apr 1, 2010 at 9:38 PM, John Merrells john@merrells.com wrote:

2010-04-02_04:29:23.35442 FATAL: Cannot find a cookbook named apache2; did you forget to add metadata to a cookbook? (http://wiki.opscode.com/display/chef/Metadata)

This is most often the problem. Does the cookbooks/munin/metadata.rb
file contain the line:

depends “apache2”

Do you have the apache2 cookbook installed as well?

Bryan


#3

On Apr 1, 2010, at 9:47 PM, Bryan McLellan wrote:

This is most often the problem. Does the cookbooks/munin/metadata.rb
file contain the line:

depends “apache2”

ah… it does not… i’ll add it and see if that changes anything…

Do you have the apache2 cookbook installed as well?

Yes, I can see it through the chef-server-webui

John


John Merrells
http://johnmerrells.com
+1.415.244.5808


#4

On Thu, Apr 1, 2010 at 10:16 PM, John Merrells john@merrells.com wrote:

This is most often the problem. Does the cookbooks/munin/metadata.rb
file contain the line:

depends “apache2”

ah… it does not… i’ll add it and see if that changes anything…

The chef server decides what additional cookbooks to send to the
client from the metadata of cookbooks assigned to the node. This way
every node does not need to have a copy of every cookbook.

http://wiki.opscode.com/display/chef/Metadata#Metadata-depends

Bryan


#5

On Apr 1, 2010, at 10:21 PM, Bryan McLellan wrote:

On Thu, Apr 1, 2010 at 10:16 PM, John Merrells john@merrells.com wrote:

This is most often the problem. Does the cookbooks/munin/metadata.rb
file contain the line:

depends “apache2”

ah… it does not… i’ll add it and see if that changes anything…

Yes, that fixed the problem.

The chef server decides what additional cookbooks to send to the
client from the metadata of cookbooks assigned to the node. This way
every node does not need to have a copy of every cookbook.

http://wiki.opscode.com/display/chef/Metadata#Metadata-depends

That makes sense then. So, this is a bug in the opscode cookbooks recipe.
I’ll file it as an issue on github.

Thanks for helping me out :slight_smile:

John


John Merrells
http://johnmerrells.com
+1.415.244.5808


#6

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello!

On Apr 1, 2010, at 11:27 PM, John Merrells wrote:

That makes sense then. So, this is a bug in the opscode cookbooks
recipe.
I’ll file it as an issue on github.

Please file the ticket on http://tickets.opscode.com. We don’t use the
issues tracking on GitHub.


Opscode, Inc
Joshua Timberman, Senior Solutions Engineer
C: 720.334.RUBY E: joshua@opscode.com

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (Darwin)

iEYEARECAAYFAku1gMMACgkQO97WSdVpzT2BawCgoWuzbto0URSBMr+Vb479ZuLq
5jYAoIuKYUkQiT3384iYQPNl4pUGoKlo
=aKIQ
-----END PGP SIGNATURE-----