On Thu, 12 Aug 2010, James Turnbull wrote:
> http://puppetlabs.com/downloads/puppet/puppet-2.6.1rc2.tar.gz
In my brief testing with "puppetmasterd --compile", I see performance
of 2.6.1rc2 being almost identical to performance of 0.25.5. This is
a great improvement over 2.6.0 or 2.6.1rc1, which w
James Turnbull writes:
> Daniel Pittman wrote:
>
>> I suggest you look to replacing webrick with one of the other options that
>> give multiple, load balanced puppetmasters. Passenger and 0.25.* work well
>> for me, but bugs with that have me holding off the 2.6 series for now
>
> Are there t
The config file said those were only used with mongrel so I didn't uncomment
them. However, after fiddling for while I found that I had missed the exact
same thing on the apache virtual hosts config. The following lines were
missing:
RequestHeader set X-SSL-Subject %{SSL_CLIENT_S_DN}e
I think you might have missed this bit:
*Setup your puppet.conf*
*Make sure you have the following set in your puppetmaster’s puppet.conf:*
*[puppetmasterd]*
*ssl_client_header = SSL_CLIENT_S_DN*
*ssl_client_verify_header = SSL_CLIENT_VERIFY*
On Tue, Aug 17, 2010 at 5:59 PM, Sven Schott wro
Hi,
On Wed, Aug 18, 2010 at 1:01 PM, parag(PK) wrote:
> I wanted to automate this, as my server do not want to execute the
> same command again and again for various clients.
You want to configure autosign.conf -- take a look at
http://projects.puppetlabs.com/projects/puppet/wiki/Certificates_A
Jomo wrote:
> The line in config.rb
>
> " require 'puppet/application/puppetmasterd' "
>
> it should be " require 'puppet/application/master' " ?
It is:
http://github.com/reductivelabs/puppet/blob/2.6.x/ext/rack/files/config.ru
Fixed for 2.6.1.
Regards
James Turnbull
--
Puppet Labs - htt
Hi,
Usually, when a client request for a certificate the server
corresponds to it by,
puppetca --sign name.example.com
I wanted to automate this, as my server do not want to execute the
same command again and again for various clients.
I was searching for the solution to this.
Regards,
Debain squeeze with passenger 2.2.15 , I got these errors:
[Tue Aug 17 16:40:31 2010] [notice] Apache/2.2.16 (Debian) PHP/5.3.2-1
with Suhosin-Patch mod_python/3.3.1 Python/2.6.6rc1+ mod_ssl/2.2.16
OpenSSL/0.9.8o Phusion_Passenger/2.2.15 configured -- resuming normal
operations
*** Exception LoadE
The line in config.rb
" require 'puppet/application/puppetmasterd' "
it should be " require 'puppet/application/master' " ?
On Aug 18, 2:41 am, James Turnbull wrote:
> Daniel Pittman wrote:
> > I suggest you look to replacing webrick with one of the other options that
> > give multiple, load
Hi everyone
I'm having a problem with a clean install of puppet (2.6.0) on a Mac server
(Mac OS 10.5.8). I set up puppet initially with MySQL and the puppetmaster
standalone (Webrick) and that works fine. Clients can connect and there are
no problems. But when I configured it to use Apache and Pas
Wont that also ignore the scheduled 30min runs? I believe thats what Craig
wanted if I'm not mistaken.
Sent from my iPhone
On Aug 13, 2010, at 1:32 PM, Patrick Mohr wrote:
>
> On Aug 13, 2010, at 7:21 AM, Christopher Johnston wrote:
>> ignoreschedules = true
>
> This will cause puppet t
On 17 August 2010 20:20, James Turnbull wrote:
> For 40 days and 40 nights Facter wandered in the wilderness sustained
> only by the occasional patch and bottle of Kool-Aid. Tanned and happy
> Facter 1.5.8rc1 has now emerged from its desert retreat.
Testing on various virtual environments and hos
Yep, this was our solution -- I raised the issue more to point out
that finding out that yum-updater was the problem was difficult as a
result of quiet execution and yum's hang. Once we figured out the
problem the solution was fairly easy, but that's almost always the
case...
-Eric
On Tue, Aug
For 40 days and 40 nights Facter wandered in the wilderness sustained
only by the occasional patch and bottle of Kool-Aid. Tanned and happy
Facter 1.5.8rc1 has now emerged from its desert retreat.
1.5.8 is a feature and maintenance release containing a number of fixes,
updates and additional tests
Steven,
Thanks for sharing your findings. I've created ticket #4553 to either
add some README documentation about this or somehow setup a default
for log size.
Matt
http://projects.puppetlabs.com/issues/4553
On Mon, Aug 16, 2010 at 3:32 PM, Steven L. Seed wrote:
> I found the root cause of my p
Thanks for all your answers, but I settled for a different solution.
It appeared the perl-package was available in the debian-repo, so I
can use package{}.
On Aug 17, 5:49 am, Brian Gallew wrote:
> Sorry, when you use Gmail you end up top-posting whether you like it or not.
>
> On Mon, Aug 16,
matonb wrote:
> Thanks for the pointer Rob, the link on the page you referenced for
> the templating docs (http://docs.puppetlabs.com/trac/puppet/wiki/
> PuppetTemplating) is unfortuantely broken!
>
This is fixed in the next release. When we regenerate the documentation
for 2.6.1 the correct link
Daniel Pittman wrote:
> I suggest you look to replacing webrick with one of the other options that
> give multiple, load balanced puppetmasters. Passenger and 0.25.* work well
> for me, but bugs with that have me holding off the 2.6 series for now
>
Daniel
Are there tickets logged for the i
On Aug 16, 2010, at 4:31 PM, Hanspeter Kunz wrote:
> today I restricted the maximal number of results of my openldap server
> to 50. As a result, on all of my client machines puppetd hanged
> (indefinitely, i.e. longer than 5mins). After restoring the number of
> results to 500 (the original setti
Hi,
On Thu, Aug 05, 2010 at 09:48:21PM -0700, Matthew Cluver wrote:
> If you have been working on the same thing and have any code that
> you'd like to contribute it would certainly be appreciated!
Attaching my old faithful if a little dusty ve type and openvz provider.
Maybe you'll find there so
Dan, yes I know I could do that, and in fact that's what I was doing (that
is, simply do a puppet /path/to/manifest-that-could-just-be-site.pp) but
yes, that article and occurrences elsewhere misled me. Appreciate your help,
I am just trying to learn. Thanks and apologies for being a bit
presumptuo
Hi,
On Tue, Aug 17, 2010 at 9:50 AM, mohit chawla wrote:
> I am sure I didn't make this up, but I was under the impression that either
> it will autoload the default site.pp (under /etc/puppet/manifests) or the
> one mentioned with the --manifest option. So, essentially I thought just the
> modu
I am sure I didn't make this up, but I was under the impression that either
it will autoload the default site.pp (under /etc/puppet/manifests) or the
one mentioned with the --manifest option. So, essentially I thought just the
modulepath option (with or without the explicit --manifest option) would
Hi,
when splay is enabled on a client and a run is triggered with puppetrun,
a new random time is picked before the run is started (second last and
last line):
puppetd --no-daemonize --verbose
info: Loading fact nrpe_collect
info: Loading fact envname
info: Loading fact want_ntp
info: Loading fa
the puppet executable expects one of the following:
path to manifest file
puppet code passed to stdin
with the -e options, it accepts puppet code to execute.
when you call puppet code without one of these options, it is patiently
waiting for code from STDIN.
What behavior are you expecti
On 08/17/2010 04:04 PM, Adrian Snyman wrote:
Well, I wonder if there is a way to make puppet turn off the updater
before starting it's run ?
Instead of trying to disable it, why bother installing it at all ? Just
remove the package in your kickstart config and be done with it.
%packages
# d
On Aug 17, 2010, at 8:38 AM, matonb wrote:
> Thanks for the pointer Rob, the link on the page you referenced for
> the templating docs (http://docs.puppetlabs.com/trac/puppet/wiki/
> PuppetTemplating) is unfortuantely broken!
A lot of them are since the migration. You can find it on the main docs
Well, I wonder if there is a way to make puppet turn off the updater
before starting it's run ?
On Tue, Aug 17, 2010 at 2:00 PM, Eric Shamow wrote:
> I have seen this behavior before as well. I've also seen it where
> yum-updater (which is evil and shouldn't be running, but in some cases
> hasn't
Thanks for the pointer Rob, the link on the page you referenced for
the templating docs (http://docs.puppetlabs.com/trac/puppet/wiki/
PuppetTemplating) is unfortuantely broken!
On Aug 17, 1:16 pm, Rob McBroom wrote:
> On Aug 17, 2010, at 5:07 AM, matonb wrote:
>
> > Is it possible to use a date v
Thank you.
On Aug 17, 12:02 am, denmat wrote:
> Could not find default node or by name with 'free30.test.com,
> free30.test, free30' on node free30.test.com
>
> DNS? Change your node to description to:
>
> node 'free30' inherits basenode {
>
> }
>
> make sure that the puppet master can resolve it
On Aug 17, 2010, at 5:07 AM, matonb wrote:
> Is it possible to use a date variable in /etc/puppet/
> manifests.site.pp?
>
> I would like to put it in
>
> File { backup => @@.@@ }
There may be a cleaner way, but you could definitely accomplish that with an
inline template.
http://docs.puppetla
I have seen this behavior before as well. I've also seen it where
yum-updater (which is evil and shouldn't be running, but in some cases
hasn't been turned off yet by kickstart or puppet) will switch on and
demolish a bootstrap Puppet run.
It would help if the yum handler was a little more verbose
Is it possible to use a date variable in /etc/puppet/
manifests.site.pp?
I would like to put it in
File { backup => @@.@@ }
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To
Jomo writes:
> I host about 700 directories and 1300 files on the puppetmaster
> server, using default Webrick server.
I believe the standard response is "get a better server"; the default is
really not well optimized for high volume loads — and while this is a high
volume of file traffic, not m
34 matches
Mail list logo
