> Cobbler manages all its internal info. To get Puppet to manage it
> would, IMO, either involve hacking Cobbler or wrapping Cobbler
> command line calls in Puppet "exec" resources.
Cobbler has also an API you can talk to. There is a cobbler gem [1], [2]
that provides you an easy way to interact
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
>>> I am hesitant for us to put something like this in the core distribution
>>> though, simply because we know it's a maintenance problem over time.
>>
>> Fair enough.
>>
>> Though I imagine not having this feature will lose puppet some people.
>
> T
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> [root@foo me]# ./puppet-wget file_content/sudo/sudoers
> https://foo.bar:8140/file_content/sudo/sudoers
> warning: peer certificate won't be verified in this SSL session
> /usr/lib/ruby/1.8/net/http.rb:2099:in `error!': 403 "Forbidden request:
> foo.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi
> If you have used a public accessible manifest for ruby 1.8.7 ree or
> you are willing to share ... I am looking for one!
I would look on how to generate packages for your distro for REE (if
they aren't yet available) put them in a local reposito
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> as i m able to see that puppet master taking around 7-8 seconds to
> compiler catalog
> and puppet client taking around 1106 second to apply catalog .
run the client with --summarize and see on which resource types it is
spending most of the time, t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/04/2011 08:49 PM, Michael Halligan wrote:
> Forgive my cluelessness, but why is it so difficult for Puppet to at least
> tell me what file this came from like 90% of other errors I've encountered?
I don't think there is a particular reason. Did
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> File: 1539.03
This indicates clearly a problem in serving files, so does the other
error you posted.
As others asked: Are you still running with Webrick (means default
puppetmaster without setting up passenger/mongrel)? And how many
c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This
> file { "a":
> path => " aaa ",
> before => Exec[ "b" ],
> }
>
> exec { "b":
> command => "bbb",
> before => File[ "c" ],
> }
>
> file { "c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/12/2011 05:26 PM, Dan White wrote:
> This tells me RedHat picked Foreman over Cobbler. It does not tell
> me WHY.
>
> Their reasons may not apply to my situation.
>
> I am not trying to be difficult, but I find that I cannot accept an
> opinio
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Is using an empty class in init.pp problematic ? All of these modules
> worked just fine before going from 2.6.8 to 2.7.1.
I have no idea, whether this is the problem. But why do you do:
> # manifests/init.pp
> import "classes/*.pp"
>
> class kv
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/12/2011 12:19 PM, Al @ Lab42 wrote:
> You might find this define useful (
> https://github.com/example42/puppet-modules/blob/master/common/manifests/defines/netinstall.pp
>
> ):
>
or as a general best practice you might want to build your ow
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/13/2011 08:51 AM, Roni wrote:
> I created manifest for our webserver. manifest included git clone,
> database creation and restore database etc How to order the
> installation and exec exactly
by using require, before, notify, subscribe...
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> same problem for me.. I've notice the problem on modules using
> autoloading...
>
> I think I will stick to version 2.6.9...
can you at least file a detailed bug report? Thanks! Otherwise the
situation can't be really improved...
~pete
-BEGIN
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
>> I'm guessing I'll have to write my own to do that -- does anyone have
>> any examples of logging the error message and also adding it to the
>> report object? (... and I don't really want to use the exec {
>> "/bin/false": } workaround)
>
> Diggi
> The swapfiles is a large directory with lots of files. Is there a way
> to avoid this, since its taking lots of time to compile the catalog
> from the puppetmaster. Can i somehow prevent this?
I guess it's not during compilation, as this happens on the master,
rather while applying the catalog.
On 07/25/2011 05:07 AM, Zain Memon wrote:
> Is there some way I can access variables from puppet.conf (e.g.
> $confdir) in my manifest?
${settings::confdir} but in a master client/setup these are the settings
from the master. So what you want to do is to write a custom fact that
exposes your setti
> I have about 130 customer puppet.
> I left the default time interval.
Are you still running with default webrick on the puppetmaster? (If you
didn't change anything, then yes you are).
If yes, it's time to scale out and use either a Mongrel or
Passenger-based Setup:
http://projects.puppetlabs.c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/28/2011 12:09 AM, Nick Moffitt wrote:
> vagn scott:
>> Funny you should mention that. I have been playing around with
>> separating the puppetmaster config from the agent config. See here:
>>
>> http://agawamtech.com/blog/?p=383
>
> I solv
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> It just seemed to me that there must be some way to derive what is
> installed on the client within a manifest but I couldn't find any
> suggestions on Google or PuppetLabs site so I asked.
Manifests are compiled to a catalog on the master. The cata
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> I know that there's a 'certname' option but it looks like it's only valid in
> the [agent], not the master section. How do I do this?
It works in the master section as well.
~pete
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Com
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
>> Is this a known issue? Is there any work-around? It's really breaking my
>> CentOS 6 servers' ability to find their REPOs. :-)
>
> You need to have the lsb_release command installed for the lsb* results
> to appear.
>
> Fedora/Redhat have it in t
On 08/02/2011 04:20 AM, Aaron Grewell wrote:
> I recommend taking a look at R I Pienaar's alternative extlookup
> implementation. It supports YAML in addition to csv which allows for the
> full range of available variable types to be pulled in from external
> sources. I've combined this with a Y
>> Can someone walk me through the steps of sending out a password to all
>> my computers for user "student."
>
> I do this a lot:
>
> yes 'PASSWORD' | passwd username
>
> Then you can extract the password from /etc/shadow
>
> also see here:
>
> http://serverfault.com/questions/87874/how-shou
> Its my understanding the 'customfact1' fact is meant to be transferred
> to the host as part of the pluginsync process before the catalogue is
> rendered, but this doesn't seem to be happening on our new builds from
> the above error.
Yes it works exactyl that way.
> Does anyone have any insigh
On 08/03/2011 04:44 PM, Matthew J Black wrote:
> Not sure if that'll work right but one option is you should be able to use
> the generate function in the manifest to make an external call within the
> puppetmaster to create the encrypted password. The downside is that its
> going to execute every
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi
> I wanted to manage a couple of groups membership, under RedHat,
> without managing the users (as they are LDAP users) but found out it
> is not supported Is there a workaround to this?
As denmat mentioned as well I would generally try to avo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Also I noticed I can only read the first file, the changed file, not
> the second, the original (content changed '{md5}
> 70c1c6de6d4b1a02ec32b463e4d255b0' to '{md5}
> 78124298c2b4c1e63658599a2c208853') :
>
> info: FileBucket read 70c1c6de6d4b1a02ec
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> modules/rep/templates/test_template.xml.erb
>
>
>
But for reusable modules etc. I would recommend you to look into hiera
[1] and to combine it with parametrized classes as shown in [2], it
makes it quite easy and really extensible.
~pete
[1]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Well this is all awfully confusing. The documentation pretty clearly
> says that using the require function automatically adds that class as
> a dependancy. If so, why would I need to explicitly add require => to
> resources? If I had to do that, I'd
On 09/07/2011 11:44 AM, piavlo wrote:
> Trying to use extlookup from within template i use
>
> <%= scope.function_extlookup("blah") %>
>
> but get the undefined method `function_extlookup' error
>
> According to
> http://docs.puppetlabs.com/guides/templating.html#access-to-variables-and-puppet-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> This change in the init script fixed the problem:
>
> #pidfile=/var/run/puppet/puppetmasterd.pid
> pidfile=/var/lib/puppet/run/puppetmasterd.pid
>
> Is that a bug worth reporting?
I would, at least somebody can then decide if it's really a bug or
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
>> You've seen this with your own resources where the parent is a directory and
>> the child is a file?
>> Please bug report, as it's been a very long time since that autorequire was
>> put in (0.24.x ? 0.25.x?), and I haven't seen a reported bug since
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Let me start by saying I'm really jazzed by what i'm uncovering on the
> *nix front with Chef - seems like a LOT of what I'm looking for is
> already done.
>
> Is there a writeup somewhere that shows/documents manipulating an esx
> server/creating/c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> We're at about the 100 hosts, but have closer to 1500 services - maybe we
> have exceeded what storeconfigs can do then. If that is the case, is there
> a recommended alternative that isn't manually maintaining config files?
Just to be clear: Afte
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> The good thing with this method is that you can manage the module
> directory (where the different config file excerpts are stored) with
> 'purge => true' so that only exported resources are present in the final
> nagios configuration (something that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> I expect the default user provider should be useradd(8) but
> ProviderUseradd seems to be looking for 'chage' binary which isn't
> used on OpenBSD. I've checked out the 'Puppet OpenBSD' doc but didn't
> find anything applicable. Searching archives an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> I would reference from back from the sysconfig::permissions module to
> the ntp module file by specifying
> name => "/var/lib/ntp"
>
> Do I need to change all my modules because I used a feature of puppet
> which should not be there, and if so, how
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> A single manifests works fine, but this is not the only module I have
> where I set permissions using the sysconfig::permissions module.
Ah, now I as I read your problem better: The error indicates more that
you name two resources with the same name
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> 1) Use a template. Templates have embedded ruby code and run on the clients.
template() is a function and as any other function it will run on the
server.
~pete
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi
> I'll try to setup apt-pinning.
the apt module @ https://labs.riseup.net/code/projects/shared-apt/
Can help you by setting up pinning:
https://labs.riseup.net/code/projects/shared-apt/repository/revisions/master/entry/README#L303
~pete
-BE
Is it ok if i just upgrade puppetmaster to 2.6.12 and still using
old puppet.conf with certdnsnames?
The certdnsnames have been abandonned in favor of a new option:
http://docs.puppetlabs.com/references/stable/configuration.html#certdnsnames
And if your current client certificates contain a
Wish I could've found that in the docs.
This will certainly get me going again.
Sounds like a ticket for puppet documentation...
~pete
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To post to this group, send email to puppet-users@googlegro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/01/2011 02:50 AM, Jo Rhett wrote:
> Mon Oct 31 23:03:31 + 2011 Puppet (notice): Caught TERM;
> calling stop
>
> Ever since the 2.6.12 upgrade I've been seeing these reports reach
> us. As in, about a hundred of a half thou machines. Most of
> Thanks Chris, that's helpful. I am wondering if I should be mixing
> Ruby DSL manifests with the Puppet DSL manifests. Is there any
> recommended practice for keeping both styles together?
Afaik you can mix both DSL. If one file in a module ends with .rb it's
ruby dsl, if it ends with .pp it's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> I've been using hiera for a few weeks now, but I'm stuck now trying
> to set a value to false
>
> Basically, I have a class that read its parameter in hiera, and in
> a yaml file I have the following code:
>
> --- use_ecrypt_fs: true server_region:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> When agent notices that master.passwd should be refreshed, how
> exactly does copy process happen? Is it atomic (e.g. fetch to some
> temp filename on local filesystem and then rename)?
it does it this way.
~pete
-BEGIN PGP SIGNATURE-
Ver
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/07/2011 08:55 PM, Stefan Heijmans wrote:
> The sorting in the log tab on a node report seems to be on the
> level column, which is hard to read when multiple changes take
> place, as notice and info of the actions are on the top and bottom
> of t
exec {
'oracle-extract-part':
command => "/usr/bin/printf
\"n\np\n2\n2091\n+16384M\nw\n\" | /sbin/fdisk /dev/xvdj",
unless => "/bin/cat /proc/partitions | /bin/grep
${orcl_ephm_device}2";
}
if you don't need to interpolate a variable, you can simply use single
Zitat von Max Schubert :
How about using the alternate single quotes in ruby
%q{string string string}
puppet manifests are not ruby code.
~pete
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To post to this group, send email to puppet-use
Are there still any known issues with puppet and ruby 1.9?
Or 1.8.7 is still the preferred version to use with puppet?
latest 2.7 is imho fully supported by 1.9
~pete
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To post to this group, send
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> augeas{"samba-global2":
> context => "/files/etc/samba/smb.conf/
> target[.='global']",
> changes => [
> "set workgroup MSHOME",
> "set 'os\ level' 31",
>
Hi
But we won't use the zpool type ever again. Its just not worth it.
Here's what happened:
. one of our servers lost knowledge about one of its zfs pools
. puppet didn't find the pool and .. went on to zpool create it
. we did indeed have a backup, but would have lost all data if not
Creati
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi
> On Tue, Apr 6, 2010 at 10:52 AM, Kaspar Schiess wrote:
>> Creating zpools is a manual thing in every case, since one has to know the
>> devices participating. The names of which tend to be a little bit different
>> from one server to the next.
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> I've seen excessive memory usage in some clients due to odd variants -
> the Linux OOM killer usually kicks in at some point. Check 'dmesg' to
> make sure it wasn't this.
>
> Also - are you catching core dumps on your box incidentally? And as
> Tore
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> I seem to have found the exact same bug at
> http://projects.puppetlabs.com/issues/3387
>
> Is there any way to easy way to check to see if that fix is in 0.25.5rc1?
>
it looks like it is:
http://github.com/reductivelabs/puppet/commits/0.25.5rc1?
I would like to specify a condition, what is the wright syntax for
<% if hostname == 'some' or 'someother' then %>
erb is plain ruby, so have a look at the ruby language, how the right
syntax would be. I assume you would like to do something like:
<% if (hostname == 'some') || (hostname == '
That's great! And what to do with various passwords, private keys and so on?
Should I put them in manifest?
That is a hard call, and there is probably no single answer.
For what it is worth, we decided that this was an acceptable security risk in
some places (database passwords containing uncla
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> cron { "app":
> command => "nice -n -10
> /usr/bin/php/var/www/public_html/rotinas/rotinas.php 2>&1>>
> /var/log/app.log",
> environment => "PATH=$PATH",
> user=> root,
> }
>
> I got the same error:
looks like a bug,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/13/2010 10:50 PM, Darvin Denmian wrote:
> Here is the output:
and here is the url:
http://projects.puppetlabs.com/projects/puppet/issues/new
;)
cheers pete
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG wi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/13/2010 10:08 PM, ed-rfmd wrote:
> Is there a way to control the order of the mounts?
> We have a few second level directories in /a that need to mount after /
> a is mounted but it appears that /a is being mounted after /a/1 and /a/
> 2. If I do
Hi
notice: Starting Puppet client version 0.22.4
can you try with a more recent version? the current supported versions
are imho 0.24.x and 0.25.y (where x or y is the latest version of that
branch).
cheers pete
--
You received this message because you are subscribed to the Google Group
I was thinking of bumping to 0.25.3 (latest EPEL, puppetmaster then
nodes), and then switching over
to Passenger. Is that a sensible approach? Thanks!
yes, but I would go for 0.25.4 (You'll find EPEL rpms for them) or
wait a little and get 0.25.5. both versions contain numerous fixes and
0.2
Is there a way that I can ensure that puppet renders the file in order
the script is written ?
No. And that's not a bug it's (really!) a feature.
If you have dependencies and they matter, then define (via
require,before,subscribe,notify) and hence _document_ them. If there
are no dependenci
and:
Now in many cases puppet tries to execute Exec["install-mysql-gem"]
before Package["ruby-devel"] or Package["rubygems"] or both.
no that shouldn't be the case. if you define such a require, both
packages are installed _before_ the exec is executed.
Are you really sure that it is the w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Now I am able to get puppet work for me in very first run. I had to do a
> require => Exec["updateyum"] for every package installation in order to
> ensure that the command yum update -y ran before package is being installed.
> However this brings me
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Is is true enough to say that eventually, everything will run?
One simple rule: if order matters, specify and hence document it,
otherwise everything will run.
cheers pete
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Usi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/19/2010 07:26 PM, SyRenity wrote:
>> Just to clarify, Func does not use SSH.It uses XMLRPC over SSL, very
>> similar
>> to how Puppet works (no REST though), and has a daemon.
>
> I see, so Fabric is actually the only tool which allows agen
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> distid = Facter.value('lsbdistid')
> if distid.match(/RedHatEnterprise|CentOS|Fedora/)
sidenote: you can use confine for such things.
[...]
> I can see the fact on the client node (but only if I add "--puppet"):
> # facter --puppet|
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> But this should not be. Has Puppet problems, when I have serveral
> words in afact, since it works perfectly for Xen Systems.
as far as I can see not:
$ cat foo.pp
$manufacturer1 = 'Xen'
if ($manufacturer1 == 'Xen') or ($manufacturer1 == 'Sun Micro
You saved my day. Actually there was a lot of white space :-) Now my
module looks like:
imho this shouldn't be, can you file a bug?
cheers pete
--
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...@
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Our suspicion comes down to its a problem with a timeout since
> usually it stops after a high catalog run time.
>
> So ... Any idea on how to track this down ? _any_ input is welcome
No except, that I see the problem as well:
http://projects.redu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/23/2010 10:07 AM, Phillip B Oldham wrote:
> So, am I correct in thinking then that the following workflow *can't*
> be done with puppet?
>
> 1) The EC2 instance starts up, and the puppet client on the instance
> connects to the puppet master.
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/24/2010 01:02 AM, Douglas Garstang wrote:
> Is there a way to stop puppetd from logging the command line arguments
> passed to an Exec() ?
>
> I need to pass sensitive options, ie passwords, on the command line,
> and don't want them to appear i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> How can do I this with File{}? I'm can't seem to find a way to do it.
> In general times, how can you deploy file A only when file B does not
> exist?
use a fact indicating that file A exists.
cheers pete
-BEGIN PGP SIGNATURE-
Version: GnuP
include opsys::$operatingsystem
include "opsys::${operatingsystem}"
cheers pete
--
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 t
class opsys::CentOS {
class opsys::centos {
cheers pete
--
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.
right, classes cant have Caps as the first char (or maybe even
anywhere? not sure).
anyway, you'd probably need to look at a case statement then that
includes opsys::centos for $operatingsystem == CentOS and similar
for your other operating systems. :(
puppet does that already for us:
$
Well that's weird and mildly confusing. The class is opsys::centos but
we're really including opsys::CentOS. Nice.
because puppet can't have any classes started with capitalized letters
(global resource identifier clash) and anything else behind is anyway
downcased (class tEST == class test)
Your site.pp should look like:
include os::setup
Package {
require => Class["os::setup"]
}
other wise the classes is not avaiable, how should puppet set a
relation to something that is not included in its manifests?
cheers pete
--
You received this message because you are subscrib
Your site.pp should look like:
include os::setup
Package {
require => Class["os::setup"]
}
other wise the classes is not avaiable, how should puppet set a relation to
something that is not included in its manifests?
Oh, well... that's also ugly. :(
what?
--
You received this message b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> [0] I have various nodes defined by function (e.g. database server) that
> inherit from a base node. One thing the base node does is check a fact
> that returns the location of the client. It then includes a module with
> the location-specific config
Is there any editor that can understand puppet DSL with syntax high-
lighting?
vim, emacs . At least those are the one for which there are syntax
files: http://github.com/reductivelabs/puppet/tree/master/ext/
I remember that there was also some support for textmate.
cheers pete
--
You re
A feature request - if puppet can't read the local certificate, it
should throw a permission error of some sort.
Please file one at: http://projects.puppetlabs.com/projects/puppet Thanks.
cheers pete
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" g
This might be a good project for someone interested in Eclipse.
Maybe you could take a stab at it using those as a reference and then
we could check them in for others to use?
I talked once with an eclipse contributor about that and he mentioned
that with the various built in support for DSL s
I saw an error like this when the client was 0.25.x and the server
was 0.24.x.
Thank you - but I've got both 0.25 - this is the same node which is
running puppetmaster.
I've purge storedconfig database - and this solved problem. Strange...
which version of 0.25.x ? There was issue that have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> From what I see, yours will cope with the case where I update menu.lst
> server-side, but what if somebody changes the client's copy
> of /boot/grub/menu.lst? It seems puppet won't notice it so won't recover
> the "proper" contents (as per the pu
Puppet.domain.com puppetmaster.domain.com both point to the correct
machine. The client can connect to the server with no problem, and
also vice versa. The firewall is relaxed sufficiently on both client
and server for puppet to communicate. Both systems are on the same
network switch, all
but I'm not too sure how to set the value of $CLASSNAME.
we do something similar:
file{'/etc/exim/exim.conf':
source => [ "puppet://$server/modules/site-exim/${fqdn}/exim.conf",
"puppet://$server/modules/site-exim/${exim_type}/exim.conf",
"puppet://$server/modules/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> The names of the hosts have been changed to protect the innocent.
>
> Puppetmaster is version 24.8 and running on FreeBSD 7.2.
can you check how your puppetmaster is started? sometimes init script
add additional cli parameters which overwrite what
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Does this mean a default for /var/lib/puppet/lib/facter/ instead
> of /var/lib/puppet/facter/? Seems a bit weird, doesn't it?
This change puts the plugins stuff more in line with modules etc.
Additionally, for example other plugins for puppet go t
However, if I open it in debug mode, it says:
[r...@server /usr/local/etc/rc.d]# puppetmasterd --no-daemonize --
debug --verbose /usr/local/etc/puppet/puppet.conf
shouldn't you use:
# puppetmasterd --no-daemonize --debug --verbose --config
/usr/local/etc/puppet/puppet.conf
?
cheers pete
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> I specifically want to use the RPM provider, not the yum provider.
> Otherwise (as I understand it) I will have to set up a yum repository
> for each machine (or at least environment), and updating/rolling back
> our app will be more complicated than
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> I suspect we will turn 'node default' into 'class default', then include that
> rather than inheriting that, since that does fix the scope issue.
this is imho the way to go if you don't want to switch over to an
external node tool.
For each node I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi
>> I think about whats the best solution to have puppet-proxys for
>> systems without direct connection to the puppetmaster.
>>
>> - Route all the trafic with iptable forwarding to one puppetmaster.
>> - Build puppetmaster-proxy vm's installed from
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi
> These are the ones I know about:
>
> http://github.com/camptocamp/puppet-apache
> http://github.com/wesabe/puppet-apache2
> http://github.com/puppet-modules/puppet-apache
> http://github.com/simpsonjulian/puppet-apache-ubuntu
> http://github.com
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> So I just upgraded my master from 0.24.8 to 0.25.4. Apparently there
> is some bug with the EPEL version of rails that results in mysql "too
> many connections" with stored configs, so I just bailed from the
> packaged stuff and went to a standalone
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/20/2010 03:03 AM, mathie wrote:
> Hello,
>
> I would like to manage configs for the server that is also the
> puppetmaster. I declare a simple node (just write out a file) and ran
> this:
>
> puppetd --test --graph -w 10 --server puppetmaster.e
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> While I haven't used them (yet?), there are a few modules available on
> github that provide the ability to declare unmanaged hosts. Here's an
> example, but not the only one:
>
> http://github.com/duritong/puppet-nagios
>
where [1] is the much n
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/28/2010 07:30 AM, prudhvi wrote:
> I face the same problem when trying the package type
> [...]
> It asks me for root privileges..
well I know 0 system-wide package management systems that don't require
root to change the system. but if you got
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> we´ve upgraded puppet from 0.24.8 to 0.25.5 last week, since then we
> ´re experiencing load/memory (and then swapping) problems. Our setup
> is based on nginx (0.8.20, four worker processes) balancing to five
> puppetmaster instances (servertype mon
1 - 100 of 605 matches
Mail list logo
