I haven't had that experience with puppet, but I have had it with other
services.
Assuming you've gone through things like checking load, logs (for the
puppetserver/puppet master), continuous ping, strace, and so on, I recommend
that you capture packets on either side. Checking timestamps may
Hello,
i am trying to run a master+agent setup on 2 Centos 7 vms with one
ethernet adapter for internetconnection and one for the connection between
the 2 vms.
But I cant seem to get them together. Since i am behind a company proxy i
entered the proxy in the yum.conf and the
when I run in the agent the command puppet master --debug --no-daemonize
stays waiting in the line debug: Finishing transaction -612625138 and does
not deliver the certificate, I run the command
openssl s_client -connect puppetc4: 8140 and habeces connects and other
times, when I run
Hi all,
We're pleased to announce that version 1.1 of the Resource API has been
released yesterday.
The Resource API provides a simple way to create new native resources in
the form of types and providers for Puppet. It is provided as a Ruby gem to
be referenced within modules. Support for it
On 12/04/18 14:58, jcbollinger wrote:
On Wednesday, April 11, 2018 at 11:28:12 AM UTC-5, Henrik Lindberg wrote:
On 11/04/18 18:21, jcbollinger wrote:
> I'm writing a module for Puppet self-management, or at least I
think I
> am. I was surprised to not find very much along
