Archive now file not getting to bigfix server

Usage and Config Platform
1

ENV: Bigfix 10.0.9 running on Windows, with all Windows relays
I have
archive now
files that remain on the endpoint, and never get uploaded to the BigFix server.
I checked Index.txt and there are no errors. The files I’m referring to were created on Nov 17, 2024. Here is what I see on the ep, relay and server

---------------------------- From ep:
20241117.log:
At 17:09:27 -0500 - mailboxsite (http://wvdbsp00404.bns.bns:52311/cgi-bin/bfgather.exe/mailboxsite1074281008)
Not Relevant - Force VM Manager Tool Scan Results Upload (9.2.37.0) (fixlet:1177190)
At 17:09:28 -0500 -
[ThreadTime:17:09:28] Starting upload of file ‘b6fa2caaa92fb2bffb3b71d9529aaf37e77211fed78652fd21ac47b206d19f1c’ of size 199430
At 17:09:29 -0500 -
[ThreadTime:17:09:28] Successfully uploaded file ‘c:\Program Files (x86)\BigFix Enterprise\BES Client__BESData__Global\Upload\sha256\b6fa2caaa92fb2bffb3b71d9529aaf37e77211fed78652fd21ac47b206d19f1c’
At 17:10:03 -0500 -
Report posted successfully

C:\Program Files (x86)\BigFix Enterprise\BES Client__BESData__Global\Archive\Last>dir /o:-d
Volume in drive C has no label.
Volume Serial Number is 6E21-3931

Directory of C:\Program Files (x86)\BigFix Enterprise\BES Client__BESData__Global\Archive\Last

11/17/2024 05:09 PM …
11/17/2024 05:09 PM .
11/17/2024 05:09 PM 10,737 Index.txt
11/17/2024 05:09 PM 252,254 vmman_scan_3_0_1074281008_3_vmman.zip
11/17/2024 02:51 PM 252,014 vmman_scan_2_0_1074281008_2_vmman.zip
11/17/2024 02:27 PM 520,442 vmman_scan_1_0_1074281008_1_vmman.zip

11/16/2024 04:51 PM 210,722 vmman_scan_0_0_1074281008_0_vmman.zip
11/16/2024 04:21 AM 209,172 vmman_scan_9_0_1074281008_9_vmman.zip
11/15/2024 04:54 PM 114 slmtagsearch_0_1074281008_0_slmtag.zip
11/15/2024 04:54 PM 722 isotagsearch_0_1074281008_isotag.zip
11/15/2024 04:09 PM 122,282 vmman_scan_8_0_1074281008_8_vmman.zip
11/15/2024 09:54 AM 194,806 vmman_scan_7_0_1074281008_7_vmman.zip
11/14/2024 09:48 PM 133,334 vmman_scan_6_0_1074281008_6_vmman.zip
11/14/2024 09:30 AM 187,762 vmman_scan_5_0_1074281008_5_vmman.zip
11/13/2024 08:59 PM 221,821 vmman_scan_4_0_1074281008_4_vmman.zip
10/12/2024 08:45 PM 3,056 cit_capacity_0_1074281008_tlm_hw.zip
10/15/2023 02:37 AM 111 citsearch_0_1074281008_cit.xml.bz2
15 File(s) 2,319,349 bytes
2 Dir(s) 66,887,880,704 bytes free

C:\Program Files (x86)\BigFix Enterprise\BES Client__BESData__Global\Archive\Last>
---------------------------- From Relay
Sun, 17 Nov 2024 16:17:12 -0500 - /cgi-bin/bfenterprise/clientregister.exe (7404) - Uncaught exception in plugin ClientRegister with client 10.91.40.32: HTTP Error 55: Failed sending data to the peer: Connection died, tried 5 times before giving up
Sun, 17 Nov 2024 17:18:49 -0500 - 2108 - BES Relay received stop request (I tried restarting relay here to see if that helps kick start the upload, but it did not)
---------------------------- From Bigfix Server

C:\Program Files (x86)\BigFix Enterprise\BES Server\UploadManagerData\BufferDir\sha1\8\1074281008>dir /o:-d
Volume in drive C has no label.
Volume Serial Number is DA23-5BFD

Directory of C:\Program Files (x86)\BigFix Enterprise\BES Server\UploadManagerData\BufferDir\sha1\8\1074281008

11/17/2024 08:02 AM …
11/17/2024 08:02 AM . Note: nothing from 11/17, not even Index.txt
11/16/2024 04:51 PM 10,737 Index.txt
11/16/2024 04:51 PM 210,722 vmman_scan_0_0_1074281008_0_vmman.zip
11/16/2024 04:21 AM 209,172 vmman_scan_9_0_1074281008_9_vmman.zip
11/15/2024 04:54 PM 114 slmtagsearch_0_1074281008_0_slmtag.zip
11/15/2024 04:54 PM 722 isotagsearch_0_1074281008_isotag.zip
11/15/2024 04:09 PM 122,282 vmman_scan_8_0_1074281008_8_vmman.zip
11/15/2024 09:54 AM 194,806 vmman_scan_7_0_1074281008_7_vmman.zip
11/14/2024 09:48 PM 133,334 vmman_scan_6_0_1074281008_6_vmman.zip
11/14/2024 09:30 AM 187,762 vmman_scan_5_0_1074281008_5_vmman.zip
11/13/2024 08:59 PM 221,821 vmman_scan_4_0_1074281008_4_vmman.zip
11/13/2024 08:30 AM 120,568 vmman_scan_3_0_1074281008_3_vmman.zip
11/12/2024 08:02 PM 219,274 vmman_scan_2_0_1074281008_2_vmman.zip
11/12/2024 07:32 AM 134,542 vmman_scan_1_0_1074281008_1_vmman.zip
10/12/2024 08:45 PM 3,056 cit_capacity_0_1074281008_tlm_hw.zip
10/15/2023 02:37 AM 111 citsearch_0_1074281008_cit.xml.bz2
15 File(s) 1,769,023 bytes
2 Dir(s) 20,280,664,064 bytes free

C:\Program Files (x86)\BigFix Enterprise\BES Server\UploadManagerData\BufferDir\sha1\8\1074281008>

Besrelay.log:
Sun, 17 Nov 2024 16:51:39 -0500 - RelayNotifier9 (6252) - Error running task RelayNotifier9: HTTP Error 28: Timeout was reached: Failed to connect to 192.168.159.40 port 52311 after 10013 ms: Timeout was reached
Sun, 17 Nov 2024 17:08:33 -0500 - RelayNotifier7 (4424) - Error running task RelayNotifier7: HTTP Error 28: Timeout was reached: Failed to connect to 192.168.159.40 port 52311 after 10000 ms: Timeout was reached
Sun, 17 Nov 2024 17:26:53 -0500 - RelayNotifier9 (6252) - Error running task RelayNotifier9: HTTP Error 28: Timeout was reached: Failed to connect to 192.168.159.40 port 52311 after 10013 ms: Timeout was reached

==============================

Any suggestions on what to look at next, now sure why it did not upload the Nov 17 files to Bigfix server ???

Thanks in advance.

Regards … Leslie

2

The upload has started, because what is written on the client log ‘Successfully uploaded file’ … then maybe the file uploaded has not reach the server

Would suggest to check if need to increase the values for these settings on the relays ( on the server the default values are high enough, better remain not used there )
_BESRelay_UploadManager_BufferDirectoryMaxSize
_BESRelay_UploadManager_BufferDirectoryMaxCount

and set a good value for this setting on the server:
_BESRelay_UploadManager_CompressedFileMaxSize

It is not Your case, because the upload has started, but another setting to check this time on the agent is the following:
_BESClient_ArchiveManager_MaxArchiveSize

Set temporarly the trace at verbose on the relay and the server could provide some additional information about the scenario … warning about RelayNotifier are not errors and are information related to up/down communication, totally unrelated with upload manager is working down/up:
https://support.hcltechsw.com/csm?id=kb_article&sysparm_article=KB0023389

Here are two public pages on the wiki about upload manager if can be useful:
https://bigfix-wiki.hcltechsw.com/wikis/home?lang=en-us#!/wiki/BigFix%20Wiki/page/Upload%20and%20Archive%20Manager
https://bigfix-wiki.hcltechsw.com/wikis/home?lang=en-us#!/wiki/BigFix%20Wiki/page/Troubleshooting%20Upload%20Manager

1 Like
3

Thanks for the feedback, but it looks like the upload ran to the bigfix server overnight ??? Not sure what kicked it off, but it took a while.

Regards … Leslie

4

The problem has come back again. :frowning:
Is there any way to kick start the upload of the recently updated files in
C:\Program Files (x86)\BigFix Enterprise\BES Client__BESData__Global\Archive\Last
ie.

Directory of C:\Program Files (x86)\BigFix Enterprise\BES Client__BESData__Global\Archive\Last

2024-11-22 06:39 PM …
2024-11-22 06:39 PM .
2024-11-22 06:39 PM 7,025 Index.txt
2024-11-22 06:17 PM 2,946,413 logcollector_0_9350315_logCollectorAgent.zip
2024-11-22 05:57 PM 114 slmtagsearch_0_9350315_0_slmtag.zip
2024-11-22 05:57 PM 722 isotagsearch_0_9350315_isotag.zip
2024-11-22 12:44 PM 3,324 vmman_scan_9_0_9350315_9_vmman.zip
2024-10-05 09:31 PM 919 cit_capacity_0_9350315_tlm_hw.zip

none of the files from Nov 22 made it to the sha1 directory on the besserver
i.e…
Directory of C:\Program Files (x86)\BigFix Enterprise\BES Server\UploadManagerData\BufferDir\sha1\15\9350315

11/16/2024 04:39 AM …
11/16/2024 04:39 AM .
11/15/2024 05:18 PM 5,831 Index.txt
11/15/2024 05:17 PM 114 slmtagsearch_0_9350315_0_slmtag.zip
11/15/2024 05:16 PM 114 isotagsearch_0_9350315_isotag.zip
10/05/2024 09:31 PM 919 cit_capacity_0_9350315_tlm_hw.zip
02/26/2022 01:58 PM 111 citsearch_0_9350315_cit.xml.bz2

So that’s since around 1pm, and now its 7pm. If its like before, it will kick of sometime overnight, but I would like to know what’s keeping it from going thru.
I tried restart the client and the relay but it had no effect.
What is the trigger?

Regards … Leslie

5

You’ll probably need to open a support case, if you haven’t already, as the UploadManager may be subject to any size or volume limits on any parent relay in the chain, and we might have to help you diagnose performance issues at any link in the chain from client to server.

6

Thanks for the recommendation Jason, as expected the upload ran overnight, so it will be difficult to co-ordinate support case within 24 hour period to troubleshoot.
Regards … Leslie