Issue #16562 has been updated by Adam Dorsey.
My utmost apologies, this turned out to be a DNS issue; the server's hostname isn't currently in DNS yet, so I had to add its IP to its hosts file (the puppet client is running on the puppet server). Also for some reason local DNS is getting redirected when the hostname isn't found, probably Comcast's stupid DNS redirection crap. Now that I've fixed the hosts file everything is working as intended. ---------------------------------------- Bug #16562: "Unknown protocol" SSL error when running puppet agent on puppet server https://projects.puppetlabs.com/issues/16562#change-71724 Author: Adam Dorsey Status: Needs More Information Priority: Normal Assignee: Adam Dorsey Category: Target version: Affected Puppet version: 2.7.19 Keywords: Branch: Expected behavior: I run 'puppet agent --test', it creates a new cert request for the puppet server Actual behavior: [root@server1 puppet]# puppet agent --test err: Could not retrieve catalog from remote server: SSL_connect returned=1 errno=0 state=SSLv2/v3 read server hello A: unknown protocol warning: Not using cache on failed catalog err: Could not retrieve catalog; skipping run err: Could not send report: SSL_connect returned=1 errno=0 state=SSLv2/v3 read server hello A: unknown protocol running Puppet 2.7.19-1.el6 from the yum.puppetlabs.com repo. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
