We recently reinstalled Big Fix, and the clients are not reporting properly. Upon examination of the client logs, I see the following
At 12:18:27 -0400 -
GatherHash command received.
No matching site.
GatherHash command received.
No matching site.
At 12:23:42 -0400 -
ForceRefresh command received. Version up to date, gather skipped
Report posted successfully.
Apparently its an issue with the action site? I opened up the BES Admin and clicked on Edit Masthead to the change the Action Site Masthead parameters. I adjusted the Gathering Interval to 15 Minutes. I was prompted to initiate and Action Site Propagation to make the change. I then received the following message:
Site propagation aborted by BES Server for the following reason:
When you say “not reporting properly”, what do you mean? Do you mean that the agents aren’t updating their last report time? Or that they aren’t responding to actions? (if the latter, see http://support.bigfix.com/cgi-bin/kbdirect.pl?id=173)
The “heartbeat” in the BES Console “File > Preferences” controls how often the BigFix Agents report. If they are not reporting on this schedule and updating their last report time, you might have an agent issue
Those log messages by themselves are normal. The “GatherHash command received. No matching site.” means that the agent heard from the server that there was new information, but it didn’t think it needed to get the information because it is not subscribed to that site. This is normal if you have lots of operators because the agents only gather actions from operators if they are managed by that user.
Changing the BESAdmin gather interval to 15 minutes is probably not what you want to do. Usually you would not want the gatherinterval under 30 minutes because it adds some extra load to your relays and generally interrupts the agent. You can put it at an hour if you want, but generally it is unnecessary if UDP is not blocked in your environment (and from your log, it appears that UDP is working fine).
Your “unauthorized signature on propagation message” means that either your key files are not correct or that you might have a corrupted or unauthorized Fixlet or action in your database. I think the best way to solve this is to contact support.