On Fri, Aug 13, 2010 at 8:46 AM, Adrian Snyman a.sny...@gmail.com wrote:
On Fri, Aug 13, 2010 at 8:02 AM, Adrian Snyman a.sny...@gmail.com wrote:
On Thu, Aug 12, 2010 at 1:38 PM, Trevor Hemsley
trevor.hems...@codefarm.com wrote:
You're not exec'ing some install program that is stopping and
Puppet version is 0.25.5 on Debian Squeeze.
On Tue, Aug 17, 2010 at 11:43 AM, alcy mohit.chawla.bin...@gmail.comwrote:
If I do
1) puppet --modulepath=/home/abc/puppet/modules
OR
2) puppet --modulepath=/home/abc/puppet/modules --manifest=/home/abc/
puppet/site.pp
(...where site.pp has
I host about 700 directories and 1300 files on the puppetmaster
server, using default Webrick server. On the client, it takes about 6
minutes to get these files, and responses lots of errors which like
Failed to retrieve current state of resource :(
--
You received this message because you are
Jomo zhan...@gmail.com 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
Is it possible to use a date variable in /etc/puppet/
manifests.site.pp?
I would like to put it in
File { backup = @@.date format@@ }
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to
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
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 = @@.date format@@ }
There may be a cleaner way, but you could definitely accomplish that with an
inline template.
Thank you.
On Aug 17, 12:02 am, denmat tu2bg...@gmail.com 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
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 mailingli...@skurfer.com wrote:
On Aug 17, 2010, at 5:07 AM, matonb wrote:
Is it
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 eric.sha...@gmail.com 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
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
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
#
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
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
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)
Hi,
On Tue, Aug 17, 2010 at 9:50 AM, mohit chawla mohit.chawla.bin...@gmail.com
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,
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
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
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
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
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
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 g...@gallew.org wrote:
Sorry, when you use Gmail you end up top-posting whether you like it or not.
On
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 slseed1...@gmail.com wrote:
I found
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
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
On 17 August 2010 20:20, James Turnbull ja...@puppetlabs.com 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
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 kc7...@gmail.com wrote:
On Aug 13, 2010, at 7:21 AM, Christopher Johnston wrote:
ignoreschedules = true
This will
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
The line in config.rb
require 'puppet/application/puppetmasterd'
it should be require 'puppet/application/master' ?
On Aug 18, 2:41 am, James Turnbull ja...@puppetlabs.com wrote:
Daniel Pittman wrote:
I suggest you look to replacing webrick with one of the other options that
give
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,
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 -
Hi,
On Wed, Aug 18, 2010 at 1:01 PM, parag(PK) myselfpk...@gmail.com 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
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
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
34 matches
Mail list logo
