Hello, I am very new to puppet and have been able to get it setup and a test module installed on the server running the agent. I am not trying ot test out a tomcat module. I have installed the module and edited the manifest files to specify the path to where the files are located ie. </etc/puppetlabs/puppet/modules/tomcat> However, I am still getting this error: Level Message Source File Line Time err Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find class tomcat for puppetagent.agilexhealth.com on node puppetagent.agilexhealth.com Puppet 2012-07-26 18:57 UTC err Could not retrieve catalog; skipping run Puppet 2012-07-26 18:57 UTC notice Using cached catalog Puppet 2012-07-26 18:57 UTC Any ideas on what I am doing wrong? Thanks, Robbie -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/RhoyFeZtMBkJ. 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 Thursday, July 26, 2012 2:18:12 PM UTC-5, R. Mason wrote:> > err Could not retrieve catalog from remote server: Error 400 on > SERVER: Could not find class tomcat for puppetagent.agilexhealth.com on > node puppetagent.agilexhealth.com Puppet 2012-07-26 18:57 > UTC >My first guess would be that the module you are trying to use is not installed correctly. Alternatively, it might not offer a class "tomcat", but only classes of the form "tomcat::config", "tomcat::application", etc.. Supposing that the module''s name is "tomcat" and that Puppet''s module path is just /etc/puppet/modules, in a correct installation you would expect a layout something like this: /etc/puppet/modules/tomcat/ /etc/puppet/modules/tomcat/manifests/ /etc/puppet/modules/tomcat/manifests/init.pp /etc/puppet/modules/tomcat/manifests/<someclass>.pp /etc/puppet/modules/tomcat/manifests/<anotherclass>.pp there might also be /etc/puppet/modules/tomcat/files/ /etc/puppet/modules/tomcat/lib/ and other files and directories thereunder. Possibly other subtrees, too. Furthermore, everything needs to be accessible to the puppetmaster user, who typically is not privileged. If you installed the module as root then you may need to update file ownership, permissions, SELinux labeling, or something else along those lines. John -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/x38D90FtPygJ. 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.
Basically what John said, either the tomcat module doesn''t offer a class "tomcat" or you installed the module outside of your puppetmaster modulepath. You can look up where your puppetmaster will look for modules by running: # puppet config print modulepath /etc/puppet/modules:/usr/share/puppet/modules On Friday, July 27, 2012 10:02:26 PM UTC+2, jcbollinger wrote:> > > > On Thursday, July 26, 2012 2:18:12 PM UTC-5, R. Mason wrote: >> >> err Could not retrieve catalog from remote server: Error 400 on >> SERVER: Could not find class tomcat for puppetagent.agilexhealth.com on >> node puppetagent.agilexhealth.com Puppet 2012-07-26 >> 18:57 UTC >> > > My first guess would be that the module you are trying to use is not > installed correctly. Alternatively, it might not offer a class "tomcat", > but only classes of the form "tomcat::config", "tomcat::application", etc.. > > Supposing that the module''s name is "tomcat" and that Puppet''s module path > is just /etc/puppet/modules, in a correct installation you would expect a > layout something like this: > > /etc/puppet/modules/tomcat/ > /etc/puppet/modules/tomcat/manifests/ > /etc/puppet/modules/tomcat/manifests/init.pp > /etc/puppet/modules/tomcat/manifests/<someclass>.pp > /etc/puppet/modules/tomcat/manifests/<anotherclass>.pp > > there might also be > > /etc/puppet/modules/tomcat/files/ > /etc/puppet/modules/tomcat/lib/ > > and other files and directories thereunder. Possibly other subtrees, too. > > Furthermore, everything needs to be accessible to the puppetmaster user, > who typically is not privileged. If you installed the module as root then > you may need to update file ownership, permissions, SELinux labeling, or > something else along those lines. > > > John > >-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/7xDkHQyVvtEJ. 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.