Hi.
Scenario: Install puppet/puppet-dashboard successfully, puppet is run by
passenger. Changes are push from master to client perfectly.
Issue: Nodes are not reporting on dashboard. When: Never/actually.
apache2 vhost
1.name= puppetmasterd
Listen 8140
<VirtualHost *.8140>
Servername xlupupet01
........
........
</VirtualHost>
2. name = dashboard
<VirtualHost *.80>
Servername dashboard.example.com
........
........
</VirtualHost>
puppet master --- > puppet.conf
[master]
# Where puppet agent stores the last run report in yaml format.
# The default value is '$statedir/last_run_report.yaml'.
lastrunreport = /var/lib/puppet/state/last_run_report.yaml
# The server to send transaction reports to.
# report_server = puppet
# report_server = xlupupet01
# Whether to send reports after every transaction.
# report = true
# The port to communicate with the report_server.
# report_port = 8140
* report_port = 80*
# Where puppet agent stores the last run report summary in yaml format.
# (Deprecated for 'report_server') The server to which to send
transaction reports.
# reportserver = puppet
# reports, allowing you to correlate changes on your hosts to the
source version on the server.
# The directory in which to store reports
# The default value is '$vardir/reports'.
*reportdir = /var/lib/puppet/reports*
# reported in its facts)
# The URL used by the http reports processor to send reports
# The default value is 'http://localhost:3000/reports/upload'.
*reporturl = http://dashboard.example.com/reports/upload*
# The list of reports to generate. All reports are looked for
# in `puppet/reports/name.rb`, and multiple report names should be
*reports = store, http*
# The 'from' email address for the reports.
# The default value is 'report@xlupupet01.'.
# reportfrom = report@xlupupet01.
# The mapping between reporting tags and email addresses.
# The server through which to send email reports.
# This should match how often the hosts report back to the server.
# Directories for each reporting host will be created under
puppet client --- > puppet.conf
[main]
server=xlupupet01
logdir=/var/log/puppet
vardir=/var/lib/puppet
ssldir=/var/lib/puppet/ssl
rundir=/var/run/puppet
factpath=$vardir/lib/facter
templatedir=$confdir/templates
prerun_command=/etc/puppet/etckeeper-commit-pre
postrun_command=/etc/puppet/etckeeper-commit-post
*reports=store, http
report=true
reporturl= http://dashboard.example.com/reports/upload*
runinterval=3600
Storie: Troubleshoot for a while with not success.
I will thanks, any idea.
El viernes, 4 de mayo de 2012 13:23:32 UTC-3, Nan Liu escribió:
>
> 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 view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/v6AdrZkSmZoJ.
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.
