10.7.2 client not seeing 10.7.3 on Internal SUS

[ericbenfer]

Our internal SUS has downloaded all the 10.7.3 updates.

We use a Casper Policy to set the SUS on all the clients.
They all end up with this address:
http://asus.ourdomain.edu:8088/index.sucatalog

Problem is none of the 10.7.x Macs see the 10.7.3 updates.
If I browse to that address in Safari there is no 10.7.3 anything in the index.

It works if I point the Macs to:
http://asus.ourdomain.edu:8088/index-lion-snowleopard-leopard.merged-1.sucatalog
They can see the 10.7.3 updates.

I thought http://asus.ourdomain.edu:8088/index.sucatalog was supposed to be a universal address for all versions of OS X.
Casper is creating the server address automatically based on the name of the server.

Thoughts?

[abz_mungul]

do you have a catalogs.sucatalog file

so try browse to
http://asus.ourdomain.edu:8088/catalogs.sucatalog

does that work?

I'm currently in the process of setting up asus in each of our offices an running through teething problems. also try running a software update on your asus i found that fixed some of my problems

[ericbenfer]

I do have a catalogs.sucatalog
It is the CatalogsList.

################################
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict> <key>CatalogsList</key> <array> <string>http://asus.ourdomain.edu:8088/content/catalogs/index.sucatalog</string> <string>http://asus.ourdomain.edu:8088/content/catalogs/others/index-leopard.merged-1.sucatalog</string> <string>http://asus.ourdomain.edu:8088/content/catalogs/others/index-leopard-snowleopard.merged-1.sucatalog</string> <string>http://asus.ourdomain.edu:8088/content/catalogs/others/index-lion-snowleopard-leopard.merged-1.sucatalog</string> </array> <key>PrimaryCatalog</key> <string>http://asus.ourdomain.edu:8088/content/catalogs/index.sucatalog</string>
</dict>
</plist>
######################

Note the PrimaryCatalog.

http://asus.ourdomain.edu:8088/index.sucatalog is a symlink to http://asus.ourdomain.edu:8088/content/catalogs/index.sucatalog

In the end I think the problem is http://asus.ourdomain.edu:8088/index.sucatalog does not list the 10.7.3 updates.
Why does the Primary Catalog not have this?

[andyinindy]

I can verify that our managed Lion machines are not seeing the 10.7.3 update either.

In the swupd logs on my sus I see the following error:

NSURLErrorDomain error -3001

So this doesn't seem to be caused by Casper. I will check Apple's discussion boards to see if others have found a fix/workaround.

[update]

Found a thread with others having the same issue:

https://discussions.apple.com/thread/3501282?start=0&tstart=0

No resolution, but it's a start.

--Andy

[bentoms]

For any updates you're having the "NSURLErrorDomain error -3001" delete whatever exists for them in /var/db/swupd/ (or wherever your updates are located), then re-sync.

[andyinindy]

I figured it out. My SUS' storage is on the same disk as my Casper repository. I have had to propagate permissions several times to correct issues with packages refusing to install. I guess that this screwed up the permissions on my SUS folders such that swupd was unable to write to them. I created a new SUS folder via server admin and bounced the service, and SUS updates are downloading without any issues.

[ericbenfer]

Well for now I am setting SUS on all of our Macs (10.5.x, 10.6.x and 10.7.x) to this address
http://asus.ourdomain.edu:8088/index-lion-snowleopard-leopard.merged-1.sucatalog

Is anyone else having this problem?

[bentoms]

Index.sucatalog works for me.

Are you seeing any errors in the logs?

[nessts]

I have found that unless the Mac is on the same subnet the short URL does not work and the longer version as you just used is what we have needed to use.

[ericbenfer]

Yeah our SUS server is on a different subnet/vlan.

[taugust04]

I had some issues with this as well. I did a total reset of SUS, and still had problems. Turns out the 'shortened' catalog URL was not working properly. I ended up creating a managed system preference on the JSS to point to the longer Lion specific catalog URL for Lion clients, and the longer Snow Leopard specific catalog URL for Snow Leopard clients. After rebooting the Lion clients (to receive the updated managed preferences from the JSS) they started seeing the 10.7.3 updates.

~Ted