Adam Hamner
2012-Aug-29 20:19 UTC
[Puppet Users] Puppet-Dashboard nodes showing up as unreported
Hello, I have followed the documentation at http://docs.puppetlabs.com/dashboard/manual/1.2/bootstrapping.html to try to setup dashboard but after I manually add a node it shows up as unreported. The agent has successfully completed a very basic catalog run just adding a file to the file-system. Dashboard v1.2 Puppet puppet-server.noarch 2.7.19-1.el6 SERVER: -bash-4.1$ cat /etc/puppet/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 [master] reports = store, http reporturl = http://us3sm2ppt001.comp.prod.local:3000/reports/upload [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 certname = us3sm2ppt001.comp.prod.local server = us3sm2ppt001.comp.prod.local report = true AGENT -bash-4.1$ cat /etc/puppet/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 server = us3sm2ppt001.comp.prod.local certname = us3sm2nn010r07.comp.prod.local report = true I am uncertain about where the master should be configured to send reports to. reports/upload doesn''t seem to exist and I just followed the default location in the documentation. -- 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/-/xNNacEjU660J. 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.
Peter Bukowinski
2012-Aug-29 21:46 UTC
Re: [Puppet Users] Puppet-Dashboard nodes showing up as unreported
Adam, in dashboard''s upper-left corner, do you see any pending tasks listed in the Background Tasks section? If so, then you simply need to start the delayed job workers (http://docs.puppetlabs.com/dashboard/manual/1.2/bootstrapping.html#starting-and-managing-delayed-job-workers) and they will start processing the backlogged puppet reports. -- Peter Bukowinski On Aug 29, 2012, at 1:19 PM, Adam Hamner <adamhamner00@gmail.com> wrote:> Hello, > I have followed the documentation at http://docs.puppetlabs.com/dashboard/manual/1.2/bootstrapping.html to try to setup dashboard but after I manually add a node it shows up as unreported. The agent has successfully completed a very basic catalog run just adding a file to the file-system. > > Dashboard v1.2 > Puppet puppet-server.noarch 2.7.19-1.el6 > > > SERVER: > -bash-4.1$ cat /etc/puppet/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 > [master] > reports = store, http > reporturl = http://us3sm2ppt001.comp.prod.local:3000/reports/upload > [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 > certname = us3sm2ppt001.comp.prod.local > server = us3sm2ppt001.comp.prod.local > report = true > > > AGENT > -bash-4.1$ cat /etc/puppet/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 > server = us3sm2ppt001.comp.prod.local > certname = us3sm2nn010r07.comp.prod.local > report = true > > I am uncertain about where the master should be configured to send reports to. reports/upload doesn''t seem to exist and I just followed the default location in the documentation. > -- > 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/-/xNNacEjU660J. > 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.-- 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.
Apparently Analagous Threads
- Trying to get tagmail to work
- classes.txt missing
- (New To Puppet)Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find class sudo for pupclient on node pupclient
- Puppet / Passenger SSL Problems with DRBD
- puppetmaster built via puppetd