"GetURL failure" and "http failure code 404" messages for opsites

Technote (FAQ)


Question

Getting "General transport failure" and "http failure code 404" in relay logs for opsite

Cause

The Relay log shows the following types of gather errors for opsites

Id: 6 Date: Fri, 11 Jan 2013 16:33:00 +0000 Url: http ://bigfix:52311/cgi-bin/bfgather.exe/opsite110 Error Message: 6: GetURL failure on [http://bigfix:52311/cgi-bin/bfenterprise/besgathermirror.exe?url=http://bigfix:52311/cgi-bin/bfgather.exe/opsite110&ManyVersionSHA1=da39a3ee5e6b4b0d3255bfef95601890afd80709&Expect404Flag=true&Time=1357921974: General transport failure.

'http://bigfix:52311/cgi-bin/bfenterprise/besgathermirror.exe?url=http://bigfix:52311/cgi-bin/bfgather.exe/opsite110&ManyVersionSHA1=da39a3ee5e6b4b0d3255bfef95601890afd80709&Expect404Flag=true&Time=1357921974' http failure code 404 .

This is caused by having defined a BES Console operator that is subscribed to computers but has not issued any actions yet (ie. content to its opsite).

Answer

Either

1) login as that operator (refer to technote
http://www.ibm.com/support/docview.wss?uid=swg21620356
How to correlate opsites to a BES Console operators

to find out the BES Console userid that correlates to the opsite number)
then submit a blank custom action.

OR

2) if the BES Console operator is no longer needed, remove it.


Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Tivoli Endpoint Manager

Software version:

8.2

Operating system(s):

Windows

Reference #:

1622240

Modified date:

2013-06-20

Translate my page

Machine Translation

Content navigation