BigFix Relay Logs showing NotASigned Message Error from Client

1

I noticed my Deployment Health Checks dashboard in BigFix started showing gather errors for some of my relays. Next to the relay it shows the number of bigfix clients with gather errors. Normally its anywhere from 4-6 clients. If you click on that number it will show you the error logs for the clients. Any idea why all of a sudden certain BigFix clients are showing NotASigned Message error when looking at my relay logs?

Example of the error below.

http://xxxxx.xxx.xxx:52311 - This is our root server

Tue, 18 Jun 2024 12:38:47 -0400 - 4104 - 10: class NotASignedMessage - from 17x.xx.xx.xxx
Tue, 18 Jun 2024 12:53:59 -0400 - 7104 - Unable to find ( or problems occurred ) with site id for URL: http://xxxxx.xxx.xxx:52311/cgi-bin/bfgather.exe/opsite115 - from 17x.xx.xx.xxx
Tue, 18 Jun 2024 12:53:59 -0400 - 7104 - 10: class NotASignedMessage - from 17x.xx.xx.xxx
Tue, 18 Jun 2024 12:54:01 -0400 - 5744 - Unable to find ( or problems occurred ) with site id for URL: http://xxxxx.xxx.xxx:52311/cgi-bin/bfgather.exe/opsite124 - from 17x.xx.xx.xxx
Tue, 18 Jun 2024 12:54:01 -0400 - 5744 - 19: class NotASignedMessage - from 17x.xx.xx.xxx

2

I have done a gather reset on some of the relays. It does take down the count from say 6 to about 1. So it does help somewhat but does not fully resolve the problem.

3

From the log exerpt, it seems to be Operator Sites to be affected.
You can try to force the Root Server to re-propagate all operator sites:

.\BESAdmin.exe /propagateAllOperatorSites
1 Like
4

Appreciate the feedback. I tried that a few hours ago. I was hoping that would help but still showing those errors.

5

file a support case; maybe a Root Server gather reset is necessary and the guys can help you with the steps.

1 Like