I used to have issues with the agent leaking memory over time. This is
going back to 2.6 days.
I implemented a cron job back then to restart the agent every night and
never removed the job (even though I'm now running 3.6), so I don't know if
there are still memory issues with the agent daemon.
Try using the splay config option on the agents. It should help to
distribute the agent runs.
https://docs.puppetlabs.com/references/latest/configuration.html#splay
If that fails, you could try running the puppet agent from a cron job
instead with randomised start times as per the below link.
Hi Trey,
You could always use the concat module.
https://forge.puppetlabs.com/puppetlabs/concat
Create the global fragment in the class and then use a defined type to
create a concat fragment for each entry that you want. You can pass a
template to each fragment.
--
You received this message
Hi,
In the cs_primitive provider, I added debug code to write the updated var
to a file in /tmp. I then tried applying that with crm update as the
provider does. Crm was returning errors to me that the provider wasn't.
I was able to use that to determine that I didn't have all the params set
Hi Georg,
I had issues when I was first using this module with the primitives.
I ended up adding some debug code to the provider to try and work out what
was going on. I'm sure there are better ways of doing it, but I used
File.write to shove log messages into a file on the client in strategic
p
Hi,
Since you aren't getting any errors, it would suggest to me that puppet
thinks those values are already set correctly and therefore require no
further action.
The module essentially parses the output from "crm configure show xml", so
I'd check what is being returned in that output for those
Try running the agent with --debug and --evaltrace to identify what Puppet
is doing in relation to those resources.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
On Thursday, 6 February 2014 21:37:55 UTC, Larry Fast wrote:
The default value for the private key path in the eyaml CLI is
./keys/private_key.pkcs7.pem. Is there an CLI option to override the
default?
yep :)
$ eyaml --help
Hiera-eyaml is a backend for Hiera which provides OpenSSL
encryption/
On Monday, 6 January 2014 15:59:53 UTC, Joseph Swick wrote:
>
> On 01/02/2014 03:18 AM, james.e...@fasthosts.com wrote:
> > How about chaining the resources, ala
> >
> http://docs.puppetlabs.com/puppet/2.7/reference/lang_relationships.html#chaining-arrows
>
> > .
> >
> > Yumrepo <| |> -> Pa
How about chaining the resources, ala
http://docs.puppetlabs.com/puppet/2.7/reference/lang_relationships.html#chaining-arrows
.
Yumrepo <| |> -> Package<| |>
This declared in site.pp should apply globally to all nodes and would avoid
the use of run stages (if I understand it correctly).
J
On
And thanks from me.
Felix, thank you for your investigation on this issue, it's really appreciated
:)
From: puppet-users@googlegroups.com [mailto:puppet-users@googlegroups.com] On
Behalf Of Louise Baker
Sent: 10 December 2013 23:36
To: puppet-users@googlegroups.com
Subject: Re: [Puppet Users] R
Thanks Luke.
I just found a bug report describing that this behaviour has changed in 3.x
http://projects.puppetlabs.com/issues/17692
For me, being able to determine the agent environment is very useful.
We use git for the Puppet manifests and each branch is an environment.
So we'll create new b
Hi,
I'm seeing something rather strange with puppetdb (1.5.2) in regards to the
environment fact.
On my puppetdb host:
If I run the following query:
curl -G 'http://localhost:8080/v3/facts' --data-urlencode 'query=["=",
"name", "environment"]'
I would expect to receive the environment fact f
Hi,
For reference, I've just upgraded my puppet masters from 2.7.22 to 3.3.2
and haven't seen any errors of this kind.
I presume you are running with passenger? I am too. CentOS EL6 masters.
Maybe there is a change between 3.3.1 and 3.3.2 that will resolve this for
you both.
I have seen one
On Tuesday, 5 November 2013 15:14:26 UTC, jcbollinger wrote:
>
>
>
> On Monday, November 4, 2013 10:38:00 AM UTC-6, james.e...@fasthosts.comwrote:
>>
>> Hi,
>>
>> I am having some issues with facter on a couple of servers which have a
>> large number of ip addresses.
>>
>> Essentially, all my pup
Hi,
I am having some issues with facter on a couple of servers which have a
large number of ip addresses.
Essentially, all my puppet runs time out because facter takes in excess of
25 seconds to populate the facts.
Here is the list of interfaces - pretty much each one has an IP assigned.
inte
Hi,
I believe the following link should resolve this problem for you.
https://groups.google.com/forum/#!topic/foreman-users/p5w0if2AGlo
J
On Wednesday, 30 October 2013 08:47:13 UTC, AVE1810 wrote:
>
> Hi,
>
> When I run puppet agent --test --environment 42A, I have the following
> warning :
>
The exec resource has an unless parameter too which I think is what you
need.
From: http://docs.puppetlabs.com/references/latest/type.html#exec
onlyif If this parameter is set, then this exec will only run if the
command returns 0
unless If this parameter is set, then this exec will run unles
Looks like this message didn't reach the group for some reason.
For clarity though, I found that this was occurring on all three
masters. I was able to resolve this by downgrading the activerecord
gem on the puppet masters from 3.1.3 to 3.0.5.
On 13 January 2012 08:31, jamese wrote:
> I'm curre
19 matches
Mail list logo
