By default puppet will report the changes to any files it updates. If the
file includes any secure data like passwords or private encryption keys,
that also shows up in the logs. Is there any way to block this level of
logging for individual files? Disabling it for all files is also
acceptab
Declaring the Service as a Virtual Resource might help but I'm not sure how
you inject B's dependencies.
http://docs.puppetlabs.com/guides/virtual_resources.html It might just
require a Notify inside B.
On Monday, February 17, 2014 3:41:14 AM UTC-8, zerozer...@gmail.com wrote:
>
> Hi,
> I have
graceful-stop seems to be a modest improvement but its not a panacea.
AFAIK it only ensures that open connections are not dropped. A puppet run
seems to involve multiple connections. At best this only completes
individual transactions before shutdown. Also, when I look at this
problem in a
https://ask.puppetlabs.com/question/4694/updating-puppet-agents/
I'm looking at this thread from ask.puppetlabs and so far the the only
answer seems to be - don't use puppet to manage puppet. I'm asking the
broader community because I'm still naively hopeful that puppet can manage
its own inst
If I need to do any maintenance on my puppetmaster I would like to ensure
that I don't break any partially completed puppet runs. Is there any way to
quiesce the puppetmaster before shutting down the service?
I run my puppetmaster on top of apache passenger. If I execute "service
httpd stop" it
And now I see why I hadn't found --help helpful. In 2.0.0 eyaml --help
does not give a dump of options. You have to run eyaml --help to see
a list of options for that command. Don't know if that's good or bad. IMO
it would be nice to see more information in top level help.
--
You received
Our plan for eyaml is that operations owns and protects the private key.
So developers only have access to the public key and after creating new
encrypted values cannot decrypt them. Unless I'm missing something,
developers won't be able to use 'eyaml edit' because it requires the
private key.
Thanks James. --help should have been blindingly obvious but it slipped my
flu infested mind. Cheers!
--
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
The default value for the private key path in the eyaml CLI is
./keys/private_key.pkcs7.pem. Is there an CLI option to override the
default?
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving ema
Correction: I was running puppet 3.2.3. I upgraded my server to 3.4.2 and
the problem is still there.
--
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-us
Correction: I'm running puppet 3.2.3. I will upgrade to 3.4.2 to see if
the problem goes away.
--
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+uns
Correction: I'm running puppet 3.2.3. I will upgrade to 3.4.2 to see if
the problem goes away.
On Thursday, February 6, 2014 10:22:07 AM UTC-8, Larry Fast wrote:
>
> I just started evaluating hiera-eyaml and hit a glitch. It seems that any
> attempt to read a hash in an ey
I just started evaluating hiera-eyaml and hit a glitch. It seems that any
attempt to read a hash in an eyaml file using hiera_hash(), produces an
error:
"Error 400 on SERVER: Resolution type is hash but parsed_answer is a Hash"
The error occurs even if the hash does not contain any encrypted val
Thanks Denmat,
It was probably crosstalk between gems and RPMs. Turns out that the
rubygems RPM was missing some files. Likely cause was accidentally
installing and uninstalling rubygems via non-rpm. Reinstalling the RPM
fixed the problem. For the benefit of others, here's how we found the
p
I have a puppetmaster running within passenger+rack. It has been running
properly for almost a year and decided to stop working on the weekend. Now
I'm getting the Purple "Ruby (Rack) application could not be started"
screen with
Error: no such file to load -- rack
Application: /data1/rack/pupp
I'm getting unexpected behavior from my provider methods. Here's the
example.
parameter p
resource[ :p ] = 'hello'
def p()
return 'hello'
end
def p()=
return true # Does the return value even matter?
end
Problem 1: p()= is getting called. Given that the return from p() matches
the re
Thanks, yes it was that simple. It would have worked first time if I just
had put the file in the provider folder instead of the type folder. Doh!
Cheers,
Larry
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group an
I'm turning an existing ruby script into a type-provider pair. My first
desire was to simply 'require' the original ruby file in the new provider
file. Unfortunately my ruby file doesn't get downloaded from master to
agent. Is there something reasonably simple I can do to ensure that this
fil
Is there any way to pass puppet run details to an ENC. Most importantly I
want to know the Environment value the puppet Agent is asking for. More
generally is it possible to query the puppet configuration values?
One thought I had is to turn the puppet config into FACTS. Then the ENC can
get t
> > I'm curious to your opinion on point # 3, are you talking about OS
> packages or your organizations app version? If the latter, I was thinking
> of using hiera, maybe with a backend other than yaml such as redis, to
> store the version of the app, that way like you said it could be used in
What about the larger processes involved in incremental updates? Eg.
sequencing your updates so that the service keeps running. I'm
considering using Jenkins to orchestrate sequencial activity.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" grou
with my co-workers.
Caveate Emptor: We're still hemming and hawwing about all this.
Cheers, Larry Fast
--
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 em
...finger slipped...
Thanks David,
I started using geppetto as well. Yes, my error count has dropped
significantly. The other thing I discovered is that hiera("name") produces
a very clear error if the name doesn't exist. So I moving toward that as
well.
Cheers larry
--
You received this mess
On Friday, May 3, 2013 2:12:41 AM UTC-7, David Schmitt wrote:
>
> On 02.05.2013 22:43, Larry Fast wrote:
> > I'm still a puppet newbie and these days I'm struggling with undefined
> > variables. At least once a week I hit an error message like this:
> >
module_name}
- %{environment}/%{project}/%{role_name}-role/common
- %{environment}/%{project}/%{module_name}
- %{environment}/%{location}/%{module_name}
- %{environment}/%{module_name}
- %{environment}/common
Cheers
Larry Fast
--
You received this message because you are subscrib
I'm still a puppet newbie and these days I'm struggling with undefined
variables. At least once a week I hit an error message like this:
Error: Failed to apply catalog: '' is not qualified and no path was
specified. Please qualify the command or specify a path.
IMO, the core issue is th
I assume I have a syntax problem of some kind. I created a class file and
puppet complains on line 4. If I remove that block of code it complains
about the next block. What silly little mistake have I made? The error
reported for the code example below is:
Could not match ‘george’, at
Thank you all. Yes, tidy should be exactly what I need.
--
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...@googlegroups.com.
To post to th
I keep running into the following upgrade pattern.
Previous Puppet run declared:
file { "my_jar.1.2.3.jar": ... }
New puppet run declares:
file {"my_jar.2.4.6.jar": ... }
But the new puppet run doesn't delete the older versions of this jar file.
Is there a standard puppet pattern f
RESOLVED
The multi-puppetmaster-single-CA documentation is complete but a bit
scattered. Here the short list of what I needed to do for puppetmasters
running apache-passenger.
pm1 = CA
pm2 = non-CA puppetmaster
- needs to reference pm1 as the ca_server
- disable local ca in [master]
- get
I'm getting errors when following this webpage to setup a second
puppetmaster (pm2) while using pm1 as the CA:
http://docs.puppetlabs.com/guides/scaling_multiple_masters.html#centralize-the-certificate-authority
and I'm using option 1: Direct agent nodes to the CA Master
As far as I can tell, i
Solution:
Find the .rb files that contained Facter::Util::Resolution.exec and ...
Facter.add("my_function") do
confine :kernel => [ 'Linux' , 'SunOS' , 'FreeBSD' , 'Darwin' ]
...
Thanks everyone!
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" g
etter. The error did not indicate
a source file. And Pluginsync does not indicate the source module for any
of the files it loads. Not even in debug mode.
Cheers,
Larry Fast
>
>
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" gr
Oh yes, I forgot the first line of my snippet. But I still don't have a
working syntax for reading the facts from that object.
facts = File.read(filename)
myFact = YAML.load( facts )
print myFacts.inspect
>
> # @ivars={"values"=>{"timezone"=>"UTC", "puppet_vardir"=>"/var/lib/puppet",
> "m
Starting to get some clarity but still need help. Using YAML to load Facts
produces the YAML object below. But I'm still not clear on how to access
the contents.
myFacts = YAML.load( facts.yaml )
print myFacts.inspect
### output:
#{"timezone"=>"UTC", "puppet_vardir"=>"/var/lib/puppet",
"maca
Hope I'm not being too thick about this but I'm having trouble creating a
Hash from my server's Facts.
I've tried the following:
facts = File.read( "#{puppetdir}/yaml/facts/#{certname}.yaml" )
factH = YAML.load( facts ) # fails
factH = YAML.load( facts ).to_hash # fails
I
>
>
> https://puppetlabs.com/blog/module-of-the-week-puppetlabs-stdlib-puppet-labs-standard-library-part-2/
>
>
> https://puppetlabs.com/blog/module-of-the-week-puppetlabsstdlib-puppetlabs-standard-library-part-3/
>
> I find it very useful. Hope you do as well.
>
> On Apr
> From that page: "External facts are only available in Facter 1.7 and
later."
> I expect you need to either upgrade or install the stdlib module.
Thanks for that. I knew I missed something. ... but tell me more about
the stdlib option. I'm a bit leery of depending on the first RC of facter
1
I'm trying to load custom facts via /etc/facter/facts.d/* according to
instructions on
http://docs.puppetlabs.com/guides/custom_facts.html#structured-data-facts
I must have missed a setting somewhere because I get nothing. The first
clue may be that /etc/facter didn't exist. I had to create i
Using puppet 3.0.1, can exec ENC see the incoming environment value?
Perhaps indirectly from a log or report somewhere?
--
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 e
Windows NuBQ:
I'm running windows with a clean install of puppet and an empty node
definition. puppet agent -t pauses with no prompt. When I hit enter, I
get this warning:
Using Facter::Util::Resolution.exec with a shell built-in is deprecated.
Most built-ins can be replaced with native ruby
I'm guessing that the problem is in
example42/mcollective/manifests/init.pp...
class mcollective (
$install_dependencies = params_lookup( 'install_dependencies' ),
$stomp_host = params_lookup( 'stomp_host' ),
$stomp_port = params_lookup( 'stomp_port' ),
$stomp_user
When I define the mcollective_version variable using hiera I get the
following error. There is no indication where the problem has occurred.
Error: Failed to apply catalog: You cannot specify more than one of
content, source, target
If I set this variable in code it pretents to work but I think
Hi Andy,
I guess my most important request for Hiera 2 is diagnostic information.
It's probably a broader request for better diagnostics in puppet as a
whole. Here's what I dream of ...
1. The ability to run Puppet on the puppetmaster using the cached Facts
from a server.
2. A postmortem (sorr
My Hiera tree is turning into a chaotic mess. I'm guessing that my tree
structure is one problem source. So I'm wondering how other real users have
setup hiera. Here are the core problems that are giving me headaches.
# I need to version control my modules separately but hiera data is
monolithi
I have an odd problem. The first time I install my new package, puppet
comes back with "Execution of '/sbin/service chirp_fe start' returned 1:"
When I run this command manually and on all subsequent puppet runs it
succeeds.
So I'm looking for a way to capture the console output from the in
46 matches
Mail list logo
