404 Error (Package does not appear on the server) deploying 10.8 upgrade via Self Service

[akurth]

I just finished upgrading my JSS machine to 10.8 server, and upgraded JSS and Casper Suite apps to 8.71. Everything appears to be working as it did before, but when I tried packaging an upgrade to OSX 10.8 to deploy via self service, the policy fails with the following errors:

/usr/sbin/jamf is version 8.71
Executing Policy Install OSX Mountain Lion (10.8)...
[STEP 1 of 6]
Downloading http://172.16.0.105:80/CasperShare/Packages//Install OS X Mountain Lion.dmg...
Verifying DMG...
Error: The package does not appear to be on the server (404).
[STEP 2 of 6]
Creating directory structure for /Library/Application Support/JAMF/Downloads/
Downloading http://172.16.0.105:80/CasperShare/Scripts/install_osx108.sh...
Error running script: The script could not be found on the server..

I thought that perhaps a permissions issue had arisen after the 10.8 upgrade, but attempting to install other packages that existed prior to the upgrade is working fine, and the permissions on the share and on the files in the share appear to be the same. I've verified that the files in question (the DMG and the script) did upload from Casper Admin, and do exist on my server share.

Has anybody run across this type of issue? Any suggestions?

[jhalvorson · Accepted solution]

It is strange there is a difference between pre-upgrade and post-upgrade files. Do you have multiple Distribution Points?

If you copy and past the following address into a web browser, does it download?
http://172.16.0.105:80/CasperShare/Scripts/install_osx108.sh

[mm2270]

Its posible the symlink pointing to your CasperShare got broken during the OS upgrade, though I'm not sure if that would explain how other installs are working and this one isn't , Still, worth a shot to take a look at this kb and give some of these troubleshooting steps a try-
https://jamfnation.jamfsoftware.com/article.html?id=116

[jhalvorson]

Server on 10.7 or 10.8, the web site hosting defaults to the following path: /Library/Server/Web/Data/Sites/Default
(Use the Server app to confirm the path.)

10.6 and prior versions of server, the web site defaulted to the following path
/Library/WebServer/Documents
(The directory above is still included in 10.7 and 10.8 server, it's just not the default.)

In my experience, even with the current JSS 8.71 installer, JAMF assumes or configures DP at the older path. When I create a new DP and enable HTTP, it creates a symbolic link within /Library/WebServer/Documents

For all of my 10.7 and 10.8 DPs, I've had to create the symbolic link to the CasperShare, within /Library/Server/Web/Data/Sites/Default

Browse to either path mentioned above on your server. Does either location have an alias icon to the location of your CasperShare files? Does clicking on it take you to the CasperShare?

[akurth]

The upgrade was from 10.7 to 10.8; that, along with other preexisting packages still working as usual, makes me think that a symlink issue is unlikely. I tried deleting the package and script and adding again via Casper admin, but get the same error. That said, I'll look further into the symlink issue when I'm back in the office later today.

[jhalvorson · Accepted solution]

It is strange there is a difference between pre-upgrade and post-upgrade files. Do you have multiple Distribution Points?

If you copy and past the following address into a web browser, does it download?
http://172.16.0.105:80/CasperShare/Scripts/install_osx108.sh

[mm2270 · Accepted solution]

The existing uploads working and recent one not is also confusing to me, and I'd agree it likely isn't the symlink since that would seem to break any http downloads.

Like jhalvorson I also wondered if you had multiple DPs and if perhaps it wasn't showing up on the one the policy is pointing the Mac to. It sounded from your post that the Mac server is your only JSS and distribution point though.

You could also try to force the policy to use AFP/SMB as a quick test. If it works like that then it most likely has something to do with your http setup.

[akurth]

Definitely an HTTP issue; still haven't solved it, but when I forced AFP/SMB, it worked just fine. Thanks for all your help!

[mm2270]

I don't recall specifically, but I think 10.8 changed the way http and web services gets set up on OS X Server, so its possible ti just disabled something during the upgrade. Sorry I can't offer any specifics as I don't have much experience right now in moving OS X server up to 10.8 to be sure. But I do seem to remember reading that Apple removed or changed some of how that works.

You can try searching around on http://www.afp548.com to see if its documented there.

[bentoms]

What happens if you try the URL in a web browser?

[yan1212]

I had exactly the same issue in a new Casper 8.71 setup on 10.8 server. I had to re-create the symlink from /Library/WebServer/Documents to /Library/Server/Web/Data/Sites/Default and the issue was solved.

[usd210org]

We had this error after upgrading from 10.7 to 10.8 on DP server. To resolve, I had to trash the old symlink located in /Library/Server/Web/Data/Sites/Default. If you look, you can see that it hasn't been modified since your upgrade to 10.8.

After you trash the old symlink, you can run the command in Terminal to re-create it.

sudo ln -s /Shared Items/CasperShare /Library/Server/Web/Data/Sites/Default

[Gavxyz]

Thanks usd210org that fixed it for me.