On Tue, May 8, 2012 at 9:53 AM, Kaya Saman <kayasa...@gmail.com> wrote: > On Fri, May 4, 2012 at 5:23 PM, Nan Liu <n...@puppetlabs.com> wrote: >> On Fri, May 4, 2012 at 3:59 AM, Kaya Saman <kayasa...@gmail.com> wrote: >>> Hi, >>> >>> I am still learning Puppet meaning that I'm still struggling through things. >>> >>> >>> I have setup Puppet on CentOS 6.x (latest release), installed the >>> Puppet Labs repos and followed the instructions on the site: >>> >>> http://docs.puppetlabs.com/guides/setting_up.html >>> >>> So far I am able to get the server to sign hosts and run: puppet agent >>> --test on the host successfully (which is more luck then I had with >>> the Puppet training ISO). >>> >>> >>> With regards to the dashboard I have gone through this documentation: >>> >>> http://docs.puppetlabs.com/dashboard/index.html >>> >>> >>> Which has got me to be able to get the Puppet Dash in my web browser. >>> >>> My issue is that I have added nodes to the Dash but they are claiming >>> to be unreported?? >>> >>> >>> I entered the FQDN's of both server and host, the Parameters, Groups, >>> and Classes sections are blank; but unfortunately the Dash is claiming >>> that the hosts are not reporting in? >>> >>> >>> Puppet Client (puppet.conf): >>> >>> [main] >>> # The Puppet log directory. >>> # The default value is '$vardir/log'. >>> logdir = /var/log/puppet >>> >>> # Where Puppet PID files are kept. >>> # The default value is '$vardir/run'. >>> rundir = /var/run/puppet >>> >>> # Where SSL certificates are kept. >>> # The default value is '$confdir/ssl'. >>> ssldir = $vardir/ssl >>> >>> >>> [agent] >>> # The file in which puppetd stores a list of the classes >>> # associated with the retrieved configuratiion. Can be loaded in >>> # the separate ``puppet`` executable using the ``--loadclasses`` >>> # option. >>> # The default value is '$confdir/classes.txt'. >>> classfile = $vardir/classes.txt >>> >>> # Where puppetd caches the local configuration. An >>> # extension indicating the cache format is added automatically. >>> # The default value is '$confdir/localconfig'. >>> localconfig = $vardir/localconfig >>> >>> report = true >>> >>> server = ps.jabber.com >>> >>> Puppet Server (puppet.conf): >>> >>> [main] >>> # The Puppet log directory. >>> # The default value is '$vardir/log'. >>> logdir = /var/log/puppet >>> >>> # Where Puppet PID files are kept. >>> # The default value is '$vardir/run'. >>> rundir = /var/run/puppet >>> >>> # Where SSL certificates are kept. >>> # The default value is '$confdir/ssl'. >>> ssldir = $vardir/ssl >>> >>> reports = store, http >>> reporturl = http://ps.jabber.com:3000/reports >>> >>> [agent] >>> # The file in which puppetd stores a list of the classes >>> # associated with the retrieved configuratiion. Can be loaded in >>> # the separate ``puppet`` executable using the ``--loadclasses`` >>> # option. >>> # The default value is '$confdir/classes.txt'. >>> classfile = $vardir/classes.txt >>> >>> # Where puppetd caches the local configuration. An >>> # extension indicating the cache format is added automatically. >>> # The default value is '$confdir/localconfig'. >>> localconfig = $vardir/localconfig >>> >>> >>> report = true >>> >>> server = ps.jabber.com >>> >>> >>> Here is output of puppet agent --test on client: >>> >>> >>> # puppet agent --test >>> info: Caching catalog for pc.jabber.com >>> info: Applying configuration version '1336044868' >>> notice: Finished catalog run in 0.01 seconds >>> >>> >>> ...and server: >>> >>> >>> puppet agent --test >>> info: Caching catalog for ps.jabber.com >>> info: Applying configuration version '1336044868' >>> notice: Finished catalog run in 0.04 seconds >>> >>> >>> >>> Can anybody help me? >> >> Based on the configuration provided above, it appears you still need >> to configure puppet so dashboard is the external node terminus: >> >> http://docs.puppetlabs.com/dashboard/manual/1.2/bootstrapping.html#using-dashboard-for-node-classification >> >> HTH, >> >> Nan >> >> -- >> 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+unsubscr...@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/puppet-users?hl=en. >> > > Thanks Nan for the help, however not when the new config is added.... > puppet-dashboard service won't start? > > I have checked the logs to see if there is anything defined but > nothing comes out as being a guide to what the error maybe :-( > > > Regards, > > Kaya
Additionally something weird that has happened this morning is that my Puppet agents won't sync up?? I've tested the time, ran ntpdate <server> and then enabled ntpd; this unfortunately doesn't help. What is strange is that it was working fine last week, even with reboots.??? The logs don't really give any information other then: "Could not retrieve catalog from remote server, not using cache on failed catalog, could not retrieve catalog, could not send report" I will continue debugging but I don't understand what's going on! --K -- 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+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
