Re: [Puppet Users] Puppet system deployment hanging ..
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 waiting for input? When we deploy Platform Symphony, we have to do something like an exec that runs echo Y | symphony-installer or we get a similar problem. Hmm, I am not aware of any installers running ... I will take a look and see if there are any background processes waiting for input .. thanks ! Well, I have run through the installation, and it appears to be hanging on the installation of our grid software. The commandline is executing, but the rpm's aren't downloading - so I will keep looking ... Adrian Snyman wrote: On Thu, Aug 12, 2010 at 12:49 PM, Ohad Levy ohadl...@gmail.com wrote: Does the puppet run starts at all? I've seen similar case when the clock were out of sync, ntp started and aligned it, but puppet got hanged because of it (or sleeping for a really long time). does debug mode provide more info? Ohad On Thu, Aug 12, 2010 at 9:11 AM, MadX a.sny...@gmail.com wrote: We have successfully installed puppet on a CentOS Server, but I am battling with a deployment. It has to do with grid software. The repository gets created, then begins installation. The problem is that it just hangs - no errors, no network activity. I can see puppet is running, but nothing it being updated. Any pointers ? -- 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 unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- 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 unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. Well, This is happening at about 50% of the installation - so it is definitely deploying .. I am running : puppetd --test --verbose And, as listed above - that's the last message I am seeing .. :S Any other logs etc. I could give ? Okay, just a heads up here ... I found the issue to be a faulty rpm. The user/group did not exist on the target system, and so after about 300 warnings, yum simply freezes. Installing the rpm manually showed the error. After creating the user and group - the deployment was successful. Unfortunately, puppet simply hangs while waiting for the rpm transaction to finish, and there is no indication as to what is holding up the install ... -- Regards, Adrian -- 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 unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Puppet Standalone Behavior
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 import nodes.pp, and nodes.pp has a default
node definition that includes basic modules defined under /home/abc/
puppet/modules)
OR
3) 2) with confdir set as /home/abc/puppet with a puppet.conf just
pointing to the var, ssl and other directories.
, then I do not get any output (or anything in the logfile with the
logdest set) whatsoever even with trace, logdest, debug and verbose
options set.
If however I explicitly do
4) puppet -e node default { include xyz include pqr} --modulepath=/
home/abc/puppet/modules
,then the modules are applied fine.
Any pointers regarding this behavior of the standalone executable ?
Suggestions/tips for better understanding its working ?
--
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 unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.compuppet-users%2bunsubscr...@googlegroups.com
.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
--
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 unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Puppet performance test
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 subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Puppet performance test
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 traffic, not manifest traffic, it probably counts. 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 -- ✣ Daniel Pittman✉ dan...@rimspace.net☎ +61 401 155 707 ♽ made with 100 percent post-consumer electrons -- 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 unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Using date in site.pp
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 puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Puppet system deployment hanging ..
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 or had some kind of watchdog that could reap stale processes after a while. The hardest thing about this kind of problem is actually figuring out what causes the issue, since Puppet/Yum only log the action after it's completed. -Eric On Tue, Aug 17, 2010 at 2:04 AM, Adrian Snyman a.sny...@gmail.com wrote: 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 waiting for input? When we deploy Platform Symphony, we have to do something like an exec that runs echo Y | symphony-installer or we get a similar problem. Hmm, I am not aware of any installers running ... I will take a look and see if there are any background processes waiting for input .. thanks ! Well, I have run through the installation, and it appears to be hanging on the installation of our grid software. The commandline is executing, but the rpm's aren't downloading - so I will keep looking ... Adrian Snyman wrote: On Thu, Aug 12, 2010 at 12:49 PM, Ohad Levy ohadl...@gmail.com wrote: Does the puppet run starts at all? I've seen similar case when the clock were out of sync, ntp started and aligned it, but puppet got hanged because of it (or sleeping for a really long time). does debug mode provide more info? Ohad On Thu, Aug 12, 2010 at 9:11 AM, MadX a.sny...@gmail.com wrote: We have successfully installed puppet on a CentOS Server, but I am battling with a deployment. It has to do with grid software. The repository gets created, then begins installation. The problem is that it just hangs - no errors, no network activity. I can see puppet is running, but nothing it being updated. Any pointers ? -- 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 unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- 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 unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. Well, This is happening at about 50% of the installation - so it is definitely deploying .. I am running : puppetd --test --verbose And, as listed above - that's the last message I am seeing .. :S Any other logs etc. I could give ? Okay, just a heads up here ... I found the issue to be a faulty rpm. The user/group did not exist on the target system, and so after about 300 warnings, yum simply freezes. Installing the rpm manually showed the error. After creating the user and group - the deployment was successful. Unfortunately, puppet simply hangs while waiting for the rpm transaction to finish, and there is no indication as to what is holding up the install ... -- Regards, Adrian -- 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 unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- 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 unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Using date in site.pp
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.
http://docs.puppetlabs.com/references/latest/function.html#inline_template
--
Rob McBroom
http://www.skurfer.com/
--
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 unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Could not find default node or by name
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 resolve it.
On Aug 17, 6:30 am, bmort propertywholesa...@gmail.com wrote:
I have this working on 2 other machines. Would you help me determine
what I've overlooked?
Version
[b...@free30 manifests]# puppet -V
0.25.5
The command and error:
[b...@free30 etc]$ sudo puppet -v /etc/puppet/manifests/site.pp --
debug
debug: importing '/etc/puppet/manifests/modules.pp'
debug: importing '/etc/puppet/modules/testfile/manifests/init.pp'
debug: importing '/etc/puppet/modules/freetds/manifests/init.pp'
debug: importing '/etc/puppet/modules/odbc/manifests/init.pp'
debug: importing '/etc/puppet/modules/odbcinst/manifests/init.pp'
debug: importing '/etc/puppet/modules/monit/manifests/init.pp'
debug: importing '/etc/puppet/manifests/nodes.pp'
debug: Adding code to main on line 30 in file /etc/puppet/manifests/
nodes.pp
debug: Adding code to main on line 14 in file /etc/puppet/manifests/
site.pp
debug: Failed to load library 'selinux' for feature 'selinux'
Could not find default node or by name with 'free30.test.com,
free30.test, free30' on node free30.test.com
[b...@free30 etc]$
nodes.pp:
# /etc/puppet/manifests/nodes.pp
# make sure you know what you are doing.
node basenode {
include testfile
include freetds
include odbc
include odbcinst
include monit
}
node 'free30.test.com' inherits basenode {
}
site.pp:
# /etc/puppet/manifests/site.pp
import modules
import nodes
# The filebucket option allows for file backups to the server
# *Note this is not working but appears to be required
filebucket { main: server = 'no.where.com' }
# Set global defaults - including backing up all files to the main
filebucket and adds a global path
File { backup = main }
Exec { path = /usr/bin:/usr/sbin/:/bin:/sbin }
--
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 unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Using date in site.pp
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 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.
http://docs.puppetlabs.com/references/latest/function.html#inline_tem...
--
Rob McBroom
http://www.skurfer.com/
--
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 unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Puppet system deployment hanging ..
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 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 or had some kind of watchdog that could reap stale processes after a while. The hardest thing about this kind of problem is actually figuring out what causes the issue, since Puppet/Yum only log the action after it's completed. -Eric On Tue, Aug 17, 2010 at 2:04 AM, Adrian Snyman a.sny...@gmail.com wrote: 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 waiting for input? When we deploy Platform Symphony, we have to do something like an exec that runs echo Y | symphony-installer or we get a similar problem. Hmm, I am not aware of any installers running ... I will take a look and see if there are any background processes waiting for input .. thanks ! Well, I have run through the installation, and it appears to be hanging on the installation of our grid software. The commandline is executing, but the rpm's aren't downloading - so I will keep looking ... Adrian Snyman wrote: On Thu, Aug 12, 2010 at 12:49 PM, Ohad Levy ohadl...@gmail.com wrote: Does the puppet run starts at all? I've seen similar case when the clock were out of sync, ntp started and aligned it, but puppet got hanged because of it (or sleeping for a really long time). does debug mode provide more info? Ohad On Thu, Aug 12, 2010 at 9:11 AM, MadX a.sny...@gmail.com wrote: We have successfully installed puppet on a CentOS Server, but I am battling with a deployment. It has to do with grid software. The repository gets created, then begins installation. The problem is that it just hangs - no errors, no network activity. I can see puppet is running, but nothing it being updated. Any pointers ? -- 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 unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- 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 unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. Well, This is happening at about 50% of the installation - so it is definitely deploying .. I am running : puppetd --test --verbose And, as listed above - that's the last message I am seeing .. :S Any other logs etc. I could give ? Okay, just a heads up here ... I found the issue to be a faulty rpm. The user/group did not exist on the target system, and so after about 300 warnings, yum simply freezes. Installing the rpm manually showed the error. After creating the user and group - the deployment was successful. Unfortunately, puppet simply hangs while waiting for the rpm transaction to finish, and there is no indication as to what is holding up the install ... -- Regards, Adrian -- 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 unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- 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 unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- Regards, Adrian -- 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 unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: Using date in site.pp
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 site, though. http://docs.puppetlabs.com/guides/templating.html -- Rob McBroom http://www.skurfer.com/ It's not that I think guns, drugs, prostitution, swimming, eating and reading should be legal. It's just that no one on Earth has the authority to make them illegal. -- 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 unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Puppet system deployment hanging ..
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 # don't install the yum-updatesd package -yum-updatesd Or the equivalent in whatever your deployment system is... -- Daniel Maher dma AT witbe DOT net The Internet is completely over. -- Prince -- 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 unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Puppet Standalone Behavior
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 expecting? Maybe you should look into the
puppetmasterd/puppetd executables.
-Dan
On Mon, Aug 16, 2010 at 11:17 PM, mohit chawla
mohit.chawla.bin...@gmail.com wrote:
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 import nodes.pp, and nodes.pp has a default
node definition that includes basic modules defined under /home/abc/
puppet/modules)
OR
3) 2) with confdir set as /home/abc/puppet with a puppet.conf just
pointing to the var, ssl and other directories.
, then I do not get any output (or anything in the logfile with the
logdest set) whatsoever even with trace, logdest, debug and verbose
options set.
If however I explicitly do
4) puppet -e node default { include xyz include pqr} --modulepath=/
home/abc/puppet/modules
,then the modules are applied fine.
Any pointers regarding this behavior of the standalone executable ?
Suggestions/tips for better understanding its working ?
--
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 unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.compuppet-users%2bunsubscr...@googlegroups.com
.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
--
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 unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.compuppet-users%2bunsubscr...@googlegroups.com
.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
--
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 unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Immediate puppetrun with splay
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 fact hnhostname info: Starting handler for Runner info: Starting server for Puppet version 0.24.8 info: Listening on port 8139 notice: Starting Puppet client version 0.24.8 info: Sleeping for 1605 seconds (splay is enabled) notice: puppetmaster.test.local(10.0.0.12) triggered run info: Sleeping for 1486 seconds (splay is enabled) Is there a way I can tell the client to start the run immediately? Thank you. Best regards, Bernhard -- 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 unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Puppet Standalone Behavior
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 be
sufficient in either case.
I was mainly trying out alternative deployment approaches apart from the
client/server arch that I have been using. Mainly inspired by this article:
http://bitfieldconsulting.com/scaling-puppet-with-distributed-version-control
Didn't think asking this would be so offensive.
On Tue, Aug 17, 2010 at 12:10 PM, Dan Bode d...@puppetlabs.com wrote:
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 expecting? Maybe you should look into the
puppetmasterd/puppetd executables.
-Dan
On Mon, Aug 16, 2010 at 11:17 PM, mohit chawla
mohit.chawla.bin...@gmail.com wrote:
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 import nodes.pp, and nodes.pp has a default
node definition that includes basic modules defined under /home/abc/
puppet/modules)
OR
3) 2) with confdir set as /home/abc/puppet with a puppet.conf just
pointing to the var, ssl and other directories.
, then I do not get any output (or anything in the logfile with the
logdest set) whatsoever even with trace, logdest, debug and verbose
options set.
If however I explicitly do
4) puppet -e node default { include xyz include pqr} --modulepath=/
home/abc/puppet/modules
,then the modules are applied fine.
Any pointers regarding this behavior of the standalone executable ?
Suggestions/tips for better understanding its working ?
--
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 unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.compuppet-users%2bunsubscr...@googlegroups.com
.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
--
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 unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.compuppet-users%2bunsubscr...@googlegroups.com
.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
--
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 unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.compuppet-users%2bunsubscr...@googlegroups.com
.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
--
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 unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Puppet Standalone Behavior
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, essentially I thought just the
modulepath option (with or without the explicit --manifest option) would be
sufficient in either case.
you can achieve this functionality by running
#puppet /etc/puppet/manifests/site.pp
only the puppet server (puppetmasterd) uses manifest/manifestdir to
automatically find site.pp
I was mainly trying out alternative deployment approaches apart from the
client/server arch that I have been using. Mainly inspired by this article:
http://bitfieldconsulting.com/scaling-puppet-with-distributed-version-control
I had a look at that article, it is slightly misleading. I think the
examples are trying to highlight that you can specify modulepath with the
puppet executalbe, but the statements:
puppet --modulepath=/etc/puppet/modules
are not valid, they will just hang unless the puppet manifest is also passed
as an argument.
Didn't think asking this would be so offensive.
I am definitely not offend, and I don't mean to offend, just trying to help.
On Tue, Aug 17, 2010 at 12:10 PM, Dan Bode d...@puppetlabs.com wrote:
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 expecting? Maybe you should look into the
puppetmasterd/puppetd executables.
-Dan
On Mon, Aug 16, 2010 at 11:17 PM, mohit chawla
mohit.chawla.bin...@gmail.com wrote:
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 import nodes.pp, and nodes.pp has a default
node definition that includes basic modules defined under /home/abc/
puppet/modules)
OR
3) 2) with confdir set as /home/abc/puppet with a puppet.conf just
pointing to the var, ssl and other directories.
, then I do not get any output (or anything in the logfile with the
logdest set) whatsoever even with trace, logdest, debug and verbose
options set.
If however I explicitly do
4) puppet -e node default { include xyz include pqr} --modulepath=/
home/abc/puppet/modules
,then the modules are applied fine.
Any pointers regarding this behavior of the standalone executable ?
Suggestions/tips for better understanding its working ?
--
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 unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.compuppet-users%2bunsubscr...@googlegroups.com
.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
--
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 unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.compuppet-users%2bunsubscr...@googlegroups.com
.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
--
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 unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.compuppet-users%2bunsubscr...@googlegroups.com
.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
--
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 unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.compuppet-users%2bunsubscr...@googlegroups.com
.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
--
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 unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Puppet Standalone Behavior
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
presumptuous.
Cheers.
On Tue, Aug 17, 2010 at 10:29 PM, Dan Bode d...@puppetlabs.com wrote:
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, essentially I thought just
the modulepath option (with or without the explicit --manifest option) would
be sufficient in either case.
you can achieve this functionality by running
#puppet /etc/puppet/manifests/site.pp
only the puppet server (puppetmasterd) uses manifest/manifestdir to
automatically find site.pp
I was mainly trying out alternative deployment approaches apart from the
client/server arch that I have been using. Mainly inspired by this article:
http://bitfieldconsulting.com/scaling-puppet-with-distributed-version-control
I had a look at that article, it is slightly misleading. I think the
examples are trying to highlight that you can specify modulepath with the
puppet executalbe, but the statements:
puppet --modulepath=/etc/puppet/modules
are not valid, they will just hang unless the puppet manifest is also
passed as an argument.
Didn't think asking this would be so offensive.
I am definitely not offend, and I don't mean to offend, just trying to
help.
On Tue, Aug 17, 2010 at 12:10 PM, Dan Bode d...@puppetlabs.com wrote:
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 expecting? Maybe you should look into the
puppetmasterd/puppetd executables.
-Dan
On Mon, Aug 16, 2010 at 11:17 PM, mohit chawla
mohit.chawla.bin...@gmail.com wrote:
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 import nodes.pp, and nodes.pp has a default
node definition that includes basic modules defined under /home/abc/
puppet/modules)
OR
3) 2) with confdir set as /home/abc/puppet with a puppet.conf just
pointing to the var, ssl and other directories.
, then I do not get any output (or anything in the logfile with the
logdest set) whatsoever even with trace, logdest, debug and verbose
options set.
If however I explicitly do
4) puppet -e node default { include xyz include pqr} --modulepath=/
home/abc/puppet/modules
,then the modules are applied fine.
Any pointers regarding this behavior of the standalone executable ?
Suggestions/tips for better understanding its working ?
--
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 unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.compuppet-users%2bunsubscr...@googlegroups.com
.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
--
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 unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.compuppet-users%2bunsubscr...@googlegroups.com
.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
--
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 unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.compuppet-users%2bunsubscr...@googlegroups.com
.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
--
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 unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.compuppet-users%2bunsubscr...@googlegroups.com
.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to
Re: [Puppet Users] Puppet + OpenVZ
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 something you'd like to reuse. -- Marcin Owsiany mar...@owsiany.pl http://marcin.owsiany.pl/ GnuPG: 1024D/60F41216 FE67 DA2D 0ACA FC5E 3F75 D6F6 3A0D 8AA0 60F4 1216 Every program in development at MIT expands until it can read mail. -- Unknown -- 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 unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. ve.rb Description: application/ruby openvz.rb Description: application/ruby
Re: [Puppet Users] strange interaction between ldap and puppet
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 setting), all worked well again. So what are you using LDAP for? Users, groups and authentication? From what I've seen, those types of searches only expect one result, so a limit of 50 shouldn't hold anything up. Are there any clues in the LDAP server's logs? (Maybe where `nentries` is 50 or more during a Puppet run.) -- Rob McBroom http://www.skurfer.com/ -- 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 unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Puppet performance test
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 issues? Indeed what are the issues? Just want to make sure we're actually working to fix these. Cheers James Turnbull -- Puppet Labs - http://www.puppetlabs.com C: 503-734-8571 -- 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 unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: Using date in site.pp
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 will be displayed. Thanks James Turnbull -- Puppet Labs - http://www.puppetlabs.com C: 503-734-8571 -- 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 unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: puppet and cpan
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 Mon, Aug 16, 2010 at 8:45 PM, Daniel Pittman dan...@rimspace.net wrote:
Brian Gallew g...@gallew.org writes:
It is always nice if y'all follow the existing quoting style in mails; it
makes it much less confusing to follow later.
I have to agree with Daniel on this one. While it's annoying to build
Solaris (in my case) packages for every CPAN package you want to install,
then end result is that I can control the installed version *precisely*.
While it may never have been a problem for you, I've been bitten more
than
once by CPAN upgrades that break my software, so old systems work while
new systems don't.
FWIW, at work we gave up on that despite using Debian and having pretty
good
support tools to do the job. We settled on packaging all the Perl bits we
use
as a single package and landing that everywhere.
That gives us a good balance between the two paths, and has worked out well
to
date. Plus it keeps system Perl and company Perl separate...
Daniel
--
✣ Daniel Pittman ✉ dan...@rimspace.net ☎ +61 401 155
707
♽ made with 100 percent post-consumer electrons
--
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 unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.compuppet-users%2bunsubscr...@googlegroups.com
.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
--
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 unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] puppet dashboard takes a long time to display
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 the root cause of my problem. After running of about 1 month using the development environment my log file grew to over 24GB. I had no idea this log file was even there since it's in a less than standard location (/opt/puppet-dashboard/log/development.log). I switched to using the production environment and that initially helped along with purging about 3GB of my report data from the database, but ultimately, the very large log file was impacting things as well. Igal Koshevoy wrote: On 08/04/2010 01:50 PM, Steven L. Seed wrote: I've been noticing my puppet dashboard is taking longer and longer to load up in my we browser the longer I've used it. I have roughly 1300 nodes being managed by puppet. It's almost as if there is too much data for it to process. I have about 1 month worth of data in my mysql database now. I've recently upgraded to version 1.0.3 but it hasn't improved the performance. It's taking typically around 60 - 90 seconds for the page to load...the browser sits waiting for a response from the server. Some things that you can do to make Dashboard run faster: 1. Run it in `production` mode, which is explained further in application's README. 2. Remove older reports from the database, e.g. keep only the last 15 days: `rake RAILS_ENV=production reports:prune upto=15 unit=day` 3. Run the Dashboard and its database on the same machine, and give them enough CPU cycles and RAM to run comfortably. If these don't help, it's likely that you're running into performance problems with how Dashboard is currently implemented. Resolving these issues is a high priority because it affects sites like yours with many nodes and reports and is on the schedule for the next major release. -igal -- 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 unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- 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 unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] ANNOUNCE: Facter 1.5.8rc1
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. You can get the release candidate at: http://reductivelabs.com/downloads/facter/facter-1.5.8rc1.tar.gz Please test and log any bugs to Redmine (http://projects.puppetlabs.com). CHANGELOG 4398b36 Updated CHANGELOG rake task e02be1d [#4156] Updating spec to match Kai's change bff84c2 [#4156] Applying patch by Kai b7fe989 [#2330] Update uptime calculation to use /bin/cat e9a60bc Facter::Manufacturer - sunos test + simplified regex be411c0 Facter::Manufacturer - test for SunOS and FreeBSD 67f6604 [#4062] Implement operating system facts for MeeGo a2bcacd [#2330] Uptime should not make redundant system calls ce7bd9f Refactor rakefile to use spec.ops, separate rcov task faaa169 Fix #4352 - Support for detecting KVM virtuals on FreeBSD 82286e4 Fix #4352 - Support for detecting virtuals (jails) on FreeBSD b2c2114 Properly wrapped the windows ipaddress fact in a setcode block. 1bd2ca2 Fixed #3929 - Added user confine to AIX memory facts 8106bc3 Adding HP-UX support to Facter's IP facts 83b3ea6 Fixed #3393 - Updates to Facter for MS Windows ffcae46 Fixed #3403 - Added fact to query vlans; added spec test d4b8401 Merged Jos Backus patch to remove requirement for ftools altogether 73dcbb9 Fixed #2355 read hang on /proc/xen/capabilties on RHEL 4.7 d109def Fix #1365 - load all facts via cli 6c87917 Fixed failing test introduced by previous commit c5b8d3b Fixes #3740 - split dmi output on regex 25bf5c2 Fix virtual unit test on non-linux by stubbing kernel 9a00eae Fixed #2313 - Somewhat essential hardware facts not available on OpenBSD, patch included e19024b Fixed #2938 - interfaces that don't match ^\w+[.:]?\d+ are ignored 97879f9 Added support for Slackware in operatingsystem and operatingsystemrelease 802e6c2 Fixed #3542 - Ruby 1.9: broken unittest, String#each no longer exists 2f016f3 Fixed #3541 - Ruby 1.9: broken unittest, unexpected invocation: Process.waitall() 84d3d9f Fixed #3445 - Facter does not handle solaris branded zones properly b5a8de0 Fix for #3411 install.rb should not put . first in the tmp_dirs 8ea33eb Fixed #3447 - OVS and OEL not matching in operatingsystemrelease aeee83c Fixed #3410 - Warnings in rake spec 8bf8cb5 Fixes #3397 - is_virtual fact does not detect Linux-VServer 62b6773 Add kvm support to virtual fact dca615c fixes #2573, #2085, #1291 - fixes domain and fqdn facts resolution 86447c8 Revert use popen3 in Resolution.exec 7750f03 Fix #2341 - stricter handling of dmidecode split f4269d9 Fix #2746 - add architecture support for GNU/kFreeBSD 50cef83 Fix missing error case 356cf15 Remove whitespace in DMI facts (#3008, #3011) feecd39 Only ignore IPs starting with 127. 68fc123 Added package signing task 33fb770 use popen3 in Resolution.exec to catch stderr 8109806 introduce a warn mechanism for debugging b2c1ca5 Add docs to Mac OS X package creation script and clean out old docs in the preflight 5412eab Fixed : 2788 - ftools missing in Ruby 1.9 5b95a12 Fixes #2704. Problem finding install.rb three levels up 9aef69e Removed all ChangeLog Regards James Turnbull -- Puppet Labs - http://www.puppetlabs.com C: 503-734-8571 -- 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 unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Puppet system deployment hanging ..
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 17, 2010 at 10:31 AM, Daniel Maher d...@witbe.net wrote: 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 # don't install the yum-updatesd package -yum-updatesd Or the equivalent in whatever your deployment system is... -- Daniel Maher dma AT witbe DOT net The Internet is completely over. -- Prince -- 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 unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- 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 unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] ANNOUNCE: Facter 1.5.8rc1
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 environments and hosts greatfully accepted. For fact regressions, 1.5.7 output to compare would be useful, please include that in bug reports. Paul -- 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 unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: Push changes to clients
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 cause puppet to ignore schedule resources. It won't do what you want. Cant you just use those two options to allow puppetruns to work and not have the client attempt to do updates? On Fri, Aug 13, 2010 at 6:44 AM, matonb brett.ma...@googlemail.com wrote: Is there a puppet.conf equivalent to --no-client ? All the nodes are RHEL and will use the puppet service (init script). I'd rather not tweak that if possible. Thanks. On Aug 13, 11:38 am, Craig Dunn li...@codenation.net wrote: On Fri, Aug 13, 2010 at 10:05 AM, ScubaDude brett.ma...@googlemail.comwrote: I was wondering how to configure the puppet clients to only listen, not to periodically pull configs down from the puppetmaster. I'd rather push the configs out from the puppetmaster with puppetrun... Running puppetd with --no-client should have this effect. Craig -- 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 unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- 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 unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- 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 unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- 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 unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] auth.conf in puppet 2.6 with Apache + Passenger
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 Passenger, the client responds that the request is forbidden. err: Could not retrieve catalog from remote server: Error 403 on SERVER: Forbidden request: XXX.XXX.XXX(xx.xx.xx.xx) access to /catalog/XXX.XXX.XXX[find] at line 97 So after going through the mailing lists and google I've found that the auth.conf file is the problem. I have stock standard auth.conf which looks like this: http://pastie.org/1098939 And yes, adding auth no to the first four methods does make it work, but I know that's not the problem (or the solution). Am I missing something? Is it a bug or PEBKAC? Some of the relevant puppet.conf entries vardir = /var/lib/puppet confdir = /etc/puppet puppetdlog = '$logdir/puppetd.log' logdir = '$vardir/log' rest_authconfig = '$confdir/auth.conf' masterlog = '$logdir/puppetmaster.log' The Gem versions I am using: facter (1.5.7) mongrel (1.1.5) passenger (2.2.15) puppet (2.6.0) rack (1.2.1, 1.1.0) ruby-mysql (2.9.3) The backtrace on the server is: http://pastie.org/1098964 Ruby version is : ruby 1.8.7 (2009-06-12 patchlevel 174) Virtualhost entry in apache looks like this: http://pastie.org/1098973 and the config.ru file looks like this: http://pastie.org/1098974 The client and server certs are fine (standalone works fine) and there are no connectivity problems between the client and server. Anyone seen this or have any ideas? Any help would be greatly appreciated. Regards Sven Schott -- 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 unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Puppet performance test
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 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 issues? Indeed what are the issues? Just want to make sure we're actually working to fix these. Cheers James Turnbull -- Puppet Labs -http://www.puppetlabs.com C: 503-734-8571 -- 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 unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Signing_Certificate
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, Parag -- 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 unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: Puppet performance test
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 - http://www.puppetlabs.com C: 503-734-8571 -- 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 unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Signing_Certificate
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 http://projects.puppetlabs.com/projects/puppet/wiki/Certificates_And_Security for more info. Cheers, Avi -- 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 unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] auth.conf in puppet 2.6 with Apache + Passenger
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 sven.sch...@gmail.com wrote: 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 Passenger, the client responds that the request is forbidden. err: Could not retrieve catalog from remote server: Error 403 on SERVER: Forbidden request: XXX.XXX.XXX(xx.xx.xx.xx) access to /catalog/XXX.XXX.XXX[find] at line 97 So after going through the mailing lists and google I've found that the auth.conf file is the problem. I have stock standard auth.conf which looks like this: http://pastie.org/1098939 And yes, adding auth no to the first four methods does make it work, but I know that's not the problem (or the solution). Am I missing something? Is it a bug or PEBKAC? Some of the relevant puppet.conf entries vardir = /var/lib/puppet confdir = /etc/puppet puppetdlog = '$logdir/puppetd.log' logdir = '$vardir/log' rest_authconfig = '$confdir/auth.conf' masterlog = '$logdir/puppetmaster.log' The Gem versions I am using: facter (1.5.7) mongrel (1.1.5) passenger (2.2.15) puppet (2.6.0) rack (1.2.1, 1.1.0) ruby-mysql (2.9.3) The backtrace on the server is: http://pastie.org/1098964 Ruby version is : ruby 1.8.7 (2009-06-12 patchlevel 174) Virtualhost entry in apache looks like this: http://pastie.org/1098973 and the config.ru file looks like this: http://pastie.org/1098974 The client and server certs are fine (standalone works fine) and there are no connectivity problems between the client and server. Anyone seen this or have any ideas? Any help would be greatly appreciated. Regards Sven Schott -- 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 unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.compuppet-users%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- 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 unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] auth.conf in puppet 2.6 with Apache + Passenger
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
RequestHeader set X-Client-DN %{SSL_CLIENT_S_DN}e
RequestHeader set X-Client-Verify %{SSL_CLIENT_VERIFY}e
which *are* in the instructions on the puppet wiki but not on the
instructions I had. Once I added that to the virtual hosts config,
everything went peachy. Thanks for the reply anyways. I appreciate it.
On Wed, Aug 18, 2010 at 1:19 PM, Patrick Mohr kc7...@gmail.com wrote:
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 sven.sch...@gmail.comwrote:
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
Passenger, the client responds that the request is forbidden.
err: Could not retrieve catalog from remote server: Error 403 on SERVER:
Forbidden request: XXX.XXX.XXX(xx.xx.xx.xx) access to /catalog/
XXX.XXX.XXX [find] at line 97
So after going through the mailing lists and google I've found that the
auth.conf file is the problem. I have stock standard auth.conf which looks
like this:
http://pastie.org/1098939
And yes, adding auth no to the first four methods does make it work, but I
know that's not the problem (or the solution). Am I missing something? Is it
a bug or PEBKAC?
Some of the relevant puppet.conf entries
vardir = /var/lib/puppet
confdir = /etc/puppet
puppetdlog = '$logdir/puppetd.log'
logdir = '$vardir/log'
rest_authconfig = '$confdir/auth.conf'
masterlog = '$logdir/puppetmaster.log'
The Gem versions I am using:
facter (1.5.7)
mongrel (1.1.5)
passenger (2.2.15)
puppet (2.6.0)
rack (1.2.1, 1.1.0)
ruby-mysql (2.9.3)
The backtrace on the server is:
http://pastie.org/1098964
Ruby version is : ruby 1.8.7 (2009-06-12 patchlevel 174)
Virtualhost entry in apache looks like this:
http://pastie.org/1098973
and the config.ru file looks like this:
http://pastie.org/1098974
The client and server certs are fine (standalone works fine) and there are
no connectivity problems between the client and server.
Anyone seen this or have any ideas? Any help would be greatly appreciated.
Regards
Sven Schott
--
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 unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.compuppet-users%2bunsubscr...@googlegroups.com
.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
--
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 unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.compuppet-users%2bunsubscr...@googlegroups.com
.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
--
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 unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
