Hi all,
How can I retrieve a file's most recent checksum as reported by puppet?
I'm running Puppet 3.1, PuppetDB 1.4, and Foreman 1.2, and have looked
through the various APIs as well as /var/lib/puppet/ on each node, but
can't find a specific field for the checksum. I think it used to be in
Scratch my note about storeconfigs not being supported in Foreman 1.2.
More clarification about this stuff in
https://groups.google.com/forum/#!topic/foreman-users/UxON4FtROUk
On Saturday, September 7, 2013 3:33:05 PM UTC-4, banjer wrote:
>
> If you are upgrading to Foreman 1.2, note th
If you are upgrading to Foreman 1.2, note that you will need to set up
puppetDB as the typical puppet storeconfigs is no longer used/supported as
of Foreman 1.2.
So don't delete or alter your type column in the hosts table, or you'll get
this issue I was having:
https://groups.google.com/f
I had to install the puppet stdlib module with:
*puppet module install puppetlabs/stdlib*
and that fixed the issue. It wasn't available in my /etc/puppet/modules.
I'm not sure if its *supposed* to be installed by default. I'm running
puppet 3.x and had upgraded from 2.7.
On Monday, January
Thanks, I was about to roll out a puppet module for tuned-adm and found
this. Easy to use and working great in my environment.
Cheers!
On Friday, January 4, 2013 8:25:16 AM UTC-5, Romain PELISSE wrote:
>
> Hi all,
>
> tuned-adm module: https://github.com/rpelisse/puppet-tuned
>
> I'm using
> t
Is it possible to have puppet doc show all of the manifest code in the
generated docs? I'm generating some html docs and would love to be able to
look at the actual code for each class or define statement. With syntax
highlighting would be even sweeter.
I'm using the following to create my do
The puppet error was:
err: Failed to apply catalog: Parameter source failed: Could not
understand source # This file managed by Puppet
Sorry for not seeing that error before...I kept looking at the "Bad URI"
error message which I posted in my original email. So anyway, it turns out
I was u
RB.new('*.notice;news.none;cron.none @<%= @host
> %>:514').result(binding)
> "*.notice;news.none;cron.none @localhost:514"
> => nil
> >>
>
> matti@acrux ~ $ cat | puppet apply --noop
> notice inline_template('*.notice;news.none;cron.none @<%= @h
Hi,
I have a template named rsyslog.conf.erb, and the puppet agents seem to be
choking on this:
**.notice;news.none;cron.none @loghost:514*
The agents report an error of ": bad URI(is not URI?): " followed by a
bunch of jargon. I'm pretty sure its the literal '@' symbol that its
trying to ev
It usually involves doing this one the server:
puppet cert clean myhost
and on the client:
rm -rf /var/lib/puppet/ssl
Then try it again on your client: `puppet agent --test` Then back to your
master: `puppet cert sign myhost`.
On Friday, August 10, 2012 8:30:50 AM UTC-4, Axel Bock wro
> If there is a new "foohost" client then you may not need to do anything.
> If not, then yes, you should clear its configuration out of your
> storeconfigs DB.
>
>
Its a new hostname as well as a new key. I wasn't clear on that earlier.
Also, I had run `puppet node clean foohost` before
I am attempting to remove an old ssh host key from
/etc/ssh/ssh_known_hosts. In my manifest, I have the following:
# add keys
@@sshkey { $hostname:
ensure => present,
type => "rsa",
key => $sshrsakey,
}
# remove key
@@sshkey { "foohost":
ensure => absent,
type => "rsa",
}
S
om wrote:
>
>
>
> On Thursday, August 2, 2012 8:54:58 AM UTC-5, banjer wrote:
>>
>> I just switched from using Puppet Dashboard with PuppetDB 0.9 to using
>> Foreman 1.0.0. This is on CentOS 6.3. I've been unable to get Foreman to
>> work Puppet
I just switched from using Puppet Dashboard with PuppetDB 0.9 to using
Foreman 1.0.0. This is on CentOS 6.3. I've been unable to get Foreman to
work PuppetDB, so I had to revert to using the "old" way of storeconfigs
without puppetdb.
Perhaps I had something set up incorrectly, but I could
Hi, does anyone have any elegant solutions for managing shosts.equiv? In
my puppet ssh module, host keys for /etc/ssh/ssh_known_hosts are
automatically managed with:
@@sshkey { $hostname:
ensure => present,
type => "rsa",
key => $sshrsakey,
}
/dashboard-vhost.conf I
added:
RailsBaseURI /
On Wednesday, July 25, 2012 8:10:55 AM UTC-4, banjer wrote:
>
> Hi,
> I am trying to configure my puppet master to be served by
> Apache/Passenger. I was successful in getting puppet-dashboard to run
> under Apache/Passenger, but have be
Hi,
I am trying to configure my puppet master to be served by
Apache/Passenger. I was successful in getting puppet-dashboard to run
under Apache/Passenger, but have been running into issues with puppet
master.
When I visit https://foo:8140 in my browser to test things out, I get:
Ruby on Ra
UTC-4, banjer wrote:
>
> I'm having the same exact problem trying to get Apache to serve puppet
> dashboard on CentOS 6.3. Apache is set up to serve my puppet master, and
> the puppetmaster is configured and working just fine. I get this in the
> apache error log:
>
>
I'm having the same exact problem trying to get Apache to serve puppet
dashboard on CentOS 6.3. Apache is set up to serve my puppet master, and
the puppetmaster is configured and working just fine. I get this in the
apache error log:
Directory index forbidden by Options directive:
/usr/sha
My original post should read "abc" and not "btp" in the "facter -p | grep
datacenter" examples. Edited inline below..
On Wednesday, June 27, 2012 2:20:35 PM UTC-4, banjer wrote:
>
> I'm running the following query to get a list of hosts in datacenter &qu
I'm running the following query to get a list of hosts in datacenter "abc":
root@puppet:~> curl -k -H "Accept: pson"
https://puppet:8140/production/facts_search/search?facts.datacenter=abc
["host04","host05","web01","db01"]
*datacenter *is a custom fact distributed with pluginsync. The problem i
If your hosts do not appear to be reporting, and you're seeing some
background tasks pending (top left in the puppet dashboard web gui), then
you probably need to start the "delayed_job" tasks on your puppet dashboard
server in order to process the reports. Run this:
*env RAILS_ENV=production
22 matches
Mail list logo
