Re: [Puppet Users] Puppet 6 removed native Nagios provider

El 19/10/18 a las 5:45, comport3 escribió: Hi All, We are testing some Nagios stuff on Puppet 6 and it seems all the previously native functionality was completely removed. Is it available to be re-added via a Module? If not, why was it removed - technical issues, etc??

[Puppet Users] Puppet 6 removed native Nagios provider

Hi All, We are testing some Nagios stuff on Puppet 6 and it seems all the previously native functionality was completely removed. Is it available to be re-added via a Module? If not, why was it removed - technical issues, etc?? Example to reproduce: (on server to be monitored, exporting it's

[Puppet Users] Re: Apache module + Ubuntu 18.04 + mpm prefork breaks PHP version

OK I have managed to debug this one. It only seems to apply when using mpm_module: prefork with cgid and/or php There is a fix to the Apache module as follows: Bump the $php_version in params.pp from 7.0 to 7.2 on line 268 Add this section beneath the preceding logic around line 85/86 in

[Puppet Users] Re: Puppet Certificate Issues

Hi Rohit, Is the hostname from `/CN=our.puppet.domain` showing up in your puppetserver's certificate? You can verify that with `puppet cert list --all` on the puppetserver container. This looks like a DNS issue. On Thursday, October 18, 2018 at 11:41:16 AM UTC-7, Rohit wrote: > > Hello, we

[Puppet Users] Puppet Gurus, Question

Puppet Gurus, I am looking for a person or contracting company to assist my company in the Washington DC area for a Contract Puppet SME. Where is a good place to look or post? Any help would be appreciated. The agencies around here DONT specialize in it and I am fed a lot of BS. Any help would

[Puppet Users] Puppet Certificate Issues

Hello, we currently have a puppet docker container setup and are experiencing certificate issues. Basically, in our docker setup (on our main server) I had generated and signed new certificates, but the puppet_db container keeps restarting. Here are logs from the puppet_db container:

Re: [Puppet Users] pip package provider on Redhat

Yeah, I know we're old. I'm asking in general though (imagining it would be happening with the current version for example?), what would be an elegant way to fix this? On Wednesday, October 17, 2018 at 5:22:05 AM UTC-5, Ben Ford wrote: > > Hi Sergei! > > Puppet 3.x is quite old, and in fact

[Puppet Users] Using variable for user password hash causes password updated each run.

I have been asked to set password for a user so it is unique on every single host we support. I have a script that generates the password and I had pulled it in via a generate call. The scripts takes in two of facter values to be used to aid in generating the password. $myvar =

Re: [Puppet Users] Re: Pass parameters to the 'postgresql' module when instantiated as a dependency of the 'puppetdb' module

On Thursday, October 18, 2018 at 6:57:41 AM UTC-5, Eirik Øverby wrote: > > > class foo:bar( > > $param1, # This enables you to provide 'param1' when > instantiating the class, > > # and it enables auto-parameter-lookup for > foo::bar::param1 in Hiera. > >

Re: [Puppet Users] Re: Pass parameters to the 'postgresql' module when instantiated as a dependency of the 'puppetdb' module

Hi Eirik, I can't speak for those antique 2.x/3.x versions ;-) The automatic parameter lookup feature is available from Puppet 4.8 onwards, see the official description of it here . As you can see from the documentation, setting

Re: [Puppet Users] Re: Pass parameters to the 'postgresql' module when instantiated as a dependency of the 'puppetdb' module

> class foo:bar( > $param1, # This enables you to provide 'param1' when instantiating > the class, > # and it enables auto-parameter-lookup for foo::bar::param1 > in Hiera. > # if no value is given or found in Hiera, the value of > $param1 will be

Re: [Puppet Users] Re: Pass parameters to the 'postgresql' module when instantiated as a dependency of the 'puppetdb' module

Hi Eirik, the parameter behavior is actually the other way around: class foo:bar( $param1, # This enables you to provide 'param1' when instantiating the class, # and it enables auto-parameter-lookup for foo::bar::param1 in Hiera. # if no value is given

Re: [Puppet Users] Re: Pass parameters to the 'postgresql' module when instantiated as a dependency of the 'puppetdb' module

Hi, > I don't fully understand Part 2: "2. You need any applicable resource-like > declaration of class postgresql::server in the manifest set to not itself > bind a value to the config_hash parameter." You are probably declaring your class/resource setting default values for parameters

[Puppet Users] Re: Pass parameters to the 'postgresql' module when instantiated as a dependency of the 'puppetdb' module

Hi John, Thank you for your response. I tried putting the parameters directly into Hiera as suggested and nothing happened. I don't fully understand Part 2: "2. You need any applicable resource-like declaration of class postgresql::server in the manifest set to not itself bind a value to the

[Puppet Users] Apache module + Ubuntu 18.04 + mpm prefork breaks PHP version

Hi All, When testing the latest version of ' puppetlabs-apache', in default mode and settings on Ubuntu 18.04 it works fine. When changing the mpm + php + cgi it all ends in tears when the PHP version mysteriously tries to go from 7.2 (available and default on OS) to 7.0. Ala - ``` class {