On Sun, Aug 21, 2011 at 7:53 PM, Khoury wrote:
> Adding the entry "127.0.0.1 " solved the
> problem. I suppose that means dns/reverse dns is one of the ways that
> puppet determines what the node name is (although in my case it
> appears to be inconsistently applied). I'm just going to make
On Aug 21, 5:30 pm, Khoury Brazil wrote:
> Hi Everyone,
>
> I have a weird issue where the puppet client running under launchd
> generates a new certificate request for 'localhost' which I thought
> was pretty odd (with the side effect of it failing to run and report).
> Running puppetd manually n
Hi Everyone,
I have a weird issue where the puppet client running under launchd
generates a new certificate request for 'localhost' which I thought
was pretty odd (with the side effect of it failing to run and report).
Running puppetd manually never generates this behavior.
Details:
Client:
pupp
Hello, all.
I have a box that I'd like to have striping swap spaces. I attempted:
mount { 'swap':
alias => 'swap0',
atboot => true,
device => '/dev/xvdo',
ensure => 'mounted',
options=> 'defaults',
fstype => 'swap',
}
mount { 'swap':
alias => 'swap1',
atb
Hmm, in that specific situation, sure. I can see how some of these would be
an odd fit for the language as currently implemented, I sure would like:
* transactional builds ( so an error does not leave a box in an
inconsistent, half configured state )
* more of an ability to specify error state
On Sun, Aug 21, 2011 at 8:31 AM, Nicolai wrote:
> To make sure you have a clean client and master knows nothing about it,
> (ssl-wise) do the following:
>
> on master:
> puppetca --clean client.example.com
>
> on client:
> rm -r /var/lib/puppet/ssl
> puppetd --test
>
The puppetca and puppetd too
On Sat, Aug 20, 2011 at 7:40 PM, Denmat wrote:
> Hi,
>
> The standard port is 8140, are you using a different port?
>
Didn't know that was standard, but yes.
> You will need to pass --server on the puppet agent. The command line is
> different from the daemon config.
>
In what way?
> With c
To make sure you have a clean client and master knows nothing about it,
(ssl-wise) do the following:
on master:
puppetca --clean client.example.com
on client:
rm -r /var/lib/puppet/ssl
puppetd --test
back to master:
puppetca --list (to check for the signing request from client)
puppetca --sig
Am using dashboard 1.1.1 with the use_file_bucket_diffs option.
When clicking on the links within a report it will show the old md5
file (on the left) but not the new md5 file (on the right)
like;
content content changed '{md5}26a3112822d01f2ce6b3f052bf2809de' to
'{md5}dd97364ab0559344d73231f51795
Sans wrote:
> Thanks Matthias! I noticed the semicolon typo.
> What does ${::hostname}-cert.pem implicate (as opposed to ${hostname}-
> cert.pem)?
It just makes explicit that it's a variable from the global scope (as
it's a fact) and not from the current local scope.
Check out recent puppet doc
Which version of dashboard are you running, 1.2x?
I'm running puppet 2.6.6 (from EPEL5) and dashboard 1.1.1 with
passenger 3.0.8 on RHEL 5.6 with ruby 1.8.5.
You could try this ruby 1.8.7 package from
http://rpm.aegisco.com/aegisco/rhel/5Server/x86_64/
They are Allowed Contributors to Chef
On A
11 matches
Mail list logo
