been looking to troubleshoot.
>
> On Wed, 17 Jun 2015 07:11:09 -0700 (PDT)
> Ed Deloye > wrote:
>
> > Discovered truncated yaml files on the puppet master in
> > /var/lib/puppet/yaml/node for the 24 systems. Identified as each one
> > was 4096 bytes. After
Discovered truncated yaml files on the puppet master in
/var/lib/puppet/yaml/node for the 24 systems. Identified as each one was
4096 bytes. After deleting those files puppet runs successfully on the
nodes.
On Thursday, May 29, 2014 at 3:57:49 PM UTC-4, Sans wrote:
>
> I have two identical nod
Did anyone find a solution to this. We suddenly started seeing this on 24
of our 251 nodes.
Thanks,
Ed
On Thursday, May 29, 2014 at 3:57:49 PM UTC-4, Sans wrote:
>
> I have two identical nodes - serv106 and serv107 - one of which is
> working just fine but the other one failing with these err
On Tuesday, May 12, 2015 at 2:48:21 PM UTC-4, Ramin K wrote:
>
> On 5/12/15 10:48 AM, Ed Deloye wrote:
> > We recently upgraded puppet to 2.7.26 with the puppetmaster running
> > CentOS 6.6.
> >
> > Building a new RHEL5 system using kickstart, after the firs
We recently upgraded puppet to 2.7.26 with the puppetmaster running CentOS
6.6.
Building a new RHEL5 system using kickstart, after the first reboot puppetd
runs and creates a new SSL key which is autosigned by the puppetmaster. At
the completion of the puppetd run the system reboots. When puppe
I am building a new puppet master server and trying to get it to run puppet
on itself.
I deleted everything in the /var/lib/puppet/ssl directory and generated a
new cert.
I get this error:
err: Could not retrieve catalog from remote server: SSL_connect returned=1
errno=0 state=SSLv3 read serve
