Hi,
Thanks, I needed to add the `manifest' option to my puppmaster under
[main] and [staging]. I removed [production] all together.
Notice, that output from the client node always showed manifestdir to
be /etc/puppet/manifests:
#puppetd --test --debug --environment staging-- configprint
2010/3/30 smain kahlouch smain...@gmail.com
2010/3/30 Ben Lovell benjamin.lov...@gmail.com
On 30 March 2010 16:38, smain kahlouch smain...@gmail.com wrote:
2010/3/30 smain kahlouch smain...@gmail.com
2010/3/30 smain kahlouch smain...@gmail.com
2010/3/30 Peter Meier
Can you post your apache config? Maybe you want to compare it to i
config i posted:
http://www.linuxaddicted.de/blog/2010/03/18/puppetmasterd-and-passenger/
On Wed, Mar 31, 2010 at 9:48 AM, smain kahlouch smain...@gmail.com wrote:
2010/3/30 smain kahlouch smain...@gmail.com
2010/3/30 Ben
2010/3/30 Peter Meier peter.me...@immerda.ch
gem update rack
Updating installed gems
Updating rack
Successfully installed rack-1.1.0
Gems updated: rack
I still have the same error.
just to be sure: you restarted apache, right?
can you give us a list of your installed gems, as
2010/3/31 Daniel Kerwin dan...@linuxaddicted.de
Can you post your apache config? Maybe you want to compare it to i
config i posted:
http://www.linuxaddicted.de/blog/2010/03/18/puppetmasterd-and-passenger/
On Wed, Mar 31, 2010 at 9:48 AM, smain kahlouch smain...@gmail.com
wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 31/03/10 6:29 PM, Tore wrote:
I wish I could update the documentation on the wiki, but for some
reason Redemi believes I've allready got an registered account, but
I'm not able to log in with OpenID :/
What's your user name?
Regards
James
Hi,
i'm following the steps of the documentation but the links are not working.
I can't download the files :
http://projects.reductivelabs.com/projects/puppet/wiki/Using_Mongrel_On_Debian
Thanks for your help,
Grifith
--
You received this message because you are subscribed to the Google
2010/3/31 Ben Lovell benjamin.lov...@gmail.com
On 31 March 2010 11:03, smain kahlouch smain...@gmail.com wrote:
2010/3/31 Ben Lovell benjamin.lov...@gmail.com
2010/3/30 Peter Meier peter.me...@immerda.ch
gem update rack
Updating installed gems
Updating rack
Successfully installed
Hi,
Since puppet doesn't have HA/fail over capabilities as of now. How does one
mitigate a puppet master failure( Ex. Hardware). When you replace the server
and configure the Puppet masterd, the clients may no longer be able to
communicate with the server, since the server's SSL certificates
Le mercredi 31 mars 2010 à 16:22 +0530, LOhit a écrit :
Hi,
Hi,
Since puppet doesn't have HA/fail over capabilities as of now. How
does one mitigate a puppet master failure( Ex. Hardware). When you
replace the server and configure the Puppet masterd, the clients may
no longer be able to
On 31 March 2010 11:20, smain kahlouch smain...@gmail.com wrote:
2010/3/31 Ben Lovell benjamin.lov...@gmail.com
On 31 March 2010 11:03, smain kahlouch smain...@gmail.com wrote:
2010/3/31 Ben Lovell benjamin.lov...@gmail.com
2010/3/30 Peter Meier peter.me...@immerda.ch
gem update
On 3/31/10 6:52 AM, LOhit lohi...@gmail.com wrote:
BTW, I am using puppet to manage about 700+ hosts,
Before we started using rsync and running puppet locally on each host, we
actually added the SSL certs to SVN. Cheesy, but we could quickly, and
easily, move clients from master to master.
--
hello,
The master doesn't actually need a copy of the signed certs
on the its drives.
All the master needs is the CA that signed the nodes. If
you set your masters up that you access them via a CNAME
such as 'puppet' all you need to really bother with
is making sure your new master is on
R.I.Pienaar r...@devco.net wrote:
All the master needs is the CA that signed the nodes. If
you set your masters up that you access them via a CNAME
such as 'puppet' all you need to really bother with
is making sure your new master is on that name and has
the same CA as before.
Excuse me for
On Tue, Mar 30, 2010 at 9:46 PM, Daniel Pittman dan...@rimspace.net wrote:
[...]
Your client logs *still* show that there is no MOTD stuff being touched at
all; try this on the client that should manage MOTD and see what is output:
puppetd --test --debug 21 | grep -i motd
I suspect the
hello,
- Cosimo Streppone cos...@streppone.it wrote:
R.I.Pienaar r...@devco.net wrote:
All the master needs is the CA that signed the nodes. If
you set your masters up that you access them via a CNAME
such as 'puppet' all you need to really bother with
is making sure your new
Ok, thanks.
I'll check the code too.
Gus
--- Original message ---
From: James Turnbull ja...@lovedthanlost.net
To: puppet-users@googlegroups.com
Sent: 30.3.'10, 22:58
On 31 March 2010 11:36, Paul Lathrop paul.lath...@gmail.com wrote:
It does exist!
Sadly, the documentation is the
On Wed, Mar 31, 2010 at 6:02 AM, Charles Johnson gm.johns...@gmail.com wrote:
On Tue, Mar 30, 2010 at 9:46 PM, Daniel Pittman dan...@rimspace.net wrote:
[...]
Your client logs *still* show that there is no MOTD stuff being touched at
all; try this on the client that should manage MOTD and
On Wed, Mar 31, 2010 at 6:05 AM, smain kahlouch smain...@gmail.com wrote:
Hi,
i'm following the steps of the documentation but the links are not working.
I can't download the files :
http://projects.reductivelabs.com/projects/puppet/wiki/Using_Mongrel_On_Debian
Thanks for your help,
On Wed, 2010-03-31 at 10:45 -0300, Gustavo Soares wrote:
Ok, thanks.
I'll check the code too.
You can also have a look to the auth.conf file which lists most of the
REST urls.
--
Brice Figureau
Follow the latest Puppet Community evolutions on www.planetpuppet.org!
--
You received this
On Wed, Mar 31, 2010 at 7:19 AM, Brice Figureau
brice-pup...@daysofwonder.com wrote:
On Wed, 2010-03-31 at 10:45 -0300, Gustavo Soares wrote:
Ok, thanks.
I'll check the code too.
You can also have a look to the auth.conf file which lists most of the
REST urls.
I found that using ssldump to
On Tue, Mar 30, 2010 at 8:36 PM, Paul Lathrop paul.lath...@gmail.comwrote:
It does exist!
Sadly, the documentation is the code, as far as I've been able to
determine. You can get a fair amount of information if you are using a
webserver like Apache in front of puppetmasterd by watching your
On Wed, Mar 31, 2010 at 9:16 AM, Nigel Kersten nig...@google.com wrote:
/etc/puppet/modules/motd/manifests/init.pp looks like this
class motd {
include prodcomputenode
include prodgateway
shouldn't this be
include motd::prodgateway ?
include testcomputenode
On Wed, Mar 31, 2010 at 7:41 AM, Charles Johnson gm.johns...@gmail.com wrote:
On Wed, Mar 31, 2010 at 9:16 AM, Nigel Kersten nig...@google.com wrote:
/etc/puppet/modules/motd/manifests/init.pp looks like this
class motd {
include prodcomputenode
include prodgateway
shouldn't
On Wed, 2010-03-31 at 07:29 -0700, Nigel Kersten wrote:
On Wed, Mar 31, 2010 at 7:19 AM, Brice Figureau
brice-pup...@daysofwonder.com wrote:
On Wed, 2010-03-31 at 10:45 -0300, Gustavo Soares wrote:
Ok, thanks.
I'll check the code too.
You can also have a look to the auth.conf file
LOhit,
The main two things to take into account are:
1. keep your manifests elsewhere, IMHO puppetmasters always gets RO copy
of your puppet data (e.g. from a VCS).
2. Solve the SSL hell, then everything is simple.
I've been using in my setup (with approx 15 productive puppetmasters
On Wed, Mar 31, 2010 at 10:02 AM, Nigel Kersten nig...@google.com wrote:
Which examples?
I've always qualified the full class name, in 0.24 and 0.25. I didn't
realize you could do what you've done above.
It seems undesirable, ie:
class foo {
...
}
class eggs {
include foo
}
Thanks! I will be trying that, or going back to 0.24.8 :)
On Wed, Mar 31, 2010 at 10:33 AM, Nigel Kersten nig...@google.com wrote:
On Wed, Mar 31, 2010 at 8:29 AM, Charles Johnson gm.johns...@gmail.com
wrote:
On Wed, Mar 31, 2010 at 10:02 AM, Nigel Kersten nig...@google.com
wrote:
Guys,
I can't make it to the pub. Have a great time!
Julian.
On 30 March 2010 10:17, Paul Nasrat pnas...@googlemail.com wrote:
On 30 March 2010 08:04, Gary Law gary@gmail.com wrote:
Sorry guys, made my suggestion before I say this! Go for the Green Man...
Not a problem.
I owe you
As I mentioned previously, Puppet is part of Google Summer of Code this
year. I'm really excited to see this.
If you are or know a student who might like to work on Puppet and related
tools, sign up for Google Summer of Code ends April 9th.
If you'd like to talk about
My thanks to Daniel Pittman and Nigel Kersten for their help. They
helped put me on the right track to solving the problem.
I had the problem of upgrading a puppet server from 0.24.8 to 0.25.4.
Subsequently, classes were not imposed on the clients. There were no
error messages either on the
Me either unfortunately. See you all at DevOps at the Guardian
instead, or PuppetCamp if not!
On 31 Mar 2010, at 17:17, Julian Simpson wrote:
Guys,
I can't make it to the pub. Have a great time!
Julian.
On 30 March 2010 10:17, Paul Nasrat pnas...@googlemail.com wrote:
On 30 March 2010
LOhit writes:
Hi,
Since puppet doesn't have HA/fail over capabilities as of now. How does one
mitigate a puppet master failure( Ex. Hardware). When you replace the server
and configure the Puppet masterd, the clients may no longer be able to
communicate with the server, since the
Greetings,
I'm having a bit of a problem where file{} doesn't support globbing...
Say I have the following directory tree:
/foo (mode: 0751)
/foo/bar1
/foo/baz1
/foo/random1
...
/foo/randomN
All subdirectories under '/foo' can be arbitrary names...
How I would like to be able to express this,
We had exactly the same problem at our site over the weekend and
resolved it by... logging in to every node, stopping puppetd, cleaning
out /var/lib/puppet, and starting puppetd once again. We still use a
twisted-python tool to run one-off commands and executables in
parallel with ssh,
Hello,
I have the following define:
define adduser ($shell, $group, $fullname, $ingroups = none, $home = none) {
user { $name:
ensure = present,
comment = $fullname,
gid = $group,
groups = $ingroups,
membership = minimum,
shell = $shell,
home = $home,
On 3/31/10 5:37 PM, Terra wrote:
Greetings,
I'm having a bit of a problem where file{} doesn't support globbing...
Say I have the following directory tree:
/foo (mode: 0751)
/foo/bar1
/foo/baz1
/foo/random1
...
/foo/randomN
All subdirectories under '/foo' can be arbitrary names...
How I
ok, I will do that.
I am using apache + passenger.
Thanks.
On Wed, Mar 31, 2010 at 12:05 PM, Brice Figureau
brice-pup...@daysofwonder.com wrote:
On Wed, 2010-03-31 at 07:29 -0700, Nigel Kersten wrote:
On Wed, Mar 31, 2010 at 7:19 AM, Brice Figureau
brice-pup...@daysofwonder.com wrote:
Hello Brian,
On Mar 31, 3:24 pm, Brian Wingenroth wingenr...@jhu.edu wrote:
On 3/31/10 5:37 PM, Terra wrote:
Greetings,
I'm having a bit of a problem where file{} doesn't support globbing...
Say I have the following directory tree:
/foo (mode: 0751)
/foo/bar1
/foo/baz1
On Wed, Mar 31, 2010 at 6:30 PM, Darvin Denmian darvin.denm...@gmail.comwrote:
Hello,
I have the following define:
define adduser ($shell, $group, $fullname, $ingroups = none, $home =
none) {
user { $name:
ensure = present,
comment = $fullname,
gid = $group,
I was hoping that there was a way for Puppet to remember the
subdirectories and only chmod on new subdirectories that are not mode
700...
or if that is too complicated to support internally, then something
simple like:
If file{} had globbing ability, then
[pseudo] file { /foo/*: ... }
Message initial
De: Michael DeHaan mich...@puppetlabs.com
Reply-to: puppet-users@googlegroups.com
À: puppet-users@googlegroups.com
Cc: James Turnbull ja...@lovedthanlost.net
Sujet: Re: [Puppet Users] Mongrel : Can't download files
Date: Wed, 31 Mar 2010 10:17:24 -0400
On Wed,
42 matches
Mail list logo