Content caching

After reading that High Sierra now offers content caching, I immediately enabled it, waiting for the first AppStore update, which was available to me this morning in the form of the HS Supplemental update. My understanding is that if you have selected one machine on your network, and enabled Content Caching, it would collect the update and then make it available to all the other devices on your network. I chose my iMac as it is permanently connected via ethernet; enabled Content Caching; made sure the options that other Macs would find the update(s) were enabled; rebooted the other and allowed the other Macs to find the caching machine; download and install the updates.


My iMac downloaded the update and applied it. But on the Sharing options, it shows my iMac cached only 3.4MB. Thus the other two Macs eventually downloaded the update individually. Some 915MB per update makes for 2.7GB bandwidth consumed.


My network uses a Time Capsule, DHCP reservations, and all the Macs are connected via ethernet.


What do you think I could have done wrong?

iMac with Retina 5K display, macOS High Sierra (10.13), Late 2015, 4Ghz, 16GB, 500GB SSD

Posted on Oct 5, 2017 8:34 PM

Reply
23 replies
Sort By: 

Oct 6, 2017 1:31 PM in response to woodmeister50

Good, it finds a content cache. Is it the one you expect?


It does not find any configured public IP address ranges. That is normal if you have only one public IP address. Do you use more than one?


Is your public IP address "associated with your iTunes Store region," as specified in Content types that macOS Server caching and macOS caching support, or do any of the other exclusions listed there apply to you?

Reply

Oct 6, 2017 1:54 PM in response to More Broccoli Please

More Broccoli Please wrote:


Good, it finds a content cache. Is it the one you expect?


It does not find any configured public IP address ranges. That is normal if you have only one public IP address. Do you use more than one?


Is your public IP address "associated with your iTunes Store region," as specified in Content types that macOS Server caching and macOS caching support, or do any of the other exclusions listed there apply to you?

Yes, No, and No.


Well, there is more to updates it seems that what Apple advertises.

It appears that after the update, Content Caching seems to be working.

I updated this morning but did not test until a moment ago. Thanks

for the log tips. Someone needs to wrap a GUI around this stuff

like Apple eliminated from Server. Mmmm.....


Anyway, I digress. went through my purchases to fin something I had

previously deleted from my Macs (replaced by a better non-app store version).

On the server, started log streaming per the command you gave (thanks again).

On Mac 1, downloaded the app from the Mac App Store. The log started

spewing a stream of stuff and sorting through it received a request cached it

and served it. On status it correctly showed additional cache used and that it stored

and served.


Then the acid test on Mac 2. Proceeded to do the same. Again log spewed, indicating

a request was received and based on the log was served from cache!!! The status function

also backed it up, not showing any additional stored from origin but showed the additional

returned to clients.


So it does seem that Apple slipped more into the Supplemental Update than stated

(pretty much had to with 1GB download size). This did not work at all previously.


So, so far so good, Will monitor closely (and maybe think about how much work it

would be to wrap something more user friendly around all this, like it used to be).

Reply

Oct 5, 2017 8:56 PM in response to andrieso

What do you think I could have done wrong?


From what you describe, absolutely nothing.


For what it's worth I haven't observed any obvious results either, and I am wondering if it even works yet. Did you investigate the Advanced Options in Sharing?


What is the AssetCache process doing in Activity Monitor? Anything?

Reply

Oct 5, 2017 9:29 PM in response to John Galt

John


Many thanks for the quick answer. I had a good look at the Advanced Options and everything seems correct, given the Parent/Child relationship used. Asset Cache seems to be rather quiet, with no unusual activity. I just noticed now that storage used in Content Caching has gone up to 9.1MB, and at the same time my iPhone 6 shows that there are three app updates available from the AppStore, two being Netflix and WhatsApp. But these updates are typical much larger than about 5MB, so the extra space used for caching content cannot be the updates for the three apps.


Anyway, since I am sure many of us will want to save bandwidth, Content Caching can be important - updating thee Macs to High Sierra and four iPhones to iOS 11 put quite a dent in my available bandwidth. While my broadband connection is fast and stable, I only have a fixed amount for the 30 day period and topping up is expensive - that is how ISPs make their money.

Reply

Oct 6, 2017 5:26 AM in response to andrieso

Content Caching is a joke and simply does not work!


I have 4 Macs, all associated with the same Apple ID on the

same network, all app and Apple update requests made from

the Mac App Store with the same Apple ID are completely and

totally ignored! No change in the amount of cache size, all Macs

continue to download directly from the app store.


Another useless or broken feature!

Reply

Oct 6, 2017 5:39 AM in response to woodmeister50

Woodmeister50


Ouch, I was so hoping that I did something stupid, but like you, I have a number of devices all using the same Apple ID and for me Content Caching would have been great, if it worked. I seldom complain about Apple's products, but when I followed the instructions for setting up content caching this morning, there were just too many holes in the process and I doubted if it would work. Your experience confirmed it.


