Issue with createOSXinstallPkg installing 10.9

Kevin
Contributor II

I have been using Greg Neagle's createOSXinstallPkg to deploy 10.8 for the past year or so.

I downloaded the updated files (createOSXinstallPkg ) for 10.9 and built the first package today. I cached it to a test system a few minutes ago and ran a policy to "install all cached policies" just like I have done with 10.8.

I get the following error when the policy runs:
An error occurred executing the policy "Install Mavericks" on the computer "FAxxxx68".

Event log from the policy:

/usr/sbin/jamf is version 8.73 Executing Policy Install Mavericks... [STEP 1 of 3] Mounting afp://xxxxx/CasperShare to /Volumes/CasperShare... [STEP 2 of 3] Installing tmp Scripts.dmg... Closing package... [STEP 3 of 3] Installing InstallOSX_10.9_13A603_custom.pkg... Installation failed. The installer reported: dyld: DYLD_ environment variables being ignored because main executable (/System/Library/PrivateFrameworks/Install.framework/Resources/runner) is setuid or setgid
installer: Package name is OS X
installer: Installing at base path /
installer: The install failed (The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance.) Unmounting file server... Creating Reboot Script...

You can access the full details of this log at:
xxxxxxx…

Has anyone else seen this type of error when trying to run a package built with this tool?

1 ACCEPTED SOLUTION

Kevin
Contributor II

OK, this turned out to be a problem - but only on one specific computer. On a couple of other test boxes, it ran fine. I believe the createOSXinstallPkg software and my process are fine. I will look at my test box to see what blew up…

View solution in original post

12 REPLIES 12

bentoms
Release Candidate Programs Tester

It looks like you're trying to install off the network.

Can you cache it locally & then install from cached?

Kevin
Contributor II

It was cached.

bentoms
Release Candidate Programs Tester

But were you installing from cached?

Else it'll try & install from the network.

Kevin
Contributor II

The policy installs cached packages only- same as I did with 10.8.

bentoms
Release Candidate Programs Tester

Fair enough. Sadly that's all I've got. Hopefully someone else can assist.

bentoms
Release Candidate Programs Tester

Fair enough. Sadly that's all I've got. Hopefully someone else can assist.

lionelgruenberg
New Contributor III

I was running into all kinds of errors with my 10.9 upgrade policy using a package I created using createOSXinstallPkg.

My quick fix work around installs a script I packaged up & deployed into the "/Library/Application Support/JAMF/Waiting Room" which I'll later call from a Self Service policy to install my cached 10.9 package.
Script:

#!/bin/sh
sudo installer -pkg /Library/Application Support/JAMF/Waiting Room/10.9.pkg -target /
sudo jamf recon
sudo shutdown -r now

My Self Service 10.9 Upgrade policy: Run Command: ```
sudo /Library/Application Support/JAMF/Waiting Room/10.9_install.sh
```
I've scoped this policy using a smart group to clients which have installed my 10.9 installer script package and have cached our 10.9 upgrade package.

Best of luck!

ImAMacGuy
Valued Contributor II

so is createosxinstallpkg updated to work with 10.9? We never really had good luck with it, pristine machines (lab machines I imaged to an old os to try the upgrade) worked fine, but in production it was nearly a 90% failure rate with crashing to the multi-language screen of death.

Kevin
Contributor II

Maybe I did not provide enough information…
Here is my workflow:
(JSS Version 8.73)

I create a 10.9 pkg using the updated version (10/07/2013) of createosxinstallpkg from Greg Neagle.

I upload that pkg to my JSS using Casper Admin.

I scope computers capable of running Mavericks (smart group from an extension attribute that checks hardware) to a policy that caches that package to the /Library/Application Support/ JAMF/ Waiting Room/ folder.

Using an extension attribute that checks for the presence of "InstallOSX_10.9_13A603_custom.pkg" in the waiting room folder, I create a smart group with a policy scoped to it that "Installs all cached packages" and make it available in Self Service.

When that policy is run, I get the "dyld: DYLD_ environment variables being ignored because main executable (/System/Library/PrivateFrameworks/Install.framework/Resources/runner) is setuid or setgid" error.

martin
Contributor III

Hi Kevin,

To make sure this is related to Casper Suite. What happens when you run the "InstallOSX_10.9_13A603_custom.pkg" manually?

Martin

lionelgruenberg
New Contributor III

@jwojda][/url Yes, createOSXinstallPkg released on 10/8/13 supports Mavericks.
https://code.google.com/p/munki/downloads/detail?name=createOSXinstallPkg_20131007.zip&can=2&q=

Haven't run into any issues in my tests or with faculty who have upgraded before the rest of the pack using a Self Service policy. No multi-language screens of death/crashing during any 10.9 upgrades in our environment so far (crossing my fingers).
-Lionel

Kevin
Contributor II

OK, this turned out to be a problem - but only on one specific computer. On a couple of other test boxes, it ran fine. I believe the createOSXinstallPkg software and my process are fine. I will look at my test box to see what blew up…