Relay log - class NotASignedMessage

Hi all …

I have a few Relay which is working normally: according to Relay Diagnostics.
However, on the Gather Status Page from Relay Diagnostics, I see the following error messages; what do they mean?

Gather Status Report

Failed:

Id: 59 Date: Wed, 23 Aug 2017 12:17:59 +0000
Url: http://HWBFES01.harel-office.com:52311/cgi-bin/bfgather.exe/CustomSite_SharePoint
Error Message: 59: class NotASignedMessage

Id: 60 Date: Wed, 23 Aug 2017 12:17:59 +0000
Url: http://sync.bigfix.com/cgi-bin/bfgather/osdeployment
Error Message: 60: class NoMastheadMatchesURL

Id: 61 Date: Wed, 23 Aug 2017 12:17:59 +0000
Url: http://sync.bigfix.com/cgi-bin/bfgather/patchesforesx3
Error Message: 61: class NoMastheadMatchesURL

Id: 62 Date: Wed, 23 Aug 2017 12:17:59 +0000
Url: http://sync.bigfix.com/cgi-bin/bfgather/patchesforesxi
Error Message: 62: class NoMastheadMatchesURL

i use this articale to reslove the issue http://www-01.ibm.com/support/docview.wss?uid=swg21697473 but after few seconds the Failed sites returned, with deferent ID

im trying to understand why its hapened if this critical and how can i reslove it

Thank you
Julia

@juliac,

Have you tried running the “resignsecuritydata” function via BESAdmin?

@cmcannady

Shouldn’t require “resignsecuritydata.” That should only be necessary when you have to make manual changes to users/roles in the database or recover from db corruption in those areas.

Gather operations are triggered by lower level client/relay gather requests. So when you do a gather reset to clear out old sites (like the ones with NoMastheadMatchesURL which mean the site is no longer enabled on the server), you need to start from bottom up across all relays. Since the sites have been removed, clients should not longer be requesting them, but relays that have previously gathered the site will periodically ask for updates. This task on bigfix.me can help you do this reset on your relays remotely. Target all bottom tier relays first, then the tier above that, and so on. Once all the relays are done, then you can do the manual process on the server.

I do recommend testing the action on a single accessible relay first, since I haven’t validated it on any of the 9.x releases, but I expect it to still work.

For the SharePoint custom site, you probably just need to propagate some change to the site to correct the error.

2 Likes

Is there still supposed to be a “ContentLocation” of that registry key? I don’t see one on my BES 9.5.8 Relay and evaluation is non-existent object.

value "ContentLocation" of key "HKLM\SOFTWARE\BigFix\Enterprise Server\GatherService" of registry