Found an error using deployment health checks

(imported topic written by Bjowah91)

Hi,

When I run the health check I see this error (below) on most of my relays. When I look in the client log I see a “general transport failure” when the client try to report to 127.0.0.0 (the relay on the local machine). Since the faiulre is so widly spread I doubt its a network error on the other hand it does not say when this error first occour. Does anyone have a clue on the remidation of this?

Thanks

/Björn

Gather Status

The GatherStatus.xml file records errors in the BES Relay or BES Server gathering Fixlet sites. If a BES Relay or the BES Server fails to gather a Fixlet site the BES Clients will not receive updates for the sites with failures.

Results:

BES Relay: Number of Gather Errors

SLTBPC101: 3

LISTPC001: 4

LISRSRV001: 3

SLGLSRV001: 3

LICISRV001: 3

LIDYSRV001: 4

LIBNSRV001: 3

(imported comment written by SystemAdmin)

Hi Bjowah,

Could you post one of the GatherStatus.xml files? A day or two of BES Client logs from one of the BES Relays may help as well.

The error may be caused by an opsite for a non Master BES Console operator that was never created. The requested logs will help show that.

If it is an opsite problem, you can fix it by having the operator log in a take an action (any action will do).

(imported comment written by Bjowah91)

Thanks for your reply Tyler.

I’ve zipeed the gatherstate.xml file together with 2 log files from our main relay, which shows most errors.

/björn

(imported comment written by SystemAdmin)

Hi Bjowah,

It looks like there are only 2 errors now:

17: Gather failed - Empty Directory Listing Error: http://lidtsrv009.line.stenanet.com:52311/cgi-bin/bfgather.exe/opsite3

49: Gather failed - Empty Directory Listing Error: http://lidtsrv009.line.stenanet.com:52311/cgi-bin/bfgather.exe/opsite51

The ‘Empty Directory Listing Error’ is usually cause by an empty operator site. This means that you didn’t hit ‘Apply’ in BES Admin after creating the user and the user hasn’t logged into the BES Console and taken an action.

The operators that are having the errors are opsite3 and opsite51. You can get the operator names for these sites out of the masthead file (export the current version using BES Admin). You should have those users log in to the BES Console and take an action.

The other option would be to run BESAdmin.exe /propagateAllOperatorSites. This will go through and propagate a site for all your operators and create a site for any that haven’t been initialized.

(imported comment written by Bjowah91)

Looking into the exported masthead show no sign of the operators 3 and 51.

For this problem I have had a case open with support. I think it was Kevin McManamon that supported me but we never get to the finish line.

However he told me to run a task that stops all opsite request and then adds them again.

I have run this taks without any luck.

I had a look yesterday in the health check and it looks like the errors is not increasing, and I don’t know how old they are. Is there away to clean the error log to see if this is still a problem or if that was a temprary issue?

/Björn

The code of the task:

delete __appendfile

delete clientuser.reg

appendfile Windows Registry Editor Version 5.00

appendfile

appendfile {("") of settings whose (it as string contains “__Group___AdminBy”) of client}

appendfile

-HKEY_LOCAL_MACHINE\SOFTWARE\BigFix\EnterpriseClient\Settings\Administrators

move __appendfile clientuser.reg

wait regedit /s clientuser.reg

wait {((preceding text of last “” of pathname of regapp “BESClient.exe”) & “__BESData\BES Support\restartClient.bat”)}

(imported comment written by BenKus)

Hi Bjorn,

Some useful info might be here: http://forum.bigfix.com/viewtopic.php?id=595

You can delete the errors from that XML file directly if you don’t want to see them anymore. If the site is completely gone, you can delete the whole " … " line.

Ben

(imported comment written by Bjowah91)

Thanks Ben,

Good information. However my problem in tht the users are not in the masthead file any more.

Will the BESAdmin.exe /propagateAllOperatorSites solve that to?

/Björn