Dear all
I am trying to view the puppet reports in the foreman gui, but foreman tell
me it is not configured.
I have on the agent in section agent
report = true
in the puppet master /var/lib/puppet/reports
total 48
-rw-r–r-- 1 root root 1904 25. Jul 14:51 foreman.rb
drwxr-x— 2 root root 4096 10. Jul 09:56 vm6739.muc.baag
drwxr-x— 2 puppet puppet 36864 25. Jul 11:09 vm6740.muc.baag
$foreman_url='http://rh6-puppet-master:3000'
In the puppet.conf section main
reports = log, foreman
and I get an error message in /var/log/messages
Jul 25 14:06:23 vm6739 puppet-master[2023]: No report named 'foreman'
Can somebody please help me?
Best regards
Andreas
This is the wrong dir, the foreman.rb needs adding inside the
puppetmaster installation, usually alongside the "tagmail.rb" file.
If you're using RHEL6, this would usually be:
/usr/lib/ruby/site_ruby/1.8/puppet/reports/foreman.rb
···
On 25/07/13 14:00, Andreas Dvorak wrote:
> Dear all
>
> I am trying to view the puppet reports in the foreman gui, but foreman
> tell me it is not configured.
> I have on the agent in section agent
> report = true
>
> in the puppet master /var/lib/puppet/reports
> total 48
> -rw-r--r-- 1 root root 1904 25. Jul 14:51 foreman.rb
> drwxr-x--- 2 root root 4096 10. Jul 09:56 vm6739.muc.baag
> drwxr-x--- 2 puppet puppet 36864 25. Jul 11:09 vm6740.muc.baag
–
Dominic Cleal
Red Hat Engineering
Hi Dominic,
thank you for the answer but it still does not work.
now I have
ls -l /usr/lib/ruby/site_ruby/1.8/puppet/reports
total 32
-rw-r–r-- 1 root root 1904 26. Jul 08:42 foreman.rb
-rw-r–r-- 1 root root 894 13. Jun 20:15 http.rb
-rw-r–r-- 1 root root 326 13. Jun 20:15 log.rb
-rw-r–r-- 1 root root 4240 13. Jun 20:15 rrdgraph.rb
-rw-r–r-- 1 root root 1921 13. Jun 20:15 store.rb
-rw-r–r-- 1 root root 5809 13. Jun 20:15 tagmail.rb
I executed this
[root@vm6740 tmp]# puppet agent --server=rh6-puppet-master.baag
–no-daemonize --verbose --onetime
Info: Retrieving plugin
Info: Caching catalog for vm6740.muc.baag
Info: Applying configuration version '1374822789'
Notice: /Stage[main]/Test1/File[/var/tmp/test1.txt]/ensure: defined content
as '{md5}5d6b05dc20045b7cd84567722828a87d'
Notice: Finished catalog run in 0.21 seconds
The message in /var/log/messages "No report named 'foreman'" is gone.
Here is my puppet.conf
[master]
Zertifikatsname
certname=rh6-puppet-master.baag
[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 = log, foreman
[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
Best regards,
Andreas
···
Am Donnerstag, 25. Juli 2013 15:00:58 UTC+2 schrieb Andreas Dvorak:
Dear all
I am trying to view the puppet reports in the foreman gui, but foreman
tell me it is not configured.
I have on the agent in section agent
report = true
in the puppet master /var/lib/puppet/reports
total 48
-rw-r–r-- 1 root root 1904 25. Jul 14:51 foreman.rb
drwxr-x— 2 root root 4096 10. Jul 09:56 vm6739.muc.baag
drwxr-x— 2 puppet puppet 36864 25. Jul 11:09 vm6740.muc.baag
$foreman_url=‘http://rh6-puppet-master:3000’
In the puppet.conf section main
reports = log, foreman
and I get an error message in /var/log/messages
Jul 25 14:06:23 vm6739 puppet-master[2023]: No report named 'foreman’
Can somebody please help me?
Best regards
Andreas
the path of report is error,
e.g. /usr/lib/ruby/1.8/puppet/reports/foreman.rb,
/usr/lib/ruby/site_ruby/1.8/puppet/reports/foreman.rb,
/var/lib/gems/1.8/gems/puppet-2.6.4/lib/puppet/reports/foreman.rb or
/usr/lib/ruby/vendor_ruby/puppet/reports.
linkto : Foreman :: Manual
在 2013年7月25日星期四UTC+8下午9时00分58秒，Andreas Dvorak写道：
···
>
> Dear all
>
> I am trying to view the puppet reports in the foreman gui, but foreman
> tell me it is not configured.
> I have on the agent in section agent
> report = true
>
> in the puppet master /var/lib/puppet/reports
> total 48
> -rw-r--r-- 1 root root 1904 25. Jul 14:51 foreman.rb
> drwxr-x--- 2 root root 4096 10. Jul 09:56 vm6739.muc.baag
> drwxr-x--- 2 puppet puppet 36864 25. Jul 11:09 vm6740.muc.baag
> $foreman_url='http://rh6-puppet-master:3000'
>
> In the puppet.conf section main
> reports = log, foreman
>
> and I get an error message in /var/log/messages
> Jul 25 14:06:23 vm6739 puppet-master[2023]: No report named 'foreman'
> Can somebody please help me?
>
> Best regards
> Andreas
>
Hi Andreas,
Which version of Puppet are you using? On Puppet 2.6, you will need to
add "report = true" to the [agent] section of puppet.conf to enable
reporting. If you're on newer versions, it's not needed, so probably
not that.
Can you check /var/log/foreman/production.log immediately after running
the Puppet agent? You should see a logging block starting:
Started POST "/reports/create?format=yml"
Can you paste this bit of logging?
···
--
Dominic Cleal
Red Hat Engineering
On 26/07/13 08:20, Andreas Dvorak wrote:
Hi Dominic,
thank you for the answer but it still does not work.
now I have
ls -l /usr/lib/ruby/site_ruby/1.8/puppet/reports
total 32
-rw-r–r-- 1 root root 1904 26. Jul 08:42 foreman.rb
-rw-r–r-- 1 root root 894 13. Jun 20:15 http.rb
-rw-r–r-- 1 root root 326 13. Jun 20:15 log.rb
-rw-r–r-- 1 root root 4240 13. Jun 20:15 rrdgraph.rb
-rw-r–r-- 1 root root 1921 13. Jun 20:15 store.rb
-rw-r–r-- 1 root root 5809 13. Jun 20:15 tagmail.rb
I executed this
[root@vm6740 tmp]# puppet agent --server=rh6-puppet-master.baag
–no-daemonize --verbose --onetime
Info: Retrieving plugin
Info: Caching catalog for vm6740.muc.baag
Info: Applying configuration version '1374822789’
Notice: /Stage[main]/Test1/File[/var/tmp/test1.txt]/ensure: defined
content as '{md5}5d6b05dc20045b7cd84567722828a87d’
Notice: Finished catalog run in 0.21 seconds
The message in /var/log/messages “No report named ‘foreman’” is gone.
Here is my puppet.conf
[master]
Zertifikatsname
certname=rh6-puppet-master.baag
[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 = log, foreman
[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
Best regards,
Andreas
Am Donnerstag, 25. Juli 2013 15:00:58 UTC+2 schrieb Andreas Dvorak:
Dear all
I am trying to view the puppet reports in the foreman gui, but
foreman tell me it is not configured.
I have on the agent in section agent
report = true
in the puppet master /var/lib/puppet/reports
total 48
-rw-r--r-- 1 root root 1904 25. Jul 14:51 foreman.rb
drwxr-x--- 2 root root 4096 10. Jul 09:56 vm6739.muc.baag
drwxr-x--- 2 puppet puppet 36864 25. Jul 11:09 vm6740.muc.baag
$foreman_url='http://rh6-puppet-master:3000
<http://rh6-puppet-master:3000>'
In the puppet.conf section main
reports = log, foreman
and I get an error message in /var/log/messages
Jul 25 14:06:23 vm6739 puppet-master[2023]: No report named 'foreman'
Can somebody please help me?
Best regards
Andreas
–
You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/groups/opt_out.
Hi Dominic,
I user puppet 3.2.2 on Redhat 6.4
after the agent run I find this in the log file pwd
Started POST "/reports/create?format=yml" for 10.15.67.39 at 2013-07-26
09:40:18 +0200
Processing by ReportsController#create as YML
Parameters: {"report"=>"[FILTERED]"}
No smart proxy server found on ["vm6739.muc.baag"] and is not in
trusted_puppetmaster_hosts
Redirected to http://rh6-puppet-master:3000/users/login
Filter chain halted as :require_puppetmaster_or_login rendered or redirected
Completed 403 Forbidden in 6ms (ActiveRecord: 0.5ms)
"Forbidden" does not look good. Is there a problem with the alias and
hostname oder login permission the the foreman?
nslookup rh6-puppet-master
Server: 10.10.10.207
Address: 10.10.10.207#53
rh6-puppet-master.baag canonical name = vm6739.muc.baag.
Name: vm6739.muc.baag
Address: 10.15.67.39
Best regards
Andreas
···
Am Freitag, 26. Juli 2013 09:25:19 UTC+2 schrieb Dominic Cleal:
Hi Andreas,
Which version of Puppet are you using? On Puppet 2.6, you will need to
add “report = true” to the [agent] section of puppet.conf to enable
reporting. If you’re on newer versions, it’s not needed, so probably
not that.
Can you check /var/log/foreman/production.log immediately after running
the Puppet agent? You should see a logging block starting:
Started POST “/reports/create?format=yml”
Can you paste this bit of logging?
–
Dominic Cleal
Red Hat Engineering
On 26/07/13 08:20, Andreas Dvorak wrote:
Hi Dominic,
thank you for the answer but it still does not work.
now I have
ls -l /usr/lib/ruby/site_ruby/1.8/puppet/reports
total 32
-rw-r–r-- 1 root root 1904 26. Jul 08:42 foreman.rb
-rw-r–r-- 1 root root 894 13. Jun 20:15 http.rb
-rw-r–r-- 1 root root 326 13. Jun 20:15 log.rb
-rw-r–r-- 1 root root 4240 13. Jun 20:15 rrdgraph.rb
-rw-r–r-- 1 root root 1921 13. Jun 20:15 store.rb
-rw-r–r-- 1 root root 5809 13. Jun 20:15 tagmail.rb
I executed this
[root@vm6740 tmp]# puppet agent --server=rh6-puppet-master.baag
–no-daemonize --verbose --onetime
Info: Retrieving plugin
Info: Caching catalog for vm6740.muc.baag
Info: Applying configuration version '1374822789’
Notice: /Stage[main]/Test1/File[/var/tmp/test1.txt]/ensure: defined
content as '{md5}5d6b05dc20045b7cd84567722828a87d’
Notice: Finished catalog run in 0.21 seconds
The message in /var/log/messages “No report named ‘foreman’” is gone.
Here is my puppet.conf
[master]
Zertifikatsname
certname=rh6-puppet-master.baag
[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 = log, foreman
[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
Best regards,
Andreas
Am Donnerstag, 25. Juli 2013 15:00:58 UTC+2 schrieb Andreas Dvorak:
Dear all
I am trying to view the puppet reports in the foreman gui, but
foreman tell me it is not configured.
I have on the agent in section agent
report = true
in the puppet master /var/lib/puppet/reports
total 48
-rw-r--r-- 1 root root 1904 25. Jul 14:51 foreman.rb
drwxr-x--- 2 root root 4096 10. Jul 09:56 vm6739.muc.baag
drwxr-x--- 2 puppet puppet 36864 25. Jul 11:09 vm6740.muc.baag
$foreman_url='http://rh6-puppet-master:3000
<http://rh6-puppet-master:3000>'
In the puppet.conf section main
reports = log, foreman
and I get an error message in /var/log/messages
Jul 25 14:06:23 vm6739 puppet-master[2023]: No report named
‘foreman’
Can somebody please help me?
Best regards
Andreas
–
You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to foreman-user...@googlegroups.com <javascript:>.
To post to this group, send email to forema...@googlegroups.com<javascript:>.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/groups/opt_out.
Foreman authorises access to these puppetmaster interfaces by checking
for a Foreman proxy server registered on the same hostname.
Do you have a foreman-proxy service running and registered on the
puppetmaster? It's looking for one with a hostname of "vm6739.muc.baag".
You can also add the hostname "vm6739.muc.baag" to the
trusted_puppetmaster_hosts list in More>Settings>Auth, which will allow
your puppetmaster to upload reports.
···
--
Dominic Cleal
Red Hat Engineering
On 26/07/13 08:51, Andreas Dvorak wrote:
Hi Dominic,
I user puppet 3.2.2 on Redhat 6.4
after the agent run I find this in the log file pwd
Started POST “/reports/create?format=yml” for 10.15.67.39 at 2013-07-26
09:40:18 +0200
Processing by ReportsController#create as YML
Parameters: {“report”=>"[FILTERED]"}
No smart proxy server found on [“vm6739.muc.baag”] and is not in
trusted_puppetmaster_hosts
Redirected to http://rh6-puppet-master:3000/users/login
Filter chain halted as :require_puppetmaster_or_login rendered or redirected
Completed 403 Forbidden in 6ms (ActiveRecord: 0.5ms)
“Forbidden” does not look good. Is there a problem with the alias and
hostname oder login permission the the foreman?
nslookup rh6-puppet-master
Server: 10.10.10.207
Address: 10.10.10.207#53
rh6-puppet-master.baag canonical name = vm6739.muc.baag.
Name: vm6739.muc.baag
Address: 10.15.67.39
Best regards
Andreas
Am Freitag, 26. Juli 2013 09:25:19 UTC+2 schrieb Dominic Cleal:
Hi Andreas,
Which version of Puppet are you using? On Puppet 2.6, you will need to
add "report = true" to the [agent] section of puppet.conf to enable
reporting. If you're on newer versions, it's not needed, so probably
not that.
Can you check /var/log/foreman/production.log immediately after running
the Puppet agent? You should see a logging block starting:
Started POST "/reports/create?format=yml"
Can you paste this bit of logging?
--
Dominic Cleal
Red Hat Engineering
On 26/07/13 08:20, Andreas Dvorak wrote:
> Hi Dominic,
>
> thank you for the answer but it still does not work.
>
> now I have
> ls -l /usr/lib/ruby/site_ruby/1.8/puppet/reports
> total 32
> -rw-r--r-- 1 root root 1904 26. Jul 08:42 foreman.rb
> -rw-r--r-- 1 root root 894 13. Jun 20:15 http.rb
> -rw-r--r-- 1 root root 326 13. Jun 20:15 log.rb
> -rw-r--r-- 1 root root 4240 13. Jun 20:15 rrdgraph.rb
> -rw-r--r-- 1 root root 1921 13. Jun 20:15 store.rb
> -rw-r--r-- 1 root root 5809 13. Jun 20:15 tagmail.rb
> I executed this
> [root@vm6740 tmp]# puppet agent --server=rh6-puppet-master.baag
> --no-daemonize --verbose --onetime
> Info: Retrieving plugin
> Info: Caching catalog for vm6740.muc.baag
> Info: Applying configuration version '1374822789'
> Notice: /Stage[main]/Test1/File[/var/tmp/test1.txt]/ensure: defined
> content as '{md5}5d6b05dc20045b7cd84567722828a87d'
> Notice: Finished catalog run in 0.21 seconds
> The message in /var/log/messages "No report named 'foreman'" is gone.
>
> Here is my puppet.conf
> [master]
> # Zertifikatsname
> certname=rh6-puppet-master.baag
> [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 = log, foreman
> [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
> Best regards,
> Andreas
>
> Am Donnerstag, 25. Juli 2013 15:00:58 UTC+2 schrieb Andreas Dvorak:
>
> Dear all
>
> I am trying to view the puppet reports in the foreman gui, but
> foreman tell me it is not configured.
> I have on the agent in section agent
> report = true
>
> in the puppet master /var/lib/puppet/reports
> total 48
> -rw-r--r-- 1 root root 1904 25. Jul 14:51 foreman.rb
> drwxr-x--- 2 root root 4096 10. Jul 09:56 vm6739.muc.baag
> drwxr-x--- 2 puppet puppet 36864 25. Jul 11:09 vm6740.muc.baag
> $foreman_url='http://rh6-puppet-master:3000
<http://rh6-puppet-master:3000>
> <http://rh6-puppet-master:3000>'
>
> In the puppet.conf section main
> reports = log, foreman
>
> and I get an error message in /var/log/messages
> Jul 25 14:06:23 vm6739 puppet-master[2023]: No report named
'foreman'
> Can somebody please help me?
>
> Best regards
> Andreas
>
> --
> You received this message because you are subscribed to the Google
> Groups "Foreman users" group.
> To unsubscribe from this group and stop receiving emails from it,
send
> an email to foreman-user...@googlegroups.com <javascript:>.
> To post to this group, send email to forema...@googlegroups.com
<javascript:>.
> Visit this group at http://groups.google.com/group/foreman-users
<http://groups.google.com/group/foreman-users>.
> For more options, visit https://groups.google.com/groups/opt_out
<https://groups.google.com/groups/opt_out>.
>
>
–
You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/groups/opt_out.
Thank you, the configuration of trusted_puppetmaster_hosts was the solution.
Now I see reports.
Best regards
Andreas
···
Am Freitag, 26. Juli 2013 09:53:57 UTC+2 schrieb Dominic Cleal:
Foreman authorises access to these puppetmaster interfaces by checking
for a Foreman proxy server registered on the same hostname.
Do you have a foreman-proxy service running and registered on the
puppetmaster? It’s looking for one with a hostname of “vm6739.muc.baag”.
You can also add the hostname “vm6739.muc.baag” to the
trusted_puppetmaster_hosts list in More>Settings>Auth, which will allow
your puppetmaster to upload reports.
–
Dominic Cleal
Red Hat Engineering
On 26/07/13 08:51, Andreas Dvorak wrote:
Hi Dominic,
I user puppet 3.2.2 on Redhat 6.4
after the agent run I find this in the log file pwd
Started POST “/reports/create?format=yml” for 10.15.67.39 at 2013-07-26
09:40:18 +0200
Processing by ReportsController#create as YML
Parameters: {“report”=>"[FILTERED]"}
No smart proxy server found on [“vm6739.muc.baag”] and is not in
trusted_puppetmaster_hosts
Redirected to http://rh6-puppet-master:3000/users/login
Filter chain halted as :require_puppetmaster_or_login rendered or
redirected
Completed 403 Forbidden in 6ms (ActiveRecord: 0.5ms)
“Forbidden” does not look good. Is there a problem with the alias and
hostname oder login permission the the foreman?
nslookup rh6-puppet-master
Server: 10.10.10.207
Address: 10.10.10.207#53
rh6-puppet-master.baag canonical name = vm6739.muc.baag.
Name: vm6739.muc.baag
Address: 10.15.67.39
Best regards
Andreas
Am Freitag, 26. Juli 2013 09:25:19 UTC+2 schrieb Dominic Cleal:
Hi Andreas,
Which version of Puppet are you using? On Puppet 2.6, you will need
to
add "report = true" to the [agent] section of puppet.conf to enable
reporting. If you're on newer versions, it's not needed, so
probably
not that.
Can you check /var/log/foreman/production.log immediately after
running
the Puppet agent? You should see a logging block starting:
Started POST "/reports/create?format=yml"
Can you paste this bit of logging?
--
Dominic Cleal
Red Hat Engineering
On 26/07/13 08:20, Andreas Dvorak wrote:
> Hi Dominic,
>
> thank you for the answer but it still does not work.
>
> now I have
> ls -l /usr/lib/ruby/site_ruby/1.8/puppet/reports
> total 32
> -rw-r--r-- 1 root root 1904 26. Jul 08:42 foreman.rb
> -rw-r--r-- 1 root root 894 13. Jun 20:15 http.rb
> -rw-r--r-- 1 root root 326 13. Jun 20:15 log.rb
> -rw-r--r-- 1 root root 4240 13. Jun 20:15 rrdgraph.rb
> -rw-r--r-- 1 root root 1921 13. Jun 20:15 store.rb
> -rw-r--r-- 1 root root 5809 13. Jun 20:15 tagmail.rb
> I executed this
> [root@vm6740 tmp]# puppet agent --server=rh6-puppet-master.baag
> --no-daemonize --verbose --onetime
> Info: Retrieving plugin
> Info: Caching catalog for vm6740.muc.baag
> Info: Applying configuration version '1374822789'
> Notice: /Stage[main]/Test1/File[/var/tmp/test1.txt]/ensure:
defined
> content as '{md5}5d6b05dc20045b7cd84567722828a87d'
> Notice: Finished catalog run in 0.21 seconds
> The message in /var/log/messages "No report named 'foreman'" is
gone.
>
> Here is my puppet.conf
> [master]
> # Zertifikatsname
> certname=rh6-puppet-master.baag
> [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 = log, foreman
> [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
> Best regards,
> Andreas
>
> Am Donnerstag, 25. Juli 2013 15:00:58 UTC+2 schrieb Andreas > Dvorak:
>
> Dear all
>
> I am trying to view the puppet reports in the foreman gui, but
> foreman tell me it is not configured.
> I have on the agent in section agent
> report = true
>
> in the puppet master /var/lib/puppet/reports
> total 48
> -rw-r--r-- 1 root root 1904 25. Jul 14:51 foreman.rb
> drwxr-x--- 2 root root 4096 10. Jul 09:56 vm6739.muc.baag
> drwxr-x--- 2 puppet puppet 36864 25. Jul 11:09 vm6740.muc.baag
> $foreman_url='http://rh6-puppet-master:3000
<http://rh6-puppet-master:3000>
> <http://rh6-puppet-master:3000>'
>
> In the puppet.conf section main
> reports = log, foreman
>
> and I get an error message in /var/log/messages
> Jul 25 14:06:23 vm6739 puppet-master[2023]: No report named
'foreman'
> Can somebody please help me?
>
> Best regards
> Andreas
>
> --
> You received this message because you are subscribed to the Google
> Groups "Foreman users" group.
> To unsubscribe from this group and stop receiving emails from it,
send
> an email to foreman-user...@googlegroups.com <javascript:>.
> To post to this group, send email to forema...@googlegroups.com
<javascript:>.
> Visit this group at http://groups.google.com/group/foreman-users
<http://groups.google.com/group/foreman-users>.
> For more options, visit https://groups.google.com/groups/opt_out
<https://groups.google.com/groups/opt_out>.
>
>
–
You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to foreman-user...@googlegroups.com <javascript:>.
To post to this group, send email to forema...@googlegroups.com<javascript:>.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/groups/opt_out.
