Configuration settings for large file downloads

Usage and Config
1

I’m trying to get BigFix to handle downloading the Solaris Critical Patch Update to a Server that has just had the OS upgraded. The size of the Critical Patch Update is about 2.6GB, and it seems that the file is getting cut off at about 2GB.

I made the following changes on the target machine as well as the relay that the download will be coming through. The original source of this download is Oracle.

_BESClient_Download_NormalStageDiskLimitMB             20000
_BESClient_Download_PreCacheStageDiskLimitMB         20000

After I let these setting take place, the problem is still occurring. Does this change need to be made on the root server as well, or is there some other setting that I am missing?

Root and Relay Servers are Linux based, and the client is Solaris.

Thanks for any help you can offer.

BobK

2

Those settings are effective on the client. For the Relay and Root Server you need to set

__BESGather_Download_CacheLimitMB

See https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli%20Endpoint%20Manager/page/Configuration%20Settings

3

JasonWalker

I tried that, still stopping at 1.9GB (2009876375 bytes)

Getting the following error:

At 15:10:23 -0600 - 
   ActionLogMessage: (action:50728) JobFailed - cancel and fail action
At 15:10:25 -0600 - 
   ActionLogMessage: (action:50728) DownloadJobFailed
At 15:10:47 -0600 - 
   ActionLogMessage: (action:50728) ending action

BobK

4

Did you check your limit on the main server for the Download_CacheLimitMB setting also?

5

The _BESGather_Download_CacheLimitMB is only for relays and root servers. On the root server, it should be set to at least 300000. See here: https://bigfix.me/fixlet/details/6324

Related:

See this example clientsettings.cfg file I use for most clients: https://gist.github.com/jgstew/51a99ab4b5997efa0318

6

Here is the BES Relay Cache Information from the root server:

BES Relay Cache Size 300000 MB
BES Relay Drive Info /repository - 87190 MB free
BES Relay Used Action Cache 32 MB
BES Relay Used Download Cache 2610 MB

If the /repository free space is 87,190 MB and total space is 100,611 MB, is this OK?

Thanks,
BobK

7

Is this the free space on the drive itself?

Is this the total space on the drive itself?

Over 80GB should be plenty for a relay for things to function, though I’m not sure what happens if the Relay Cache size is set to be larger than the actual hard drives total size. That seems like it could be an issue, but it doesn’t appear to be one yet in this case.

8

Is the 300000 coming from the Configuration Setting: _BESGather_Download_CacheLimitMB?

Thanks,
BobK

9

It should be, yes. You can look at the analysis property relevance to see where it is reading it from.

10

Any issues with a proxy or the download actually timing out?

Verify the file manually. Download in a browser, run the “sha1.exe” tool against it, and verify the size and sha1 match what the fixlet expects. You might find that the file has been modified and the Fixlet is not up to date with the actual download, or that your proxy or something else in your infrastructure is preventing the download from completing.

Try manually precaching the file - if you successfully download it, and the size and sha1 match the Fixlet, then rename the file to match the sha1 value and store it at wwwrootbes/bfmirror/downloads/sha1

1 Like