Hi Alex,
Agents write their last catalog to disk in
/var/lib/puppet/client_yaml/catalog/${hostname}.yaml. If you've got an
Agent that hasn't done a Puppet run since you deleted that module, this
file will contain the information you're after. It's not the most
prettily formatted thing though,
Does autosign work? I have a scratch workstation that may be rebuilt frequently
and will therefore acquire a new client certificate. I was hoping that adding
its certificate name to /etc/puppet/autosign.conf on the puppetmaster would
allow just this one client to have its new certificates autosi
Autosigning certificates work, what you're probably running into is that
autosigning does not clear off an old Agent's certificate, so you're
getting certificate mismatch errors. Puppet's RESTful API allows you to
manage certificates. It's been a long time since I tested this but I
have this in
Hello guys,
I would like to get some help with puppet about using an array in a
template.
I've a custom facts that return me this:
tsm_vmp / /home /tmp /var/tmp /usr /var
I have a class that use this facts to split it on every space and to a
an entry in a template for each value, here i
Sounds good.
One problem that I have with the forge is that the extent to which the
modules have been tested is not clear to me. Can I take it that the core
modules that ship with puppet will have been through a similar testing
cycle as puppet itself?
On Monday, April 23, 2012 11:03:39 PM UT
Very close:
<% virtualmountpoints.each do |fs| -%>
[<%= fs %>]
virtualmountpoint<%= fs %>
<% end -%>
I don't understand the Ruby in that, I copied it from someone else ;-)
On 24/04/12 09:18, digrouz wrote:
Hello guys,
I would like to get some help with puppet about using an array in a
templat
Hello Mike,
Sorry for the late feedback.
On this page
http://docs.puppetlabs.com/guides/installation.html
it is written
"
OS Packages
If installing from a distribution maintained package, such as those
listed on the Downloading Puppet Wiki Page all OS prerequisites should
be handled by your pack
Many thanks - this is now working better. What was tripping me up was that if
the puppet agent has tried to run, and there is a certificate request on the
master, then the next run of the agent either doesn't try to get the
coresponding certificate signed or else the auto-signing is silently blo
I just found my problem,
It is in the split in fact I don't have space between the value but carried
returns, so if I split to "\n", it works.
Regards
On Tue, Apr 24, 2012 at 10:55 AM, Luke Bigum wrote:
> Very close:
>
>
> <% virtualmountpoints.each do |fs| -%>
> [<%= fs %>]
>
> virtualmountpo
Not sure about the first question, are you saying your Agent had a
non-autosigned certificate waiting on the Puppet Master, then you
configured auto signing on the Master and expected it to work? I think
the autosigning is done only when an Agent first connects and it won't
sign any pending or
I just found my problem,
It is in the split in fact I don't have space between the value but
carried returns, so if I split to "\n", it works.
Regards
On 24 avr, 10:55, Luke Bigum wrote:
> Very close:
>
> <% virtualmountpoints.each do |fs| -%>
> [<%= fs %>]
> virtualmountpoint<%= fs %>
> <% end
Hi,
[...]
> It is in the split in fact I don't have space between the value but
> carried returns, so if I split to "\n", it works.
>
This is slightly worrisome. I encourage you to go with separating values
with a comma, not only because it follows style of how other facts return
values, bu
Right now all our different environments (test/stage/prod) are being served
by the same puppet master. We have tried some things that tend to break
puppet which obviously is not good on a production machine. I have been
tasked to match our puppet environment with the enterprise environment. I
propo
Dear all,
Since last night, Puppet is started creating a directory, named *false* in
the present working directory, if I run *puppetd -t* manually on the puppet
agent. The directory contents are like this:
8/3/e/5/8/6/5/9/83e586594432759eb7aed007e888a172/contents
> 8/3/e/5/8/6/5/9/83e5865944327
alright, i was doint it wrong. just enable "pluginsync=true" on the
client.
On Apr 19, 5:05 pm, Ernest Beinrohr wrote:
> Hi, I have trouble installing vcsrepo. I cloned vcsrepo onto my
> Centos6 and when I run "rake" i get this:
>
> (in /etc/puppet/modules/vcsrepo)
> ** Invoke default (first_time
Looks like you have an error in your filebucket definition. Did you, perhaps,
put quotes around "false" when you defined the path?
-- Peter
On Apr 24, 2012, at 8:13 AM, Sans wrote:
> Dear all,
>
> Since last night, Puppet is started creating a directory, named false in the
> present working
Not sure what exactly do you mean; I haven't defined and path with "false"
in it.
It appears that the "false" directory is being created for this file
definition:
'facts.yaml':
> name=> '/tmp/facts.yaml',
> content => inline_template("<%= scope.to_hash.reject { |k,v| !(
>
Hiya,
On Tue, Apr 24, 2012 at 14:07, Sharuzzaman Ahmat Raslan
wrote:
> Ok, I think that narrows it down to cron issue possibility, as you mentioned
> the other server with the same puppet configurations works well.
>
> Reports only generated if puppet is running, even if there are errors. When
>
On Apr 23, 9:43 pm, Walter Heck wrote:
> Hi all,
>
> in an unfortunate incident, I managed to lock myself out of a client's
> server. Basically an openssh module that by default disabled remote
> root logins did that on a server that was only accessed by remote root
> login (no other use raccoun
I don't know what exactly you mean: I don't have any path defined with
"false" in it.
Just figured out that whenever the content of a file is being modified, the
"*false*" directory is being created with the old file (as "content") in
it. So, looks like it's actually not modifying the file (in q
Having read the scary warnings about autosign, I need to think it through some
more. However the helpful comments about allowing a client to revoke and delete
its OWN certificate will probably useful on their own. Luke said that his
addition to auth.conf was not working. It appears that the inte
Hi,
I worked with puppet (< 0.25) back in 2008/2009. We were able to
deploy 200 servers from scratch and manage them. It worked fine.
I'm now with a new customer and I'm pushing Puppet (and I'm also back
to puppet on a side project).
We're considering Puppet 2.6 to manage RHEL/CentOS 5 or 6 host
Thanks Peter! Got it now!
You were absolutely right - I had *path => 'false' *for filebucket (in
the site.pp).
But I thought, Puppet recommends to quote around everything (apart from
variables). That's not true, I see. Cheers!!
On Tuesday, April 24, 2012 2:12:02 PM UTC+1, Sans wrote:
>
> I
This was a long email! The answer to your problems is definitely something
like
Hiera. You make a common.yaml that has all your "defaults" and then you can
overwrite these based on any fact you like, when building the hierarchy.
You can
make a hierarchy like:
fqdn
environment
common.yaml
Then
Glad you got it sorted. You've discovered the importance of quoting and *not*
quoting. The best practice is to single quote any string that does not contain
a variable. If you're using a variable, use double quotes so it gets
interpreted properly. Quotes should *not* be used around any of puppet
Hi',
I'm looking for a way to increment variable in template (erb file).
I tried this, but it didn't work
Compteur <%= compteur %>
> <% compteur = compteur + 1 %>
> Compteur <%= compteur %>
>
I've got this error :
> Error 400 on SERVER: Failed to parse template test/test.erb: undefined
> met
Hi,
On Tuesday, 24 April 2012 14:38:28 UTC+1, AnOnJoe wrote:
>
> Hi',
>
> I'm looking for a way to increment variable in template (erb file).
>
> I tried this, but it didn't work
>
> Compteur <%= compteur %>
>> <% compteur = compteur + 1 %>
>> Compteur <%= compteur %>
>>
>
> I've got this error :
Hi,
I've written a set of Puppet modules to manage servers, but am
slightly concerned about the structure I've used as it seems to differ
significantly from anything else I've seen in Puppet Forge/elsewhere
on the internet.
I've made extensive use of definitions so that defaults for modules
can b
I've got it :
Compteur <%= compteur %>
> *<% compteur = compteur.to_i -%>*
> <% compteur += 1 -%>
> Compteur <%= compteur %>
>
Le mardi 24 avril 2012 15:38:28 UTC+2, AnOnJoe a écrit :
>
> Hi',
>
> I'm looking for a way to increment variable in template (erb file).
>
> I tried this, but it didn
I also need to figure out how to code this rule:
-A POSTROUTING -o virbr0 -p udp -m udp --dport 68 -j CHECKSUM --checksum-fill
--checksum-fill is not supported, in puppet-iptables, right? or can
arbitrary iptables parameters be passed along somehow?
I am using the purge option How would you
Have you had any luck with puppeting mysql51-server or mysql55-server ?
Everything I've read suggests the $operatingsystem won't work for name on
packages and the application tries to keep installing as posted here:
https://groups.google.com/forum/?fromgroups#!topic/puppet-users/Yc1Et5dSAHM
Co
Hi,
\o/
KW
On Tuesday, 24 April 2012 15:18:56 UTC+1, AnOnJoe wrote:
>
> I've got it :
>
> Compteur <%= compteur %>
>> *<% compteur = compteur.to_i -%>*
>> <% compteur += 1 -%>
>> Compteur <%= compteur %>
>>
>
>
> Le mardi 24 avril 2012 15:38:28 UTC+2, AnOnJoe a écrit :
>>
>> Hi',
>>
>> I'm loo
On 24 avr, 15:34, Ashley Penney wrote:
> This was a long email!
Yeah, I know it might get a few "TL;DR" but I wanted to provided all
relevant information. :)
> The answer to your problems is definitely something
> like
> Hiera. You make a common.yaml that has all your "defaults" and then you
On Apr 24, 9:13 am, Andy Taylor wrote:
> Hi,
>
> I've written a set of Puppet modules to manage servers, but am
> slightly concerned about the structure I've used as it seems to differ
> significantly from anything else I've seen in Puppet Forge/elsewhere
> on the internet.
>
> I've made extensi
On Apr 24, 8:19 am, Calimero wrote:
> Hi,
>
> I worked with puppet (< 0.25) back in 2008/2009. We were able to
> deploy 200 servers from scratch and manage them. It worked fine.
>
> I'm now with a new customer and I'm pushing Puppet (and I'm also back
> to puppet on a side project).
>
> We're co
Autosign works, but not as you're expecting: it will sign new
certificates, but not overwrite existing ones. At least, that's my
experience here :)
--
Bill Weiss
Backstop Solutions Group
On 2012/4/24 3:34 AM, "C R Ritson" wrote:
>Does autosign work? I have a scratch workstation that may be r
On 04/24/2012 09:19 AM, Calimero wrote:
Hi,
I worked with puppet (< 0.25) back in 2008/2009. We were able to
deploy 200 servers from scratch and manage them. It worked fine.
I'm now with a new customer and I'm pushing Puppet (and I'm also back
to puppet on a side project).
We're considering P
Maybe you could use puppet to configure send to a remote syslog. If that
works, you could then add your problem module back, and get visibility to
exactly what the client is doing, and any errors it is seeing.
Or make some small modification to the existing log file on the remote
server, with fil
Thank you very much for your detailed reply John. I hadn't looked at
Hiera before, it looks very interesting. On the point of it's not good
to include node/site data in manifests, it's kind of essential in my
eyes to the setup I am trying to implement.
At my company, one server may serve a site wh
This should get reported as a bug though.
We should probably only accept absolute paths for the 'path' parameter, and
"false" should get interpreted as the boolean.
On Tue, Apr 24, 2012 at 6:38 AM, Peter Bukowinski wrote:
> Glad you got it sorted. You've discovered the importance of quoting and
I suspect something is wrong with the underlying ssl libraries on the
client with the problem. Does the output of 'rpm -qa | grep ssl' on the
non-working client look the same as the client which works? How about
ldd -r `rpm -ql ruby-libs | grep openssl.so`
?
On Sunday, April 22, 2012 2:19:27
It checks every layer of the hierarchy, so it would look for:
fqdn/server1.yaml
environment/staging.yaml
common.yaml
But the important thing to know is it's looking for an actual variable. If
you had defined
selinux: disabled in common.yaml and nowhere else then it would always
reach that
file a
err: Could not retrieve catalog from remote server: SSL_connect returned=1
errno=0
I've seen that when the clocks on the two hosts were out of sync. Even when I
brought the clocks back into sync I found that I had to regenerate the certs to
get it working.
master:
puppet cert --clean
(restar
Stefan;
Thanks for the suggestion. However, we are running puppet via
Passenger. So, I assume I need to update the config.ru file. Do you
have any suggestions about that? Greatly appreciate your help and
advice!
On Thu, Apr 19, 2012 at 6:17 PM, Stefan Schulte
wrote:
> On Thu, Apr 19, 2012 a
On Tue, Apr 24, 2012 at 11:18 AM, JA wrote:
> Stefan;
>
> Thanks for the suggestion. However, we are running puppet via
> Passenger. So, I assume I need to update the config.ru file. Do you
> have any suggestions about that? Greatly appreciate your help and
> advice!
>
Look for the ARGV line
Thanks!
I am (obviously) very new to ruby/rack!!
Thanks!
On Tue, Apr 24, 2012 at 2:30 PM, Nigel Kersten wrote:
>
>
> On Tue, Apr 24, 2012 at 11:18 AM, JA wrote:
>>
>> Stefan;
>>
>> Thanks for the suggestion. However, we are running puppet via
>> Passenger. So, I assume I need to update the c
Puppet 2.7.14rc3 is a maintenance release candidate for Puppet in the
2.7.x series.
Downloads are available:
* Source http://downloads.puppetlabs.com/puppet/puppet-2.7.14rc3.tar.gz
## Bug Fixes ##
(#13682) Rename Puppet::Module::Tool to Puppet::ModuleTool
Without this patch, Puppet will mo
On 24 avr, 19:10, Les Ault wrote:
>
> I use facter variables to set dynamic parameters based on the host. For
> example I created a module to modify sysctl entries:
>
> node dbserver.example.com {
> include sysctl
>
> # Modify sysctl values
> $shmall = inline_template("<%= (memorysizei
On 24 avr, 19:54, Ashley Penney wrote:
> It checks every layer of the hierarchy, so it would look for:
>
> fqdn/server1.yaml
> environment/staging.yaml
> common.yaml
>
> But the important thing to know is it's looking for an actual variable. If
> you had defined
> selinux: disabled in common.ya
On Apr 23, 5:49 pm, Tim Sharpe wrote:
> So, rspec-puppet can't and won't ever work this way. What it's testing is
> the resulting catalogue of Puppet resources that your host executes (the
> behaviour of Puppet). Instead of testing that a variable is defined, you
> should be testing the reso
Hi,
I need to run a the generate() function (server side) in order to populate
a data file for one of my modules. Is there a way to ensure that the
generate function is
run before a config file is created (the contents of the file doesn't come
directly from generate()).
Right now I'm getting
Hi,
On Tuesday, April 24, 2012 6:38:27 PM UTC+1, Nigel Kersten wrote:
>
> This should get reported as a bug though.
>
> We should probably only accept absolute paths for the 'path' parameter,
> and "false" should get interpreted as the boolean.
>
+1
KW
--
You received this message because yo
Hi List,
In a module that I am developing I would like to do different things
depending on if storeconfigs is true or false.
Is there any way to:
if $storeconfigs == true {
# Use stored config values
} else {
# Use non stored config values
}
Thanks,
Peter.
--
You rece
Hey Peter,
You should be able to do $settings::storeconfigs to get that value.
On Tue, Apr 24, 2012 at 2:14 PM, Peter Foley wrote:
> Hi List,
>
> In a module that I am developing I would like to do different things
> depending on if storeconfigs is true or false.
>
> Is there any way to:
>
>
54 matches
Mail list logo
