Puppet users - Apr 2008 - Certificate retrieval failed: Connection reset by peer

Hi.


When registering a new client with the puppetmaster I get the
following error:

[root@host ~]# puppetd --server puppetmaster --waitforcert 50 --test
info: Creating a new certificate request for host
info: Creating a new SSL key at /var/lib/puppet/ssl/private_keys/
host.pem
warning: peer certificate won''t be verified in this SSL session
err: Could not call puppetca.getcert: #<Errno::ECONNRESET: Connection
reset by peer>
/usr/lib/ruby/site_ruby/1.8/puppet/network/client/ca.rb:31:in
`request_cert'': Certificate retrieval failed: Connection reset by peer
(Puppet::Error)
        from /usr/sbin/puppetd:356

I''m not sure what may be causing this, but should add that we recently
upgraded from 0.24.1 to 0.24.2


Regards,
kenneho
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users-unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

On Apr 25, 2008, at 1:48 AM, kenneho wrote:
>
> Hi.
>
>
> When registering a new client with the puppetmaster I get the
> following error:
>
> [root@host ~]# puppetd --server puppetmaster --waitforcert 50 --test
> info: Creating a new certificate request for host
> info: Creating a new SSL key at /var/lib/puppet/ssl/private_keys/
> host.pem
> warning: peer certificate won''t be verified in this SSL session
> err: Could not call puppetca.getcert: #<Errno::ECONNRESET: Connection
> reset by peer>
> /usr/lib/ruby/site_ruby/1.8/puppet/network/client/ca.rb:31:in
> `request_cert'': Certificate retrieval failed: Connection reset by
peer
> (Puppet::Error)
>        from /usr/sbin/puppetd:356
>
> I''m not sure what may be causing this, but should add that we
recently
> upgraded from 0.24.1 to 0.24.2

You will almost definitely have useful information on your server-side  
that you can use to figure out what the problem is.

-- 
You can''t wait for inspiration. You have to go after it with a club.
     -- Jack London
---------------------------------------------------------------------
Luke Kanies | http://reductivelabs.com | http://madstop.com


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users-unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

The problem seems to have been resolved over the weekend, so things seems to
work fine at the moment.

But before posting on this list I had taken a look in /var/log/puppet on the
puppetmaster, but found no relevant (as far as I could see) information on
this problem. Are there other log files defined for puppet that are worth
looking into when debugging Puppet?

Regards,
kenneho

On 4/25/08, Luke Kanies <luke@madstop.com> wrote:
>
>
> On Apr 25, 2008, at 1:48 AM, kenneho wrote:
>
> >
> > Hi.
> >
> >
> > When registering a new client with the puppetmaster I get the
> > following error:
> >
> > [root@host ~]# puppetd --server puppetmaster --waitforcert 50 --test
> > info: Creating a new certificate request for host
> > info: Creating a new SSL key at /var/lib/puppet/ssl/private_keys/
> > host.pem
> > warning: peer certificate won''t be verified in this SSL
session
> > err: Could not call puppetca.getcert: #<Errno::ECONNRESET:
Connection
> > reset by peer>
> > /usr/lib/ruby/site_ruby/1.8/puppet/network/client/ca.rb:31:in
> > `request_cert'': Certificate retrieval failed: Connection
reset by peer
> > (Puppet::Error)
> >        from /usr/sbin/puppetd:356
> >
> > I''m not sure what may be causing this, but should add that we
recently
> > upgraded from 0.24.1 to 0.24.2
>
>
> You will almost definitely have useful information on your server-side
> that you can use to figure out what the problem is.
>
> --
> You can''t wait for inspiration. You have to go after it with a
club.
>     -- Jack London
> ---------------------------------------------------------------------
> Luke Kanies | http://reductivelabs.com | http://madstop.com
>
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users-unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

On Apr 28, 2008, at 5:17 AM, Kenneth Holter wrote:
> The problem seems to have been resolved over the weekend, so things  
> seems to work fine at the moment.
>
> But before posting on this list I had taken a look in /var/log/ 
> puppet on the puppetmaster, but found no relevant (as far as I could  
> see) information on this problem. Are there other log files defined  
> for puppet that are worth looking into when debugging Puppet?

Puppet uses syslog by default for all logging.  I should probably just  
remove those log directories, since they seem to just confuse  
everyone, but I know at least a couple of people use them.

-- 
Charm is a way of getting the answer yes without asking a clear
question. -- Albert Camus
---------------------------------------------------------------------
Luke Kanies | http://reductivelabs.com | http://madstop.com


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users-unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

I got the same problem yesterday, and restarting the puppetmaster resolved
the problem. Is anyone else experiencing this?


On 4/28/08, Luke Kanies <luke@madstop.com> wrote:
>
>
> On Apr 28, 2008, at 5:17 AM, Kenneth Holter wrote:
>
> > The problem seems to have been resolved over the weekend, so things
> > seems to work fine at the moment.
> >
> > But before posting on this list I had taken a look in /var/log/
> > puppet on the puppetmaster, but found no relevant (as far as I could
> > see) information on this problem. Are there other log files defined
> > for puppet that are worth looking into when debugging Puppet?
>
>
> Puppet uses syslog by default for all logging.  I should probably just
> remove those log directories, since they seem to just confuse
> everyone, but I know at least a couple of people use them.
>
> --
> Charm is a way of getting the answer yes without asking a clear
> question. -- Albert Camus
> ---------------------------------------------------------------------
> Luke Kanies | http://reductivelabs.com | http://madstop.com
>
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users-unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---