Forgot mentioning the env details:

[user@puppetmaster ~]# rpm -qa | grep puppet
puppetlabs-release-6-6.noarch
puppetdb-terminus-1.0.4-1.el6.noarch
mcollective-puppet-agent-1.4.1-1.noarch
puppet-2.7.20-1.el6.noarch
hiera-puppet-1.0.0-1.el6.noarch
puppet-server-2.7.20-1.el6.noarch
mcollective-puppet-common-1.4.1-1.noarch

[user@puppetmaster ~]# cat /etc/centos-release
CentOS release 6.3 (Final)

On Thu, Mar 28, 2013 at 6:23 PM, Mohit Chawla
<[email protected]> wrote:
> Hello,
>
> Stuck in a weird place here. I am trying to do 'puppet master
> --compile foo.com', however I am not getting the catalog json. So far,
> I have noticed two sort of outputs:
>
> 1) The above command results in :
> notice: Compiled catalog for foo.com in environment production in 10.60 
> seconds
> Failed to submit 'replace catalog' command for foo.com to PuppetDB at
> puppetdb:8081: SSL_connect SYSCALL returned=5 errno=0 state=SSLv3 read
> finished A
>
> Notice that I don't actually get any json & of course, the ssl error.
>
> 2) Other output:
> Failed when searching for node bar.com: Could not retrieve facts for
> bar.com: Failed to find facts from PuppetDB at puppetdb:8081:
> SSL_connect SYSCALL returned=5 errno=0 state=SSLv3 read finished A
>
> Disabling storeconfig allows me to get a proper catalog json.
>
> Regarding the ssl errors, we've established the correctness of
> certificates in the relevant places - and done tests using curl and
> using ruby net/http. Here's a gist of for the curl and ruby snippet.
> https://gist.github.com/alcy/5262866
>
> Any suggestions what could be happening here ? Perhaps in
> indirector/facts/puppetdb.rb,  http_get doesn't get the correct ssl
> params or something ?

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to