Justin, I implemented the suggestion you made however after running the
curl command against the 2 environments having the issue and receiving the
204 response, the puppet module is still getting the 500 error. Do you or
anyone else have any other suggestions? Is it possible it's related to
r
Dirk, why wouldn't puppet just do this automatically when a module
changes? Is there a bug somewhere?
On Tuesday, August 25, 2020 at 2:43:03 AM UTC-4 Dirk Heinrichs wrote:
> Am Montag, den 24.08.2020, 11:06 -0700 schrieb pkraw...@gmail.com:
>
> Justin, I implemented the sugge
pet apply --modulepath=/home/toor --test -e
"include testmod" --verbose
On Tuesday, August 25, 2020 at 12:38:05 PM UTC-4 pkraw...@gmail.com wrote:
> Dirk, why wouldn't puppet just do this automatically when a module
> changes? Is there a bug somewhere?
>
> O
urce_types in the root of your environment that should be removed and
> regenerated like Dirk said. Possibly you could have an older version in a
> different environment that's being loaded first, but I don't think that'd
> cause a problem for uncached, new parameters on
hing the server cache. Both domains have a value of 0 for
environment_timeout for each environment.
On Friday, August 28, 2020 at 2:32:05 PM UTC-4 Justin Stoller wrote:
> On Fri, Aug 28, 2020 at 10:14 AM pkraw...@gmail.com
> wrote:
>
>> Great info but I think I might have found th
urce_types
directory?
On Friday, August 28, 2020 at 2:47:26 PM UTC-4 pkraw...@gmail.com wrote:
> Justin, yes it's happening in all environments which leads me to believe
> it's related to an old copy
> in /opt/puppetlabs/puppet/cache/lib/puppet/type. Still trying to wrap my
Thanks Justin/Josh. Josh, I did come across this during my recent searches
on trying to resolve my original issue.
On Tuesday, September 15, 2020 at 1:48:47 PM UTC-4 Josh Cooper wrote:
>
>
> On Tue, Sep 15, 2020 at 5:25 AM pkraw...@gmail.com
> wrote:
>
>> So I've
Version: Puppet 5.5
We have an open source puppet environment which has been up for almost 5
years and certs are about to expire. We are running 5.5. I know it's an
older version but we are sunsetting puppet by year end.
Setup:
PuppetCA Server
Pupper Master Server 1
Puppet Master Server 2
Pu
-in ca_crt.pem -noout -text|grep -A 3 Validity
> chown puppet: ./*
> cd /etc/puppetlabs/puppet/ssl
> cp -a ca/ca_crt.pem certs/ca.pem
>
> # CLIENTS
>
> /opt/puppetlabs/bin/puppet resource file
> /etc/puppetlabs/puppet/ssl/certs/ca.pem ensure=absent
> /opt/puppe
When we installed puppet open source and upgrade to V5, mcollective was
also installed and running both the mcollective servers and the service on
each remote node.
Can I shutdown mcollective on both the nodes and servers since we don't use
it? We use another tool for automation management on
10 matches
Mail list logo
