So I got puppet working the way I want in a single client environment. Now I have a puppetmaster and I''m trying to get it to setup a test VM Centos box. I started out with the example42 configs and modified them to fit my environment if that helps any. I''m running into the following error - Nov 22 17:09:09 puppet-test puppetd[2342]: Could not retrieve catalog from remote server: Error 400 on SERVER: no such file to load -- mysql Nov 22 17:09:09 puppet-test puppetd[2342]: Using cached catalog Nov 22 17:09:09 puppet-test puppetd[2342]: Could not retrieve catalog; skipping run Searched for this and found a page that said it could be a possible yaml issue with my nodes.pp (I''d link but I think the site is offline for some reason). My nodes.pp is very simplistic so I don''t think its that. I have stored configs set thin and to use mysql. I checked the database manually and the puppet db doesn''t even have tables in it. Is this normal for a new install? -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
I get this error when I run puppet site.pp --noop
warning: You cannot collect without storeconfigs being set on line 31
in file /etc/puppet/modules/puppet/manifests/server/mysql.pp
Storeconfigs IS set on...in like line 22 of my node file. I modified
to the line to read $puppet_storeconfigs = "no" and it still threw
that error.
This puppet stuff all brand new to me despite going to puppetcamp and
really I have no clue at all what I''m doing, so any advice is much
appreciated. (and yes I have read all the documentation)
--- Here is my mbsbooks.com.pp node file
node ''puppet.mbsbooks.com'' inherits prod {
$puppet_allow = [ "mbsbooks.com" , "10.10.23.55" ]
$puppet_nodetool = "dashboard"
# $puppet_nodetool = "foreman"
# $puppet_externalnodes = "no"
$dashboard_db = "mysql"
$puppet_storeconfigs = "yes"
$puppet_db = "mysql"
$puppet_db_server = "localhost"
$puppet_db_user = "puppet"
$puppet_db_password = "PASSWORD"
include role::puppet
}
#Test Nodes
node ''puppet-test.mbsbooks.com'' inherits prod {
include general
}
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
On Nov 23, 2010, at 11:26 AM, Russell Perkins wrote:> I get this error when I run puppet site.pp --noop > > warning: You cannot collect without storeconfigs being set on line 31 > in file /etc/puppet/modules/puppet/manifests/server/mysql.pp >What''s on line 31 of /etc/puppet/modules/puppet/manifests/server/mysql.pp and the surrounding lines? Also, you should eventually put your stuff into modules although you probably don''t want to do that until stuff works. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Tue, Nov 23, 2010 at 11:26:36AM -0800, Russell Perkins wrote:> I get this error when I run puppet site.pp --noop > > warning: You cannot collect without storeconfigs being set on line 31 > in file /etc/puppet/modules/puppet/manifests/server/mysql.pp > > Storeconfigs IS set on...in like line 22 of my node file. I modified > to the line to read $puppet_storeconfigs = "no" and it still threw > that error. > > > This puppet stuff all brand new to me despite going to puppetcamp and > really I have no clue at all what I''m doing, so any advice is much > appreciated. (and yes I have read all the documentation) > > --- Here is my mbsbooks.com.pp node file > node ''puppet.mbsbooks.com'' inherits prod { > $puppet_allow = [ "mbsbooks.com" , "10.10.23.55" ] > $puppet_nodetool = "dashboard" > # $puppet_nodetool = "foreman" > # $puppet_externalnodes = "no" > $dashboard_db = "mysql" > $puppet_storeconfigs = "yes" > $puppet_db = "mysql" > $puppet_db_server = "localhost" > $puppet_db_user = "puppet" > $puppet_db_password = "PASSWORD" > > include role::puppet > }At first: It''s normal that your storeconfig database is empty. Puppet will create the right tables as soon as the first clients wants to store data in it. But you have to set configs in /etc/puppet/puppet.conf, not in your nodemanifest. http://projects.puppetlabs.com/projects/1/wiki/Using_Stored_Configuration#Configuring+storeconfigs+for+MySQL If you''re using a recent puppet version (>=2.6.0) you have to put the config in a [master] section (not [puppetmasterd]) -Stefan
my node sets the variables to be used in my puppet.conf here is the puppetmasterd section of my /etc/puppet/puppet.conf. I use version 0.25.5 of puppet. [puppetmasterd] # autosign = true # Storeconfigs activated storeconfigs = true thin_storeconfigs = true # Sets MySQL database backend dbadapter=mysql dbserver=localhost dbuser=puppet dbpassword=PASSWORD -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Well It started working. I think the storeconfigs = false fixed the issue temporarily. I also noticed ruby-mysql was not installed, so that could have been causing issues. Russell Perkins wrote:> my node sets the variables to be used in my puppet.conf here is the > puppetmasterd section of my /etc/puppet/puppet.conf. I use version > 0.25.5 of puppet. > > [puppetmasterd] > # autosign = true > > # Storeconfigs activated > storeconfigs = true > thin_storeconfigs = true > > # Sets MySQL database backend > dbadapter=mysql > dbserver=localhost > dbuser=puppet > dbpassword=PASSWORD-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Russell Perkins <rperkins@digitalshiftstudios.com> writes:> Well It started working. I think the storeconfigs = false fixed the > issue temporarily. I also noticed ruby-mysql was not installed, so > that could have been causing issues....I see you arrived at the solution before I got there, but yes: The error you are seeing comes from Ruby, which is reporting that the command "require ''mysql''" can''t find the MySQL Ruby interface files. If you install ruby-mysql and enable storeconfigs again that problem should go away. You might want to put in a bug report suggesting that those require statements be wrapped in a bit more error handling, so they can provide a more helpful error message or something. :) Daniel -- ✣ Daniel Pittman ✉ daniel@rimspace.net ☎ +61 401 155 707 ♽ made with 100 percent post-consumer electrons -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.