On 05/26/2014 10:03 PM, Matthew Herzog wrote:
> Boos to puppetlabs.
Disclaimer: I've no affiliation with Puppet Labs.
This rubs me wrong regardless.
Please note that the documentation *is* also open source, and you are
more than welcome to improve it as you see fit. Barring your ability to
contr
I have my puppetmaster setup with httpd and mod_passenger. My agents can
successfully pull manifests, but they are unable to pull files. As far as I
can tell, I do not have any rewrite rules setup in my puppetmaster.conf
(see below). In my httpd access log, I see that the agent tries to request
It sounds like you need to read through these:
http://garylarizza.com/blog/2014/02/17/puppet-workflow-part-1/
http://garylarizza.com/blog/2014/02/17/puppet-workflow-part-2/
I don't see why you'd want to remove parameters from classes. They are
pretty critical to having a flexible infrastr
I've just encountered and fixed the exact same error message.
The repo (and the .git directory in it) contained files not owned by the
user specfied in the vcsrepo command. Ensure the ownership of the directory
before vcsrepo-ing it:
file { "/home/myuser/myrepo":
ensure => directory,
Hi,
I'm statrting using puppet with role/profile pattern and i'm facing a
problem.
I use puppet 3.4.3 with a master running on red hat 2.6 and a client on a
local VM centOS 6.5.
When i try to test my code with the command above i got an error : Error
400 on SERVER could not find class vstar::apa
Class vstar::apache should be in
/etc/puppet/modules/vstar/manifests/apache.pp
To allow autoloader find it.
Regards,
El 30/05/2014 15:48, "Christian Charpentier" escribió:
> Hi,
> I'm statrting using puppet with role/profile pattern and i'm facing a
> problem.
> I use puppet 3.4.3 with a mast
I am moving our environment from puppet 2.7.1 with puppet dashboard to
puppet 3.5.1 with puppetdb 2.0. During testing on a separate host with the
identical setup as our puppet CA, everything seems to be functioning
properly: puppet agents are able to be added on the master and receive
everythin
> I am moving our environment from puppet 2.7.1 with puppet dashboard to
> puppet 3.5.1 with puppetdb 2.0. During testing on a separate host with the
> identical setup as our puppet CA, everything seems to be functioning
> properly: puppet agents are able to be added on the master and receive
> eve
How did you not define any environments. I've removed the
/etc/puppet/environments folder and have no envs. set anywhere else. Still
happens with WebRick.
On Tuesday, May 27, 2014 1:31:34 PM UTC-2:30, Atom Powers wrote:
>
> I struggled with this for a while on Friday.
> The error doesn't occur u
Don't define an environment in your config file, master or client, and
don't define an environment through your ENC or as a fact. (I think that is
all the ways.)
On May 30, 2014 11:06 AM, wrote:
> How did you not define any environments. I've removed the
> /etc/puppet/environments folder and have
I've introduced the following code into one of my working manifests, and am
now returning an error that I don't understand at all. I've searched the
web for a similar instance of this error but found none that seem relevant.
The code is...
## Roll in the entire theme folder.
file { "${d
Hi,
On 05/30/2014 06:16 PM, Mark McFate wrote:
> The error returned is: Failed to generate additional resources using
> 'eval_generate': getaddrinfo: Name or service not known.
you're in luck - 'modules' does not resolve to an actual machine's
address in your environment.
You lack one / in your
Hi,
Just wrote my first puppet module for Windows provisioning. All is working
well except I am having a problem running a windows exe file in that Puppet
appears to wait for the exe to complete. At least this is the case when I
run Puppet agent --test from the Windows Server command line.
Wh
I actually already made this change and pushed it. Nick merged it
yesterday.
On May 30, 2014 1:37 AM, "Felix Frank"
wrote:
> On 05/26/2014 10:03 PM, Matthew Herzog wrote:
> > Boos to puppetlabs.
>
> Disclaimer: I've no affiliation with Puppet Labs.
>
> This rubs me wrong regardless.
>
> Please no
Thank you Felix! You saved the day. As usual, I did a cut/paste to build
this portion of my manifest. I have no idea how that / got removed, and
since this was my first use of recurse I just assumed I was doing it wrong.
Thanks again. Take care.
-Mark
On Friday, May 30, 2014 11:18:54 AM UT
John,
Thanks for the assist. I guess I was working from a less than stellar
example.
On Thursday, May 29, 2014 9:53:14 AM UTC-4, jcbollinger wrote:
>
>
>
> On Wednesday, May 28, 2014 9:16:47 AM UTC-5, smalderma wrote:
>>
>> Hi,
>>
>> I'm working on custom fact that uses Facter::Util::Resolutio
Hi,
Is there any way to audit the contents of a file using no-op mode in puppet.
Help me
--
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+unsub
> It would be very hard to create a large resource type, but not
> impossible. Whats more likely is that the title of one of your
> resources is excessively large. This is possible most likely with an
> exec {} or something similar that uses a very large command as the
> title of the exec, i
Hi,
How to set loglevel=debug in puppet to get detailed information of what
commands puppet is executing when it runs puppet agent.
In cd /etc/puppetlabs/mcollective/server.cfg file I edited loglevel=debug.
But aftersome time it is changing to loglevel=info
How do I set loglevel=debug in pu
AFAIK, Windows does not have a true "fork" capability. Here are some ideas
that might help:
- Use srvany (or something else) to define a custom service. It sounds
like this is probably what you really should be doing anyway. Puppet is
not meant to control programs over a long term (i.e. service
On Thu, May 29, 2014 at 02:26:21PM -0400, Brian Mathis wrote:
>It sounds like you need to read through these:
> [1]http://garylarizza.com/blog/2014/02/17/puppet-workflow-part-1/
> [2]http://garylarizza.com/blog/2014/02/17/puppet-workflow-part-2/
I've read those and recommended t
On 5/29/2014 10:58 AM, Christopher Wood wrote:
(I'm not sure how to phrase my question precisely, so this may not
all be totally clear.)
Has anybody else successfully moved away from using params.pp and
default values, and if so, what did you do and how did it go? If not,
what made you go back?
On 05/27/2014 05:39 PM, Andy Parker wrote:
On Tuesday, May 27, 2014 5:53:29 AM UTC-7, Konrad Scherer wrote:
On 14-05-22 03:21 PM, Daniele Sluijters wrote:
> The environment caching is already there, use the environment_timeout
> setting. Mine is set to unlimited and I reload at dep
Hi Henrik,
I don't really use WEBrick but apache/passenger for the normal operation. I
think WEBrick is used to run puppet master in background in debug mode. Is
there a way to use apache/passenger for that?
Anyway, I'm running puppet v2.7.3 and getting the same error for one of
those nodes ev
Hi all,
this used to work in Puppet 2.7, but doesn't in 3.4.3:
<% case @environment
when "production"
foo
else
bar
end -%>
this continues to work:
<%= @environment %> (prints the $environment var as expected).
It almost looks like Ruby isn't getting evaluated at all. Even a sim
Templates are evaluated on the puppetmaster, so <% puts "hello" %> happens
entirely on the puppetmaster and substitutes no text.
Any reason why the first one doesn't use (<%=)? I wouldn't expect it to work as
you have it. "This tag will execute the code it contains, but will not be
replaced by
I should clarify: this is supposed to actually set a value to another
variable that's used elsewhere in the template, e.g.:
<% case @environment
when "production"
bucket = "foo.path"
else
bucket = "bar.path"
end -%>
rewrite ^/images$ http://s3.amazonaws.com/<%= @bucket %>;
etc.
bucket and @bucket are two different variables.
The main change in ERB templates between 2.7 and 3.x was deprecating the
use of non-class variables to pass information from the calling scope into
the template. Perhaps you got a little over-zealous prepending '@' to
variable names while fixing depr
On 2014-30-05 20:54, Sans wrote:
Hi Henrik,
I don't really use WEBrick but apache/passenger for the normal
operation. I think WEBrick is used to run puppet master in background in
debug mode. Is there a way to use apache/passenger for that?
Anyway, I'm running puppet v2.7.3 and getting the same
On Friday, May 30, 2014 11:13:51 PM UTC+1, Henrik Lindberg wrote:
>
>
> Ok, then webrick is not the cause of your problem.
>
> Run with --trace set to get a ruby stack trace. That will help to find
> what is causing the problem.
>
> - henrik
>
Yes, that was the output from --trace and that's
It's weird, but it looks like the hostname isn't being defined, or isn't
being sent properly. See
"info: Expiring the node cache of"
With just a blank afterwards. Does running facter on the affected node show
anything unusual?
On Friday, May 30, 2014 3:18:58 PM UTC-7, Sans wrote:
>
>
>
> On
31 matches
Mail list logo
