BFI VM Manager uploads stuck in /Temp

Usage and Config BFI
1

Hi, in BigFix Inventory, I’m seeing the schedule uploads of the VM Manager tool results being uploaded to the BES root server but they are getting stuck in Program Files (x86)\BigFix Enterprise\BES Server\UploadManagerData\BufferDir\Temp (each upload is 22MB each) and don’t seem to make it to Program Files (x86)\BigFix Enterprise\BES Server\UploadManagerData\BufferDir\sha1\24\894924

Any ideas?

_BESClient_ArchiveManager_FileSet-citsearch=D%3a%5cProgram%20Files%20%28x86%29%5cBigFix%20Enterprise%5cBES%20Client%5cLMT%5cCIT%5c894924_cit.xml.bz2
_BESClient_ArchiveManager_FileSet-cit_capacity=D%3a%5cProgram%20Files%20%28x86%29%5cBigFix%20Enterprise%5cBES%20Client%5cLMT%5cCIT%5c894924_tlm_hw.zip
_BESClient_ArchiveManager_FileSet-isotagsearch=D%3a%5cProgram%20Files%20%28x86%29%5cBigFix%20Enterprise%5cBES%20Client%5cLMT%5cCIT%5c894924_isotag.zip
_BESClient_ArchiveManager_FileSet-itsitsearch=D%3a%5cProgram%20Files%20%28x86%29%5cBigFix%20Enterprise%5cBES%20Client%5cLMT%5cCIT%5c894924.xml.bz2
_BESClient_ArchiveManager_FileSet-itsitsearchdelta=D%3a%5cProgram%20Files%20%28x86%29%5cBigFix%20Enterprise%5cBES%20Client%5cLMT%5cCIT%5c894924_deltafs.zip
_BESClient_ArchiveManager_FileSet-slmtagsearch=D%3a%5cProgram%20Files%20%28x86%29%5cBigFix%20Enterprise%5cBES%20Client%5cLMT%5cCIT%5cslmUploadDir%5c%2a
_BESClient_ArchiveManager_FileSet-vmman_scan_0=D%3a%5cProgram%20Files%20%28x86%29%5cBigFix%20Enterprise%5cBES%20Client%5cLMT%5cVMMAN%5c894924_0_vmman.zip
_BESClient_ArchiveManager_FileSet-vmman_scan_1=D%3a%5cProgram%20Files%20%28x86%29%5cBigFix%20Enterprise%5cBES%20Client%5cLMT%5cVMMAN%5c894924_1_vmman.zip
_BESClient_ArchiveManager_FileSet-vmman_scan_2=D%3a%5cProgram%20Files%20%28x86%29%5cBigFix%20Enterprise%5cBES%20Client%5cLMT%5cVMMAN%5c894924_2_vmman.zip
_BESClient_ArchiveManager_FileSet-vmman_scan_3=D%3a%5cProgram%20Files%20%28x86%29%5cBigFix%20Enterprise%5cBES%20Client%5cLMT%5cVMMAN%5c894924_3_vmman.zip
_BESClient_ArchiveManager_FileSet-vmman_scan_4=D%3a%5cProgram%20Files%20%28x86%29%5cBigFix%20Enterprise%5cBES%20Client%5cLMT%5cVMMAN%5c894924_4_vmman.zip
_BESClient_ArchiveManager_FileSet-vmman_scan_5=D%3a%5cProgram%20Files%20%28x86%29%5cBigFix%20Enterprise%5cBES%20Client%5cLMT%5cVMMAN%5c894924_5_vmman.zip
_BESClient_ArchiveManager_FileSet-vmman_scan_6=D%3a%5cProgram%20Files%20%28x86%29%5cBigFix%20Enterprise%5cBES%20Client%5cLMT%5cVMMAN%5c894924_6_vmman.zip
_BESClient_ArchiveManager_FileSet-vmman_scan_7=D%3a%5cProgram%20Files%20%28x86%29%5cBigFix%20Enterprise%5cBES%20Client%5cLMT%5cVMMAN%5c894924_7_vmman.zip
_BESClient_ArchiveManager_FileSet-vmman_scan_8=D%3a%5cProgram%20Files%20%28x86%29%5cBigFix%20Enterprise%5cBES%20Client%5cLMT%5cVMMAN%5c894924_8_vmman.zip
_BESClient_ArchiveManager_FileSet-vmman_scan_9=D%3a%5cProgram%20Files%20%28x86%29%5cBigFix%20Enterprise%5cBES%20Client%5cLMT%5cVMMAN%5c894924_9_vmman.zip
_BESClient_ArchiveManager_LastArchive=eebee4c4648cced39b09852ce4c1b1d856a15786
_BESClient_ArchiveManager_MaxArchiveSize=450000000
_BESClient_ArchiveManager_OperatingMode=0
2

Check if MaxArchiveSize is exceeded on this endpoint, you can see that in software scan status analysis

3

The issue isn’t with the software scan uploads but rather the VM Manager tool uploads. MaxArchiveSize is set to 450MB which should be plenty.

4

Right, but that analysis check for MaxArchiveSize exceeded, hence you can use it to troubleshoot VM tool upload as well.

5

“is Archive Size exceeded?” property value = FALSE.

6

You should also chek the _BESRelay_UploadManager_BufferDirectoryMaxSize in the relay chain that connects your VMManager with the BigFix server… if this is exceeded (including the server…) the transfer will be on hold.

7

Since the VM Manager Tool lives on the BES root server, there are no Relays in play.

Looking at the client settings of the Root server, “_BESRelay_UploadManager_BufferDirectoryMaxSize” does not exist so there is no default value enforced.

8

Ok…I didn’t look at the issue description as I should… from what you said, files made the server’s bufferdir, just they were not managed from the server and moved into their correct location.
Which BigFix version are you running?

9

Running BFI 9.2.13.0 / BigFix 9.5.9

10

This is a server’s process issue…BFI is not involved (yet) … are all server processes running, including the server plugin? any warning fixlets relevant in the console?

11

True. I’m 99% sure that server plugins are not needed for the Upload Manager to work. No warning fixlets for the Root server having to do with Upload Manager full or anything.
If anyone from IBM can comment on the server side processing that happens when files in the/TEMP folder are processed, that would be helpful.

12

Did you look at the server log for any messages that could be related?

13

looks like setting “_BESRelay_UploadManager_CompressedFileMaxSize” on the root server solved the problem

2 Likes