If anyone else has any luck, kindly share this with us.

Reply

Oct 6, 2017 7:07 AM in response to andrieso

What do you mean by "holes in the process"? For most folks the instructions are: turn it on, and restart any devices you expect to use it immediately. (If you don't restart them, they will eventually discover the new content cache but not right away.) The AssetCacheLocatorUtil command can help troubleshoot content caching issues. You only need advanced settings if your network is complex or uses multiple public IP addresses.

Reply

Oct 6, 2017 7:30 AM in response to More Broccoli Please

More Broccoli Please


I used what I would consider to be default settings, just as Apple recommends. There is one option where on the clients you can supply the IP address for the parent in the settings for the remote computer's Parent settings. Since my Time Capsule manages a range of DHCP reservations, I figured it should be quit simple. I also restarted all the services.


Anyway, no harm done, it gives me something to do to try and figure it out. Running AssetCacheLocatorUtil gave a long list of results, but the last two seem to be meaningful:


2017-10-06 18:27:40.235 AssetCacheLocatorUtil[1208:374970] Testing all found servers for reachability...

2017-10-06 18:27:40.245 AssetCacheLocatorUtil[1208:374970] This computer is able to reach all of the above caching servers.

Reply

Oct 6, 2017 8:41 AM in response to andrieso

The parents feature is for complex networks with multiple content caches. A child content cache downloads from its parent content cache(s) instead of directly from Apple. If you have only one content cache, or more than one but they're on the same subnet, you should not specify any parents.


Posting that long list of results would have been helpful. Did it report the content cache(s) you expect?

Reply

Oct 6, 2017 8:53 AM in response to John Galt

John Galt wrote:


What do you think I could have done wrong?


From what you describe, absolutely nothing.


For what it's worth I haven't observed any obvious results either, and I am wondering if it even works yet. Did you investigate the Advanced Options in Sharing?


What is the AssetCache process doing in Activity Monitor? Anything?

FWIW, I had run the command line:

AssetCacheManagerUtil status


on the Mac I chose as "the server" and it show zero, zilch, nada,

nothing in terms of any activity whatsoever even though on multiple

Macs I downloaded apps as well as Apple updates?


The only thing that wasn't zero was cache allocated, oh, and the date.


It is totally useless!

Reply

Oct 6, 2017 12:47 PM in response to More Broccoli Please

More Broccoli Please wrote:


Does your disk have at least a few GB of free space? Content caching doesn't do much on a nearly-full disk.


....

I would thing setting a cache size of 150 GB on a 500GB disk that has nothing

else on it would suffice.


More Broccoli Please wrote:

...


Also, what does AssetCacheLocatorUtil report? Complaining might feel good, but we can't help you without data.

All it has is zeroes, zeroes, and more zeroes as previously stated.


It was all good until it was decided to yank it from the Server app.

Can't even easily get logs now, just a summary. When it was part of the

server app, you just opened the service log to see what happened or didn't.

As it is now, there isn't (at least easy ) way to have a clue as to trace what may

be happening (or not).

Reply

Oct 6, 2017 12:55 PM in response to woodmeister50

As its man page states, "AssetCache logs to the os_log(3) subsystem com.apple.AssetCache." Read the man pages for os_log and the log command. You can use log show --predicate 'subsystem == "com.apple.AssetCache"' to show past log messages and log stream --predicate 'subsystem == "com.apple.AssetCache"' to monitor new ones.


You seem to be running AssetCacheManagerUtil status, not AssetCacheLocatorUtil. Run AssetCacheLocatorUtil on a Mac that is not using your content cache (not on the Mac where content caching is running), and examine the results. Posting the results here will let us help you.

Reply

Oct 6, 2017 1:21 PM in response to More Broccoli Please

More Broccoli Please wrote:

......Run AssetCacheLocatorUtil on a Mac that is not using your content cache (not on the Mac where content caching is running), and examine the results. Posting the results here will let us help you.

here it is FWIW and BTW, haven't checked function after the supplemental update,

though it was not specifically addressed but at almost 1GB....:

2017-10-06 16:09:49.779 AssetCacheLocatorUtil[1462:643150] AssetCacheLocatorUtil version 71, framework version 71

2017-10-06 16:09:49.780 AssetCacheLocatorUtil[1462:643150] Determining public IP address...

2017-10-06 16:09:50.502 AssetCacheLocatorUtil[1462:643150] This computer's public IP address is xxx.xx.xx.xx.

2017-10-06 16:09:50.502 AssetCacheLocatorUtil[1462:643150] --- Information for system services:

2017-10-06 16:09:50.502 AssetCacheLocatorUtil[1462:643150] Checking whether there might be caching server(s) available...

2017-10-06 16:09:50.503 AssetCacheLocatorUtil[1462:643150] There might be caching server(s) available.

2017-10-06 16:09:50.503 AssetCacheLocatorUtil[1462:643150] Finding saved servers supporting personal caching...

2017-10-06 16:09:50.504 AssetCacheLocatorUtil[1462:643150] There is no saved result. (This is not an error.)

2017-10-06 16:09:50.504 AssetCacheLocatorUtil[1462:643150] Finding saved servers supporting personal caching and import...

2017-10-06 16:09:50.505 AssetCacheLocatorUtil[1462:643150] There is no saved result. (This is not an error.)

2017-10-06 16:09:50.505 AssetCacheLocatorUtil[1462:643150] Finding saved servers supporting shared caching...

2017-10-06 16:09:50.505 AssetCacheLocatorUtil[1462:643150] There is no saved result. (This is not an error.)

2017-10-06 16:09:50.505 AssetCacheLocatorUtil[1462:643150] Finding refreshed servers supporting personal caching...

2017-10-06 16:09:50.768 AssetCacheLocatorUtil[1462:643150] Found 1 server

2017-10-06 16:09:50.768 AssetCacheLocatorUtil[1462:643150] Finding refreshed servers supporting personal caching and import...

2017-10-06 16:09:50.769 AssetCacheLocatorUtil[1462:643150] Found 1 server

2017-10-06 16:09:50.769 AssetCacheLocatorUtil[1462:643150] Finding refreshed servers supporting shared caching...

2017-10-06 16:09:50.770 AssetCacheLocatorUtil[1462:643150] Found 1 server

2017-10-06 16:09:50.770 AssetCacheLocatorUtil[1462:643150] xxx.xxx.x.x:xxxx, rank 3, guid xxxxxx, valid until 2017-10-06 17:09:50; supports personal caching: yes, and import: yes, shared caching: yes

2017-10-06 16:09:50.770 AssetCacheLocatorUtil[1462:643150] Determining configured public IP address ranges...

2017-10-06 16:09:50.770 AssetCacheLocatorUtil[1462:643150] No public IP address ranges are configured.

2017-10-06 16:09:50.770 AssetCacheLocatorUtil[1462:643150] --- Information for user 502 (results for other users may be different):

2017-10-06 16:09:50.770 AssetCacheLocatorUtil[1462:643150] Checking whether there might be caching server(s) available...

2017-10-06 16:09:50.770 AssetCacheLocatorUtil[1462:643150] There might be caching server(s) available.

2017-10-06 16:09:50.770 AssetCacheLocatorUtil[1462:643150] Finding saved servers supporting personal caching...

2017-10-06 16:09:50.771 AssetCacheLocatorUtil[1462:643150] There is no saved result. (This is not an error.)

2017-10-06 16:09:50.771 AssetCacheLocatorUtil[1462:643150] Finding saved servers supporting personal caching and import...

2017-10-06 16:09:50.771 AssetCacheLocatorUtil[1462:643150] There is no saved result. (This is not an error.)

2017-10-06 16:09:50.771 AssetCacheLocatorUtil[1462:643150] Finding saved servers supporting shared caching...

2017-10-06 16:09:50.771 AssetCacheLocatorUtil[1462:643150] There is no saved result. (This is not an error.)

2017-10-06 16:09:50.772 AssetCacheLocatorUtil[1462:643150] Finding refreshed servers supporting personal caching...

2017-10-06 16:09:50.970 AssetCacheLocatorUtil[1462:643150] Found 1 server

2017-10-06 16:09:50.970 AssetCacheLocatorUtil[1462:643150] Finding refreshed servers supporting personal caching and import...

2017-10-06 16:09:50.971 AssetCacheLocatorUtil[1462:643150] Found 1 server

2017-10-06 16:09:50.971 AssetCacheLocatorUtil[1462:643150] Finding refreshed servers supporting shared caching...

2017-10-06 16:09:50.971 AssetCacheLocatorUtil[1462:643150] Found 1 server

2017-10-06 16:09:50.971 AssetCacheLocatorUtil[1462:643150] xxx.xxx.x.x:xxxxx, rank 3, guid xxxxx..., valid until 2017-10-06 17:09:50; supports personal caching: yes, and import: yes, shared caching: yes

2017-10-06 16:09:50.971 AssetCacheLocatorUtil[1462:643150] Determining configured public IP address ranges...

2017-10-06 16:09:50.972 AssetCacheLocatorUtil[1462:643150] No public IP address ranges are configured.

2017-10-06 16:09:50.972 AssetCacheLocatorUtil[1462:643150] Testing all found servers for reachability...

2017-10-06 16:09:50.992 AssetCacheLocatorUtil[1462:643150] This computer is able to reach all of the above caching servers.

Reply

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Content caching

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.