Yes, I've added the temp path arg to the pe-puppetserver init as well. No go.
Has anyone installed successfully from scratch using an ubuntu 12.04 or 14.04 distro? Not an existing one, but a nice fresh build? On Thursday, April 30, 2015 at 11:49:29 AM UTC-6, Martin Alfke wrote: > > Hi Kamil, > > have you tried setting the path attribute at the exec resource? > Puppet exec starts with an empty environment and you are using several > Unix commands without full path. > > hth, > Martin > On Apr 30, 2015 7:29 PM, "Kamil Keski" <[email protected] > <javascript:>> wrote: > >> Thanks for the reply Josh. I worked through this and other posts I found >> pointing to the tmp issue. However I don't have /tmp or /usr/tmp mounted, >> they are just dir's on the root mount. >> >> fstab: >> >> # <file system> <mount point> <type> <options> <dump> <pass> >> /dev/mapper/ITTPuppet--vg-root / ext4 errors=remount-ro >> 0 1 >> # /boot was on /dev/sda1 during installation >> UUID=89c2c14f-03a6-4f43-9935-25061c52e4f9 /boot ext2 >> defaults 0 2 >> /dev/mapper/ITTPuppet--vg-swap_1 none swap sw >> 0 0 >> /dev/fd0 /media/floppy0 auto rw,user,noauto,exec,utf8 0 0 >> >> Pretty vanilla stuff here, so noexecute should not be an issue in this >> instance. For good measure I tried creating a new dir (/usr/tmp) with 777 >> and defined -Djava.io.tmpdir=/usr/tmp globally via my /bashrc profile for >> the user I'm running under and root. Verified that was picked up via java >> -version. >> >> Picked up _JAVA_OPTIONS: -Djava.io.tmpdir=/usr/tmp >> java version "1.6.0_35" >> OpenJDK Runtime Environment (IcedTea6 1.13.7) >> (6b35-1.13.7-1ubuntu0.12.04.2) >> OpenJDK 64-Bit Server VM (build 23.25-b01, mixed mode) >> >> Still same behavior. I don't see how anyone has worked through a fresh >> install on Ubuntu at this point. >> >> Thanks, >> K >> >> On Wednesday, April 29, 2015 at 4:03:13 PM UTC-6, Josh Cooper wrote: >>> >>> >>> >>> On Wed, Apr 29, 2015 at 1:10 PM, Kamil Keski <[email protected]> >>> 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 [email protected]. >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/puppet-users/75aa1033-96b8-4a09-9028-447d6e27eb1b%40googlegroups.com >>>> >>>> <https://groups.google.com/d/msgid/puppet-users/75aa1033-96b8-4a09-9028-447d6e27eb1b%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> I agree the error message is anything but useful, and you're not the >>> first to run into it. I think this is the issue you're seeing >>> https://docs.puppetlabs.com/puppetserver/latest/known_issues.html#tmp-directory-mounted-noexec >>> >>> Josh >>> >>> -- >>> Josh Cooper >>> Developer, Puppet Labs >>> >>> *PuppetConf 2015 <http://2015.puppetconf.com/> is coming to Portland, >>> Oregon! Join us October 5-9.* >>> *Register now to take advantage of the Early Adopter discount >>> <https://www.eventbrite.com/e/puppetconf-2015-october-5-9-tickets-13115894995?discount=EarlyAdopter> >>> * >>> *—**save $349!* >>> >> -- >> 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] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/puppet-users/ac8ddeaf-d59d-45d0-a83f-abc031dc12fe%40googlegroups.com >> >> <https://groups.google.com/d/msgid/puppet-users/ac8ddeaf-d59d-45d0-a83f-abc031dc12fe%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/7a2a6caa-b90a-4a29-a56d-e828cc0d9fe7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
