Hi,
I have Puppet working with PuppetDB (postgresql) but puppetdb after start
service this say is dead and the service not running.
1. Start service (not fail)
[...]
[root@master ~]# service puppetdb start
Starting puppetdb: [ OK ]
[
When you have hundreds of hosts and run Puppet every 30 mins (splayed
across the hour), it seems that you end up running into various 'dpkg'
locks fairly randomly and at a surprisingly high occurrence (once or twice
a day at least). This happens if you do something simple like a cron-based
'apt-get
I had it set to 3 minutes for this test.
I am going to work on trying some different settings.
So far the best result has been with the following settings
PassengerMaxRequests 5000
environment_timeout 15 minutes
"service httpd graceful" whenever my svn update script detects a change.
I will be
What you could do is a mix of gerrit/gitolite and r10k.
r10k[1] allows you to deploy environment based on branches name. So if
you have a branch called team1, team2 and team42 you will have team1,
team2 and team42 puppet environment. Reading Garry Larizza's blog[2]
will give you a great overv
I'm looking at this code:
define logstash::configfile(
$content = undef,
$source = undef,
$order = 10
) {
file_fragment { $name:
tag => "LS_CONFIG_${::fqdn}",
content => $content,
source => $source,
order => $order,
before => [ File_concat['ls-config'] ]
}
Hi John,
Thanks for reply again .
*That totally does not make sense. I'm not sure exactly how you would
apply a pre-compiled catalog to a random machine.*
This setup would leverage vmware appdirector and integration with puppet
master , Where i will create blueprint of first creating a vm and
Hi Tristan, Chuck,
What environment_timeout do you have set currently?
On Friday, May 23, 2014 12:20:33 PM UTC-7, Tristan Smith wrote:
>
> Whuf. I'm already at 1, so that's not it for me.
>
> Seems like the doubled run time was just murdering me in the face. Trying
> to run 1000 clients i
Finally got around to checking into this. I needed to actually read the rest
api docs:
http://docs.puppetlabs.com/guides/rest_api.html
So:
#!/bin/bash
exit `curl -s --cacert /var/lib/puppet/ssl/certs/ca.pem
https://puppet.mycompany.com:8140/production/certificate/ca | grep '500
Internal Serve
On Fri, May 23, 2014 at 12:00 PM, Kylo Ginsberg wrote:
> On Fri, May 23, 2014 at 2:58 AM, Paul Seymour wrote:
>
>>
>>> +1 - let's file a bug report.
>>>
>>
>> https://tickets.puppetlabs.com/browse/PUP-2650
>>
>
> For more context here, puppet has a 'deprecation_warning' method which is
> used fo
Whuf. I'm already at 1, so that's not it for me.
Seems like the doubled run time was just murdering me in the face. Trying
to run 1000 clients in 30m was just too much. Guess I could make it an hour
splay, but the overall resource requirement change is sufficiently large
I'm probably just go
On Thu, May 22, 2014 at 9:42 PM, David Gillies wrote:
> So I hope you actually meant Ubuntu *13.04* (Raring Ringtail) and not
> Ubuntu 12.04 (Precise Pangolin) right?
>
Yes, we meant 13.04. That was a typo in the announcement. The release notes
should be updated shortly as well.
Thanks
Kylo
>
Strike that strike!
I just updated from Ruby 1.8 to 2.0 and got bitten by the Psych parser
issue: https://ask.puppetlabs.com/question/314/hiera-installconfig-problem/
Nothing to see here.
On Fri, May 23, 2014 at 1:20 PM, Trevor Vaughan wrote:
> *sigh* strike that. Even though the tests pas
I am noticing increase CPU and Memory requirements from Puppet 3.4.3
I had to set the following passenger config so that my server would not run
out of memory:
PassengerMaxRequets 1
CPU idle 3.4.3 = 70% - 80%
Memory utilization = 52%
CPU idle 3.6.1 = 60% - 73%
Memory utilization = 85%
--
*sigh* strike that. Even though the tests passed, something's wrong in
production.
On Fri, May 23, 2014 at 1:04 PM, Trevor Vaughan wrote:
> I just pushed a patch against 1.3.3 to
> https://github.com/onyxpoint/hiera/tree/bugs/HI-183.
>
> Thanks,
>
> Trevor
>
>
> On Fri, May 23, 2014 at 10:05 AM,
I just pushed a patch against 1.3.3 to
https://github.com/onyxpoint/hiera/tree/bugs/HI-183.
Thanks,
Trevor
On Fri, May 23, 2014 at 10:05 AM, Yanis Guenane wrote:
> Same here. We use a dirty eval if is_a?(Array) or is_a?(Hash). Having this
> fix being part of upstream will be great.
>
> Kudos
On Fri, May 23, 2014 at 2:58 AM, Paul Seymour wrote:
>
>> +1 - let's file a bug report.
>>
>
> https://tickets.puppetlabs.com/browse/PUP-2650
>
For more context here, puppet has a 'deprecation_warning' method which is
used for this new message and also in a number of other places. In puppet
3.7,
Regarding SVN/Git.
I've done both and I much prefer Git, even though there are only two of us
working on the Puppet code. We don't, yet, use branches as environment
paths though I believe it would be much easier to do so with Git than SVN.
These may help, they helped me.
http://nvie.com/posts/a-su
So this problem is tracked here:
https://tickets.puppetlabs.com/browse/PDB-686. I've been unable to
find a work-around beyond 'switch ruby' or completely change the way
we submit JSON (which would be a shame, the new method is more
efficient). Some people have had success using the newer brightbox
Same here. We use a dirty eval if is_a?(Array) or is_a?(Hash). Having this
fix being part of upstream will be great.
Kudos for the release,
On Fri, May 23, 2014 at 10:01 AM, Clayton O'Neill
wrote:
> On Fri, May 23, 2014 at 9:16 AM, Trevor Vaughan wrote:
>
>> Nice!
>>
>> Any chance of getting th
On Fri, May 23, 2014 at 9:16 AM, Trevor Vaughan wrote:
> Nice!
>
> Any chance of getting this patch (or something equivalent) into the next
> release?
>
>
> https://github.com/onyxpoint/hiera/commit/9fe491eca3cf3bbe203436b779f102f1ffe7b30f
>
I'll second that. This would clean up a lot of our hie
Hi José
Sorry about the delay in responding I was sidetracked with other work. A
massive thank you!
Your solution works! As a temporary work around I ended up just moving
files in and out of the facter fact.d, this solution is a bit more
convenient.
Thanks,
Peter
On Friday, 9 May 2014
On Thursday, May 22, 2014 11:17:48 AM UTC-5, Ritesh Nanda wrote:
>
> Hello John,
>
> Thanks for your reply , sorry for providing less information .
> I am working on developing websphere multi-node deployment module
>
>From the (little) code you provided, I infer that you are using the term
"m
Hi puppet peeps,
Something to think about for the weekend. We're running puppet 3.6 now
and it is warning me that config environments are deprecated and that I
should migrate. That's fine, but I'm not quite sure how to replicate the
setup I've got now with directory environments.
Currently,
Nice!
Any chance of getting this patch (or something equivalent) into the next
release?
https://github.com/onyxpoint/hiera/commit/9fe491eca3cf3bbe203436b779f102f1ffe7b30f
Thanks,
Trevor
On Thu, May 22, 2014 at 11:08 PM, Eric Sorenson <
eric.soren...@puppetlabs.com> wrote:
> Hiera 1.3.3 is a
Hey John
Dont forget to pass basemodulepath on config.ru directly..that might help.
On Tuesday, 8 April 2014 07:29:24 UTC+10, John Pyeatt wrote:
>
> Tried to convert from webrick to passenger today. Failed.
>
> When I run
>
> puppet agent -tv
>
> I get two things that are troubling.
>
> 1)
> I
Hi
I currently have enterprise puppet on a RHEL server.
The agent install element of the master install fails (as do subsequent
runs of the agent) with
curl -f -L -o puppet-enterprise-3.2.1-el-5-x86_64-agent.tar.gz
https://pm.puppetlabs.com/puppet-enterprise/3.2.1/puppet-enterprise-3.2.1-el-5-
In 3.6.1 facts are also loaded twice when environmentpath is set in
main-section of puppet.conf , see
https://tickets.puppetlabs.com/browse/PUP-2651
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop recei
Hi,
I keep getting the following error in my logs and according to what I am
seeing around the performance improves alot when we change the report
format and agent server communication to JSON
YAML in network requests is deprecated and will be removed in a future
version
I am using puppet maste
>
>
> +1 - let's file a bug report.
>
https://tickets.puppetlabs.com/browse/PUP-2650
--
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
to puppet-users+unsubscr..
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
>> I know we can set a top level default but does that really have
>> to come out constantly ?
>
> I agree, I was thinking of filing a bug for this to request that
> it's dialled down to info or notice level, if it must be printed at
> all.
>
> Depre
On 23/05/14 09:31, Paul Seymour wrote:
> Just updated the test environment to 3.6.1 and I know the changes have
> been made for virtual packages. But now each agent output displays this:-
>
> Warning: The package type's allow_virtual parameter will be changing its
> default value from false to tru
>
> Now this may be related to 3.6.x but I cannot say for sure. A couple of
> facts we use are now throwing some errors.
>
> First is:-
> Could not retrieve fact='concat_basedir', resolution='':
> uninitialized constant Puppet
>
> Which comes from:-
> Facter.add("concat_basedir") do
> setcod
Hello,
Just updated the test environment to 3.6.1 and I know the changes have been
made for virtual packages. But now each agent output displays this:-
Warning: The package type's allow_virtual parameter will be changing its
default value from false to true in a future release. If you do not wa
33 matches
Mail list logo
