help you
> dig in more.
> Maggie
>
> On Thu, Jul 8, 2021 at 9:03 AM Dave Beedle wrote:
>
>> Thanks for the quick response! This may apply, we may well manipulate
>> the certs...some of our processes predate me so, I'll poke around to see
>> if I can figu
; On Thu, Jul 8, 2021 at 8:02 AM Dave Beedle wrote:
>
>> We have, in the past, generated cert on our puppet server using:
>> /opt/puppetlabs/bin/puppetserver ca generate --ca-client --certname
>> test.out.domain --subject-alt-names
>>
>> But this began failing as
We have, in the past, generated cert on our puppet server using:
/opt/puppetlabs/bin/puppetserver ca generate --ca-client --certname
test.out.domain --subject-alt-names
But this began failing as we updated to Puppetserver v6.15.3. Seems to be
unhappy with some gems (log below). I have resinta
Hi all. We've been seeing some issues after updating from puppetserver
6.15.1 to 6.15.3. Initially we had suspected the puppet-agent (6.22.1) but
have backed that out. We also have updated PuppetDB 6.15.0 to 6.16.1.
It seems that, over time performance of the server drops. Puppet agent run
ti
After updating puppetdb from v6.7.3 to 6.11.3, the puppetdb dashboard
connects and begins to show data but stops after showing the version
number. The version number is correct. All else seems to work.
In the log there is:
2020-08-20T20:04:49.049Z WARN [o.e.j.s.HttpChannel] /pdb/dashboard/dat
