FAILED to Synchronize - General transport failure : http failure code 503

Usage and Config Platform
1

(imported topic written by KR9P_Ashu_Gupta)

When I schedule any action for clients, the status always shows This has started suddenly after last night where neither any infra or network changes nor any change on TEM server was done. The agents fail to sync with relay server when they try to reach to TEM server. What does this failure code 503 mean and how to resolve this issue? Any assistance is appreciated! Thanks

At 20:15:19 +0000 - actionsite (http://myserver.domain.com:52311/cgi-bin/bfgather.exe/actionsite)

FAILED to Synchronize - General transport failure. - ‘http://myrelay.domain.com:52311/cgi-bin/bfenterprise/BESGatherMirror.exe?url=http://myserver.domain.com:52311/cgi-bin/bfgather.exe/actionsite&Time=22Dec20:15:19&rand=b3c1d85b&ManyVersionSha1=2def223ffee0a7636ba41ac3a9d7058b506a0841’ http failure code 503 - gather url - http://myrelay.domain.com:52311/cgi-bin/bfenterprise/BESGatherMirror.exe?url=http://myserver.domain.com:52311/cgi-bin/bfgather.exe/actionsite&Time=22Dec20:15:19&rand=b3c1d85b&ManyVersionSha1=2def223ffee0a7636ba41ac3a9d7058b506a0841

At 20:16:23 +0000 - actionsite (http://myserver.domain.com:52311/cgi-bin/bfgather.exe/actionsite)

FAILED to Synchronize - General transport failure. - ‘http://myrelay.domain.com:52311/cgi-bin/bfenterprise/BESGatherMirror.exe?url=http://myserver.domain.com:52311/cgi-bin/bfgather.exe/actionsite&Time=22Dec20:16:23&rand=e0fd9473&ManyVersionSha1=2def223ffee0a7636ba41ac3a9d7058b506a0841’ http failure code 503 - gather url - http://myrelay.domain.com:52311/cgi-bin/bfenterprise/BESGatherMirror.exe?url=http://myserver.domain.com:52311/cgi-bin/bfgather.exe/actionsite&Time=22Dec20:16:23&rand=e0fd9473&ManyVersionSha1=2def223ffee0a7636ba41ac3a9d7058b506a0841

At 20:17:25 +0000 - BES Support (http://sync.bigfix.com/cgi-bin/bfgather/bessupport)

FAILED to Synchronize - General transport failure. - ‘http://myrelay.domain.com:52311/cgi-bin/bfenterprise/BESGatherMirror.exe?url=http://sync.bigfix.com/cgi-bin/bfgather/bessupport&Time=22Dec20:17:25&rand=68b8a73a&ManyVersionSha1=da39a3ee5e6b4b0d3255bfef95601890afd80709’ http failure code 503 - gather url - http://myrelay.domain.com:52311/cgi-bin/bfenterprise/BESGatherMirror.exe?url=http://sync.bigfix.com/cgi-bin/bfgather/bessupport&Time=22Dec20:17:25&rand=68b8a73a&ManyVersionSha1=da39a3ee5e6b4b0d3255bfef95601890afd80709

At 20:17:26 +0000 - Enterprise Security (http://sync.bigfix.com/cgi-bin/bfgather/bessecurity)

FAILED to Synchronize - General transport failure. - ‘http://myrelay.domain.com:52311/cgi-bin/bfenterprise/BESGatherMirror.exe?url=http://sync.bigfix.com/cgi-bin/bfgather/bessecurity&Time=22Dec20:17:26&rand=edd13b59&ManyVersionSha1=da39a3ee5e6b4b0d3255bfef95601890afd80709’ http failure code 503 - gather url - http://myrelay.domain.com:52311/cgi-bin/bfenterprise/BESGatherMirror.exe?url=http://sync.bigfix.com/cgi-bin/bfgather/bessecurity&Time=22Dec20:17:26&rand=edd13b59&ManyVersionSha1=da39a3ee5e6b4b0d3255bfef95601890afd80709

At 20:17:27 +0000 - Patching Support (http://sync.bigfix.com/cgi-bin/bfgather/patchingsupport)

FAILED to Synchronize - General transport failure. - ‘http://myrelay.domain.com:52311/cgi-bin/bfenterprise/BESGatherMirror.exe?url=http://sync.bigfix.com/cgi-bin/bfgather/patchingsupport&Time=22Dec20:17:27&rand=5f4c5366&ManyVersionSha1=da39a3ee5e6b4b0d3255bfef95601890afd80709’ http failure code 503 - gather url - http://myrelay.domain.com:52311/cgi-bin/bfenterprise/BESGatherMirror.exe?url=http://sync.bigfix.com/cgi-bin/bfgather/patchingsupport&Time=22Dec20:17:27&rand=5f4c5366&ManyVersionSha1=da39a3ee5e6b4b0d3255bfef95601890afd80709

At 20:21:34 +0000 - actionsite (http://myserver.domain.com:52311/cgi-bin/bfgather.exe/actionsite)

FAILED to Synchronize - General transport failure. - ‘http://myrelay.domain.com:52311/cgi-bin/bfenterprise/BESGatherMirror.exe?url=http://myserver.domain.com:52311/cgi-bin/bfgather.exe/actionsite&Time=22Dec20:21:34&rand=7425bb66&ManyVersionSha1=2def223ffee0a7636ba41ac3a9d7058b506a0841’ http failure code 503 - gather url - http://myrelay.domain.com:52311/cgi-bin/bfenterprise/BESGatherMirror.exe?url=http://myserver.domain.com:52311/cgi-bin/bfgather.exe/actionsite&Time=22Dec20:21:34&rand=7425bb66&ManyVersionSha1=2def223ffee0a7636ba41ac3a9d7058b506a0841

2

(imported comment written by BenKus)

Hmm… I didn’t think our relay or server ever returned http error code 503 (which means “busy”)…

Are you sure that nothing is intercepting the call (like a proxy?)… Can you paste the urls in a browser and see what happens?

If you continue to have issues, you might want to contact support to investigate…

Ben

3

(imported comment written by KR9P_Ashu_Gupta)

Ben,

The VM’s or relays doesn’t have internet. The VM’s goes to relay and then to TEM server. TEM talks to internet via proxy setup using user authentication. TEM server has an exception added to route trafic internally for local intranet resolutions. The user authentication is AD based. The gather service is setup with this user to reach to internet.

The URL sometimes time-out and other throws invalid token. The first thought was that clients are too busy to run “Empty Directory” error. So, besadmin.exe /propagatealloperatorsites was used, but no luck. To continue, this kneel down to Relay server issue and so recycled TEM relay service, but no help. The relay server then bumped once and traffic starts flowing from EndPoints to relay to TEM server.

Investigating further to find the root cause, I don’t see any logs or indication on relay to find get the real cause… strange! Can you help running any utility and/or any specific logs which can give ingight what happened?

Thanks!

4

(imported comment written by Julia_C)

Hi,

Any update?

5

(imported comment written by Rafael Rodriguez)

happened to me once. I’ve solved restarting besrelay besclient and relay server which gives the error.