Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
SSL_connect SYSCALL returned=5
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
  7 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
JL  
View profile  
 More options Dec 9 2009, 3:50 pm
From: JL <jlym...@gmail.com>
Date: Wed, 9 Dec 2009 12:50:34 -0800 (PST)
Local: Wed, Dec 9 2009 3:50 pm
Subject: SSL_connect SYSCALL returned=5
During puppet catalog runs, I sometimes (~ 10%) get the following
message:

Failed to retrieve current state of resource: SSL_connect SYSCALL
returned=5 errno=0 state=SSLv2/v3 read server hello A

Has anyone else ran into this?  I am running puppet 0.25.1 on Solaris
9 and 10.  Let me know what other info you need to help debug...


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Dan Bode  
View profile  
 More options Dec 27 2009, 3:19 am
From: Dan Bode <d...@reductivelabs.com>
Date: Sun, 27 Dec 2009 00:19:52 -0800
Local: Sun, Dec 27 2009 3:19 am
Subject: Re: [Puppet Users] SSL_connect SYSCALL returned=5

Hi,

During puppet catalog runs, I sometimes (~ 10%) get the following

> message:

> Failed to retrieve current state of resource: SSL_connect SYSCALL
> returned=5 errno=0 state=SSLv2/v3 read server hello A

> Does this problem still persist? Is it always on the same clients? What

webserver are you using (webbrick?) What OS is the puppet server running on?

thanks,

-Dan


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
JL  
View profile  
 More options Dec 29 2009, 3:31 pm
From: JL <jlym...@gmail.com>
Date: Tue, 29 Dec 2009 12:31:01 -0800 (PST)
Local: Tues, Dec 29 2009 3:31 pm
Subject: Re: SSL_connect SYSCALL returned=5
> > Does this problem still persist?

yes

> > Is it always on the same clients?

It has happened on every client except (I think) the puppet server
itself.  The clients are Solaris 10 boxes with a mix of sparc and
i386.  It seems to be happening about 10x more on one particular
client, but I think that is explained by the fact that catalog runs
take much longer on that box due to a module that is only being
applied to it.

> > What webserver are you using (webbrick?)

Yes, though this will probably change soon due to what I have read in
the Puppet Scalability Notes.  We currently have only deployed puppet
to 5 nodes, but plan on managing more than 50 nodes.

> > What OS is the puppet server running on?

Solaris 10

 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Silviu Paragina  
View profile  
 More options Dec 29 2009, 5:49 pm
From: Silviu Paragina <sil...@paragina.ro>
Date: Wed, 30 Dec 2009 00:49:05 +0200
Local: Tues, Dec 29 2009 5:49 pm
Subject: Re: [Puppet Users] Re: SSL_connect SYSCALL returned=5

Just a suggestion: does this happen on nodes that have the same version
of openssl?

I'm not really sure if the local puppet connection is encrypted or not
(ie puppetd<->puppetmaster on the server).

Silviu


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Dan Bode  
View profile  
 More options Dec 30 2009, 12:34 am
From: Dan Bode <d...@reductivelabs.com>
Date: Wed, 30 Dec 2009 06:34:33 +0100
Local: Wed, Dec 30 2009 12:34 am
Subject: Re: [Puppet Users] Re: SSL_connect SYSCALL returned=5

can you recreate with

#>puppetd --test --debug --trace

then post the output

thanks,

Dan


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Peter Meier  
View profile  
 More options Dec 30 2009, 11:58 am
From: Peter Meier <peter.me...@immerda.ch>
Date: Wed, 30 Dec 2009 17:58:48 +0100
Local: Wed, Dec 30 2009 11:58 am
Subject: Re: [Puppet Users] Re: SSL_connect SYSCALL returned=5
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> I'm not really sure if the local puppet connection is encrypted or not
> (ie puppetd<->puppetmaster on the server).

the only unencrypted connection of puppet is during the cert exchange,
everything else is encrypted.

cheers pete
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEUEARECAAYFAks7hr0ACgkQbwltcAfKi386sgCYxLfhSFer2fMOOAfpmId4n4/L
GQCdHkFWNXKKI3S55ZI2Ug6a1/W83YQ=
=4VCg
-----END PGP SIGNATURE-----


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
JL  
View profile  
 More options Jan 8 2010, 9:09 am
From: JL <jlym...@gmail.com>
Date: Fri, 8 Jan 2010 06:09:49 -0800 (PST)
Local: Fri, Jan 8 2010 9:09 am
Subject: Re: SSL_connect SYSCALL returned=5

> can you recreate with

> #>puppetd --test --debug --trace

> then post the output

I don't have a debug trace, but I can tell you that I switched from
webrick to mongrel with nginx and my problem went away.

 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »