Is there a way to capture the “relay chain” (the root server to client list of relays) used to download a payload to a client?
I am trying to download a large (2.6GB file) and it never downloads to some of the clients, and it only downloads 1.9GB of the 2.6GB file on another machine. I’m trying to determine if I’m missing a relay in the chain, and a setting on that relay might be causing this issue.
Thanks,
BobK
You probably have a problem in that your cache sizes are too small at the client or its upstream relays. See https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli%20Endpoint%20Manager/page/Configuration%20Settings and post a new thread if you need more help with it.
There’s a couple of dashboards in BigFix Labs that could help here:
One that allows you see the caches and contents on relays and another that shows the relay hierarchy.
Don’t have the exact details to hand but I can dig them out if you’re OK using Labs.
You could also be hitting a case where the client stops doing things when its about to run out of disk storage. By default this is when its drive/volume reaches a minimum free of 20MB
You can create an analysis to check the settings on the relays and make sure they are correct.
Like this: https://bigfix.me/analysis/details/2994717
You can also check the hard drive space on the relays and clients, like this:
On your clients, make sure you have an appropriate value for this setting. We increase it to 4GB in our environment.
"_BESClient_Download_PreCacheStageDiskLimitMB"="4096"
On upstream Relays, set this value (16GB in this example):
"_BESGather_Download_CacheLimitMB"="16384"
Also check the hard drive space on both relays and clients as @jgstew suggests.