Hi Team,
We have created a Baseline to perform patching on Linux servers.
Patching is getting completed on some servers.
While the patching action is running, some of the servers stopped reporting and some servers are online but not responding to the actions.
Endpoints are having enough space and are not reporting in console even after restarting the besclient service.
End Points are reporting/responding only when we attempt to kill the besclient pid and restart the besclient service.
Can anyone suggest what could be the reason for this behavior.
Thank You
This behavior is most likely due to a large number of components in your baseline or patch installations taking longer than usual to complete.
If the issue consistently occurs during patching cycles, it’s typically related to the content or deployment strategy. I strongly recommend reviewing the following article on Baseline Best Practices to optimize your patch deployments:
Baseline best practices
If you’re experiencing these symptoms outside of patching windows, the issue may be due to background evaluation loops or a running action keeping the BigFix client busy.
To investigate further, consider enabling client debug logging to capture more detailed behavior:
Data Collection: BigFix Client Debug Logs
1 Like
All good tips. I’d also suggest reading through Tip: Troubleshooting Client Reponsiveness
It’s possible some of your servers are not receiving the UDP messages notifying them.about new actions. Your options involve opening the traffic, enabling Persistent Connections and/or Command Polling, and scheduling your actions in advance.
1 Like