Hello,
I'm currently running Puppet 0.25.5-1 on CentOS 5.5. Everything has
been going swimmingly until a couple of weeks ago, when I began
receiving errors on one of my nodes. The node in question is also my
puppetmaster, but the errors seem client-related. The errors are:
err: //yumrepos::cen
Thanks, John.
I just checked the contents of the files in /etc/yum.repos.d, but only
found [updates] in one file, updates.repo:
[11:26 r...@cab yum.repos.d]# grep updates /etc/yum.repos.d/*
/etc/yum.repos.d/updates.repo:[updates]
/etc/yum.repos.d/updates.repo:baseurl=http://mirror.linux.duke.edu/
t myself a custom fact 'nodetype' that gets set in some suitable
> way.
Thanks for the suggestion. I wish there was a simpler approach, like
specifying the "type" on the puppetd command-line. In large server
farms it seems like it would be a really common
On Jun 4, 4:26 pm, Thomas Bellman wrote:
> However, a "real"
> custom fact is probably cleaner.)
>
I'm working on a "real" fact by following these steps:
http://reductivelabs.com/trac/puppet/wiki/AddingFacts
I verified that the custom fact works when run locally on the server.
On the client
On Jun 4, 8:27 pm, Brad wrote:
> I'm working on a "real" fact by following these steps:
> http://reductivelabs.com/trac/puppet/wiki/AddingFacts
>
> I verified that the custom fact works when run locally on the server.
> On the client when I run:
>
at the top. I just made a page edit.
-Brad
--~--~-~--~~~---~--~~
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@googlegroups.com
To unsubscribe from this
;abc":
param => "p1",
}
b { "def":
param => "p2",
}
type { "foo":
require => B["def"],
}
What I would hope happens is that when b is instantiated with each
name, puppe
Is it okay to ask questions about the mcollective puppet module by
puppetlabs here?
If so, I'm getting this error:
err: Could not retrieve catalog from remote server: Error 400 on SERVER:
Failed to parse template mcollective/server.cfg.erb:
Filepath: /usr/lib/ruby/site_ruby/1.8/puppet/parser/
Stuart,
If I'm understanding your needs correctly, this may be what you're looking
for:
http://www.devco.net/archives/2010/03/17/scheduling_puppet_with_mcollective.php
On Monday, September 2, 2013 11:01:46 AM UTC-5, Stuart Cracraft wrote:
>
> How can this be randomized within a range?
>
> I bel
Folks,
I tried downloading the Learning VM image for VMware, and while there does
seem to be a .vmdk file inside the zip archive, along with various other
parts I would expect to find, so far as I can tell this is not something
that I can successfully import into VMware Fusion 7.
Has this imag
Fusion 7.
If you have used this VM recently with Fusion 7, can you share with me your
system details so that I can compare those with my own?
Thanks!
--
Brad Knowles
LinkedIn Profile: <http://tinyurl.com/y8kpxu>
--
You received this message because you are subscribed to the Google
file out of the
extracted archive directory before you rename it, otherwise it will be a bit
painful to refer back to the PDF if/when you want. ;)
> It works for me on OS X 10.10 Yosemite.
Working through it now. Thanks again!
--
Brad Knowles
LinkedIn Profile: <http://tinyurl.com/y8kpxu&g
ince 1984, this is another good
reminder. :-)
All the reminders notwithstanding, those are still work arounds that you can
easily avoid if you just move the file before you rename the directory.
--
Brad Knowles
LinkedIn Profile: <http://tinyurl.com/y8kpxu>
--
You received this message
Hi, I've started the DFWPUG. Please go to
http://www.meetup.com/Dallas-Fort-Worth-Puppet-User-Group
<http://www.meetup.com/Dallas-Fort-Worth-Puppet-User-Group>for details,
I'll be organizing a first meeting soon.
Brad Christian
@vhipster
--
You received this message
we require as
well as the security that we require.
I see no viable alternative to this approach.
--
Brad Knowles
LinkedIn Profile: <http://tinyurl.com/y8kpxu>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from
d devote 6GB to the puppet master and
still have enough RAM left over to run 10x nodes with 1GB RAM each, and you
should be fine.
--
Brad Knowles
LinkedIn Profile: <http://tinyurl.com/y8kpxu>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users&q
tos7 host)
> if that matters.
That sounds like it should work fine. But YMMV. ;)
--
Brad Knowles
LinkedIn Profile: <http://tinyurl.com/y8kpxu>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group an
ight.
Suggestions? Thanks!
--
Brad Knowles
LinkedIn Profile: <http://tinyurl.com/y8kpxu>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet
ane.
--
Brad Knowles
LinkedIn Profile: <http://tinyurl.com/y8kpxu>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroup
Hi,
I've been stumped by the following error for quite a while now it is
generated when running the manifest further below:
err: Could not retrieve catalog from remote server: Error 400 on
SERVER: Puppet::Parser::AST::Resource failed with error ArgumentError:
Invalid resource type drupal6::theme_
when I do so.
On Aug 22, 9:58 am, jcbollinger wrote:
> On Aug 19, 1:33 pm, Brad Krane wrote:
>
> [...]
>
> > drupal6/manifests/init.pp
> >
>
> [...]
>
> > class drupal6 {
>
> [...]
>
> >
> Then let's take a step back. Your class is rather complicated, and
> all the details may be confusing (or even causing) the issue. For
> example, you may have a nesting problem that is difficult to see in
> all that code. I suggest putting each 'define' in its own file to
> help make things c
I have spoken too soon about the nil value causing the problem. When I
set the default value from nil to "something" the error came back. It
seems that just using a hash value in the name to be expanded is what
the real issue is.
--
You received this message because you are subscribed to the Goog
Here is a very simple manifest that recreates this error:
class foo {
define bar ( $val ) {
notice("bar($val)")
}
}
$some_hash = { 'name' => "some_name" }
foo::bar { "$some_hash['name']": }
Puppet::Parser::AST::Resource failed with error ArgumentError: Invalid
resource type foo::bar a
s/manifests/applications.pp:6 on node
> foobar.test.com
>
> Is there a fix for this, or am I doing something wrong?
>
> Thanks,
> Paul
>
>
>
>
>
>
>
> On Fri, Sep 2, 2011 at 11:21 AM, Brad Krane wrote:
> > Here is a very simple manifest that recreates this error:
&
On Wednesday, 26 December 2012 02:22:35 UTC, Andrey Ageyev wrote:
> And when I try to apply manifest - getting:
> puppet agent -t
> info: Caching catalog for wproxy71.tpnt.net
> err: Failed to apply catalog: Could not find dependency
> File[/etc/apt/sources.list.d] for
> Exec[add-apt-repository
27; would be in scope unless I explicitly
copy the dev data to 'new_feature.yaml', which feels wrong.
Am I approaching this all wrong? Any advice?
--
Thanks,
Brad
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to
There
will be some things that will always be different between dev and
prod. I suppose there are other ways around that though that make more
sense. I may be inventing a problem I don't really have.
--
Brad
--
You received this message because you are subscribed to the Googl
I was thinking originally. One
Puppet environment per branch, remove the Puppet environment from the
Hiera hierarchy, and have my ENC tag machines with which Hiera
"environment" to use.
Makes sense. Thanks!
--
Brad
--
You received this message because you are subscribed to the Google Grou
they go
> into?
I recently ran into Bug #18234 [1], wherein boolean values in hashes
don't work as expected.
There's a patch available for that. No idea when it's expected to be
merged, but I can confirm it's *not* in 3.0.2.
1. http://projects.puppetlabs.com/issues/18234
time ago.
>> Maybe time to see if it got updates.
>>
>> Thanks,
>>
>>
>> --
>> Cosimo
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Puppet Users" group.
>> To post to this g
console?
> >
> > --
> > 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-u
gt; >
> > Please paste the code from the pre-commit.
> >
> > --
> > Joe McDonagh
> > AIM: YoosingYoonickz
> > IRC: joe-mac on freenode
> > "When the going gets weird, the weird turn pro."
> >
> > --
> > You received this message becaus
ixon",
}
It all seems a little verbose. Any suggestions on how to improve this?
Maybe trying to puppet manage gconf entries is a bad idea?
Brad
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Puppe
nges in case of a problem?
3. Is there a better approach? Any other suggestions for things
(including tools other than Puppet) to look at?
Thanks in advance to anyone who can help!
--Brad
--
You received this message because you are subscribed to the Google Groups
"Puppet Users&qu
rt from being
referenced by other packages.
Is anyone else having this problem? Is there a workaround that isn't "use
focal" or "build the agent yourself?"
Thanks!
Brad Reaves
--
You received this message because you are subscribed to the Google Groups
"Puppet Us
36 matches
Mail list logo
