Q: How can I verify clients are getting updates from the Caching Service?
I just set up a 10.11 Server with Server.app version 5.0.15 to act as a Caching Service server to provide updates to Mac clients (no iOS devices).
I can see that it has downloaded updates from the Stats section when I selected Bytes Served in the drop-down menu at the bottom.
I want to verify that this is working and that clients are getting updates from this sever when in the office.
I've done a lot of searching but have not found something definitive. I've seen suggestions at looking at the /Library/Server/Caching/Logs/Debug.log, but nothing in there can tell me whether or not a client received an update from the Caching Service. It is suggested in the Server Essentials book from PeachPit to look at Activity Monitor to check the network packet in and outtake, but that only shows that the Server has successfully contacted Apple and verified the IP address.
I need to know and verify that this Caching Service is actually working by provided updates to clients on our network. Does anyone know how to do this?
Thanks in advance.
EDIT: I just checked the server again and it only downloaded 226MB of data. I set this up yesterday afternoon. Shouldn't there be a lot more data?
Posted on Mar 9, 2016 8:52 AM
I need to know and verify that this Caching Service is actually working by provided updates to clients on our network. Does anyone know how to do this?
The setting you want is LogClientIdentity.
$ sudo serveradmin stop caching
$ sudo serveradmin settings caching:LogClientIdentity = yes
$ sudo serveradmin start caching
Then the clients' IP addresses will be logged and visible in Server > Logs > Caching Service Log.
As raimattern said, you should leave the LogLevel at default.
$ sudo serveradmin settings caching:LogLevel = default
(Caching does not need to be stopped and restarted when changing this setting.)
The Server app Service log for caching literally has 7 entries
Then most likely caching is not working for you, yet. Try rebooting the clients. When clients find no caching server on a network (as they likely did before you set up your new caching server) they remember that for a while so they don't keep uselessly checking. Rebooting forces a fresh lookup. If rebooting doesn't help please double-check the "Country Restrictions" section of https://support.apple.com/en-us/HT204675 and the public/private network configuration information in https://www.apple.com/support/osxserver/cachingservice/.
Posted on Mar 11, 2016 7:44 AM
