Hi Lars,
Take a look at virtual resources:
http://projects.puppetlabs.com/projects/1/wiki/Virtual_Resources
-Josh
On Nov 18, 2010, at 3:28 PM, Lars Francke wrote:
> Hi,
>
> I'm trying to manage our Hadoop cluster with Puppet but there are a
> few challenges. The one I'm facing now is managing
hi Daniel,
i got the problem of "Why does Puppet keep trying to start a running
service?"
The ideal way to check for a service is to use the hasstatus
parameter, which calls the init script with the status parameter. This
should report back to Puppet whether the service is running or
stopped.
I
hi Daniel,
i got the problem of "Why does Puppet keep trying to start a running
service?"
The ideal way to check for a service is to use the hasstatus
parameter, which calls the init script with the status parameter. This
should report back to Puppet whether the service is running or
stopped.
I
"russell.fulton" writes:
I am going to mostly use this as a soapbox to expound on how I do this sort of
thing, but will answer your questions along the way. I hope you don't mind. :)
> I have a requirement to generate several very similar config files
> which are just a couple of tokens differe
Hi
I have a requirement to generate several very similar config files
which are just a couple of tokens different and with different names.
These are barnyard conf files if anyone is interested and differ only
in the interface name which is also part of the file name. I can
include [eth1, eth2]
On Nov 18, 2010, at 5:23 PM, Ed Greenberg wrote:
> and also fileserver.conf:
> # cat /etc/puppet/fileserver.conf
> [files]
> path /var/lib/puppet/files
> allow *
> [plugins]
> path /var/lib/puppet/facts
> allow *
>
>
>
> I put my fact file (plesk_version.rb) in the /var/lib/puppet/facts
> dire
May I please ask again for some assistance with the question below? I
hope somebody can help me.
Thanks,
Ed Greenberg
Original Message
Subject:Re: [Puppet Users] Using custom facts in Puppet
Date: Tue, 16 Nov 2010 13:14:06 -0600
From: Ed Greenberg
Reply-To:
I am trying to import a hash definition from a separate file but this
fails whereas including the text verbatim in the original manifest
works fine:
class monitor ($master, $interface) {
# import "masters.pp"
$sensor_rule_categories = {
'dmzo' =>
[scan,finger,ftp,telnet,rpc,rservic
Don't know what to tell you. Commenting out the line in that file fixed the
problem. And it's been working great since.
On Thu, Nov 18, 2010 at 5:51 PM, Felix Frank <
felix.fr...@alumni.tu-berlin.de> wrote:
> On 12.11.2010 19:22, techn0gichida wrote:
>
>> I found the problem in /etc/sysconfig/pup
Hi,
I'm trying to manage our Hadoop cluster with Puppet but there are a
few challenges. The one I'm facing now is managing the following.
I've got an array variable depending on the type of server:
$hadoop_disks = ['/mnt/disk1', '/mnt/disk2', ...]
Depending on the classes I include for each role
On 12.11.2010 19:22, techn0gichida wrote:
I found the problem in /etc/sysconfig/puppetmaster. The MANIFEST
directive wasn't commented out. Shouldn't this be commented on that it
needs to be commented out for multiple environment use?
I don't really see your point. Yes, there is a commented out
Hi,
Has any work been done or is any work being planned to allow plusignment
to add values to a resource several times?
This has been discussed before at
https://groups.google.com/group/puppet-users/browse_thread/thread/b276948477fa14ae
http://projects.puppetlabs.com/issues/2825
My immediate u
On 09.11.2010 10:33, luke.bigum wrote:
Roman,
Not that I know of. I'm still aware it doesn't work in my site, but
I'm content with local file bucketing until I have the time to look at
this again.
-Luke
On Nov 9, 3:47 am, Roman wrote:
Hi James.
Could you tell if you found a resolution to th
On 11.11.2010 11:06, Chris wrote:
In the general case, even completely legitimate (and common) Latin-1
text files can cause Puppet problems because some Latin-1 bytes are
not valid UTF-8. In my opinion, the content parameter of a file
resource should be able to handle these cases.
I think yo
On Thu, Nov 18, 2010 at 1:45 AM, Nick wrote:
> Hi,
>
> On 18/11/10 03:06, Eric Sorenson wrote:
>> Note I also changed your 'recurse => true' to 'recurse => remote', a sadly
>> under-documented feature which eases recursive copies by recursing the source
>> directory to build a list of files that n
On Thu, Nov 18, 2010 at 12:01 PM, Scott Smith wrote:
> Puppetmasters (the puppetmasterds serving catalogs) don't need access to the
> same SSL dir the Puppet CA (the puppetmasterd signing and revoking certs).
> But, they do need to share the private key for presenting the certificate
> for puppet.
On Thu, Nov 18, 2010 at 12:21 PM, byron appelt wrote:
> I figured it out. I do not see the facts being synced on the bootstrap
> run and I no know why. Since I am using puppet to configure itself,
> there is no puppet.conf on the bootstrap run and therefore no
> pluginsync=true. I just have to do
I figured it out. I do not see the facts being synced on the bootstrap
run and I no know why. Since I am using puppet to configure itself,
there is no puppet.conf on the bootstrap run and therefore no
pluginsync=true. I just have to do the bootstrap run with the --
pluginsync option and all is well
Hello All,
Is there a way of suppressing DEPRECATION WARNINGS? Ever since I
upgraded rails, I keep on getting deprecation warnings that I run
puppetd. Is there any way of turning these off? i.e,
ruby --version
ruby 1.8.6 (2007-09-24 patchlevel 111) [i686-linux]
puppet --version
DEPRECATI
Puppetmasters (the puppetmasterds serving catalogs) don't need access to the
same SSL dir the Puppet CA (the puppetmasterd signing and revoking certs).
But, they do need to share the private key for presenting the certificate
for puppet.domain.com. And the CRL as well, if you use it. That director
On Nov 19, 3:22 am, jcbollinger wrote:
> Oops, sorry for the empty post.
>
> On Nov 17, 8:50 pm, kiwi wrote:
>
> > Any idea what is wrong here?
>
> Could it simply be that you have misspelled 'monitor' in your
> resource's "source" property?
Doh!!! I spent hours looking at that! I thought I
Apologies -- the last two messages I sent to the list have not
appeared ...
--
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
On Wed, Nov 17, 2010 at 9:14 PM, Patrick wrote:
> I think I heard somewhere that pluginsync ignores environments.
This is absolutely not true in the last two major versions of Puppet.
You may have been thinking about how plugins-in-modules didn't work
particularly well with environments in 0.24.
On Thu, Nov 18, 2010 at 10:04 AM, byron appelt wrote:
> I'm sure I don't understand something here, but when I look at the
> value of the facts on the puppetmaster, they are strings and some of
> them are false. I know the fact is coded to return a boolean, but I
> assumed there is a to_s occurrin
I'm sure I don't understand something here, but when I look at the
value of the facts on the puppetmaster, they are strings and some of
them are false. I know the fact is coded to return a boolean, but I
assumed there is a to_s occurring somewhere along the way. See below
(hostnames altered to prot
On Nov 18, 1:56 am, Ian Ward Comfort wrote:
> On 18 Nov 2010, at 1:06 AM, Owen Smith wrote:
> >
> > class testa {
> > notify {
> > "note_testa": message => "Test A!";
> > "note2_testa": message => "Test A take 2!"
> > }
> > }
>
> > class testb {
> > notify { "note_testb": messa
I think it's a bad idea to deal with the overhead of an NFS mount when
you have a dedicated puppet CA, as on your non-CA servers there should
be no need to ever write to that directory.
On Wed, Nov 17, 2010 at 7:55 PM, Scott Smith wrote:
> Oh, that's for sharing the puppetmaster SSL keypair betw
On Thu, Nov 18, 2010 at 6:46 AM, byron appelt wrote:
> I am delivering the fact with pluginsync, but that will not have
> occurred yet on bootstrap because puppet has yet to run for the first
> time and deliver the fact. At least that is what I think is happening.
> If I do a run that does not inc
Hi,
On 18/11/10 03:06, Eric Sorenson wrote:
> Note I also changed your 'recurse => true' to 'recurse => remote', a sadly
> under-documented feature which eases recursive copies by recursing the source
> directory to build a list of files that need checksumming, not the target.
> (see http://projec
Hi,
On Thu, Nov 18, 2010 at 4:09 AM, Daniel Pittman wrote:
> That wouldn't actually help: the package provider and the service provider
> would need to collude, and Puppet doesn't really support that.
>
I forgot runit made things simpler, by having runit-policy.d which would
prevent a service t
On 11/10/2010 05:16 PM, Gabriel Filion wrote:
> On 11/10/2010 10:18 AM, luke.bigum wrote:
>> Hi list,
>>
>> When declaring multiple resources at once with an array like this:
>>
>> file { [ "foo", "bar" ]: ... }
>>
>> Is there a way to access the current array element so as to pass this
>> value as
I am delivering the fact with pluginsync, but that will not have
occurred yet on bootstrap because puppet has yet to run for the first
time and deliver the fact. At least that is what I think is happening.
If I do a run that does not include the class referencing the fact
first, it will work fine o
You should post to the DC-SAGE mailing list.
Trevor
On Wed, Nov 17, 2010 at 6:19 PM, Mohamed Lrhazi wrote:
> We are committed to deploying puppet and using it as our main tool for
> managing all our systems but we are far from having fully deployed
> it...
>
> The person we would hire would
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> So, the logs are reporting that everything was successful, yet nothing
> is actually getting applied. Where can I begin to troubleshoot this
> issue?
what is the version of your master?
~pete
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (G
Oops, sorry for the empty post.
On Nov 17, 8:50 pm, kiwi wrote:
> Any idea what is wrong here?
Could it simply be that you have misspelled 'monitor' in your
resource's "source" property?
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post
On Nov 17, 8:50 pm, kiwi wrote:
> I am having grief with another directory -- almost identical set up as
> previous message. This time I am getting
>
> err: /Stage[main]/Monitor/File[/home/snort/conf/pp]: Failed to
> generate additional resources using 'eval_generate': Error 400 on
> SERVER: No
On Nov 18, 2:56 am, Daniel Maher wrote:
> My question is this : what have other Puppet admins done in order to
> ensure that a target machine has the freshest local dbcache before
> attempting to install a package ?
I set up a cron job (via Puppet) that periodically performs a "yum
clean all".
It looks to me like the client is receiving an essentially empty
catalog (all the resources I see mentioned belong to Puppet itself).
Since that's apparently not what you expected, it probably implies an
error in your manifests. Is there a node definition for this host?
Does it specify any resourc
On Nov 18, 2010, at 12:56 AM, Daniel Maher wrote:
> Hello,
>
> I have run into problems in the past where a package has been added to our
> yum repository, and a (new) class has been pushed to install that package,
> but puppet fails because the yum db on the target machine is too stale, and
Perhaps you could adjust one of the /etc/yum.conf parameters like
metadata_expire down from its default of 1.5 hours or keepcache = false
(not entirely sure that this one does what you want it to do). The
metadata_expire one can be set at the repo level so you could set it
only for your own repo.
On 18 Nov 2010, at 1:06 AM, Owen Smith wrote:
> I'm running into an interesting problem that I'm hoping someone out
> there knows more about than I.
>
> Consider the following code:
>
>
> class testa {
> notify {
>"note_testa": message => "Test A!";
>"note2_testa": message => "T
On 18 Nov 2010, at 12:56 AM, Daniel Maher wrote:
> I have run into problems in the past where a package has been added to our
> yum repository, and a (new) class has been pushed to install that package,
> but puppet fails because the yum db on the target machine is too stale, and
> thus isn't aw
Greetings all,
I'm running into an interesting problem that I'm hoping someone out
there knows more about than I.
Consider the following code:
class testa {
notify {
"note_testa": message => "Test A!";
"note2_testa": message => "Test A take 2!"
}
}
class testb {
notify {
Hello,
I have run into problems in the past where a package has been added to
our yum repository, and a (new) class has been pushed to install that
package, but puppet fails because the yum db on the target machine is
too stale, and thus isn't aware of the existence of the new package.
My qu
44 matches
Mail list logo
