http://sync.bigfix.com/cgi-bin/bfgather/bessecurity shows that the current version = 3253 but all 3 of my deployments are saying they are at 3252.
I’ve forced a gather of the site and confirmed they can reach the external site URL.
Anyone else seeing this issue or is it just me?
My instances have v3253 for Patches for Windows. What does your gather status report show for the site in question?
Current Version 3,253 here
Have you checked your gather log?
this is what I see on one of my root servers:
Id: 3 Date: Mon, 15 Apr 2019 15:10:34 +0000
Error Message: 3: class FormatError
This suggests that something may be interfering with the site data transfer, such as a proxy, HIPS, content filters, etc…
is there way to debug that request error?
hitting here - http://sync.bigfix.com/cgi-bin/bfgather/bessecurity from IE on root server gives this error in the browser
Error providing site directory.
The requested Fixsite cannot be serviced by this server.
Unable to stat directory listing.
From the root server, when I try from command line, I have no problem calling that URL using the same proxy that the bigfix server is configured to use HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BigFix\Enterprise Server\Proxy
c:>wget.exe -e http_proxy=xxxx:80 http://sync.bigfix.com/cgi-bin/bfgather/bessecurity
–2019-04-15 13:27:48-- http://sync.bigfix.com/cgi-bin/bfgather/bessecurity
Resolving xxxxxx (xxxxx)… x.x.x.x
Connecting to xxxx (xxxx)x.x.x.x|:80… connected.
Proxy request sent, awaiting response… 200 OK
Length: 222 [text/html]
Saving to: ‘bessecurity’
I’d suggest switching your server to gather over HTTPS. That resolves a lot of issues where the proxy server may be injecting or altering content. See https://www.ibm.com/support/knowledgecenter/SSQL82_9.5.0/com.ibm.bigfix.doc/Platform/Config/r_client_set.html for _BESGather_Use_Https
There does seem to be an issue with 1 of our sync servers, but not the other one. You might get lucky if you clear your DNS cache and get the one that is working.
I’m investigating the problem now.
that’s a client setting and not configured with “besadmin.exe /proxy” ?
I’m at an older version 3250.
@cstoneba Give it a go now. I believe Patches for Windows should be good now.
Looks better now…
May I suggest some monitoring of that 2nd sync.bigfix.com server
Mon, 15 Apr 2019 16:22:15 -0500 – Beginning DB import of version 3254 of site Enterprise Security
Correct, it’s a client setting applies to the root server.
I set “_BESGather_Use_Https” “value”=2 and everything is working again so I don’t know if it was just the sync.bigfix.com server getting fixed or a mixture of that and _BESGather_Use_Https.
It was definitely this, unless switching to HTTPS changed the sync server you ended up talking to on the back end.
The issue with the 1 sync server has been resolved and the sites that did not propagate to it correctly are being republished so this problem is getting addressed.
I just verified that the sync server issue should now be fully resolved. It should have been all clear yesterday at some point, but I was able to verify it today.