Can anyone help to get my relay register with BES Root Server, as I am getting below errors in client log file...
FAILED to Synchronize - General transport failure. - 'http://127.0.0.1:52311/cgi-bin/bfenterprise/BESGatherMirror.exe?url=http://BESSERVER:52311/cgi-bin/bfgather.exe/actionsite&Time=10Aug11:01:53&rand=37af2e34&ManyVersionSha1=da39a3ee5e6b4b0d3255bfef95601890afd80709' http failure code 404 - gather url - http://127.0.0.1:52311/cgi-bin/bfenterprise/BESGatherMirror.exe?url=http://BESSERVER:52311/cgi-bin/bfgather.exe/actionsite&Time=10Aug11:01:53&rand=37af2e34&ManyVersionSha1=da39a3ee5e6b4b0d3255bfef95601890afd80709
And below error in relay log file....Thu, 10 Aug 2017 11:25:03 +0530 - 5876 - 2: class NoMastheadMatchesURL and sometime this error PostResultsForwarder (HTTP Error 503): Parent relay is busy, backing off.
Have you tried hitting the Relay Diagnostic page on your root BES server from the relays and/or clients in question? In a browser simply go to http://your_bigfix_root_server_fdqn_here:52311/rd
If you cannot reach the RD from your relays and/or clients, then it's because port 52311 is being blocked either on the endpoints or somewhere in your LAN.
Hope this helps.@cmcannady
Have you validated that the Masthead matches with the original file?
Yes, that i have checked, and I am able to run this URL in relay, and it is opening...
But the issue is still there...
Yes, the same file i am using since a long... the size of file is same. Is anything which we can check to determine.?
Client Log error: Is it possible the relay it is trying to connect is not having the latest version of actionsite? Can you try doing gather state reset?
Relay error: Perhaps its parent relay has already reached maximum TCP connections at the port 52311. I would check the TCP Timewait setting ot it to reduce Time_Wait status and also number of files in buffer directory and latency of it.