CentOS 6.2 distribution point sees .pkg files as directories

dmcmillen
New Contributor II

I've got SMB uploads via Casper Admin working, but my .pkg files are being seen by Apache as directories, thus causing the following errors:

Here is the Casper Remote error:

Sending Wake On LAN command...
Opening SSH Connection to 10.11.0.166...
Authenticating...
Successfully authenticated.
Verifying Computer's Identity...
The MAC Address has been verified.
Checking Operating System Version...
Running Mac OS X 10.6.8 (10K549)
Verifying /usr/sbin/jamf...
/usr/sbin/jamf is current (8.52)
Verifying /usr/sbin/jamfvnc...
/usr/sbin/jamfvnc does not exist.
Verifying /Library/Preferences/com.jamfsoftware.jamf.plist...
Preparing Policy...
Installing Absolute Manage Agent Uninstaller.pkg...
Installation failed. The installer reported: installer: Error the package path specified was invalid: '/Library/Application Support/JAMF/Downloads/Absolute Manage Agent Uninstaller.pkg'.
Submitting log to https://our.jss:8443//...
Finished.

And the policy error:

/usr/sbin/jamf is version 8.52
Executing Policy Remove Absolute Manage...
Downloading BOM for Absolute Manage Agent Uninstaller.pkg...
This Apple Package did not have a valid index.bom file. Assuming it is a flat file package.
Downloading https://our.jss:443//Packages//Absolute Manage Agent Uninstaller.pkg...
Installing Absolute Manage Agent Uninstaller.pkg...
Installation failed. The installer reported: installer: Error the package path specified was invalid: '/Library/Application Support/JAMF/Downloads/Absolute Manage Agent Uninstaller.pkg'.

Adding the following to /etc/mime.types does not seem to work:

application/octet-stream bin lha lzh exe class so dll img iso pkg mpkg

application/vnd.apple.installer+xml dist distz pkg mpkg

Nor does adding the following to /etc/httpd/conf/httpd.conf :

AddType application/vnd.apple.installer+xml .dist .distz .pkg .mpkg

AddType application/octet-stream .pkg .mpkg

Any help would be appreciated!

5 REPLIES 5

rockpapergoat
Contributor III

i believe apache will always see them as folders, since they are. be sure to build an index.bom file for each bundle pkg and try again. casper admin should do that by default, no?

if not, you can run: mkbom /path/to/pkg /path/to/pkg/index.bom

jamf binary will download the files present in the .bom like an index. it uses curl under the hood. if it used wget, it could recursively download the folder/bundle structure, but wget doesn't ship with os x. jamf should bundle it…

dmcmillen
New Contributor II

Thanks for the tip. Unfortunately, both packages I've tested have valid boms and both install just fine when run manually -- so I don't think that's the solution. One of them was even created using Composer.

Kumarasinghe
Valued Contributor

Try adding .bom and .* to mime types.

These are my additional MIME types I used for Windows 2008;

   * Set ".dmg" with a MIME type of "file/download"
   * Set ".pkg" with a MIME type of "application/octet-stream"
   * Set ".mpkg" with a MIME type of "application/vnd.apple.installer+xml"
   * Set ".bom" with a MIME type of "file/download"
   * Set ".*" with a MIME type of "file/download"

dmcmillen
New Contributor II

Thanks for the tip Kumarasinghe... unfortunately those changes didn't work either. I am wondering if there is a deeper problem with my Apache install, although all other types of payloads (dmg, scripts, etc.) work fine.

rockpapergoat
Contributor III

try using a policy to cache a pkg bundle on a client, then check out whether the bundle's really intact under /Library/Application Support/JAMF/Downloads.

i've had similar problems with http and afp downloads, so i don't think it's specific to your setup. it may be some other bug.