On Nov 2, 7:33 pm, Christopher Wood
wrote:
> It's worth mentioning that find -exec this way forks a separate copy of find
> for each file. You'll notice how much slower this is on a really large set of
> files (possibly larger than yours). If you have a recursion-capable chown
> it's quicker to
On Thursday, November 3, 2011 8:27:01 PM UTC+4, Adrien Thebo wrote:
>
> Could you post the operatingsystem fact alongside the architecture
> fact for facter by itself, and then the facts as presented by puppet?
r3:/var/log# facter | grep -e '\(operatingsys\|architec\)'
architecture => amd64
ope
How do I add a new root password? What should I encrypt the password with that
foreman accepts? MD5, SHA1?
Corey Osman
co...@logicminds.biz
678-348-0582 Pacific Time
Green I.T and Datacenter Automation Specialist
--
You received this message because you are subscribed to the Google Groups
thanks a lot
On Nov 3, 3:44 am, Jo Rhett wrote:
> --logdest=/some/file/name on the cli, or set as a parameter in puppet.conf.
> Right now it appears your logdest is syslog.
>
> On Nov 2, 2011, at 11:45 AM, Kanishka Hettiarachchi wrote:
>
>
>
>
>
> > Have noticed puppet agent continue to write a
Thanks so much for the input
On Nov 2, 2:57 pm, Christopher Wood
wrote:
> On Wed, Nov 02, 2011 at 11:45:11AM -0700, Kanishka Hettiarachchi wrote:
> > Hello all,
>
> > Have noticed puppet agent continue to write agent runtime output to /
> > var/log/messages, although $vardir, logdir default to /v
Why not document how the client decides the runtime, and how to adjust it?
On Nov 3, 2011, at 1:08 PM, Christopher Wood wrote:
> I thought the chosen run time was selected on the agent. It sounds like
> you'll have to reconfigure the agent to have it decide differently. So far
> your options see
On Nov 3, 2011, at 1:01 PM, Adam Crews wrote:
> This is exactly why I use cron instead of the daemon.
we "puppet kick" a lot.
--
Jo Rhett
Net Consonance : consonant endings by net philanthropy, open source and other
randomness
--
You received this message because you are subscribed to the Goo
On Nov 1, 10:45 pm, Nan Liu wrote:
> On Tue, Nov 1, 2011 at 12:50 PM, Rob Terhaar wrote:
> > Hi All,
>
> > Does anyone have a good git pre-commit hook that's compatible with
> > Puppet 2.7? The example pre-commit hook on the PuppetLabs wiki[1] no
> > longer works, because the puppet binary no l
On 2011-11-03 02:17 , Dominique Servelle wrote:
> the 10/31/2011 ubuntu upgrade facter from
> facter_1.5.6-2ubuntu2.1_all.deb facter_1.5.6-2ubuntu2.2_all.deb.
>
> Since nothing work and I've got a message : "Could not run Puppet
> configuration client: Could not retrieve local facts: execution
> e
PuppetCommander is another option:
http://projects.puppetlabs.com/projects/mcollective-plugins/wiki/ToolPuppetcommander
It deals with 'splay' globally instead of on a per node basis with
random sleeps.
ken.
On Thu, Nov 3, 2011 at 8:08 PM, Christopher Wood
wrote:
> On Thu, Nov 03, 2011 at 12:41
On Thu, Nov 03, 2011 at 12:41:50PM -0700, Jo Rhett wrote:
>Nigel, As you've said, the time chosen for the run cycle will be
>consistent. All of these settings are already set -- this isn't a
>question of how to change how often to run, it's how to affect the chosen
>runtime?
I tho
On Thu, Nov 3, 2011 at 12:41 PM, Jo Rhett wrote:
> Nigel, As you've said, the time chosen for the run cycle will be consistent.
> All of these settings are already set -- this isn't a question of how to
> change how often to run, it's how to affect the chosen runtime?
> I've got an awful lot of s
As far as concat goes, I wouldn't call my concat resource and my
concat::fragment resource by the same name. In theory it shouldn't
break anything, but...
On Thu, Nov 3, 2011 at 12:20 PM, Douglas Garstang
wrote:
> Actually I can. That's sweet! Thanks!
>
> On Thu, Nov 3, 2011 at 12:10 PM, Dou
Nigel, As you've said, the time chosen for the run cycle will be consistent.
All of these settings are already set -- this isn't a question of how to change
how often to run, it's how to affect the chosen runtime?
I've got an awful lot of systems (> 100) which have decided to all roll at 28
an
Actually I can. That's sweet! Thanks!
On Thu, Nov 3, 2011 at 12:10 PM, Douglas Garstang
wrote:
> Just from looking at the example there, it doesn't appear that I can
> call sysctl::conf more than once That's what I like about concat,
> ie each module that needs to add to it can do so indi
Just from looking at the example there, it doesn't appear that I can
call sysctl::conf more than once That's what I like about concat,
ie each module that needs to add to it can do so individually.
Doug.
On Thu, Nov 3, 2011 at 12:04 PM, Mark Christian wrote:
> Can't speak to concat, but you
Can't speak to concat, but you might consider using augeas for managing
/etc/sysctl.conf. There is an excellent example of this at:
http://projects.puppetlabs.com/projects/1/wiki/Puppet_Augeas , see "Working
Examples"
> -Original Message-
> From: puppet-users@googlegroups.com [mailto:p
All,
Trying to use the concat module with:
class sysctl::common {
include concat::setup
concat {
'/etc/sysctl.conf':
owner => 'root',
group => 'root',
mode => '0644';
}
concat::fragment {
'/etc/sysctl.conf':
Thanks all. That worked.
On 11/03/2011 08:36 AM, Nigel Kersten wrote:
FWIW the bug was put in as:
https://projects.puppetlabs.com/issues/10442
(adding these comments to it)
On Thu, Nov 3, 2011 at 5
Could you post the operatingsystem fact alongside the architecture
fact for facter by itself, and then the facts as presented by puppet?
On Mon, Oct 31, 2011 at 11:33 AM, Alexander Azarov wrote:
> The simplest default, that is WEBrick I guess.
>
> On Monday, October 31, 2011 10:28:12 PM UTC+4, Ad
On Thu, Nov 3, 2011 at 8:52 AM, Randall Hansen wrote:
> On Thu, Nov 3, 2011 at 8:38 AM, Nigel Kersten
> wrote:
>
> > In your puppet.conf agent block:
> > ...
> > # The maximum time to delay before runs. Defaults to being the same
> as the
> > # run interval.
> > # The default value i
(splay inline)
On Thu, Nov 03, 2011 at 08:38:39AM -0700, Nigel Kersten wrote:
>On Thu, Nov 3, 2011 at 8:36 AM, Jo Rhett <[1]jrh...@netconsonance.com>
>wrote:
>
> For a long time it appeared that run cycles were fairly balanced -- a
> few every 30 seconds over the 30 minute perio
On Thu, Nov 3, 2011 at 8:38 AM, Nigel Kersten wrote:
> In your puppet.conf agent block:
> ...
> # The maximum time to delay before runs. Defaults to being the same as
> the
> # run interval.
> # The default value is '$runinterval'.
> splaylimit = 1800
Having this uncommented as
On Thu, Nov 3, 2011 at 8:36 AM, Jo Rhett wrote:
> For a long time it appeared that run cycles were fairly balanced -- a few
> every 30 seconds over the 30 minute period. Right now I'm seeing more than
> 100 systems hit in the same minute: 28 and 58 minutes after the hour. Is
> there some way to
For a long time it appeared that run cycles were fairly balanced -- a few every
30 seconds over the 30 minute period. Right now I'm seeing more than 100
systems hit in the same minute: 28 and 58 minutes after the hour. Is there
some way to alter the spread of these systems back to even out the
FWIW the bug was put in as:
https://projects.puppetlabs.com/issues/10442
(adding these comments to it)
On Thu, Nov 3, 2011 at 5:19 AM, Luke Bigum wrote:
> FYI this is a lot faster to delete everything from a MySQL table:
>
> TRUNCATE TABLE delayed_job_failures;
>
> On Nov 3, 12:10 pm, Evgeny
On Wed, Nov 2, 2011 at 1:00 PM, Craig White wrote:
>
> On Nov 2, 2011, at 12:50 PM, Nigel Kersten wrote:
>
> >
> >
> > On Wed, Nov 2, 2011 at 12:13 PM, Craig White
> wrote:
> >
> > err: Could not retrieve catalog from remote server: Error 400 on SERVER:
> No support for http method POST
> > warn
On Nov 2, 9:57 am, Baptiste Grenier
wrote:
> Hello,
>
> Le 31/10/11 16:09, jcbollinger t l scripta :
>
>
>
>
>
> > On Oct 28, 10:07 am, Baptiste Grenier
> > wrote:
>
> > > I am trying to define the modules' run order like this:
>
> > You are running up against a common source of confusion: the
On Nov 2, 3:31 am, Johan Sunnerstig
wrote:
> Hi.
>
> I've been reading up on inheritance, parameterized classes and whatnot, and
> basically wish to see whether I'm thinking right or if I'm just confused(more
> than usual).
> I'll use a trivial NFS module as an example since it should cover th
On Nov 3, 5:28 am, Russell Howe wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 02/11/11 22:15, Douglas Garstang wrote:> Ok, what am I doing wrong here?
> I'm including
> > splunkforwarder::app_server and it's all working except that it
> > appears that splunkforwarder::common i
FYI this is a lot faster to delete everything from a MySQL table:
TRUNCATE TABLE delayed_job_failures;
On Nov 3, 12:10 pm, Evgeny wrote:
> then only it will help:
>
> delete FROM `delayed_job_failures` WHERE 1
--
You received this message because you are subscribed to the Google Groups
"Puppe
then only it will help:
delete FROM `delayed_job_failures` WHERE 1
--
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+u
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/11/11 22:15, Douglas Garstang wrote:
> Ok, what am I doing wrong here? I'm including
> splunkforwarder::app_server and it's all working except that it
> appears that splunkforwarder::common isn't including
> splunkforwarder::enabled...
>
> class
gotcha, now it´s working again.
thanks RI !
--
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
the 10/31/2011 ubuntu upgrade facter from
facter_1.5.6-2ubuntu2.1_all.deb facter_1.5.6-2ubuntu2.2_all.deb.
Since nothing work and I've got a message : "Could not run Puppet
configuration client: Could not retrieve local facts: execution
expired"
All the clients and the server are running the last
--logdest=/some/file/name on the cli, or set as a parameter in puppet.conf.
Right now it appears your logdest is syslog.
On Nov 2, 2011, at 11:45 AM, Kanishka Hettiarachchi wrote:
> Have noticed puppet agent continue to write agent runtime output to /
> var/log/messages, although $vardir, logdir
>From what I have read in the docs, you can't. You have to switch over to
>using tags.
On Nov 2, 2011, at 2:54 AM, gecko wrote:
> How could it be possible to choose an environment for deploy via
> Puppetrun ? It's easy by ssh (ssh user@hostname sudo puppetd -t --
> environment="env"), i'am runni
37 matches
Mail list logo
