Re: Help getting started with tomcat

159 views
Skip to first unread message

jcbollinger

unread,
Jul 27, 2012, 4:02:26 PM7/27/12
to puppet...@googlegroups.com


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

Andreas Paul

unread,
Jul 30, 2012, 4:27:39 AM7/30/12
to puppet...@googlegroups.com
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

Pallavi Jain

unread,
Jul 23, 2014, 10:25:24 AM7/23/14
to puppet...@googlegroups.com
Hello 

I am getting similar issue with my Jboss module, I have checked the permissions and all the files are accessible to puppet master.

Also my module is in the module  path  of puppet master. This same module use to work earlier. 

When I test using 

 puppet agent --test  --verbose --masterport=443  --trace --noop --logdest=/tmp/puppet.log

I get 

Info: Loading facts in /var/lib/puppet/lib/facter/facter_dot_d.rb
Info: Loading facts in /var/lib/puppet/lib/facter/postgres_default_version.rb
Info: Loading facts in /var/lib/puppet/lib/facter/iptables.rb
Info: Loading facts in /var/lib/puppet/lib/facter/puppet_vardir.rb
Info: Loading facts in /var/lib/puppet/lib/facter/pe_version.rb
Info: Loading facts in /var/lib/puppet/lib/facter/root_home.rb
Info: Loading facts in /var/lib/puppet/lib/facter/concat_basedir.rb
Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find class jbosseap for dev-vl-api01.sbetenv.ads on node dev-vl-api01.sbetenv.ads
/usr/lib/ruby/site_ruby/1.8/puppet/indirector/rest.rb:65:in `deserialize'
/usr/lib/ruby/site_ruby/1.8/puppet/indirector/rest.rb:121:in `find'
/usr/lib/ruby/site_ruby/1.8/puppet/indirector/indirection.rb:191:in `find'
/usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:243:in `retrieve_new_catalog'
/usr/lib/ruby/site_ruby/1.8/puppet/util.rb:351:in `thinmark'
/usr/lib/ruby/1.8/benchmark.rb:308:in `realtime'
/usr/lib/ruby/site_ruby/1.8/puppet/util.rb:350:in `thinmark'
/usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:242:in `retrieve_new_catalog'
/usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:67:in `retrieve_catalog'
/usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:107:in `prepare_and_retrieve_catalog'
/usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:159:in `run'
/usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:45:in `run'
/usr/lib/ruby/site_ruby/1.8/puppet/agent/locker.rb:20:in `lock'
/usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:45:in `run'
/usr/lib/ruby/1.8/sync.rb:230:in `synchronize'
/usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:45:in `run'
/usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:119:in `with_client'
/usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:42:in `run'
/usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:84:in `run_in_fork'
/usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:41:in `run'
/usr/lib/ruby/site_ruby/1.8/puppet/application.rb:179:in `call'
/usr/lib/ruby/site_ruby/1.8/puppet/application.rb:179:in `controlled_run'
/usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:39:in `run'
/usr/lib/ruby/site_ruby/1.8/puppet/application/agent.rb:338:in `onetime'
/usr/lib/ruby/site_ruby/1.8/puppet/application/agent.rb:312:in `run_command'
/usr/lib/ruby/site_ruby/1.8/puppet/application.rb:364:in `run'
/usr/lib/ruby/site_ruby/1.8/puppet/application.rb:456:in `plugin_hook'
/usr/lib/ruby/site_ruby/1.8/puppet/application.rb:364:in `run'
/usr/lib/ruby/site_ruby/1.8/puppet/util.rb:504:in `exit_on_fail'
/usr/lib/ruby/site_ruby/1.8/puppet/application.rb:364:in `run'
/usr/lib/ruby/site_ruby/1.8/puppet/util/command_line.rb:132:in `run'
/usr/lib/ruby/site_ruby/1.8/puppet/util/command_line.rb:86:in `execute'
/usr/bin/puppet:4
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run

I am using puppet version 3.1.1
   
and OS is CentOS 6.4

Any help is appreciated

Pallavi
Reply all
Reply to author
Forward
0 new messages