Ask Your Question

Error running /opt/puppetlabs/aws/bin/

asked 2017-07-20 11:11:07 -0600

jay007 gravatar image

Hi Guys,

I am new to puppet and just starting.

Hi Guys, I am running puppetmaster behind a AWS ELB. I can access the login page using ELB DNS name and also through a R53 public record that I configured and pointing to my ELB alias record. However, when I try to run
sudo /opt/puppetlabs/aws/bin/

It fails with following error.

/opt/puppetlabs/puppet/lib/ruby/2.1.0/net/http.rb:879:in `initialize': getaddrinfo: Name or service not known (SocketError) from /opt/puppetlabs/puppet/lib/ruby/2.1.0/net/http.rb:879:in `open' from /opt/puppetlabs/puppet/lib/ruby/2.1.0/net/http.rb:879:in `block in connect' from /opt/puppetlabs/puppet/lib/ruby/2.1.0/timeout.rb:75:in `timeout' from /opt/puppetlabs/puppet/lib/ruby/2.1.0/net/http.rb:878:in `connect' from /opt/puppetlabs/puppet/lib/ruby/2.1.0/net/http.rb:863:in `do_start' from /opt/puppetlabs/puppet/lib/ruby/2.1.0/net/http.rb:852:in `start' from /opt/puppetlabs/puppet/lib/ruby/2.1.0/net/http.rb:1375:in `request' from /opt/puppetlabs/server/data/enterprise/modules/pe_install/files/set_console_admin_password.rb:56:in `get_response' from /opt/puppetlabs/server/data/enterprise/modules/pe_install/files/set_console_admin_password.rb:101:in `get_user' from /opt/puppetlabs/server/data/enterprise/modules/pe_install/files/set_console_admin_password.rb:114:in `main' from /opt/puppetlabs/server/data/enterprise/modules/pe_install/files/set_console_admin_password.rb:118:in `<main>' configure-pe.rb: failed (status false) /opt/puppetlabs/aws/bin/configure-pe.rb:433:in `system_to_log' /opt/puppetlabs/aws/bin/configure-pe.rb:215:in `passwd=' /opt/puppetlabs/aws/bin/configure-pe.rb:658:in `<main>'

I can't seem to find any documentation around this issue. Any help would be appreciated.


edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted

answered 2017-07-21 06:23:18 -0600

jay007 gravatar image

updated 2017-07-21 07:39:07 -0600

I managed to fix this.

Here is the solution incase anyone is curious.

This error happens if your cert name and host name doesn't match. So, delete all existing certs and recreate new certs. Here are the details on how to recreate new certs

Good Luck, as you will get more errors :P

Thanks, Jay

Note: Based on my experience (as a noob) I would highly recommend not to use puppet ami to launch puppet master (on AWS) if you are launching it in private subnet and ELB infront of it.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower


Asked: 2017-07-20 11:11:07 -0600

Seen: 120 times

Last updated: Jul 21 '17