A note and a complaint. Being a lazy sysadmin, I configured my ca_ttl to
25y. I assumed (poorly) that the ca would be created with the 25 year life
span, and then certs would be created and use the end date of the root
cert. This is not correct. Somehow a root CA can create certificates
I just upgraded the second half of a two node puppetmaster cluster and now
I am having issues with puppet-dashboard report processing. If I have
workers running on both servers, they try to process each others reports,
but since the report data file is not there, it fails. I would have
2, 2013 4:29:23 PM UTC-5, jemmorey wrote:
I just upgraded the second half of a two node puppetmaster cluster and now
I am having issues with puppet-dashboard report processing. If I have
workers running on both servers, they try to process each others reports,
but since the report data file
Looks like there is no current method to prevent multiple dashboard nodes
from stomping on each others reports, the delayed_jobs table does have a
locked_by, but that is only used during the actual event processing.
mysql describe delayed_jobs;
Does anyone else have this problem with puppet-dashboard 1.2.15? The front
page will show changed/failed/etc in the graphs, but when looking at the
table it does not show anything but unchanged. When I drill down into
the individual servers it will show the changed/failed details.
Do I need
Mark,
I was able to compile puppet via the spec file included in the source up to
version 2.7.5 on RHEL4 (32 and 64-bit). I can't remember the issues I had
with 2.7.6-9 right now, but it had to do with the ancient ruby (1.8.1). I
did grab the requisite dependencies (augeas-libs, ruby-augeas,
Jason,
I was able to compile puppet via the spec file included in the source up to
version 2.7.5 on RHEL4 (32 and 64-bit). I can't remember the issues I had
with 2.7.6-9 right now, but it had to do with the ancient ruby (1.8.1). I
did grab the requisite dependencies (augeas-libs,
Would anyone please assist me on this one? This fact seems to work, but it
doesn't return when called directly via facter --puppet noop, but the
resulting facts end up in the reports.
I'm at wits end with this. Thanks!
snip
utc_hour = Facter::Util::Resolution.exec(%q/bin/date -u +%H).chomp
if utc_hour.between?(1,10)
result = false
else
result = true
end
end
#puts result #{result}
result
end
end
On Fri, Mar 16, 2012 at 10:56 AM, Jemmorey wrote:
Would anyone please assist me on this one? This fact seems to work, but
it doesn't return
Can anyone suggest a good method for automatically configuring a
puppetmaster to get it's certificate with dnscertalias's from a
standalone root CA.
I have found that if I start up the puppetmaster for the first time
with the ca = false and specifying the ca_server it will not request a
new
I'm a relatively new user of puppet, so hopefully this isn't too basic
a problem.
I have a resolv.conf module that intermittently works. When it fails,
it fails with:
err: Could not retrieve catalog from remote server: Error 400 on
SERVER: Could not parse for environment development: Syntax
? {
Linux = root,
SunOS = bin,
default = root,
},
On Thu, Jul 28, 2011 at 1:47 PM, Jemmorey jemmo...@gmail.com wrote:
I'm a relatively new user of puppet, so hopefully this isn't too basic
a problem.
I have a resolv.conf module
12 matches
Mail list logo
