Issue #11561 has been updated by Justin Stoller.
Nathan - This is really odd that the installation is succeeding in the first place. Going over your log shows that there are actually several errors occurring related to the dashboard install that should prevent it from succeeding. The main issue that is stopping you is that the dashboard cert is NOT successfully being signed as you can see at: <pre> * Starting web server pe-httpd ...done. ** cd /opt/puppet/share/puppet-dashboard; PATH=/opt/puppet/sbin:/opt/puppet/bin:$PATH rake RAILS_ENV=production cert:create_key_pair (in /opt/puppet/share/puppet-dashboard) ** cd /opt/puppet/share/puppet-dashboard; PATH=/opt/puppet/sbin:/opt/puppet/bin:$PATH rake RAILS_ENV=production cert:request (in /opt/puppet/share/puppet-dashboard) rake aborted! Connection timed out - connect(2) (See full trace by running task with --trace) ** /opt/puppet/bin/puppet cert --sign pe-internal-dashboard --color=false err: Could not call sign: Could not find certificate request for pe-internal-dashboard ** cd /opt/puppet/share/puppet-dashboard; PATH=/opt/puppet/sbin:/opt/puppet/bin:$PATH rake RAILS_ENV=production cert:retrieve (in /opt/puppet/share/puppet-dashboard) rake aborted! Connection timed out - connect(2) (See full trace by running task with --trace) ** chown -Rvf puppet-dashboard:puppet-dashboard /opt/puppet/share/puppet-dashboard/certs </pre> I've successfully used GoDaddy's Virtual Datacenter to install PE using your answers file save for two differences: passwords were: 'puppet' hostname was: localhost.miketest.local # taken from /etc/hosts as I didn't have a domain set up yet I believe it is most likely an issue with GoDaddy and your Domain Name since it's throwing a timeout error. If you're looking at having a similar setup you could try installing with hostname for dashboard and master set to `hostname -s` or something in your `/etc/hosts`. To try to go forward and repair your current setup I would comment out the SSL lines in the dashboard config that are keeping apache from starting, as well as turning your agent off (`service pe-puppet-agent stop`). Then I would check your dashboard settings file (`/opt/puppet/share/puppet-dashboard/config/settings.yml`) and see if the `ca_server` value is correctly pointing to your hostname. You should be able to add your external ip address with your hostname to your `/etc/hosts` file, ensure the settings in your dashboard settings are correct and then manually request/sign/receive the dashboard certs. To manually request/sign/recieve the dashboard certs: ensure pe-httpd is running (`service pe-httpd start` after commenting out the offending dashboard config) cd to `/opt/puppet/share/puppet-dashboard` # the dashboard directory on your dashboard machine run `/opt/puppet/bin/rake cert:request --trace` # you may need to include RAILS_ENV=production for the commands that include `rake` run `/opt/puppet/bin/puppet cert sign pe-internal-dashboard` on your master run `/opt/puppet/bin/rake cert:retrieve --trace` # back in the dashboard directory of your dashboard machine run `/opt/puppet/bin/receive_signed_certs.rb <your invetory servers name> <your masters name>` # These both should be the same for you Now in your `/opt/puppet/share/puppet-dashboard/certs` directory you should see the pems that were missing before. Uncommenting out your dashboard confs and restarting apache should do the trick. This is really odd because we do a LOT of testing on UbuntuLTS 64bit. The dashboard signing is the weakest link in the installer, and is very fragile depending on one's dns settings. The contents of your dashboard's settings file, /etc/hosts and any other dns information would be helpful for us to make the dashboard signing more robust in the future. And I'll speak to our developer about why the installer is reporting success on a failed install when he returns from his Christmas vacation. Justin ---------------------------------------- Bug #11561: Puppet Enterprise installer failing to create pems for pe-httpd https://projects.puppetlabs.com/issues/11561 Author: Nathan Valentine Status: Investigating Priority: Normal Assignee: Dominic Maraglia Category: installation Target version: Affected Puppet version: 2.7.6 Keywords: Puppet Enterprise installer certs pem Branch: Hi, I'm trying to deploy Puppet Enterprise to a 64-bit Ubuntu x86 cloud node on GoDaddy's Virtual Datacenter cloud platform. I've tried using both the *all* tarball as well as the Ubuntu 64-bit-specific tarball with the same end result. The installer runs to completion but pe-httpd will not start. A quick review of the installer debug log shows (attached) that the SSL keys are generated but the associated pem's are not present. root@brain-cloudperf-t-v-net:/root# /etc/init.d/pe-httpd start * Starting web server pe-httpd Syntax error on line 45 of /etc/puppetlabs/httpd/conf.d/puppetdashboard.conf: SSLCertificateFile: file '/opt/puppet/share/puppet-dashboard/certs/pe-internal-dashboard.cert.pem' does not exist or is empty Action 'start' failed. The Apache error log may have more information. ...fail! I've attached the following: 1) Full debug print installer log. 2) Answer file used for the installer run (minus passwords) 3) /etc/puppetlabs/httpd/conf.d/puppetdashboard.conf Interestingly enough, the same installer and answer file runs to completion on a similar Ubuntu 64-bit Rackspace node. Unfortunately, the PE install is during the very early stages of a bootstrap of a couple of new cloud environments so I don't have any config mgmt code that I can share that might highlight any differences between the two cloud nodes. I spoke with dpittman on #puppet and, as a sanity check, I'm going to try to deploy on a 32-bit GoDaddy node and see if the end result is any different. Thanks for any help you can provide! -- 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.
