The action status against default action taken for a fixlet is shown as not reported. Checked with the knowledge base which gave me two possibilities for it to show status which is
Clients offline
UDP 52311 not open between server and the client.
But in my case both these conditions are met i.e. client is online as well as UDP 52311 is also open.
Is there any other possibilities of getting this status and how can I fix it ?
If there is any reason that would cause the agents not to get the notification UDP messages or if they can’t gather the new actions for any reason, they would stay at .
We are running 6.0.21.5 and have observed an interesting behaivor but I’ve not been able to confirm this yet with support or in any documentation including the knowledge base.
We were installing several patches both standalone and a number that were bundled in baselines. Quite often a system would go through a baseline or two before the remaining actions would get stuck at .
The preferred resolutions were found by operators and included restarting the client or rebooting the node.
This week I noticed a commonality in the logs when the agent “decides” to no longer process new actions.
As soon as the BESClient log shows that a “Restart Needed” it stops processing these new actions. It continues to evaluate and report but the remaining actions that were issued back to back will remain at until something is done to jar things loose. Since reboots take time the preferred action is to recycle the BESClient and the remaining actions take off immediately.
Have others seen this? I’ll be getting ahod of support first thing next week, but I thought I’d try the forum first.
I don’t believe this is a known issue… But note that we have made quite a few changes to the agent to improve its reporting behavior (especially across restarts) since 6.0.21.5… I would recommend you consider upgrading some time soon so you have the latest/greatest agent…