Previous 1 2 3 Next 111 Replies Latest reply: Nov 8, 2015 8:13 PM by onyx4
t.pawelek Level 1 (0 points)

Hey Everyone,


So I upgraded to 10.9, which is great, purchased the new Server, which is great and no matter what I do I can't get it to work. Which is not so great.


Here's the story:


1) Clean install of 10.9 on 2013 mac mini. Multiple times in fact.


2) Install OS > Configure Network (fixed eth ip) > Disable Wifi > Set Hostname > Configure App Store ID > Download Server > Install Server > Enable Caching.


3) Server is not a gateway and is connected directly to the LAN with a fixed IP (via time capsule). External IP confirmed to be the same between Server logs and the clients. Power saving is disabled (mini is on 24/7). Firewall is disabled.


4) Multiple clients running latest OSX / iOS. All using the same Apple ID as the Server. Tried some clients with a different ID from the same region (US) and from a different region (EU).


5) No matter what I do, the only stuff that's being cached is the system updates (itunes / codecs / etc.). Not a single OSX / iOS app is being cached.


6) Tried a variety of .plist changes, increased the log verbosity. No errors in Debug.log: normal registration, etc. But not a single OSX / iOS app is being cached. Downloading apps on clients doesn't do anything (i.e. doesn't spawn a single line of log), even with logging = verbose. Restarting the services doesn't reveal any issues, just a regular registration every single time.


7) Asked Apple for help, they asked for log files and remain silent since then (couple of days now).


I wasted so much time on this already. I'd be really grateful if anyone pointed me in the right direction (other than a wall with a "bang head here" poster).

  • MrHoffman Level 6 (14,832 points)

    Mavericks Caching Server is working as expected here. 


    Caching Server requires a NAT-capable firewall, and the same subnet locally, and outbound access to some Apple IP addresses and ports (beware any nanny filters, et al), and a network configuration that's not partitioning the local traffic nor blocking multicasts or mDNS traffic.   I'm usually running the WiFi devices configured as APs with the Caching Server on the Gigabit "backbone" network, and that's the way the (working) (prototype) Caching Server configuration is set up.


    The Caching Server host should be configured to the same Apple ID across any peer Caching Server hosts, but you're probably not running multiple Caching Servers quite yet.


    I'm also running SUS, but that's a parallel cache.  If you want OS X patches cached, that's the way to go.


    Tweaking with plists seems the wrong direction to me, assuming those files aren't corrupt and a reinstall usually means the files are correct.  See if Ethereal / Wireshark or similar tooks can determine if the hosts can "see" each other  — there's almost certainly a multicast or subnet broadcast or mDNS service being used here somewhere, and I'd confirm that's being propagated.  No, I don't know what the multicast address or mDNS service name is; haven't needed to look at that level of the implementation.

  • raimattern Level 1 (95 points) 0CB0FADCDB


    The Software Update server caches only Mac updates; the Caching server can cache updates and App Store purchases for Mac computers and iOS devices.

  • t.pawelek Level 1 (0 points)

    It is NOT working as expected. It was advertised as a tool that can cache app purchases/updates, too. Not just the OS updates.


    The devices can see each other just fine. I can VNC into the server from all my macs/ipads/etc. Also, iTunes update on all my clients is properly served from the caching server.


    For some reason, apps are excluded from caching.

  • MrHoffman Level 6 (14,832 points)

    Keep digging in your network configuration...




  • t.pawelek Level 1 (0 points)

    I'd love to keep digging. I just don't know where. My home GW is a RouterBoard with quite an advanced configuration, but... this has NOTHING to do with LAN communication. As far as I understand, the only "external" factor that matters for Caching Service is the public IP used by the server and the clients. Which in my case is the same.


    So, leaving Internet apart, my Mac Mini is connected directly to a TC, which works as an AP for all the other devices. There is no network configuration that I am aware of that could come in between them talking to each other. They're all part of the same /24 local network, they're all on the same switch (TC). Mini's firewall is disabled. What else can I look at?

  • DRoush Level 1 (0 points)

    FWIW I'm having same issue on a network at my school. Several clients connected through same switch..same subnet... nothing caching at all.

  • designev Level 1 (10 points)

    We've setup a Caching Server here and it has yet to download any iOS apps. The server has been running for a few days now and multiple iPads have been used to download a whole list of apps/updates. No luck here either.


    Interestingly though when you visit Apple's business page, near the bottom it says Caching Server iOS 7 support is still 'coming soon'. Odd.


  • raimattern Level 1 (95 points)

    Needs no translation ! Just reset Caching and did download some iOS stuff. No miracle.

    Bildschirmfoto 2013-10-28 um 20.05.54.png

  • t.pawelek Level 1 (0 points)

    Are you sure this is an actual app cache? Not just the 7.0.3 update?

  • raimattern Level 1 (95 points)

    ?? 34 MB and 7.0.3 ?? This device had been updated long time ago to 7.0.3.

  • t.pawelek Level 1 (0 points)

    I thought the incremental update was around 50MB. Anyway, that proves that Caching Server works, at least for some. Now, if we could only find out what the reason is it doesn't work for the rest of us...

  • raimattern Level 1 (95 points)

    I guess that your local  iOS devices use a local proxy.

  • t.pawelek Level 1 (0 points)

    They what?


    All of the devices AND the server share the same external IP and DNS configuration. Not sure what kind of proxy you have in mind.

  • designev Level 1 (10 points)

    Same here.. our Mavericks Server and iPads are all fresh out of the box setups.. no custom configurations done that might alter the behavior of the caching server. The server and iPads are all on the same network.

Previous 1 2 3 Next