We found a likely explanation for the Puppet Server service not starting on PE 3.8.
The newer Puppet Server version in PE 3.8, through transitive dependencies, needs to be able to load the "libcrypt.so" shared library. On some Ubuntu configurations, the LD_LIBRARY_PATH doesn't include the directory that this library lives in. We found this to be the case with with a default AMI amd64 Ubuntu 14.04 in Amazon EC2, for example. This results in the master failing to start with this cryptic error message. One can workaround the problem by updating the library path that Puppet Server uses at startup. Instructions on how to do that for PE are now documented here - http://docs.puppetlabs.com/pe/latest/release_notes_known_issues.html#ubuntu-conflict-when-youre-running-on-fusion-vm-and-amazon-ec2. Also, we have a JIRA ticket with more information about this problem that we'll use for tracking the longer-term fix - see https://tickets.puppetlabs.com/browse/SERVER-592. We would be interested in learning if there are any users who continue to encounter this problem after trying the workaround. --- Jeremy On Wednesday, April 29, 2015 at 1:41:20 PM UTC-7, Kamil Keski wrote: > > Clean slate install on Ubuntu 14.04 produces the following error and will > not proceed. > > ** HTTP_PROXY= http_proxy= HTTPS_PROXY= https_proxy= curl --tlsv1 -s > https://puppetmaster.local:8140 > ** HTTP_PROXY= http_proxy= HTTPS_PROXY= https_proxy= curl --tlsv1 -s > https://puppetmaster.local:8140 > ** HTTP_PROXY= http_proxy= HTTPS_PROXY= https_proxy= curl --tlsv1 -s > https://puppetmaster.local:8140 > ** HTTP_PROXY= http_proxy= HTTPS_PROXY= https_proxy= curl --tlsv1 -s > https://puppetmaster.local:8140 > > ======================================================================== > ** cp /opt/puppet/share/installer/install_log.lastrun.ITTPuppet.log > /var/log/pe-installer > ** sed "s/^\(q_.*password\)=.*/#\1=REDACTED/g" < > "/tmp/pe-installer-M4MbxK1G/install/answers.lastrun.ITTPuppet" > > "/var/log/pe-installer/answers.install" > !! ERROR: The puppet master service failed to start within 120 > seconds; unable to proceed > > > I am using puppetmaster.local as the FQDN which is resolvable from the > server and the client machine I'm executing the web install from (mapped in > hosts file for testing). Nothing else of interest in the log files. Have > tried on two separate clean images to no avail. > > pe-puppetserver log shows the following. > > Failed to load feature test for posix: can't find user for 0 > Cannot run on Microsoft Windows without the win32-process, win32-dir and > win32-service gems: Win32API only supported on win32 > Puppet::Error: Cannot determine basic system flavour > (root) at > /opt/puppet/lib/ruby/site_ruby/1.9.1/puppet/feature/base.rb:32 > require at org/jruby/RubyKernel.java:1071 > > Well that's interesting.. > > All default packages have been updated. > > Maddening! > > Any idea's? > > Thanks, > K > -- 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 puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/14ba6639-2b26-4a52-bdc0-1bab10073268%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
