On Thu, Sep 17, 2020 at 8:12 AM Bob Negri wrote:
> We recently updated our PuppetDB servers to PuppetDB 6.12.0 and PostgreSQL
> 12.
> Started getting these errors:
>
> ERROR: relation "resource_events_20200917z" does not exist at character 13
> ERROR: relation "resource_events_20200917z"
I'm not an expert by any means.
The *easiest *way would be to use regex for this - there's an example in
https://puppet.com/docs/puppet/6.17/lang_node_definitions.html.
On Thu, Sep 17, 2020 at 6:19 PM djc...@gmail.com wrote:
> Hello experts,
>
> I apply all my current classes like so:
>
> #
This is a draft of a new 6.x tuning guide we're working on, it may be of
some help to you
https://tickets.puppetlabs.com/browse/SERVER-2771
The big things are a need for increased codecache and a very negative
effect of low max-requests-per-instance values.
hth,
Justin
On Thu, Sep 17, 2020 at
Hello experts,
I apply all my current classes like so:
# cat site.pp
node default {
class { 'selinux':
mode => 'permissive',
type => 'targeted', }
class { 'commonpackages': }
class { 'polkit': }
class { 'libstoragemgmt': }
class { 'rngd':}
class {
We recently updated our PuppetDB servers to PuppetDB 6.12.0 and PostgreSQL
12.
Started getting these errors:
ERROR: relation "resource_events_20200917z" does not exist at character 13
ERROR: relation "resource_events_20200917z" already exists
ERROR: deadlock detected
ERROR: could not
Has anyone see errors like this one? We recently upgraded from Postgresql
9.6 to Postgresql 12 and from PuppetDB 6.7 (I think as I did not do it) to
6.12.0.
2020-09-16 19:24:15.997 UTC [35203] ERROR: relation "reports_20200916z"
does not exist at character 13
2020-09-16 19:24:15.997 UTC
Hello
I upgrade one of our puppetserver from puppetserver-5.3.1- to
puppetserver-6.13.0. The puppet server became very busy than before.
The puppet compiled catalog time is about 10 times than before.
Here is one of tGhe client report:
catalog_application380.6643
transaction_evaluation
