puppet

Puppet Dashboard Error – getaddrinfo: Name or service not known (SocketError)

While configuring the Puppet Dashboard for your Puppet Instance, you might get this kind of error /usr/lib/ruby/1.8/webrick/utils.rb:63:in `getaddrinfo’: getaddrinfo: Name or service not known (SocketError) [2015-05-17 19:48:38] INFO ruby 1.8.7 (2011-06-30) [x86_64-linux] /usr/lib/ruby/1.8/webrick/utils.rb:63:in `getaddrinfo’: getaddrinfo: Name or service not known (SocketError) from /usr/lib/ruby/1.8/webrick/utils.rb:63:in `create_listeners’ from /usr/lib/ruby/1.8/webrick/server.rb:75:in `listen’ from /usr/lib/ruby/1.8/webrick/server.rb:63:in `initialize’ from /usr/lib/ruby/1.8/webrick/httpserver.rb:24:in `initialize’ from /usr/share/puppet-dashboard/script/../config/../vendor/gems/rack-1.1.6/lib/rack/handler/webrick.rb:10:in …

Puppet Dashboard Error – getaddrinfo: Name or service not known (SocketError) Read More »

Puppet error after Ruby upgrade

As per the thumb rule, all your softwares should be up to date and in-sync with other tools upgrade. But if you are getting Error in puppet after ruby upgrade like : /usr/share/puppet-dashboard/script/../config/../vendor/rails/railties/lib/rails/gem_dependency.rb:23:in `add_frozen_gem_path’: undefined local variable or method `source_index’ for Rails::GemDependency:Class (NameError) from /usr/share/puppet-dashboard/script/../config/boot.rb:47:in `load_initializer’ from /usr/share/puppet-dashboard/script/../config/boot.rb:38:in `run’ from /usr/share/puppet-dashboard/script/../config/boot.rb:11:in `boot!’ from /usr/share/puppet-dashboard/script/../config/boot.rb:110 from /usr/share/puppet-dashboard/script/server:2:in …

Puppet error after Ruby upgrade Read More »

Puppet Error: Could not request certificate: The certificate retrieved from the master does not match the agent’s private key

While configuring the new Puppet agent, sometimes its throwing error like below [root@appvm001 puppet]# puppet agent –verbose –test Info: Creating a new SSL key for appvm001 Info: Caching certificate for ca Info: Caching certificate for appvm001 Error: Could not request certificate: The certificate retrieved from the master does not match the agent’s private key. Certificate …

Puppet Error: Could not request certificate: The certificate retrieved from the master does not match the agent’s private key Read More »

Puppet error : Could not send report: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed

If you are getting the below error while configuring and running manifests in new Puppet agent Puppet error : Could not send report: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed: Warning: Unable to fetch my node definition, but the agent run will continue: Warning: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate …

Puppet error : Could not send report: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed Read More »

Scroll to Top
Scroll to Top