[Puppet Users] Why agent report is so slow?
Hi, all: I use cron to run puppet agent, but recently i found the script takes too long time. After using '--debug', i got this log: 2012-09-13 15:19:53.928744500 debug: Finishing transaction 69941650538440 2012-09-13 15:19:53.928988500 debug: Storing state 2012-09-13 15:19:54.930995500 debug: Stored state in 1.00 seconds 2012-09-13 15:19:54.931145500 notice: Finished catalog run in 48.21 seconds 2012-09-13 15:20:03.721411500 debug: Value of 'preferred_serialization_format' (pson) is invalid for report, using default (b64_zlib_yaml) 2012-09-13 15:20:03.721578500 debug: report supports formats: b64_zlib_yaml raw yaml; using b64_zlib_yaml 2012-09-13 15:21:10.805932500 Puppet run done. The last 'Puppet run done' is a bash echo after puppet agent. So we can see it took 1 minute and more before the echo line. But if i set 'report = false' in puppet.conf, there is no such long time. Does puppet use this time to generate and send reports? How can i tune this? -- 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.
Re: [Puppet Users] RHEL Kickstart and Puppet certificates
Thank you everybody! :-) That are many ways to solve the problem. -- 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/-/GToEN-CTK_EJ. 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.
Re: [Puppet Users] AW: Issue with large directory content
Thanks for your answers so far.
But beware that the huge artifacts are *not* managed by Puppet (see recurse =
false). Actually it's a Maven repository filled by Nexus. Only the top
directory is managed by Puppet to have it in place and have correct access
rights. This worked well until I initially filled the repository with the
artifacts manually. That slowed down Puppet. Seems to me as Puppet will do some
recursive scanning, but that's just an assumption, since Puppet is running with
almost 100% CPU load.
I turned debug on in Puppet but will not see anything even after a few minutes.
Presumably I would see something if I let Puppet run just long enough. However,
it's a strange behaviour I've never experienced. And I think my configuration
is OK.
Bernd
On 09/13/2012 01:24 AM, Peter Brown wrote:
On 13 September 2012 00:12, Christopher Wood
christopher_w...@pobox.commailto:christopher_w...@pobox.com wrote:
I don't have enough information to say. You might want to run the master and
agent in debug mode to get more output, though.
puppet agent --debug --verbose --no-daemonize
Also, 100 GB? Any particular reason why you're not installing this using a
content distribution system or a large number of RPMs?
Recursing through A 100Gb directory will definitely slow down your puppet run.
If the contents of the directory are reasonably static an RPM would be
the best idea.
If it's not static a git or svn repo would be a better idea.
If you are tricky you can manage the checkouts of git or svn with
puppet as well.
I wrote a few tricky resources for this a while ago and they are
infinitely handy.
On Wed, Sep 12, 2012 at 04:08:13PM +0200, Bernd Adamowicz wrote:
No ideas at all?
-Ursprüngliche Nachricht-
Von: Bernd Adamowicz
Gesendet: Dienstag, 11. September 2012 16:16
An: puppet-users@googlegroups.commailto:puppet-users@googlegroups.com
Betreff: Issue with large directory content
Hi all,
I got this directory configuration:
file {
${codebase_ng::repository_mount}/${sonatype_work_dir}:
ensure = directory,
owner = $nexus_user,
group = $nexus_group,
mode= 0755,
recurse = false,
backup = false,
}
Today I added some 100GB of artifacts to a subdirectory of
${codebase_ng::repository_mount}/${sonatype_work_dir}. Now the result
is that the Puppet seems to run forever. If I uncomment this code,
Puppet finishes in 15 seconds. So I presume Puppet is doing some
recursive scanning of this directory. Could this be true? Is there a
know issue with large content of directories?
Thanks in advance!
Bernd
--
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.
[Puppet Users] yumrepo and notify
Hi everyone,
I trying to notify a cache clean when creating a yumrepository:
yumrepo { 'XXX':
descr= 'XX Packages',
baseurl = $url,
require = [ Yum::Key['0b6f8066'], ],
gpgcheck = '1',
enabled = '1',
notify = [ Exec['YUM Clean cache'], ],
}
exec { 'YUM Clean cache':
path= '/bin:/usr/bin:/usr/local/bin',
user= 'root',
logoutput = true,
refreshonly = true,
command = 'yum clean all --verbose',
}
And I am getting the following error on RedHat 6:
info: Retrieving plugin
info: Loading facts in /var/lib/puppet/lib/facter/root_home.rb
info: Loading facts in /var/lib/puppet/lib/facter/puppet_vardir.rb
info: Loading facts in /var/lib/puppet/lib/facter/facter_dot_d.rb
info: Loading facts in /var/lib/puppet/lib/facter/meminbytes.rb
err: Could not retrieve catalog from remote server: Error 400 on SERVER:
Can't synthesize edge: File[/etc/yum.repos.d/XXX.repo] -notifies- Exec[YUM
Clean cache] (param notify)
info: Not using expired catalog for .fqdn from cache; expired at Wed
Sep 12 17:03:31 +0200 2012
notice: Using cached catalog
err: Could not retrieve catalog; skipping run
Any idea what could be the problem?
Regards,
JM
--
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.
[Puppet Users] puppet-lint
Hi everyone, Is it possible not to notify error with puppet-lint when trailing whitespace are found in a comment line? Just asking. Regards, JM -- 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.
Re: [Puppet Users] puppet-lint
Hi, The README on Github has a nice section about disabling checks: https://github.com/rodjek/puppet-lint Try the --no-check name-check flag to disable a check, I guess for the trailing whitespace the --no-trailing-whitespace-check can be used. Regards, Anton On Sep 13, 2012, at 11:46 AM, Antidot SAS antidot...@gmail.com wrote: Hi everyone, Is it possible not to notify error with puppet-lint when trailing whitespace are found in a comment line? Just asking. Regards, JM -- 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. -- 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.
Re: [Puppet Users] puppet-lint
Hi, I don't want to remove the error when it is accurate just when it is in a comment line, just asking not a big deal though... On Thu, Sep 13, 2012 at 12:42 PM, Anton Lindström m...@antonlindstrom.comwrote: Hi, The README on Github has a nice section about disabling checks: https://github.com/rodjek/puppet-lint Try the --no-check name-check flag to disable a check, I guess for the trailing whitespace the --no-trailing-whitespace-check can be used. Regards, Anton On Sep 13, 2012, at 11:46 AM, Antidot SAS antidot...@gmail.com wrote: Hi everyone, Is it possible not to notify error with puppet-lint when trailing whitespace are found in a comment line? Just asking. Regards, JM -- 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. -- 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. -- 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.
AW: [Puppet Users] AW: Issue with large directory content
This keeps being weird. Simply thought to wait until Puppet finishes, but had
to quit after one and a half hour. Also tried 'ensure = present' instead of
'ensure = directory' with no success. No log output at all. Still
investigating. But any ideas still highly appreciated!
Bernd
Von: puppet-users@googlegroups.com [mailto:puppet-users@googlegroups.com] Im
Auftrag von Bernd Adamowicz
Gesendet: Donnerstag, 13. September 2012 10:46
An: puppet-users@googlegroups.com
Betreff: Re: [Puppet Users] AW: Issue with large directory content
Thanks for your answers so far.
But beware that the huge artifacts are *not* managed by Puppet (see recurse =
false). Actually it's a Maven repository filled by Nexus. Only the top
directory is managed by Puppet to have it in place and have correct access
rights. This worked well until I initially filled the repository with the
artifacts manually. That slowed down Puppet. Seems to me as Puppet will do some
recursive scanning, but that's just an assumption, since Puppet is running with
almost 100% CPU load.
I turned debug on in Puppet but will not see anything even after a few minutes.
Presumably I would see something if I let Puppet run just long enough. However,
it's a strange behaviour I've never experienced. And I think my configuration
is OK.
Bernd
On 09/13/2012 01:24 AM, Peter Brown wrote:
On 13 September 2012 00:12, Christopher Wood
christopher_w...@pobox.commailto:christopher_w...@pobox.com wrote:
I don't have enough information to say. You might want to run the master and
agent in debug mode to get more output, though.
puppet agent --debug --verbose --no-daemonize
Also, 100 GB? Any particular reason why you're not installing this using a
content distribution system or a large number of RPMs?
Recursing through A 100Gb directory will definitely slow down your puppet run.
If the contents of the directory are reasonably static an RPM would be
the best idea.
If it's not static a git or svn repo would be a better idea.
If you are tricky you can manage the checkouts of git or svn with
puppet as well.
I wrote a few tricky resources for this a while ago and they are
infinitely handy.
On Wed, Sep 12, 2012 at 04:08:13PM +0200, Bernd Adamowicz wrote:
No ideas at all?
-Ursprüngliche Nachricht-
Von: Bernd Adamowicz
Gesendet: Dienstag, 11. September 2012 16:16
An: puppet-users@googlegroups.commailto:puppet-users@googlegroups.com
Betreff: Issue with large directory content
Hi all,
I got this directory configuration:
file {
${codebase_ng::repository_mount}/${sonatype_work_dir}:
ensure = directory,
owner = $nexus_user,
group = $nexus_group,
mode= 0755,
recurse = false,
backup = false,
}
Today I added some 100GB of artifacts to a subdirectory of
${codebase_ng::repository_mount}/${sonatype_work_dir}. Now the result
is that the Puppet seems to run forever. If I uncomment this code,
Puppet finishes in 15 seconds. So I presume Puppet is doing some
recursive scanning of this directory. Could this be true? Is there a
know issue with large content of directories?
Thanks in advance!
Bernd
--
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.commailto:puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.commailto:puppet-users+unsubscr...@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+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Where to execute script to add server to Zabbix monitoring system?
You might be able to use generate() for this - it runs the command on the puppetmaster and returns the result to the client. Should be easy enough to use safely! On Tue, Sep 11, 2012 at 7:28 PM, JeremyCampbell jeremycampbel...@gmail.com wrote: I've written a script which adds a new server to our Zabbix monitoring system using their api. This script contains the api username and password so I wouldn't want it sitting on the puppet clients. I assume to execute it on the puppetmaster side I need to configure the script as a custom function? And to avoid the script from contacting the Zabbix server every run, it could write the host name to a file which it checks beforehand. Would that be the way to go or are there any better approaches? -- 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/-/zpww3ilJjlMJ. 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. -- 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.
[Puppet Users] Re: yumrepo and notify
On Thursday, September 13, 2012 4:13:26 AM UTC-5, A_SAAS wrote:
Hi everyone,
I trying to notify a cache clean when creating a yumrepository:
yumrepo { 'XXX':
descr= 'XX Packages',
baseurl = $url,
require = [ Yum::Key['0b6f8066'], ],
gpgcheck = '1',
enabled = '1',
notify = [ Exec['YUM Clean cache'], ],
}
exec { 'YUM Clean cache':
path= '/bin:/usr/bin:/usr/local/bin',
user= 'root',
logoutput = true,
refreshonly = true,
command = 'yum clean all --verbose',
}
And I am getting the following error on RedHat 6:
info: Retrieving plugin
info: Loading facts in /var/lib/puppet/lib/facter/root_home.rb
info: Loading facts in /var/lib/puppet/lib/facter/puppet_vardir.rb
info: Loading facts in /var/lib/puppet/lib/facter/facter_dot_d.rb
info: Loading facts in /var/lib/puppet/lib/facter/meminbytes.rb
err: Could not retrieve catalog from remote server: Error 400 on SERVER:
Can't synthesize edge: File[/etc/yum.repos.d/XXX.repo] -notifies- Exec[YUM
Clean cache] (param notify)
info: Not using expired catalog for .fqdn from cache; expired at Wed
Sep 12 17:03:31 +0200 2012
notice: Using cached catalog
err: Could not retrieve catalog; skipping run
Any idea what could be the problem?
My first guess would be a parse-order issue. Try moving the declaration of
the Exec before the declaration of the Yumrepo, or if they are in different
classes then make sure the Exec's class is parsed before the Yumrepo's. My
standard way to approach the latter situation would be to have the
Yumrepo's class 'include' the Exec's.
John
--
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/-/aNQO7QnFIngJ.
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.
Re: [Puppet Users] Re: yumrepo and notify
The exec and the yumrepo are declared in the same manifest even with
declaring the exec before, it doesn't help
On Thu, Sep 13, 2012 at 3:09 PM, jcbollinger john.bollin...@stjude.orgwrote:
On Thursday, September 13, 2012 4:13:26 AM UTC-5, A_SAAS wrote:
Hi everyone,
I trying to notify a cache clean when creating a yumrepository:
yumrepo { 'XXX':
descr= 'XX Packages',
baseurl = $url,
require = [ Yum::Key['0b6f8066'], ],
gpgcheck = '1',
enabled = '1',
notify = [ Exec['YUM Clean cache'], ],
}
exec { 'YUM Clean cache':
path= '/bin:/usr/bin:/usr/local/bin'**,
user= 'root',
logoutput = true,
refreshonly = true,
command = 'yum clean all --verbose',
}
And I am getting the following error on RedHat 6:
info: Retrieving plugin
info: Loading facts in /var/lib/puppet/lib/facter/**root_home.rb
info: Loading facts in /var/lib/puppet/lib/facter/**puppet_vardir.rb
info: Loading facts in /var/lib/puppet/lib/facter/**facter_dot_d.rb
info: Loading facts in /var/lib/puppet/lib/facter/**meminbytes.rb
err: Could not retrieve catalog from remote server: Error 400 on SERVER:
Can't synthesize edge: File[/etc/yum.repos.d/XXX.**repo] -notifies-
Exec[YUM Clean cache] (param notify)
info: Not using expired catalog for .fqdn from cache; expired at Wed
Sep 12 17:03:31 +0200 2012
notice: Using cached catalog
err: Could not retrieve catalog; skipping run
Any idea what could be the problem?
My first guess would be a parse-order issue. Try moving the declaration
of the Exec before the declaration of the Yumrepo, or if they are in
different classes then make sure the Exec's class is parsed before the
Yumrepo's. My standard way to approach the latter situation would be to
have the Yumrepo's class 'include' the Exec's.
John
--
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/-/aNQO7QnFIngJ.
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.
--
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.
RE: [Puppet Users] RHEL Kickstart and Puppet certificates
Mike - Just curious, what do you mean by using cnames as the maker intended ? Are you suggesting a CNAME per hostname mapping? Thanks, Steve Steve Nielsen VP, Open Source Engineering | comScore, Inc.(NASDAQ:SCOR) o +1 (312) 775-6473 | f +1 (312) 775-6495 | mailto:sniel...@comscore.com . Introducing Mobile Metrix 2.0 - The next generation of mobile behavioral measurement www.comscore.com/MobileMetrix -Original Message- From: puppet-users@googlegroups.com [mailto:puppet-users@googlegroups.com] On Behalf Of Michael Stahnke Sent: Thursday, September 13, 2012 12:33 AM To: puppet-users@googlegroups.com Subject: Re: [Puppet Users] RHEL Kickstart and Puppet certificates I used to just institute policy that hostnames could not be re-used. It had a few benefits beyond puppet, like application people not hard-coding hostnames and using cnames as the maker intended. Mike -- 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. -- 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.
Re: [Puppet Users] Re: yumrepo and notify
Ok my bad, finally I taught the error was the yumrepo but it wasn't. The
error appears because of the following:
file { '/etc/yum.repos.d/XXX.repo' :
ensure = absent,
path = '/etc/yum.repos.d/X.repo',
notify = [ Exec['YUM Clean cache'], ],
}
So I think the attribut 'ensure = absent' is not a good candidat for
notification.
Thx for helping
JM
On Thu, Sep 13, 2012 at 3:42 PM, Antidot SAS antidot...@gmail.com wrote:
The exec and the yumrepo are declared in the same manifest even with
declaring the exec before, it doesn't help
On Thu, Sep 13, 2012 at 3:09 PM, jcbollinger john.bollin...@stjude.orgwrote:
On Thursday, September 13, 2012 4:13:26 AM UTC-5, A_SAAS wrote:
Hi everyone,
I trying to notify a cache clean when creating a yumrepository:
yumrepo { 'XXX':
descr= 'XX Packages',
baseurl = $url,
require = [ Yum::Key['0b6f8066'], ],
gpgcheck = '1',
enabled = '1',
notify = [ Exec['YUM Clean cache'], ],
}
exec { 'YUM Clean cache':
path= '/bin:/usr/bin:/usr/local/bin'**,
user= 'root',
logoutput = true,
refreshonly = true,
command = 'yum clean all --verbose',
}
And I am getting the following error on RedHat 6:
info: Retrieving plugin
info: Loading facts in /var/lib/puppet/lib/facter/**root_home.rb
info: Loading facts in /var/lib/puppet/lib/facter/**puppet_vardir.rb
info: Loading facts in /var/lib/puppet/lib/facter/**facter_dot_d.rb
info: Loading facts in /var/lib/puppet/lib/facter/**meminbytes.rb
err: Could not retrieve catalog from remote server: Error 400 on SERVER:
Can't synthesize edge: File[/etc/yum.repos.d/XXX.**repo] -notifies-
Exec[YUM Clean cache] (param notify)
info: Not using expired catalog for .fqdn from cache; expired at Wed
Sep 12 17:03:31 +0200 2012
notice: Using cached catalog
err: Could not retrieve catalog; skipping run
Any idea what could be the problem?
My first guess would be a parse-order issue. Try moving the declaration
of the Exec before the declaration of the Yumrepo, or if they are in
different classes then make sure the Exec's class is parsed before the
Yumrepo's. My standard way to approach the latter situation would be to
have the Yumrepo's class 'include' the Exec's.
John
--
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/-/aNQO7QnFIngJ.
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.
--
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.
Re: [Puppet Users] puppet-lint
Hi, Why is it OK to have trailing whitespace in comments but not code? On Thursday, 13 September 2012 at 4:43 AM, Antidot SAS wrote: Hi, I don't want to remove the error when it is accurate just when it is in a comment line, just asking not a big deal though... On Thu, Sep 13, 2012 at 12:42 PM, Anton Lindström m...@antonlindstrom.com (mailto:m...@antonlindstrom.com) wrote: Hi, The README on Github has a nice section about disabling checks: https://github.com/rodjek/puppet-lint Try the --no-check name-check flag to disable a check, I guess for the trailing whitespace the --no-trailing-whitespace-check can be used. Regards, Anton On Sep 13, 2012, at 11:46 AM, Antidot SAS antidot...@gmail.com (mailto:antidot...@gmail.com) wrote: Hi everyone, Is it possible not to notify error with puppet-lint when trailing whitespace are found in a comment line? Just asking. Regards, JM -- 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 (mailto:puppet-users@googlegroups.com). To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com (mailto:puppet-users%2bunsubscr...@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 (mailto:puppet-users@googlegroups.com). To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com (mailto:puppet-users%2bunsubscr...@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 (mailto:puppet-users@googlegroups.com). To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com (mailto:puppet-users+unsubscr...@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+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] puppet-lint
Hey, Yep, I though the code was more important then the comment from a formatting point of view but I might be confused. On Thu, Sep 13, 2012 at 4:35 PM, Tim Sharpe t...@sharpe.id.au wrote: Hi, Why is it OK to have trailing whitespace in comments but not code? On Thursday, 13 September 2012 at 4:43 AM, Antidot SAS wrote: -- 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.
WG: [Puppet Users] AW: Issue with large directory content
Hope, the list doesn't blame me for spamming, but I'd just like to provide some
more information on my problem, still hoping someone can help.
Using the 'iostat' command while Puppet is stuck, I can clearly see that
there's a very high I/O on the disk:
Device: rrqm/s wrqm/s r/s w/s rsec/s wsec/s avgrq-sz
avgqu-sz await svctm %util
sda 0.00 0.00 0.00 0.00 0.00 0.00 0.00
0.00 0.00 0.00 0.00
dm-0 0.00 0.00 0.00 0.00 0.00 0.00 0.00
0.00 0.00 0.00 0.00
dm-1 0.00 0.00 0.00 0.00 0.00 0.00 0.00
0.00 0.00 0.00 0.00
fioa 0.00 0.00 163.00 5.00 31280.00 40.00 186.43
0.04 0.25 0.25 4.20
dm-2 0.00 0.00 0.00 0.00 0.00 0.00 0.00
0.00 0.00 0.00 0.00
dm-3 0.00 0.00 0.00 0.00 0.00 0.00 0.00
0.00 0.00 0.00 0.00
dm-4 0.00 0.00 0.00 0.00 0.00 0.00 0.00
0.00 0.00 0.00 0.00
dm-5 0.00 0.00 163.00 5.00 31280.00 40.00 186.43
0.04 0.25 0.25 4.20
dm-6 0.00 0.00 0.00 0.00 0.00 0.00 0.00
0.00 0.00 0.00 0.00
drbd0 0.00 0.00 163.00 5.00 31280.00 40.00 186.43
0.96 0.53 5.72 96.10
drbd1 0.00 0.00 0.00 0.00 0.00 0.00 0.00
0.00 0.00 0.00 0.00
* The 'drbd0' device is an HP IO Accelerator card
* The 'rsec/s' column for drbd0 shows the number of sectors read from disk per
second. This value is pretty low if Puppet is not running.
* The '%util' (CPU time during the I/O requests) column for drbd0 shows that
the device is almost in saturation
* This is the mount point for drbd0: '/dev/ drbd0 on /repository' and
'/repository/sonatype-work' is the directory hosted by Puppet
Again, this is the configuration:
file {
/repository/sonatype-work:
ensure = directory,
owner = $nexus_user,
group = $nexus_group,
mode= 0755,
recurse = false,
backup = false,
}
For me it still seems there's a kind of recursive scanning done by Puppet
though 'recurse' is set to false.
Thanks for helping,
Bernd
Von: puppet-users@googlegroups.com [mailto:puppet-users@googlegroups.com] Im
Auftrag von Bernd Adamowicz
Gesendet: Donnerstag, 13. September 2012 14:45
An: 'puppet-users@googlegroups.com'
Betreff: AW: [Puppet Users] AW: Issue with large directory content
This keeps being weird. Simply thought to wait until Puppet finishes, but had
to quit after one and a half hour. Also tried 'ensure = present' instead of
'ensure = directory' with no success. No log output at all. Still
investigating. But any ideas still highly appreciated!
Bernd
Von: puppet-users@googlegroups.com [mailto:puppet-users@googlegroups.com] Im
Auftrag von Bernd Adamowicz
Gesendet: Donnerstag, 13. September 2012 10:46
An: puppet-users@googlegroups.com
Betreff: Re: [Puppet Users] AW: Issue with large directory content
Thanks for your answers so far.
But beware that the huge artifacts are *not* managed by Puppet (see recurse =
false). Actually it's a Maven repository filled by Nexus. Only the top
directory is managed by Puppet to have it in place and have correct access
rights. This worked well until I initially filled the repository with the
artifacts manually. That slowed down Puppet. Seems to me as Puppet will do some
recursive scanning, but that's just an assumption, since Puppet is running with
almost 100% CPU load.
I turned debug on in Puppet but will not see anything even after a few minutes.
Presumably I would see something if I let Puppet run just long enough. However,
it's a strange behaviour I've never experienced. And I think my configuration
is OK.
Bernd
On 09/13/2012 01:24 AM, Peter Brown wrote:
On 13 September 2012 00:12, Christopher Wood christopher_w...@pobox.com wrote:
I don't have enough information to say. You might want to run the master and
agent in debug mode to get more output, though.
puppet agent --debug --verbose --no-daemonize
Also, 100 GB? Any particular reason why you're not installing this using a
content distribution system or a large number of RPMs?
Recursing through A 100Gb directory will definitely slow down your puppet run.
If the contents of the directory are reasonably static an RPM would be
the best idea.
If it's not static a git or svn repo would be a better idea.
If you are tricky you can manage the checkouts of git or svn with
puppet as well.
I wrote a few tricky resources for this a while ago and they are
infinitely handy.
On Wed, Sep 12, 2012 at 04:08:13PM +0200, Bernd Adamowicz wrote:
No ideas at all?
-Ursprüngliche Nachricht-
Von: Bernd Adamowicz
Gesendet: Dienstag, 11. September 2012 16:16
An:
Re: [Puppet Users] Skipped Resources 'running on a host' ?
On Wed, Sep 12, 2012 at 3:43 PM, Douglas Garstang doug.garst...@gmail.comwrote: My puppet client is producing this: debug: /Schedule[daily]: Skipping device resources because running on a host debug: /Schedule[monthly]: Skipping device resources because running on a host debug: /Schedule[hourly]: Skipping device resources because running on a host debug: /Schedule[never]: Skipping device resources because running on a host debug: /Schedule[weekly]: Skipping device resources because running on a host debug: /Schedule[puppet]: Skipping device resources because running on a host When used with the --summarize option, it causes 6 skipped resources. Puppet in turn, exits with exit code 2. How can I remove these and presumably get puppet to then return 0? Could you provide enough information to reproduce the problem? -Jeff -- 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.
[Puppet Users] nodes including modules that are not assigned in the site.pp file
This is my /etc/puppet/manifests/site.pp
Can anyone see why nodes
5051,5052,5010,5110,5116,5102,5117,5118,5121,6012,and 5052
would grab/include the very last nodes module? node server616 module tomcat6
File { ignore = '.svn' }
node 'server6010' {
include centos6
}
node 'server6011' {
include centos6
include tomcat
}
node 'server6012' {
include centos6
include tomcat
}
node 'server6013' {
include centos6
include tomcat
}
node 'server6014' {
include centos6
include tomcat
}
node 'server6015' {
include centos6
include postgres
}
node 'server5010' {
include centos5
}
node 'server5039' {
include centos5
include apache
}
node 'server5051' {
include centos5
}
node 'server5071' {
include ldap
}
node 'server5052' {
include centos5
}
node 'server5092' {
include centos5
include mongodb
}
node 'igsxgjdtweb01' {
include centos5
include apache-dev
}
node 'server5110' {
include centos5
}
node 'server5116' {
include centos5
}
node 'server5117' {
include centos5
include clamav
include shakecast
}
node 'server5118' {
include centos5
}
node 'server5121' {
include centos5
include postgres
include mysql
}
node 'serverisvmlks1' {
include centos5
}
node 'server616' {
include tomcat6
}
--
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/-/r4V6d780q-UJ.
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.
Re: [Puppet Users] Why agent report is so slow?
On Thu, Sep 13, 2012 at 12:31 AM, flex frostyn...@gmail.com wrote: I use cron to run puppet agent, but recently i found the script takes too long time. After using '--debug', i got this log: 2012-09-13 15:19:53.928744500 debug: Finishing transaction 69941650538440 2012-09-13 15:19:53.928988500 debug: Storing state 2012-09-13 15:19:54.930995500 debug: Stored state in 1.00 seconds 2012-09-13 15:19:54.931145500 notice: Finished catalog run in 48.21 seconds 2012-09-13 15:20:03.721411500 debug: Value of 'preferred_serialization_format' (pson) is invalid for report, using default (b64_zlib_yaml) 2012-09-13 15:20:03.721578500 debug: report supports formats: b64_zlib_yaml raw yaml; using b64_zlib_yaml 2012-09-13 15:21:10.805932500 Puppet run done. The last 'Puppet run done' is a bash echo after puppet agent. So we can see it took 1 minute and more before the echo line. But if i set 'report = false' in puppet.conf, there is no such long time. Does puppet use this time to generate and send reports? In essence, yes: we build the report structure as we go, but transforming it for submission, and sending it over the wire, certainly take time. That is proportional to the number of resources you have in your catalog, including things like recursive file copies or tidies. How can i tune this? There really isn't any way to improve performance: there isn't (much) you can do to improve YAML output performance - although Telly, Puppet 3.0.0, will be a bit faster at building YAML when it is released. You could check to see if the performance problem comes from network transmission problems, but really there isn't much you can do to improve a single HTTPS request, which is how we submit the report back to the the master. -- Daniel Pittman ⎋ Puppet Labs Developer – http://puppetlabs.com ♲ Made with 100 percent post-consumer electrons -- 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.
Re: [Puppet Users] AW: Issue with large directory content
On Thu, Sep 13, 2012 at 8:55 AM, Bernd Adamowicz bernd.adamow...@esailors.de wrote: For me it still seems there's a kind of recursive scanning done by Puppet though 'recurse' is set to false. This does look like a bug, as you've got a directory with no remote source, no recursion, and all you want to do is to enforce owner/group/mode on it. That shouldn't be an I/O intensive process at all. -- 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.
[Puppet Users] Re: nodes including modules that are not assigned in the site.pp file
On Thursday, September 13, 2012 12:17:38 PM UTC-6, PaulS wrote:
This is my /etc/puppet/manifests/site.pp
Can anyone see why nodes
5051,5052,5010,5110,5116,5102,5117,5118,5121,6012,and 5052
would grab/include the very last nodes module? node server616 module
tomcat6
File { ignore = '.svn' }
node 'server6010' {
include centos6
}
node 'server6011' {
include centos6
include tomcat
}
node 'server6012' {
include centos6
include tomcat
}
node 'server6013' {
include centos6
include tomcat
}
node 'server6014' {
include centos6
include tomcat
}
node 'server6015' {
include centos6
include postgres
}
node 'server5010' {
include centos5
}
node 'server5039' {
include centos5
include apache
}
node 'server5051' {
include centos5
}
node 'server5071' {
include ldap
}
node 'server5052' {
include centos5
}
node 'server5092' {
include centos5
include mongodb
}
node 'igsxgjdtweb01' {
include centos5
include apache-dev
}
node 'server5110' {
include centos5
}
node 'server5116' {
include centos5
}
node 'server5117' {
include centos5
include clamav
include shakecast
}
node 'server5118' {
include centos5
}
node 'server5121' {
include centos5
include postgres
include mysql
}
node 'serverisvmlks1' {
include centos5
}
node 'server616' {
include tomcat6
}
UPDATE===
It must have been my /etc/puppet/modules/tomcat6/manifests/init.pp
could putting something like
class centos6 {
file {/etc/security:
owner = root,
source = puppet:///tomcat6/files/etc/security,
path = /etc/security,
recurse = true,
ensure = present,
selinux_ignore_defaults = true,
}
}
Note the “class centos6” and not “class tomcat6”
Would that push the files that have “include centos6” in my
/etc/puppet/manifests/site.pp?
--
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/-/vovUVa3cyVQJ.
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.
Re: [Puppet Users] nodes including modules that are not assigned in the site.pp file
Hi,
Is tomcat6 included elsewhere in your manifest?
Can you grep for 'include tomcat6' and check?
Cheers,
Den
On 14/09/2012, at 4:17, PaulS paul_spe...@hotmail.com wrote:
This is my /etc/puppet/manifests/site.pp
Can anyone see why nodes
5051,5052,5010,5110,5116,5102,5117,5118,5121,6012,and 5052
would grab/include the very last nodes module? node server616 module tomcat6
File { ignore = '.svn' }
node 'server6010' {
include centos6
}
node 'server6011' {
include centos6
include tomcat
}
node 'server6012' {
include centos6
include tomcat
}
node 'server6013' {
include centos6
include tomcat
}
node 'server6014' {
include centos6
include tomcat
}
node 'server6015' {
include centos6
include postgres
}
node 'server5010' {
include centos5
}
node 'server5039' {
include centos5
include apache
}
node 'server5051' {
include centos5
}
node 'server5071' {
include ldap
}
node 'server5052' {
include centos5
}
node 'server5092' {
include centos5
include mongodb
}
node 'igsxgjdtweb01' {
include centos5
include apache-dev
}
node 'server5110' {
include centos5
}
node 'server5116' {
include centos5
}
node 'server5117' {
include centos5
include clamav
include shakecast
}
node 'server5118' {
include centos5
}
node 'server5121' {
include centos5
include postgres
include mysql
}
node 'serverisvmlks1' {
include centos5
}
node 'server616' {
include tomcat6
}
--
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/-/r4V6d780q-UJ.
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.
--
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.
[Puppet Users] Re: nodes including modules that are not assigned in the site.pp file
On Thursday, September 13, 2012 12:17:38 PM UTC-6, PaulS wrote:
This is my /etc/puppet/manifests/site.pp
Can anyone see why nodes
5051,5052,5010,5110,5116,5102,5117,5118,5121,6012,and 5052
would grab/include the very last nodes module? node server616 module
tomcat6
File { ignore = '.svn' }
node 'server6010' {
include centos6
}
node 'server6011' {
include centos6
include tomcat
}
node 'server6012' {
include centos6
include tomcat
}
node 'server6013' {
include centos6
include tomcat
}
node 'server6014' {
include centos6
include tomcat
}
node 'server6015' {
include centos6
include postgres
}
node 'server5010' {
include centos5
}
node 'server5039' {
include centos5
include apache
}
node 'server5051' {
include centos5
}
node 'server5071' {
include ldap
}
node 'server5052' {
include centos5
}
node 'server5092' {
include centos5
include mongodb
}
node 'igsxgjdtweb01' {
include centos5
include apache-dev
}
node 'server5110' {
include centos5
}
node 'server5116' {
include centos5
}
node 'server5117' {
include centos5
include clamav
include shakecast
}
node 'server5118' {
include centos5
}
node 'server5121' {
include centos5
include postgres
include mysql
}
node 'serverisvmlks1' {
include centos5
}
node 'server616' {
include tomcat6
}
grep tomcat6 /etc/puppet/modules/tomcat6/manifests/init.pp
class tomcat6 {
source = puppet:///tomcat6/files/usr/local,
class tomcat6 {
class tomcat6 {
source = puppet:///tomcat6/files/etc/sysconfig,
class tomcat6 {
source = puppet:///tomcat6/files/etc/security,
class tomcat6 {
And
grep 'include tomcat6' /etc/puppet/manifests/site.pp
include tomcat6
just one
node 'igsfort616' {
include tomcat6
}
--
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/-/vNUOyC3y5joJ.
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.
Re: WG: [Puppet Users] AW: Issue with large directory content
Hi,
Not sure if I can help but just have couple of questions.
How long does it take to do a 'find' on the directory or a 'stat'?
Have you tried running the client with --verbose --debug --evaltrace
--summarize?
Are you trying to set any permissions inside that directory elsewhere in the
manifest?
I would expect recurse = false not to do anything too, but (and this should
throw an error) can you set recurselimit? If so, does it make any difference?
HTH
Den
On 14/09/2012, at 1:55, Bernd Adamowicz bernd.adamow...@esailors.de wrote:
Hope, the list doesn't blame me for spamming, but I'd just like to provide
some more information on my problem, still hoping someone can help.
Using the 'iostat' command while Puppet is stuck, I can clearly see that
there's a very high I/O on the disk:
Device: rrqm/s wrqm/s r/s w/s rsec/s wsec/s avgrq-sz
avgqu-sz await svctm %util
sda 0.00 0.000.000.00 0.00 0.00 0.00
0.000.00 0.00 0.00
dm-0 0.00 0.000.000.00 0.00 0.00 0.00
0.000.00 0.00 0.00
dm-1 0.00 0.000.000.00 0.00 0.00 0.00
0.000.00 0.00 0.00
fioa 0.00 0.00 163.005.00 31280.0040.00 186.43
0.040.25 0.25 4.20
dm-2 0.00 0.000.000.00 0.00 0.00 0.00
0.000.00 0.00 0.00
dm-3 0.00 0.000.000.00 0.00 0.00 0.00
0.000.00 0.00 0.00
dm-4 0.00 0.000.000.00 0.00 0.00 0.00
0.000.00 0.00 0.00
dm-5 0.00 0.00 163.005.00 31280.0040.00 186.43
0.040.25 0.25 4.20
dm-6 0.00 0.000.000.00 0.00 0.00 0.00
0.000.00 0.00 0.00
drbd0 0.00 0.00 163.005.00 31280.0040.00 186.43
0.960.53 5.72 96.10
drbd1 0.00 0.000.000.00 0.00 0.00 0.00
0.000.00 0.00 0.00
* The 'drbd0' device is an HP IO Accelerator card
* The 'rsec/s' column for drbd0 shows the number of sectors read from disk
per second. This value is pretty low if Puppet is not running.
* The '%util' (CPU time during the I/O requests) column for drbd0 shows that
the device is almost in saturation
* This is the mount point for drbd0: '/dev/ drbd0 on /repository' and
'/repository/sonatype-work' is the directory hosted by Puppet
Again, this is the configuration:
file {
/repository/sonatype-work:
ensure = directory,
owner = $nexus_user,
group = $nexus_group,
mode= 0755,
recurse = false,
backup = false,
}
For me it still seems there's a kind of recursive scanning done by Puppet
though 'recurse' is set to false.
Thanks for helping,
Bernd
Von: puppet-users@googlegroups.com [mailto:puppet-users@googlegroups.com] Im
Auftrag von Bernd Adamowicz
Gesendet: Donnerstag, 13. September 2012 14:45
An: 'puppet-users@googlegroups.com'
Betreff: AW: [Puppet Users] AW: Issue with large directory content
This keeps being weird. Simply thought to wait until Puppet finishes, but had
to quit after one and a half hour. Also tried 'ensure = present' instead of
'ensure = directory' with no success. No log output at all. Still
investigating. But any ideas still highly appreciated!
Bernd
Von: puppet-users@googlegroups.com [mailto:puppet-users@googlegroups.com] Im
Auftrag von Bernd Adamowicz
Gesendet: Donnerstag, 13. September 2012 10:46
An: puppet-users@googlegroups.com
Betreff: Re: [Puppet Users] AW: Issue with large directory content
Thanks for your answers so far.
But beware that the huge artifacts are *not* managed by Puppet (see recurse
= false). Actually it's a Maven repository filled by Nexus. Only the top
directory is managed by Puppet to have it in place and have correct access
rights. This worked well until I initially filled the repository with the
artifacts manually. That slowed down Puppet. Seems to me as Puppet will do
some recursive scanning, but that's just an assumption, since Puppet is
running with almost 100% CPU load.
I turned debug on in Puppet but will not see anything even after a few
minutes. Presumably I would see something if I let Puppet run just long
enough. However, it's a strange behaviour I've never experienced. And I think
my configuration is OK.
Bernd
On 09/13/2012 01:24 AM, Peter Brown wrote:
On 13 September 2012 00:12, Christopher Wood christopher_w...@pobox.com
wrote:
I don't have enough information to say. You might want to run the master and
agent in debug mode to get more output, though.
puppet agent --debug --verbose --no-daemonize
Also, 100 GB? Any particular reason why you're not installing this using a
content
[Puppet Users] pe version of puppet, vmware provisioning with from template with guest customization
Hi All, I'm using puppet enterprise and am getting a feel for the vmware provisioning. I've been able to provision vms by using: puppet node_vmware create NameOfMyTemplate That sort of works, but I basically have an identical copy of the original vm i created a template from. Same mac address, hostname, etc. in vSphere, you can create a vm from a template and give it a guest customization file which will set the hostname, autogenerate the mac address as well as other things. I'd like to do this from puppet but there doesn't appear to be an option to apply a customization file. If that's not possible, maybe another approach is possible. Basically i want to be able to autoprovision virtual machines. With just creating from a clone, i can't even get the vm on the network so it's basically unreachable to apply any puppet scripts that would allow me to manage configurations. Thanks for any help, -- 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/-/idL3TVma9yQJ. 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.
[Puppet Users] Announce: Puppet Dashboard 1.2.11 Available
Puppet Dashboard 1.2.11 is a maintenance and bugfix release of Puppet Dashboard. This release is available for download at: https://downloads.puppetlabs.com/dashboard/puppet-dashboard-1.2.11.tar.gz Debian packages are available at https://apt.puppetlabs.com RPM packages are available at https://yum.puppetlabs.com See the Verifying Puppet Download section at: http://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet Please report feedback via the Puppet Labs Redmine site, using an affected version of 1.2.11: http://projects.puppetlabs.com/projects/dashboard Documentation is available at: http://docs.puppetlabs.com/dashboard/index.html Puppet Dashboard 1.2.11 Highlights (#15196) Make items per page configurable This commit adds the ability to specify the number of specific items per page displayed by dashboard in the settings.yml file, including nodes, classes, groups and reports per page. Autorefresh link gen fixed to work under passenger Autorefresh link generation did not take root_path for the application into consideration. Using File.join() to try and avoid multiple /'s getting into generated url which would cause routing problems. Shift to using packaging repo for packaging tasks This release introduces Dashboard's use of the packaging repo at https://github.com/puppetlabs/packaging for packaging automation. From source, doing a rake package:bootstrap clones packaging tasks into ext/packaging and adds rake tasks for packaging of tar, srpm, rpm, and deb using tools such as rpmbuild and debuild, as well as puppetlabs-namespaced tasks that use chroot environment tools and are keyed to specifically interacting with the puppetlabs environment. The packaging repo works in tandem with the new package-builder modules designed to set up hosts for packaging, https://github.com/puppetlabs/puppetlabs-rpmbuilder, and https://github.com/puppetlabs/puppetlabs-debbuilder. This is very much a work in progress, but a model for how packaging automation could improve across many Puppet Labs projects. Puppet Dashboard 1.2.11 Changelog Boyan Tabakov (2): d6619a1 Updated debian postinst script to link properly the settings.yml file to puppet-dashboard config directory. a8a97dc Fixed linking of database.yml in debian postinst to use absolute path. Erik Dalén (1): ffe7bdd (#15196) Make items per page configurable Jani Mikkonen (1): df5a20a Autorefresh link gen fixed to work under passenger Joshua Harlan Lifton (2): c64c013 (#10477) Clean up log files by moving message to debug a8e2586 Fix spec tests broken by commit c64c013 Matthaus Litteken (2): 8806f60 (#15291) Add Vendor tag to Puppet-Dashboard spec file c0592af Update CHANGELOG, VERSION for 1.2.11 Moses Mendoza (10): 3abf9df Move packaging up to ext to avoid conflict with pkging repo 71d302a re-template debian changelog 4201990 Fixup redhat spec erb for packaging repo 42030b8 Remove obsolete package.rake file da22ddd Add packaging data files 8f03e6c Add VERSION file to source e6f6acf Fixup Rakefile for setting up packaging repo 101af75 Update supported debian versions and cows 20a109a Update mocks to accurately reflect dashboard builds dd88f0b Update CHANGELOG, VERSION for 1.2.11-rc1 Will Hopper (2): 63a0634 Add release number variable to packaging rake task 5eccef2 (#15523) Update Debian packaging rake task to create the debian and original tarballs -- 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.
[Puppet Users] I am trying to copy over a authorized_key file over to all the servers using puppet but it doe snot see to work. can any one help?
This is how my init.pp files looks below and I get this error err: Could
not retrieve catalog from remote server: Error 400 on SERVER: Could not
find class sshkey for ct-eng-pats02-devint.caretools.ent at
/etc/puppet/manifests/nodes/pats02.pp:22 on node
ct-eng-pats02-devint.caretools.ent
warning: Not using cache on failed catalog
err: Could not retrieve catalog; skipping run
class sshkey {
# file { /root/.ssh:
# ensure = directory,
# owner = root,
# group = root,
# mode = 600,
# }
exec {'mkdir -p /root/.ssh':
unless = 'test -d /root/.ssh',
}
file {
/root/.ssh/authorized_keys:
ensure = file,
source = puppet:///sshkey/authorized_keys,
owner = root,
group = root,
mode = 600;
}
}
--
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/-/kwISVzF-vA8J.
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.
Re: [Puppet Users] Re: yumrepo and notify
On 13 September 2012 23:09, jcbollinger john.bollin...@stjude.org wrote:
On Thursday, September 13, 2012 4:13:26 AM UTC-5, A_SAAS wrote:
Hi everyone,
I trying to notify a cache clean when creating a yumrepository:
yumrepo { 'XXX':
descr= 'XX Packages',
baseurl = $url,
require = [ Yum::Key['0b6f8066'], ],
gpgcheck = '1',
enabled = '1',
notify = [ Exec['YUM Clean cache'], ],
}
exec { 'YUM Clean cache':
path= '/bin:/usr/bin:/usr/local/bin',
user= 'root',
logoutput = true,
refreshonly = true,
command = 'yum clean all --verbose',
}
And I am getting the following error on RedHat 6:
info: Retrieving plugin
info: Loading facts in /var/lib/puppet/lib/facter/root_home.rb
info: Loading facts in /var/lib/puppet/lib/facter/puppet_vardir.rb
info: Loading facts in /var/lib/puppet/lib/facter/facter_dot_d.rb
info: Loading facts in /var/lib/puppet/lib/facter/meminbytes.rb
err: Could not retrieve catalog from remote server: Error 400 on SERVER:
Can't synthesize edge: File[/etc/yum.repos.d/XXX.repo] -notifies- Exec[YUM
Clean cache] (param notify)
info: Not using expired catalog for .fqdn from cache; expired at Wed
Sep 12 17:03:31 +0200 2012
notice: Using cached catalog
err: Could not retrieve catalog; skipping run
Any idea what could be the problem?
My first guess would be a parse-order issue. Try moving the declaration of
the Exec before the declaration of the Yumrepo, or if they are in different
classes then make sure the Exec's class is parsed before the Yumrepo's. My
standard way to approach the latter situation would be to have the Yumrepo's
class 'include' the Exec's.
Just as a point, the order things appear in a manifest has no impact
of what gets executed first.
Its generally random unless you enforce an ordering scheme with the
various ways of doing that. (require and/or resource chaining and
such)
John
--
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/-/aNQO7QnFIngJ.
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.
--
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.
Re: [Puppet Users] I am trying to copy over a authorized_key file over to all the servers using puppet but it doe snot see to work. can any one help?
Puppet probably can't find the class you have declared.
How are you including the init.pp file?
Is this your global init.pp file?
One question.
Why aren't you using the builtin ssh_authorized_key type?
Have a look here.
http://docs.puppetlabs.com/references/latest/type.html#sshauthorizedkey
It's best to manage your users with puppet as well but that's just as easy.
Also using an exec to create a directory is a bit strange.
Just use the file type and put ensure = directory.
On 14 September 2012 10:23, JGonza1 jgonza1...@gmail.com wrote:
This is how my init.pp files looks below and I get this error err: Could not
retrieve catalog from remote server: Error 400 on SERVER: Could not find
class sshkey for ct-eng-pats02-devint.caretools.ent at
/etc/puppet/manifests/nodes/pats02.pp:22 on node
ct-eng-pats02-devint.caretools.ent
warning: Not using cache on failed catalog
err: Could not retrieve catalog; skipping run
class sshkey {
# file { /root/.ssh:
# ensure = directory,
# owner = root,
# group = root,
# mode = 600,
# }
exec {'mkdir -p /root/.ssh':
unless = 'test -d /root/.ssh',
}
file {
/root/.ssh/authorized_keys:
ensure = file,
source = puppet:///sshkey/authorized_keys,
owner = root,
group = root,
mode = 600;
}
}
--
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/-/kwISVzF-vA8J.
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.
--
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.
