Hi team,
I have quick query about the precache configuration.
I will run the Precache config on my client machine which contains,
setting “_BESClient_Download_PreCacheStageDiskLimitMB”=“4100” on “{parameter “action issue date” of action}” for client
setting “_BESClient_Download_PreCacheStageEnabled”=“1” on “{parameter “action issue date” of action}” for client
After that Im running some enabled modules to file on client fixlet as recommended by hcl support.
Finally Im running actual baseline which three components,
components1:
import gpg key
enable multiple packahe
components2:
multiple fixlet/patchec
components3:
multiple package installation.
Also while executing the baseline I have enable start the downloads before constraints are met
But the status is showing waiting for long time.
what does waiting means is it downloaded the package and waiting time to implement as i have scheduled time
or it is waiting for the time to download and install on scheduled time
I have checked some servers have some content on cache folder but some servers are empty but all status showing as waiting.
My question why pre caching/downloading is not working.
Also I have read the document from HCL as below,
The multiple-package baseline installation feature does not support the pre-cache option Start download before all constraints are met in Take Action.
Can guide whether the above is correct or wrong. And for some servers got some content under cache and some don’t have.
By default, on a BigFix Client _BESClient_Download_PreCacheStageContinueWhenDiskLimited=0 , which means that a group action can start only after all the sub action downloads are available at the same time on the system.
Additionally you should run the “import gpg key” Fixlet outside of the Baseline.
The download plug-ins that run in the patch fixlets during precaching depend upon trusting the repository. If the GPG keys have not been imported and the yum repo is not trusted, the precaching phase will not be able to resolve dependencies and download the packages. So the GPG key import needs to execute before anything else in the baseline could precache downloads.
The status of ‘Waiting’ usually indicates that it is waiting for the scheduled action start time to arrive. ‘Pending Downloads’ has a distinct status on its own. But you could right-click a computer in the Action status and ‘Show Action Info’ to get more detailed status for each computer.
In which document/link did you see The multiple-package baseline installation feature does not support the pre-cache option Start download before all constraints are met in Take Action. ? I believe precaching should work with multi-package basline.
