From at least one client, I was seeing this message in the Client Log when connecting to a 9.5.1.9 Relay.
At 16:29:04 -0500 -
FAILED to Synchronize - Server returning old data, try again later. - http://RELAYHOSTNAME.local:52311/cgi-bin/bfenterprise/BESGatherMirror.exe?url=http://BESSERVER.gov:52311/cgi-bin/bfgather.exe/mailboxsite2290901 - gather url - http://RELAYHOSTNAME.local:52311/cgi-bin/bfenterprise/BESGatherMirror.exe?url=http://BESSERVER.gov:52311/cgi-bin/bfgather.exe/mailboxsite2290901&Time=21Apr16:29:04&rand=5942c524&ManyVersionSha1=ca38c95f52585c74366ea862f34142ae288493d5
I saw this message referencing many Operator Sites as well. When I downgraded the Relay back to 9.2.7, this client was able to gather new site updates ok. I havenât started polling other clients to see if I had this issue elsewhere, just something I noticed based on the order in which I was rolling back. Is anyone else seeing this in their clients?
Actually had a recurrence from the same client, a few minutes after downgrade its parent relay to 9.2.7. Occurred shortly after the Relayâs logfile.txt logged the following:
Thu, 21 Apr 2016 16:44:06 -0500 - /cgi-bin/bfenterprise/clientregister.exe (1592) - Uncaught exception in plugin ClientRegister with client X.X.X.X: HTTP Error 6: couldn't resolve host name: Could not resolve host: (nil); Host not found
No idea what host name it was trying & failing to resolve. The BESRelay service appeared to still be running, but does the âUncaught exceptionâ indicate that itâs really down/failed? And what host names should a Relay be trying to resolve - I would think as long as it can resolve its parent relay name, that should be all it needs?
So you know the cause of this. The client has noticed that the version of the data for the site is older than what it has. Possibly because the client switched from a âworkingâ relay to one that wasnât working properly, or one that hadnât updated the site in a long time because no one requested it. This usually clears up as soon as the relay downloads the current site. Constant issues like this are a problem though.
The client is doing its best to not go âbackwardâ in time and possibly re-fetch actions it already ran etc.
I had the same issue after a rollback from 9.5.7 to 9.2. The solution was basically reinstall the BESClientâŚhowever for BESRelays, we had to reinstall the BESRelays too.
The weird thing here was that all the clients were reporting fine to the BESConsole and the actions were executed well on themâŚBUT just some custom sites never synchronized well on clients.
Client Error Example: âFAILED to Synchronize - Server returning old data, try again laterâ
But, that never workedâŚso a the end the BESClient reinstallation resolve the issue.
Additional Workaround: Delete the site directory in the client: _D:\Program Files (x86)\BigFix Enterprise\BES Client_BESData[Site_Name]
Verify if the site was succesfully sync on: _D:\Program Files (x86)\BigFix Enterprise\BES Client__BESData_Global\Logs
Output example: Successful Synchronization with site âopsite90â (version 229392)
