Content in the Patches for Windows site has been modified
New:
*Major [ID:502165601] 5021656: Cumulative Update for Microsoft server operating system version 21H2 - Windows Server 2022 - KB5021656 (x64)
*Major [ID:502165503] 5021655: Cumulative Update for Windows Server 2019 - Windows Server 2019 - KB5021655 (x64)
*Major [ID:502165501] 5021655: Cumulative Update for Windows 10 Version 1809 - Windows 10 Version 1809 LTSC - KB5021655 (x64)
*Major [ID:502165505] 5021655: Cumulative Update for Windows 10 Version 1809 - Windows 10 Version 1809 LTSC - KB5021655
*Major [ID:502165403] 5021654: Cumulative Update for Windows Server 2016 - Windows Server 2016 - KB5021654 (x64)
*Major [ID:502165401] 5021654: Cumulative Update for Windows 10 Version 1607 - Windows 10 Version 1607 LTSB - KB5021654 (x64)
*Major [ID:502165405] 5021654: Cumulative Update for Windows 10 Version 1607 - Windows 10 Version 1607 LTSB - KB5021654
*Major [ID:502165303] 5021653: Update for Windows Server 2012 R2 - Windows Server 2012 R2 - KB5021653 (x64)
*Major [ID:502165301] 5021653: Update for Windows 8.1 - Windows 8.1 - KB5021653 (x64)
*Major [ID:502165305] 5021653: Update for Windows 8.1 - Windows 8.1 - KB5021653
*Major [ID:502165201] 5021652: Update for Windows Server 2012 - Windows Server 2012 - KB5021652 (x64)
Reason for Update:
New updates from Microsoft
Actions to Take:
None
Published site version:
Site Name: Patches for Windows
Version: 4099
You should try to force a gather since the updates are out already (2 hours ago). By default, the root server gathers once every 24 hours. From your console go to the Patches for Windows external site and force a gather of new content by clicking the Gather button on the right hand side of the screen.
If you look in the GatherDB.log located in .\Program Files (x86)\BigFix Enterprise\BES Server\GatherDBData are you seeing this at all after forcing the gather?
Fri, 18 Nov 2022 15:09:16 -0500 – Beginning DB import of version 4099 of site Enterprise Security
This indicates it is starting. It takes a while for this site to import. Still waiting on mine as I just started it.
The last “Beginning DB import” message I see was from yesterday about 4:30 PM. I’ve tried restarting the BESGather service and even rebooting the server. No dice.
However, my DSA server has already imported version 4099 of site Enterprise Security. It’s the primary server that’s a problem (of course ).
There are no other sites on that page that show a zLib error.
I’ve noticed that if I click the “gather” button in the console, then go over to that page and refresh the block for bessecurity moves from the “Failed” section down to the “In Process” section but after a few seconds goes back to the “Failed” section.
Ok. I’d need to dig more into this to be certain (I will) but at the surface it sounds like there is just a bit of a traffic jam going on with the sync servers. There has been a fair amount of content released over the past 24 hours in just that site.
About those zLib errors. I found several cases where customers had gather issues and found those same entries.
To figure out exactly what is triggering them, you can enable debug/verbose logging for the root server using the task named “Enable Server verbose log” in the BES Support site. I’d let that run for a few hours at most and then disable it with the “WARNING: Server verbose log is enabled” task in the same site.
Then open a support case and refer them to this forum thread and post those logs. Even if the patch site does gather later on - I suspect you might have some other issue that needs looking into.
Yes I did. Actually, when the tech called me, the auto-update had just finished. Footnote: my app server was acting a bit weird, so I performed maintenance (clean up old records then ran audit trail clean up) followed by a reboot.
).